Mac/Mac Programming/Cocoa/HyperTalk Books free - Melbourne

On Wed, 14 Dec 2011 00:48:15 +0000 Liam Proven <lproven at gmail.com> wrote: Yes. And that is the problem. /bin/sh should be a simple POSIX Bourne shell. /bin/sh -> /bin/bash is an evil Linuxism. I get them all the time at "apt-get install" and the like on my Debian box at work. Seconded. But I wane nuke someone to hell if the man page contains somthing like "Look in info(1) for the information you need." Unfortunately info(1) is an evil GNUism and I find it quite unusable. Similar for HTML-only documentation. Fortunately there are lynx(1) and friends... Pure idiot compatibility and very dangerous for newbies. They get used to the -i behaviour and take it for normal. Until they get to a properly configured machine... It would be acceptable as a security measure to restrict root login to the local text console. This prevents "missuse" of the root account but makes the system accessible in the event of a failure. If e.g. NIS breaks you can't get into a Ubuntu machine to fix the problem. All you can do in that situation is to hit the reset button and boot single user. But that is an other story... In 18 years of Unix I still have to see a proper implemented Linux single user mode on any distribution. Single user mode is: 1. Execute kernel. 2. Kernel mounts / read-only. 3. Kernel creates /sbin/init process with PID 1. 4. init(8) invokes /bin/sh on /dev/console. 5. root prompt and _nothing_ more. Especially no mount of any file systems other then /-read-only. To interrupt e.g. dhclient(8) or ypbind(8) in case of a network failure. ^C works perfectly on *BSD... -- \end{Jochen} \ref{http://www.unixag-kl.fh-kl.de/~jkunz/}