Ainsi parlait Tom Brinkman :
> On Monday June 30 2003 04:29 am, [EMAIL PROTECTED] wrote:
> > I had the same guess about the broken/nonexistent initrd image,
> > but at least on my box it is not related to a broken devfs,
> > because I only updated the Kernel not devfs. The last message I
> > can remember was "trying to kill init", sorry I cannot look what
> > it exactly was, because my laptop is at home.
>
> I don't believe they're related either, ie, kernel and devfsd.
> When I did manage to recover cooker (9.1 install + resync with
> urpmi to current cooker), the new devfs failed to provide scd0,
> loop, rtc, .. The only alternative was to rebuild 9.1's devfsd
> src.rpm and --force it in. Then I had a working system again (scd0,
> loop, rtc, ...)
Check in your logs for messages as
"/sbin/devfsd-try-modload"^INo such file or directory
If it is the case, just edit your /etc/devfsd.conf file and switch the comment
between the following lines:
#LOOKUP .* EXECUTE /sbin/devfsd-try-modload $devpath
LOOKUP .* MODLOAD
--
How can someone "draw a blank"?
-- Why Why Why n�4
