From: Jon Smirl <jonsmirl@yahoo.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: little udev problem - loop devices instead of hda devices!
Date: Sat, 21 Feb 2004 17:51:10 +0000 [thread overview]
Message-ID: <20040221175110.63521.qmail@web14912.mail.yahoo.com> (raw)
In-Reply-To: <1076601040.402ba0d05eb01@webmail.fish.co.uk>
On Fedora the /dev directory on your init device that you are going to mount
udev over needs to contain at the minimum an entry for console. This is not a
problem with initrd, Fedore initrd will work without change.
mknod /dev/console c 5 1
Maybe some Fedora expert can figure out how to remove this requirement.
--- Francis Barton <fbarton@fish.co.uk> wrote:
> On Thu, 2004-02-12 at 21:03, John L. Fjellstad wrote:
>
> > udev is a completely userspace program, unlike devfs that lived
> > partly in the kernel. udev will probably be started as part of init.d,
> > meaning it won't start up until after / has been mounted. This is a
> > catch-22, of course, since the system needs udev to run to find the root
> > partition and console, and udev won't start up until the system is up.
> >
> > So, the fix this, you have to create a initrd(?) image to load up the
> > initial system with the bare minimum devices statically created (your /,
> > console etc), and then switch over to udev once / has been mounted.
>
> This is the bit that is confusing me - how can I build an initrd with
> console and null support? Or is there a way of getting udev to create
> console and null - are they udev-compliant or are workarounds needed?
>
> When I boot up with just udev I hit an error "no initial console found".
> man mkinitrd seems to refer only to modules (using the --with= flag) -
> but I don't know which modules are needed for console and null.
>
> Can anybody help please?
>
> Fedora 1, kernel 2.6.2, udev 018
>
> (The loop problem has gone away BTW)
>
> Thank you.
>
>
>
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id\x1356&alloc_id438&op=click
> _______________________________________________
> 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
==Jon Smirl
jonsmirl@yahoo.com
__________________________________
Do you Yahoo!?
Yahoo! Mail SpamGuard - Read only the mail you want.
http://antispam.yahoo.com/tools
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&op=click
_______________________________________________
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
prev parent reply other threads:[~2004-02-21 17:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-12 15:50 little udev problem - loop devices instead of hda devices! fbarton
2004-02-12 21:03 ` John L. Fjellstad
2004-02-13 1:32 ` Greg KH
2004-02-15 3:28 ` Francis Barton
2004-02-21 17:43 ` Francis Barton
2004-02-21 17:51 ` Jon Smirl [this message]
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=20040221175110.63521.qmail@web14912.mail.yahoo.com \
--to=jonsmirl@yahoo.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).