All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael S. Zick <minimod@morethan.org>
To: buildroot@busybox.net
Subject: [Buildroot] Trying to build in an usual place: /opt instead of /
Date: Tue, 1 Dec 2009 12:42:45 -0600	[thread overview]
Message-ID: <200912011242.47113.minimod@morethan.org> (raw)
In-Reply-To: <5cd84ac80912010618n334b9ecck27b26d2b493dca39@mail.gmail.com>

On Tue December 1 2009, Olivier Perron wrote:
> [...]
> >>>
> >>
> >> Why not using chroot ?
> >>
> >
> > Because I still need to access /dev ?
> >
> 
> Hum... bad answer !
> # mkdir /opt/dev
> # mount -o bind /dev /opt/dev
> before chrooting should do the trick.
> 

You don't need that, unless you want the changes made in
the chroot/dev to show up outside of the chroot.

Just initialize the device nodes in chroot/dev, they will
work just fine there (the kernel uses the device numbers,
not the path).

Presuming a bare busybox in chroot/bin - (/opt/test/bin)
Here is the short version:

mount -t proc proc /opt/test/proc
mount -t sysfs sysfs /opt/test/sys
chroot /opt/test /bin/busybox sh
/bin/busybox --install -s
mdev -s

Your done.  Have fun.

Mike
> Yes, I will try the chroot route then.
> 
> Anyway, if someone knows how to do what I wanted to do in first place,
> please tell me: I'd love to learn what I failed to do !
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
> 
> 

  parent reply	other threads:[~2009-12-01 18:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-01 13:10 [Buildroot] Trying to build in an usual place: /opt instead of / Olivier Perron
2009-12-01 13:21 ` Lionel Landwerlin
2009-12-01 14:10   ` Olivier Perron
2009-12-01 14:18     ` Olivier Perron
2009-12-01 14:23       ` Lionel Landwerlin
2009-12-01 18:42       ` Michael S. Zick [this message]
2009-12-04 15:49         ` Olivier Perron
2009-12-04 16:12           ` Michael S. Zick
2009-12-04 16:30             ` Olivier Perron
2009-12-04 17:23               ` Michael S. Zick

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=200912011242.47113.minimod@morethan.org \
    --to=minimod@morethan.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.