Thanks everyone for the quick responses. I can't boot the 2.4.2 kernel
with devfs=nomount, so it looks like the devices is indeed the problem.
However, reinstalling dev is turning out to be not so simple with devfs
mounted on /dev--the install just hangs, as I suppose it is trying to
install the inodes into the devfs. I think I'm going to have to try
booting off the installation CD and try to fix the devices from the bash
prompt on console 2. With luck, I might just need /dev/tty1 to get the
system to at least boot up so I can fix it. Otherwise, if there is some
way to make an archive of inodes, I might be able to make an archive of
the inodes from another computer and restore the archive, then reboot
and reinstall dev. Or I could try to install the dev RPM that way.
Eric Sandeen wrote:
> On 07 Aug 2001 19:44:38 +0200, Seth Mos wrote:
>
> > Someone else bumped into the exact same problem. You need to reinstall the
> > devices rpm because it (obviously) didn't get installed on the 1.0
> > release installer. I am not completely sure it sure what the package is
> > called like.
>
> Actually, the dev RPM (dev-<version>.i386.rpm) should be installed even
> in 1.0, it's just not used. That's why you should be able to use
> "devfs=nomount" in a 1.0-installer-installed system, and still have
> things work.
>
> But re-installing the dev RPM is probably a good place to start w/ this
> problem.
-
"Jonathan F. Dill" (dill@xxxxxxxxxxxx)
CARB Systems and Network Administrator
Home Page: http://www.umbi.umd.edu/~dill
|