Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 4514] New: Booting OS, that requires automount of devtmpfs fails if fs image used as initramfs
Date: Wed, 23 Nov 2011 19:42:13 +0000 (UTC)	[thread overview]
Message-ID: <bug-4514-163@https.bugs.busybox.net/> (raw)

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

           Summary: Booting OS, that requires automount of devtmpfs fails
                    if fs image used as initramfs
           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


System based on devtmpfs or udev with initramfs as root won't boot, because
kernel doesn't automount devtmpfs on initramfs. Using initramfs requires manual
mount for devtmpfs.

Manual mount can be done by adding a string in the beginning of /etc/inittab:
::sysinit:/bin/mount -t devtmpfs devtmpfs /dev

As a bug of buildroot it could be fixed by adding an option to mount manually
devtmpfs, that makes buildroot add corresponding string to inittab
automatically.

-- 
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-23 19:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-23 19:42 bugzilla at busybox.net [this message]
2011-11-26 20:49 ` [Buildroot] [Bug 4514] Booting OS, that requires automount of devtmpfs fails if fs image used as initramfs 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-4514-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox