Date: Sun, 6 Jun 1999 11:18:06 GMT From: jhs@freebsd.org To: FreeBSD-gnats-submit@freebsd.org Subject: conf/12050: No spare /sbin/init from fixit flop to copy over damaged one. Message-ID: <199906061118.LAA06031@jhs.muc.de>
next in thread | raw e-mail | index | archive | help
>Number: 12050 >Category: conf >Synopsis: No /sbin/init on fixit flop >Confidential: no >Severity: critical >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Sun Jun 6 06:10:01 PDT 1999 >Closed-Date: >Last-Modified: >Originator: Julian H. Stacey jhs@freebsd.org >Release: FreeBSD 3.2-RELEASE i386 >Organization: >Environment: Small machine, EG laptop in hotel, no spare hard discs, no cdrom drive, no ether/slip/plip network, Just the fixit floppy available, >Description: If /sbin/init is destroyed or corrupted, boot -s fails, you have no spare init to copy in, you are stuck ! >How-To-Repeat: chmod -x /sbin/init boot -s # Fail to boot off hard disc Boot with fixit floppy, mount your hard drives find / -name init -print chmod +x /sbin/init # to rescue yourself from the simulation Now think: "how could I copy in a new init if mine was damaged ?" >Fix: Ideally, put an /sbin/init on fixit floppy, but no space: tunefs -m 0 /dev/rfd0c df /dev/rfd0c # 72 K free cp /sbin/init /tmp gzip /tmp/init # 109 K maybe there's room on the 2nd boot disc was introduced with 3.2 ? Or maybe we should introduce a fixit.extras floppy ? I suspect other files might also be needed on there ? >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199906061118.LAA06031>