From: Patrick Ohly <patrick.ohly@intel.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/8] initramfs-framework: create /dev/console
Date: Fri, 04 Sep 2015 09:08:32 +0200 [thread overview]
Message-ID: <1441350512.9573.43.camel@intel.com> (raw)
In-Reply-To: <78A0B9F1-2E28-492F-B07B-445089E6827E@gmail.com>
On Thu, 2015-09-03 at 14:34 -0700, Khem Raj wrote:
> > On Sep 3, 2015, at 11:42 AM, Patrick Ohly <patrick.ohly@intel.com> wrote:
> >
> > install -m 0755 ${WORKDIR}/debug ${D}/init.d/00-debug
> > +
> > + # Create device nodes expected by some kernels in initramfs
> > + # before even executing /init.
> > + install -d ${D}/dev
> > + mknod -m 622 ${D}/dev/console c 5 1
> > }
> >
>
> may be just use USE_DEVFS = “0” instead if we are not letting devtmpfs into initrd image
The fix above is meant for the case were devfs is enabled (USE_DEVFS =
"1"). In my observation, a completely empty /dev then prevents booting
under qemu (see the "qemu + initramfs" mail thread).
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
next prev parent reply other threads:[~2015-09-04 7:08 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-02 15:48 [PATCH 00/10] enhancing images, booting and runqemu Patrick Ohly
2015-09-02 15:48 ` [PATCH 01/10] runqemu: support full-disk images Patrick Ohly
2015-09-02 15:48 ` [PATCH 02/10] initrdscripts: create /dev/console Patrick Ohly
2015-09-02 16:08 ` Otavio Salvador
2015-09-02 15:48 ` [PATCH 03/10] initramfs-framework: handle kernel parameters with . inside Patrick Ohly
2015-09-02 16:09 ` Otavio Salvador
2015-09-02 15:48 ` [PATCH 04/10] initramfs-framework: add separate init_verbose log level parameter Patrick Ohly
2015-09-02 16:16 ` Otavio Salvador
2015-09-03 6:36 ` Patrick Ohly
2015-09-03 11:50 ` Otavio Salvador
2015-09-02 15:48 ` [PATCH 05/10] initramfs-framework: support mounting rootfs in modules Patrick Ohly
2015-09-02 16:19 ` Otavio Salvador
2015-09-02 16:24 ` Otavio Salvador
2015-09-03 6:29 ` Patrick Ohly
2015-09-03 11:55 ` Otavio Salvador
2015-09-02 15:48 ` [PATCH 06/10] initramfs-framework: support live images Patrick Ohly
2015-09-02 15:48 ` [PATCH 07/10] image-vm.bbclass: avoid duplicating syslinux default values Patrick Ohly
2015-09-02 15:48 ` [PATCH 08/10] image-vm.bbclass: support specifying an initramfs Patrick Ohly
2015-09-02 15:48 ` [PATCH 09/10] boot loader: support root=UUID Patrick Ohly
2015-09-02 15:48 ` [PATCH 10/10] boot-directdisk.bbclass: use rootfs UUID by default Patrick Ohly
2015-09-02 16:28 ` [PATCH 00/10] enhancing images, booting and runqemu Otavio Salvador
2015-09-03 18:42 ` [PATCH 0/8] enhancing images, booting and runqemu, simplified version Patrick Ohly
2015-09-03 18:42 ` [PATCH 1/8] runqemu: support full-disk images Patrick Ohly
2015-09-03 18:42 ` [PATCH 2/8] initramfs-framework: create /dev/console Patrick Ohly
2015-09-03 21:34 ` Khem Raj
2015-09-04 7:08 ` Patrick Ohly [this message]
2015-09-03 18:42 ` [PATCH 3/8] initramfs-live-boot: " Patrick Ohly
2015-09-03 18:42 ` [PATCH 4/8] initramfs-framework: handle kernel parameters with . inside Patrick Ohly
2015-09-03 18:42 ` [PATCH 5/8] image-vm.bbclass: avoid duplicating syslinux default values Patrick Ohly
2015-09-03 18:42 ` [PATCH 6/8] image-vm.bbclass: support specifying an initramfs Patrick Ohly
2015-09-03 18:42 ` [PATCH 7/8] boot loader: support root=UUID Patrick Ohly
2015-09-03 18:42 ` [PATCH 8/8] boot-directdisk.bbclass: use rootfs UUID by default Patrick Ohly
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=1441350512.9573.43.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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