is a screen manager with VT100/ANSI terminal emulation (multiplexing up to 10 pseudo-terminals).
| INSTALL (screen-4.8.0) | : | INSTALL (screen-4.9.0) |
|---|
| | |
| skipping to change at line 42 | | skipping to change at line 42 |
|---|
| You will be prompted to run 'make' again, which will really make screen. | | You will be prompted to run 'make' again, which will really make screen. |
| | |
| 2.) Makefile & config.h | | 2.) Makefile & config.h |
| ----------------------- | | ----------------------- |
| Look through the Makefile & user configuration section in config.h and check | | Look through the Makefile & user configuration section in config.h and check |
| pathnames. Change them to suit your installation requirements. Usually | | pathnames. Change them to suit your installation requirements. Usually |
| sysadmins discuss the location of SOCKDIR, whether it should be in /tmp or | | 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. | | 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. | | SOCKDIR must not point into an AFS (Andrew File System) mounted directory. |
| If you are uncertain 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 | | SOCKDIR. Personally, I favour a user's home directory and recommend the the |
| /tmp/ area. | | /tmp/ area. |
| The path for ETCSCREENRC may also need to be adapted. | | The path for ETCSCREENRC may also need to be adapted. |
| | |
| 3.) how to actually compile | | 3.) how to actually compile |
| --------------------------- | | --------------------------- |
| Run 'make'. Screen should compile without too many warnings :) | | Run 'make'. Screen should compile without too many warnings :) |
| The creation of term.h, comm.h, tty.c or osdef.h may fail on some machines | | The creation of term.h, comm.h, tty.c or osdef.h may fail on some machines |
| for some odd reason. (E.g. the sed under SCO-unix is known to be | | for some odd reason. (E.g. the sed under SCO-unix is known to be |
| case-insensitive and breaks term.h.) If so, please mail a short description | | case-insensitive and breaks term.h.) If so, please mail a short description |
| of the problem to screen-devel@gnu.org and use the files ending in .dist | | of the problem to screen-devel@gnu.org and use the files ending in .dist |
| as a replacement (or in case of osdef.h retry with an empty file). | | as a replacement (or in case of osdef.h retry with an empty file). |
| You can then try 'make install' (if you dare). | | You can then try 'make install' (if you dare). |
| | |
| 4.) where to install | | 4.) where to install |
| -------------------- | | -------------------- |
| You may well run screen from your private binary directory and with a | | You may well run screen from your private binary directory and with a |
| private socket directory like $HOME/.screen. But to have a full featured | | private socket directory like $HOME/.screen. But to have a full featured |
|
| screen and (from a users point of view) more secure pty's you should | | screen and (from a user's point of view) more secure pty's you should |
| consult a system administrator and discuss installing screen setuid-root | | consult a system administrator and discuss installing screen setuid-root |
| in some globally accessible directory like /usr/local/bin. | | in some globally accessible directory like /usr/local/bin. |
| | |
| Consider this, when deciding whether you install screen setuid-root: | | Consider this, when deciding whether you install screen setuid-root: |
| - On some machines root privileges 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 | | - Pty's should be owned by the user, so that she can do chmod to prevent |
| intruder 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. | | if screen is not installed setuid-root. |
| - Some commands only work properly when the pty is owned by the user. | | - Some commands only work properly when the pty is owned by the user. |
| These include mesg and biff. | | These include mesg and biff. |
| | |
| skipping to change at line 95 | | skipping to change at line 95 |
|---|
| try removing extra dots with: sed -e 's/^\.\././' < screen.1 | nroff -man | | try removing extra dots with: sed -e 's/^\.\././' < screen.1 | nroff -man |
| The info page doc/screen.texinfo contains basically the same information as | | The info page doc/screen.texinfo contains basically the same information as |
| the man-page, we may have missed one or another thing in one of the files. | | the man-page, we may have missed one or another thing in one of the files. |
| If so, mail me. | | If so, mail me. |
| | |
| 6.) etc/screenrc & etc/etcscreenrc | | 6.) etc/screenrc & etc/etcscreenrc |
| ---------------------------------- | | ---------------------------------- |
| The files screenrc and etc/etcscreenrc are instructive samples that | | The files screenrc and etc/etcscreenrc are instructive samples that |
| demonstrate what can/should be done from your private .screenrc and from | | demonstrate what can/should be done from your private .screenrc and from |
| $ETCSCREENRC -- do not just copy them. Read them. Look through the | | $ETCSCREENRC -- do not just copy them. Read them. Look through the |
|
| etcscreenrc file for system wide defaults that you like to set. e.g. | | etcscreenrc file for system wide defaults that you like to set, e.g. |
| autodetach off, startup_message off, vbell on, ... | | autodetach off, startup_message off, vbell on, ... |
| Since version 3.2.15 the screenrc file syntax changed slightly. All rc files | | 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. | | with this package. |
| If and only if you want to install screen as a console multiplexer, look | | If and only if you want to install screen as a console multiplexer, look |
| at the *.sample files and what 'make cscreen' suggests. | | at the *.sample files and what 'make cscreen' suggests. |
| | |
| 7.) terminfo/screeninfo.src & terminfo/screencap | | 7.) terminfo/screeninfo.src & terminfo/screencap |
| ------------------------------------------------ | | ------------------------------------------------ |
| Every now and then we update the termcap/terminfo entries for screen. | | Every now and then we update the termcap/terminfo entries for screen. |
| | | |
| End of changes. 3 change blocks. |
|---|
| 3 lines changed or deleted | | 3 lines changed or added |
|---|
"Fossies" - the Fresh Open Source Software Archive 