Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Laird <danieljlaird@hotmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Fakeroot issues
Date: Tue, 30 Jan 2007 01:46:16 -0800 (PST)	[thread overview]
Message-ID: <8706461.post@talk.nabble.com> (raw)


Hi I am trying to use buildroot to generate me a CPIO archive which is then
included in my kernel image as a initramfs.

The problem I am having is that is looks like all has worked, no errors etc.  
However the devices that are created by makedev are not being created as
devices but just as files.
(build_mipsel/root/dev/....)

I am presuming this is dues to an issue with fakeroot.  As I can run makedev
as root user with same parameters and it all works fine.  

It there any easy way to debug what is going on with fakeroot as I cant get
this to work at the moment.

I am using Redhat EL4 (Unfortunate Work Choice) in case that might trigger
anything.

Cheers
Dan

-- 
View this message in context: http://www.nabble.com/Fakeroot-issues-tf3141363.html#a8706461
Sent from the BuildRoot mailing list archive at Nabble.com.

             reply	other threads:[~2007-01-30  9:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-30  9:46 Daniel Laird [this message]
2007-01-30 11:03 ` [Buildroot] Fakeroot issues MikeW

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=8706461.post@talk.nabble.com \
    --to=danieljlaird@hotmail.com \
    --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