Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
miah <jjohnson at sunrise-linux.com> writes: >Sure you do, the redhat boot cdrom/disk set. Another alternative is >'toms root boot disk' http://www.toms.net/rb/ which is a rescue disk >specifically for stuff like this. Two more options are the Knoppix and Bootable Business Card Linux CDROMs. Another option for some situations is sash, a statically-linked shell with many common commands builtin. Here's part of its description: The sash program is a stand-alone shell which is useful for recovering from certain types of system failures. In particular, it was created in order to cope with the prob- lem of missing shared libraries or important executables. ...many of the standard system commands are built-in to sash. These built-in commands are: -ar, -chattr, -chgrp, -chmod, -chown, -cmp, -cp, -dd, -echo, -ed, -grep, -file, -find, -gunzip, -gzip, -kill, -ln, -ls, -lsattr, -mkdir, -mknod, -more, -mount, -mv, -printenv, -pwd, -rm, -rmdir, -sum, -sync, -tar, -touch, -umount, -where I have a lilo.conf entry that boots directly into sash: image=/boot/linux-2.4.19 label=sash append="init=/bin/sash" read-only However, sash does not have su builtin. - Jim Van Zandt
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |