From: Ivan Kuten <ivan.kuten@promwad.com>
To: buildroot@busybox.net
Subject: [Buildroot] Some devices are not created in the ext2 filesystem.
Date: Mon, 15 Oct 2007 23:52:59 +0300 [thread overview]
Message-ID: <4713D32B.3030502@promwad.com> (raw)
In-Reply-To: <406A31B117F2734987636D6CCC93EE3C02528F7F@ehost011-3.exch011.intermedia.net>
Leonid wrote:
> Hi, Ivan:
>
> As I see also on other systems, /dev/null is normally created with 660
> permission like many other devices (/dev/console for example). I thought
> that buildroot runs udev with correct user to be able to rewrite all
> devices in /dev without trouble.
>
> So, I suppose, my question is this: is it some intrinsic buildroot
> udev-related bug or something wrong in my own system which results in
> such error? What would you recommend to do?
>
I'd suggest just turn udev off.
Best regards,
Ivan
next prev parent reply other threads:[~2007-10-15 20:52 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-12 21:01 [Buildroot] svn commit: trunk/buildroot/toolchain/gcc ulf at uclibc.org
2007-10-13 8:49 ` Cristian Ionescu-Idbohrn
2007-10-13 9:57 ` Ulf Samuelsson
2007-10-13 10:19 ` Cristian Ionescu-Idbohrn
2007-10-13 11:23 ` Bernhard Fischer
2007-10-13 18:37 ` Ulf Samuelsson
2007-10-13 19:58 ` Cristian Ionescu-Idbohrn
2007-10-13 20:31 ` Ulf Samuelsson
2007-10-13 23:31 ` Cristian Ionescu-Idbohrn
2007-10-14 1:08 ` Ivan Kuten
2007-10-14 5:22 ` [Buildroot] Some devices are not created in the ext2 filesystem Leonid
2007-10-14 12:43 ` Ivan Kuten
2007-10-14 12:37 ` softa at ttechgroup.com
2007-10-14 16:59 ` Ivan Kuten
2007-10-14 16:13 ` softa at ttechgroup.com
2007-10-14 17:31 ` Leonid
2007-10-14 21:33 ` Ivan Kuten
2007-10-15 11:03 ` Leonid
2007-10-15 20:52 ` Ivan Kuten [this message]
2007-10-15 6:50 ` [Buildroot] svn commit: trunk/buildroot/toolchain/gcc Ulf Samuelsson
2007-10-15 17:40 ` Cristian Ionescu-Idbohrn
2007-10-15 18:16 ` Ulf Samuelsson
2007-10-15 18:55 ` Bernhard Fischer
2007-10-15 19:27 ` Ulf Samuelsson
2007-10-13 11:25 ` Bernhard Fischer
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=4713D32B.3030502@promwad.com \
--to=ivan.kuten@promwad.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