On Friday 01 February 2002 10:49 pm, you wrote: Me too, except re-installing and adjusting the lilo append line on the boot loader panel to remove the devfs=mount altogether will result in an install that will boot.
However, the next problem that appears during boot is: insmod /lib/modules/2.4.17-13mdk/kernel/driver/char/rtc.o No such file or directory, modprobe: insmod char-major-10-135 failed After boot, and at the command line, insmod rtc Using /lib/modules/2.4.17-13mdk/kernel/driver/char/rtc.o.gz modprobe char-major-10-135 returns no error. > Same problem here. I was just about to post myself. > > --- Matthew Schick <[EMAIL PROTECTED]> > > wrote: > > On Fri, 2002-02-01 at 22:52, Quel Qun wrote: > > Hi, > > > > After updating the pam rpm, I cannot boot my > > machines if I set > > devfs=mount > > > > Running DevFs deamon (shouldn't it be daemon?) > > Started device management > > daemon v1.3.22 for /dev > > error loading > > "/lib/security/pam_console_apply_devfsd.so" > > undefined > > symbol _pam_gerpwnam_r > > > > Then of course the hard drive is not found. > > > > Temporary solution: devfs=nomount > > > > $ rpm -q pam devfsd > > pam-0.75-15mdk > > devfsd-1.3.22-3mdk > > > > Same setup, same problem...... > > > > Matt > > __________________________________________________ > Do You Yahoo!? > Great stuff seeking new owners in Yahoo! Auctions! > http://auctions.yahoo.com
