From: "Stefan Fröberg" <stefan.froberg@petroprogram.com>
To: buildroot@busybox.net
Subject: [Buildroot] editing device_table_dev.txt
Date: Fri, 22 Feb 2013 01:32:54 +0200 [thread overview]
Message-ID: <5126AEA6.7060004@petroprogram.com> (raw)
In-Reply-To: <5126AC9B.30302@mind.be>
[snip]
>>> I'm afraid that mdev and udev no longer work with old kernels that
>>> don't support the DEVTMPFS option...
>>>
>>> mdev and udev don't create device nodes; they only do something
>>> configurable when a hotplug event happens.
>>>
>>
>> What you mean that mdev or udev does not create device nodes ???
>> If older kernels don't support devtmpfs like Baruch
>> said then who does that device node creation if not the mdev or udev
>> when event happens ???
>
> Well, nobody...
>
> Turns out that mdev still does device node creation. Makes me wonder
> if I'm not mistaken about udev as well... I just remember hearing that
> device node creation was removed when DEVTMPFS was introduced.
>
Speaking of udev, I must say that Im not very happy of that recent
including of systemd as hard dependency.
If it would be optional then it would be ok and fine, but to forcefully
cram yet-another init system (in addition to bazillion other existing ones)
down the throats of latest udev users .... not good, not good at all!
Also, what I have studied little of those Gnome3 software packages,
there also seems to spreading this systemd thing.
Stefan
next prev parent reply other threads:[~2013-02-21 23:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-20 23:37 [Buildroot] editing device_table_dev.txt John Stile
2013-02-21 10:14 ` Stefan Fröberg
2013-02-21 10:21 ` Stefan Fröberg
2013-02-21 10:23 ` Baruch Siach
2013-02-21 10:32 ` Stefan Fröberg
2013-02-21 22:57 ` Arnout Vandecappelle
2013-02-21 23:07 ` Stefan Fröberg
2013-02-21 23:24 ` Arnout Vandecappelle
2013-02-21 23:32 ` Stefan Fröberg [this message]
2013-02-23 9:30 ` Arnout Vandecappelle
2013-02-23 11:18 ` Stefan Fröberg
2013-02-24 17:26 ` Thomas Petazzoni
2013-02-24 18:11 ` Peter Korsgaard
2013-02-24 17:24 ` Thomas Petazzoni
2013-02-21 23:14 ` Arnout Vandecappelle
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=5126AEA6.7060004@petroprogram.com \
--to=stefan.froberg@petroprogram.com \
--cc=buildroot@busybox.net \
/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