All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 4508] New: /dev/console and /dev/null have to be created on udev based systems also
Date: Tue, 22 Nov 2011 09:23:14 +0000 (UTC)	[thread overview]
Message-ID: <bug-4508-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=4508

           Summary: /dev/console and /dev/null have to be created on udev
                    based systems also
           Product: buildroot
           Version: 2011.08
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: minor
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: fenixk19 at mail.ru
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


Now buildroot have two device tables - device_table.txt used in static and
dynamic /dev variants, and device_table_dev.txt, that is used only in static.

But devices /dev/console and /dev/null have to be static created for both types
of /dev filesystem.
So, probably, it would be good to move /dev/null and /dev/console definition
from device_table_dev.txt to device_table.txt?

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

             reply	other threads:[~2011-11-22  9:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-22  9:23 bugzilla at busybox.net [this message]
2011-11-22  9:29 ` [Buildroot] [Bug 4508] /dev/console and /dev/null have to be created on udev based systems also bugzilla at busybox.net

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=bug-4508-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.