My thanks to everyone who responded:
>Mike Nguyen email@example.com
Andrew Moffat amof@SubaruSparcDev.subaru1.com
>Russell Page firstname.lastname@example.org
Michael Hill Hill.Michael@tci.com
John McWilliams email@example.com
David Thorburn-Gundlach firstname.lastname@example.org
John Bradley email@example.com
My original question was how does one / the boot drive after booting
from a CD-ROM:
>ok > boot cdrom -sw
>you come up in single user mode.
>1) fsck /dev/dsk/c?t?d?s? where ? is applicable ids
>2) mount /dev/dsk/c?t?d?s? /a
>now anytime you wish to reference a directory structure or file, remember
>that you must prefix the path with '/a'. Don't forget to set your TERM
>variable as well.
>mount -F ufs -o rw /dev/dsk/c0t0d0s0 /tmp/root
>Assuming /tmp is in the mini-root from CD and your boot device root really is
>at c0t0d0s0 or sd0.
>'mount /dev/dsk/c0t0d0s0 /a` should do it - if /a exists - which it
>should. Also assuming c0t0d0s0 is your root partition too of course.
>You can get straight to a single user prompt on the cdrom by doing a single
>user boot from it.
>To mount / to the cdrom file system. Determine the block device name for
>root. (Check /etc/vfstab on the root file system before you boot from the
>cdrom). On a SparcStation it is usually /dev/dsk/c0t3d0s0.
>From the single user prompt:
>1. Make sure you are in the cdrom's root directory.
>2. Run fsck on the disk based root file system.
3. Mount the disk based system on the directory called /a in the cdrom
># cd /
># fsck /dev/rdsk/c0t3d0s0
>fsck stuff here
># mount /dev/dsk/c0t3d0s0 /a
>ok> boot cdrom -s
>Once you're in single-user mode from the CD-ROM (or network), you are not
>running on the filesystem that's on your hard drive, but on a "virtual"
>filesystem that exists only in memory. In other words, /etc is *not* the
>/etc on your disk. You need to mount the partition that needs fixing (in
>this case, your root partition). Assuming it's on slice 0 of SCSI target 3,
> 'mount /dev/dsk/c0t3d0s0 /mnt'
>(you can also use /a as the mount point, as it always exists when you boot
>from the CD-ROM or network). It may require you to fsck the
>partition first, if there are filesystem inconsistencies. Then fix whatever
>you need to, and reboot (init 6). If it's an /etc file, for instance, don't
forget to edit /mnt/etc/whatever.
Also, I asked about getting to single-user mode after loading CDE. Here
>are some suggestions people made:
>(1) It's a long time since I played with CDE... but kinda sounds like a
>problem with the rc scripts. I guess I'd check that the dtlogin startup
>(whatever its called) doesn't start up in rcS.d, and maybe is killed off when
>the system is coming down to that level. I haven't checked the one server we
>have running 2.5.1 to see what it does, but it has the following rc scripts;
>init.d/dtlogin rc0.d/K10dtlogin rc2.d/S99dtlogin
Looks like it should only be running dtlogin when its up past init level 2.
>(2) If you want to know the patches for your system, try to do this:
>showrev -a | mail firstname.lastname@example.org
>This site will return a list of your patches needed to install on your
--- It turned out I was calling openwin in /.profile and it's getting hung up on the splash screen (so it really wasn't a CDE problem but the way /.profile was setup. Does this mean openwin can only be started in run-level 3?!?
>Thank you very much!!! > Ju-Lien Lim >
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:12:02 CDT