Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Jamie Lenehan <lenehan@twibble.org>
To: axel lin <axel.lin@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: why the files in rootfs /dev folder are regular files
Date: Wed, 18 Oct 2006 16:00:03 +1000	[thread overview]
Message-ID: <20061018060003.GA26266@twibble.org> (raw)
In-Reply-To: <427d64720610172256kbad5556n6ac7caf4bc9b965a@mail.gmail.com>

On Wed, Oct 18, 2006 at 01:56:04PM +0800, "axel lin" wrote:
> hi list,
>     I'm using angstrom/mainstone config.
>     After build a bootstrap-image, I found that the files in
> rootfs/dev folder are all regular files. Is this OE bug?

That's  expected.
See the fakeroot in the reference section of the user manual:

  http://www.openembedded.org/user-manual&dpage=ch07s04

-- 
 Jamie Lenehan <lenehan@twibble.org>



      reply	other threads:[~2006-10-18  6:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-18  5:56 why the files in rootfs /dev folder are regular files axel lin
2006-10-18  6:00 ` Jamie Lenehan [this message]

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=20061018060003.GA26266@twibble.org \
    --to=lenehan@twibble.org \
    --cc=axel.lin@gmail.com \
    --cc=openembedded-devel@lists.openembedded.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