From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev - TODO update
Date: Tue, 17 Feb 2004 01:41:15 +0000 [thread overview]
Message-ID: <20040217014115.GB3596@kroah.com> (raw)
In-Reply-To: <20040212234538.GC21117@vrfy.org>
On Fri, Feb 13, 2004 at 12:52:18PM -0500, Mike Frysinger wrote:
> On Friday 13 February 2004 01:16 am, Daniel Drake wrote:
> > Yes, the default behaviour creates a devices.tar.bz2 on shutdown and
> > restores it on bootup. As far as I understand it, thats only a temporary
> > thing, implemented before udev was creating so many nodes by default.
> >
> > There is some discussion here to remove this behaviour,
> > http://bugs.gentoo.org/show_bug.cgi?id8587
>
> i've stopped doing this on my boxes just to see how far along udev has come
> (and boy, it's almost there for everything i need it for :D) ...
>
> i noticed that on my machines that use framebuffer devices, fbX wasnt being
> created, and on my ppc laptop, some adb related-nodes werent being created,
> so the way i've worked around it is to change the init scripts to
> run /etc/udev/udev.local instead of untaring the devices.tar.bz2 ... this
> script just creates a bunch of machine specific nodes via mknod and sets
> their perms correctly
Where is the startup script in gentoo that does this? I couldn't seem
to find it.
But I was able to blow away my whole /dev directory and reboot and have
udev create all of the nodes that I needed to startup. That was
impressive. Hm, Gentoo seems kinda nice now... :)
> i'm just glad udev is arch independent so i havent been forced back
> into devfs on some of my machine ;)
If udev ever gets any non-arch-independant code, please let me know, I
do not want this to happen.
thanks,
greg k-h
-------------------------------------------------------
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
next prev parent reply other threads:[~2004-02-17 1:41 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-12 23:45 udev - TODO update Kay Sievers
2004-02-13 1:26 ` Greg KH
2004-02-13 1:59 ` Kay Sievers
2004-02-13 6:16 ` Daniel Drake
2004-02-13 8:31 ` Olaf Hering
2004-02-13 17:52 ` Mike Frysinger
2004-02-13 19:34 ` Daniel Stekloff
2004-02-13 22:53 ` Greg KH
2004-02-17 1:41 ` Greg KH [this message]
2004-02-17 1:48 ` Mike Frysinger
2004-02-27 0:41 ` Kay Sievers
2004-02-27 0:49 ` Robert Love
2004-02-27 1:00 ` Greg KH
2004-02-27 1:13 ` Mike Frysinger
2004-02-27 1:23 ` Mike Waychison
2004-02-27 1:27 ` Robert Love
2004-02-27 1:36 ` Robert Love
2004-02-27 2:24 ` Bill Nottingham
2004-02-27 11:03 ` Robert McMeekin
2004-02-27 15:45 ` Kay Sievers
2004-02-27 17:35 ` Greg KH
2004-02-27 17:37 ` Greg KH
2004-02-27 18:08 ` Mike Waychison
2004-02-27 19:10 ` Bill Nottingham
2004-02-27 19:19 ` Robert Love
2004-02-27 19:20 ` Robert Love
2004-02-28 0:55 ` Greg KH
2004-02-28 13:07 ` Erik van Konijnenburg
2004-02-28 16:47 ` Robert Love
2004-02-28 22:19 ` Kay Sievers
2004-02-28 22:37 ` Robert Love
2004-02-29 4:01 ` Kay Sievers
2004-03-01 22:44 ` Greg KH
2004-03-01 23:05 ` Robert Love
2004-03-01 23:16 ` Greg KH
2004-03-02 0:04 ` Kay Sievers
2004-03-02 0:09 ` Greg KH
2004-03-02 7:24 ` [linux-hotplug-devel] " Wout Mertens
2004-03-02 7:32 ` Wout Mertens
2004-03-02 20:15 ` Greg KH
2004-03-02 20:55 ` Wout Mertens
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=20040217014115.GB3596@kroah.com \
--to=greg@kroah.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).