summaryrefslogtreecommitdiff
path: root/INSTALL
diff options
context:
space:
mode:
Diffstat (limited to 'INSTALL')
-rw-r--r--INSTALL10
1 files changed, 5 insertions, 5 deletions
diff --git a/INSTALL b/INSTALL
index b6c4442..17c2212 100644
--- a/INSTALL
+++ b/INSTALL
@@ -33,7 +33,7 @@ pathnames. Change them to suit your installation requirements. Usually
sysadmins discuss the location of SOCKDIR, whether it should be in /tmp or
not. At least it must be on a filesystem that supports sockets/fifos.
SOCKDIR must not point into an AFS (Andrew File System) mounted directory.
-If you are uncrertain about your NFS implementation, use a UFS directory for
+If you are uncertain about your NFS implementation, use a UFS directory for
SOCKDIR. Personally, I favour a users home directory and recommend the the
/tmp/ area.
The path for ETCSCREENRC may also need to be adapted.
@@ -57,9 +57,9 @@ consult a system administrator and discuss installing screen setuid-root
in some globally accessible directory like /usr/local/bin.
Consider this, when deciding whether you install screen setuid-root:
-- On some machines root priviliges are required to open pty's.
+- On some machines root privileges are required to open pty's.
- Pty's should be owned by the user, so that she can do chmod to prevent
- intrudor attacks. The PTYs used by screen will remain world read-writable
+ intruder attacks. The PTYs used by screen will remain world read-writable
if screen is not installed setuid-root.
- Some commands only work properly when the pty is owned by the user.
These include mesg and biff.
@@ -70,7 +70,7 @@ Consider this, when deciding whether you install screen setuid-root:
instead of the screen windows, if screen is not installed setuid-root.
- Multi-user screen sessions are only allowed when screen has a root-s-bit.
- If screen sockets of multiple users are kept in one directory (e.g.
- /tmp/screens), this directory must be world writeable when screen is not
+ /tmp/screens), this directory must be world writable when screen is not
installed setuid-root. Any user can remove or abuse any socket then.
@@ -91,7 +91,7 @@ $ETCSCREENRC -- do not just copy them. Read them. Look through the
etcscreenrc file for system wide defaults that you like to set. e.g.
autodetach off, startup_message off, vbell on, ...
Since version 3.2.15 the screenrc file syntax changed slightly. All rc files
-from previous versions should be run through the newsyntax script that comes
+from previous versions should be run through the 'newsyntax' script that comes
with this package.
If and only if you want to install screen as a console multiplexer, look
at the *.sample files and what 'make cscreen' suggests.