system/atarisio: Updated for version 20100113

1 files changed, 32 insertions, 23 deletions

diff --git a/system/atarisio/README.Slackware b/system/atarisio/README.Slackware
index 4cda49fe00..aabe7090a4 100644
--- a/system/atarisio/README.Slackware
+++ b/system/atarisio/README.Slackware
@@ -15,35 +15,44 @@ you're using FujiChat on your Atari, etc etc).
 
 #### READ THIS! ####
 
-# By default, atariserver and atarixfer are installed setuid root,
-# group owner "users". This is done for two reasons: (a) so the programs
-# can access the /dev/atarisio* devices, and (b) so they can set POSIX
-# realtime scheduling mode, which prevents timing issues that can cause
-# SIO frames to be retransmitted or (on a loaded system) dropped.
+By default, atariserver and atarixfer are installed setuid root,
+group owner "users". This is done for two reasons: (a) so the programs
+can access the /dev/atarisio* devices, and (b) so they can set POSIX
+realtime scheduling mode, which prevents timing issues that can cause
+SIO frames to be retransmitted or (on a loaded system) dropped.
 
-# If run setuid root, atariserver and atarixfer will drop their root
-# privileges after setting realtime mode and opening the device.
-# There are no currently known exploits against atarisio, but the code
-# hasn't exactly been audited by the NSA either.
+If run setuid root, atariserver and atarixfer will drop their root
+privileges after setting realtime mode and opening the device.
+There are no currently known exploits against atarisio, but the code
+hasn't exactly been audited by the NSA either.
 
-# You have several options here:
+You have several options here:
 
-# 1. The default. Simply run this script. On a single-user system, this
-# is reasonable, though it's the least secure. atariserver and atarixfer
-# will be setuid root, and runnable by anyone in the users group.
+1. The default. Simply run the script. On a single-user system, this is
+reasonable, though it's the least secure. atariserver and atarixfer will
+be setuid root, and runnable by anyone in the users group.
+
+2. Run atariserver and atarixfer setuid root, but restrict access to
+some group other than "users". To do this, run the script as:
 
-# 2. Run atariserver and atarixfer setuid root, but restrict access to
-# some group other than "users". To do this, run the script as:
 # SETUID=yes GROUP=wheel ./atarisio.SlackBuild
-# (replace "wheel" with any other group, as you prefer).
-# This option is more secure than option 1 and outperforms option 3.
 
-# 3. Run atariserver and atarixfer as a normal user. This can cause
-# performance problems, but on most setups it works OK. To do this,
-# run the script as:
+(replace "wheel" with any other group, as you prefer).
+This option is more secure than option 1 and outperforms option 3.
+
+3. Run atariserver and atarixfer as a normal user. This can cause
+performance problems, but on most setups it works OK (on some systems,
+it may not work at all). To do this, run the script as:
+
 # SETUID=no ./atarisio.SlackBuild
-# This should be more secure than 1 or 2.
 
-# 4. Same as 3, but extra paranoid: use a group other than "users" (I like
-# "wheel"), and be very picky about who you add to the group.
+This should be more secure than 1 or 2.
+
+4. Same as 3, but extra paranoid: use a group other than "users" (I like
+"wheel", but you could create your own "atarisio" group if you really
+want), and be very picky about who you add to the group.
+
 # SETUID=no GROUP=wheel ./atarisio.SlackBuild
+
+Like option 3, this may cause performance problems or prevent the app
+from working at all.