[Buildroot] Trying to build in an usual place: /opt instead of /
Olivier Perron
olivier.perron12 at gmail.com
Fri Dec 4 15:49:21 UTC 2009
On Tue, Dec 1, 2009 at 7:42 PM, Michael S. Zick <minimod at morethan.org> wrote:
> 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
Mike,
this doesn't work (well not completely).
Once chrooted, when I want to start X I got an error which says:
Fatal server error:
xf86OpenConsole: Cannot find a free VT: Inappropriate ioctl for device
My solution (to mount with the -bind option) works ok.
Cheers
Olivier
More information about the buildroot
mailing list