From: Marc Perkel <marc@perkel.com>
To: linux-hotplug@vger.kernel.org
Subject: Interesting Fedora Core 3 Bug
Date: Tue, 14 Dec 2004 22:10:36 +0000 [thread overview]
Message-ID: <41BF64DC.7060205@perkel.com> (raw)
When I upgraded from Fedora Core 2 to Fedora Core 3 using YUM - the UDEV
was seriously broken. After spending the last two days trying to figure
out why the /dev/nell and /dev/zero devices with giving me premission
denied because they were set to 600 instead of 666 - it turns out that
udev was never starting.
For some reason the init scripts installed without udev support. I
reinstalled initscripts and it did have initscripts support after being
reinstalled. Apparently because the server was still running FC2 instead
of FC3 the install of initscripts - specifically the rc.sysinit file
didn't have udev support.
So - after wasting two days I finially got my server working again.
There needs to be some way that ensures that if the kernel expects udev
that it doesn't just load up half way. In my case udev was being built
into the initd files but wasn't loading on the system.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
reply other threads:[~2004-12-14 22:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41BF64DC.7060205@perkel.com \
--to=marc@perkel.com \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).