mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Robert Schwebel <r.schwebel@pengutronix.de>
To: Rob Landley <rob@landley.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: initramfs for /dev/console with udev?
Date: Thu, 3 Nov 2005 07:47:27 +0100	[thread overview]
Message-ID: <20051103064727.GR23316@pengutronix.de> (raw)
In-Reply-To: <200511022140.25268.rob@landley.net>

On Wed, Nov 02, 2005 at 09:40:24PM -0600, Rob Landley wrote:
> > dir /dev 0755 0 0
> > nod /dev/console 0600 0 0 c 5 1
> > nod /dev/null 0600 0 0 c 1 3
> > dir /root 0700 0 0
> >
> > and let CONFIG_INITRAMFS_SOURCE point to that file. The gpio archive is
> > built correctly with that, but my kernel doesn't seem to use it.
> 
> 1) You have no init in initramfs, so it goes ahead and mounts whatever root= 
> points to over it. I'm guessing that's where it's looking for /dev/console 
> from.

Hmm, I thought something like that. That means that I do need a complete
klibc based early userspace, just to get these two device nodes? Seems
like I'll have to do some deeper investigation of klibc; last time I
looked it didn't even compile for ARCH=um.  

> 2) What's the directory /root for?

Just a relict from the default script; the first three lines should be
enought. But it shouldn't matter. 

> > Is anything else needed to use an initrd, like a command line argument?
> > My kernel boots from a nfs partition, so it sets nfsroot=...
> 
> Note that initramfs and initrd and very different things.

Is there any other known possibility to get just these two device nodes
in an automatic way? I'm trying to get rid of devfs, and udev works just
fine. The only thing not solved yet is how to get the beast started
without /dev/console and /dev/null. I don't want to create the nodes
statically, because that's only possible with root permissions. 

Some background: I'm building root filesystems for embedded systems with
PTXdist; the user is able to build the whole thing without root
permissions; either with a cross compiler and mount it via NFS or build
a JFFS2 image, or, with one switch, build and run it with an uml kernel.

I also tried ndevfs, just to get these two nodes, but I didn't find out
how to automatically mount it on boot yet. 

Robert
-- 
 Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de
 Pengutronix - Linux Solutions for Science and Industry
   Handelsregister:  Amtsgericht Hildesheim, HRA 2686
     Hannoversche Str. 2, 31134 Hildesheim, Germany
   Phone: +49-5121-206917-0 |  Fax: +49-5121-206917-9


  reply	other threads:[~2005-11-03  6:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-02 22:20 Robert Schwebel
2005-11-03  3:40 ` Rob Landley
2005-11-03  6:47   ` Robert Schwebel [this message]
2005-11-03 17:38     ` Rob Landley
2005-11-03 18:51       ` Robert Schwebel
2005-11-03 19:13         ` Rob Landley
2005-11-03 19:57           ` Roland Dreier
2005-11-03 21:00             ` Rob Landley
2005-11-03 21:29             ` Rob Landley
2005-11-04 21:39               ` Martin Schlemmer
2005-11-04 23:10                 ` Rob Landley
2005-11-04 23:11                   ` Rob Landley
2005-11-05  0:26                   ` Martin Schlemmer
2005-11-05  2:56                     ` Rob Landley
2005-11-03 21:41             ` Rob Landley

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=20051103064727.GR23316@pengutronix.de \
    --to=r.schwebel@pengutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob@landley.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

all inboxes | Powered by JetHome®