From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: /dev/fw major not constant (embedded mdev devtmpfs ieee1394)
Date: Thu, 21 Jan 2010 21:26:22 +0000 [thread overview]
Message-ID: <20100121212622.GA12515@kroah.com> (raw)
In-Reply-To: <4B58BF6A.6070303@fnac.net>
On Thu, Jan 21, 2010 at 04:21:26PM -0500, Mike Frysinger wrote:
> On Thu, Jan 21, 2010 at 15:57, Greg KH wrote:
> > On Thu, Jan 21, 2010 at 09:56:10PM +0100, Paul Chavent wrote:
> >> I'am working on an embedded gnu/linux system that allow to capture an ieee1394 stream.
> >>
> >> The system is compound of a kernel, a basic initrd (libc,libgcc,busybox,libdc1394,...) and my app.
> >>
> >> I use the new firewire stack.
> >>
> >> As my system is very minimalist, i tought to create the nodes in /dev at the moment of building my initrd.
> >>
> >> But when i needed to modify my kernel configuration, it has changed the major number of /dev/fw*.
> >>
> >> It's not really important for the definitive system (it will be
> >> freeze), but i wonder how to solve this issue for my future works ?
> >>
> >> I don't need hotplug, i just need to fill /dev at startup (coldplug).
> >> The target is an embedded device, so it should be easy to
> >> build/configure/install, and lightweight.
> >>
> >> For those reasons i don't want to use udev.
> >
> > Why, is udev somehow not "lightweight"?
>
> in comparison, it is absolutely not
Heh, in comparison to devtmpfs, yes, good point :)
thanks,
greg k-h
prev parent reply other threads:[~2010-01-21 21:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 20:56 /dev/fw major not constant (embedded mdev devtmpfs ieee1394) Paul Chavent
2010-01-21 20:57 ` Greg KH
2010-01-21 20:59 ` Grant Likely
2010-01-21 21:21 ` Mike Frysinger
2010-01-21 21:26 ` Greg KH [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=20100121212622.GA12515@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).