Date: Tue, 03 Nov 1998 12:46:45 -0800 From: Dan Yergeau <yergeau@gloworm.Stanford.EDU> To: questions@FreeBSD.ORG Cc: yergeau@gloworm.Stanford.EDU Subject: making device nodes with boot/fixit floppies (3.0-RELEASE) Message-ID: <199811032046.MAA22570@goose.Stanford.EDU>
next in thread | raw e-mail | index | archive | help
Am I missing something or is making device nodes (for disk slices)
under a "emergency recovery" scenario(*) with boot/fixit supposed to be
this complicated/challenging?
I didn't seen anything "obvious" in sysinstall, so I ended up
- booted using the boot floppy (well, it was already booted)
- started a holographic shell
(no /dev/MAKEDEV, so ...)
- used sysinstall to mount the fixit floppy
- copied fixit floppy's dev/MAKEDEV to /dev
(discovered that MAKEDEV doesn't work due to ...)
- added fixit floppy directories to PATH
(and ...)
- edited /dev/MAKEDEV to change some hardcoded paths and
chmod/chgrp since the boot floppy's /etc/{passwd,group} ain't
quite complete (if they even exist)
- (finally!) "sh MAKEDEV da0s2a"
I suppose I could have faked an install, adding the
disks/partitions, then commit'ing w/o extracting anything, but that
also seems needlessly complicated and is not obvious.
Dan
(*) This instance of emergency recovery was brought on by my sloppy
attempt to wire the disk at scsi target 0 to da1 (first bios disk is
an IDE). I did modify /etc/fstab, but I had forgotten to create the
device nodes for da1s2, so even booting from the hard disk in single
user mode wouldn't work for recovery (couldn't get it to remount /
in read/write mode).
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199811032046.MAA22570>