kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: renjunqu.kernel@gmail.com (Renjun Qu)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Please help me about the default rootfs
Date: Tue, 25 Oct 2011 14:07:03 +0800	[thread overview]
Message-ID: <CAPu47WTvDMa51MGjfjh_5QtN4zAn8syoxriv=dY4wLWO0D-uPw@mail.gmail.com> (raw)

Hello everyone:
       I am building a small embedded linux system right now. I
confused that why the default rootfs must has a "dev/console" node. I
have made a experiment as follow:
      1st, configure the kernel(2.6.32) to support the initramfs
and initrd, and set the source of the initramfs to a directory which
only has a "root" node.
      2nd, configure the kernel to support the root file system on
nfs, and rebuild the kernel. I have created all necessary files and
directories in the directory exported by the nfs server.
      3rd,  set the appropriate boot parameter, and boot my kernel.
      The result is, the kernel can successfully mount the root
file system, but the "/sbin/init" program can not print any
information to me. My "sbin/init" program is just a hello world
program which only print some greeting information.There is a
"dev/console" device node in the nfs exported directory.
      But if i set the source of the initramfs to empty, and redo
my experiment from the 2nd step,everything will be ok. So, i think
there must be a ?dev/console? node in the rootfs. The real root file
system already has a "dev/console" node, why default rootfs must have
a dev/console node. Please help me.

                       Best regards,

                          Ren jun Qu

                 reply	other threads:[~2011-10-25  6:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAPu47WTvDMa51MGjfjh_5QtN4zAn8syoxriv=dY4wLWO0D-uPw@mail.gmail.com' \
    --to=renjunqu.kernel@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.org \
    /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;
as well as URLs for NNTP newsgroup(s).