Perfect, thanks!
I completely missed this line where it blows the whole directory away:
https://github.com/beagleboard/image-builder/blob/24b8b155b41d4d0b4a3d7d3e2295441df81b94b0/RootStock-NG.sh#L160
I must be looking at a partial temp directory from a canceled run or
something.
Thanks for your
On Tue, Apr 27, 2021 at 1:59 PM John Allwine wrote:
>
> It seems like that tmp dir is missing a lot of data. Is there a clean up step
> I need to comment out?
If you kill it right here:
https://github.com/beagleboard/image-builder/blob/master/scripts/chroot.sh#L1363
You can re-chroot in..
It seems like that tmp dir is missing a lot of data. Is there a clean up
step I need to comment out?
On Tue, Apr 27, 2021 at 12:42 PM Robert Nelson
wrote:
> On Tue, Apr 27, 2021 at 1:36 PM John Allwine wrote:
> >
> > Is there a way to drop into a bash terminal within the qemu environment
> to
On Tue, Apr 27, 2021 at 1:36 PM John Allwine wrote:
>
> Is there a way to drop into a bash terminal within the qemu environment to
> debug? I ran the RootStock-NG.sh script and see the ignore/tmp.X
> directory. Does something like this work?
>
> After running RootStock-NG.sh;
> sudo chroot
Is there a way to drop into a bash terminal within the qemu environment to
debug? I ran the RootStock-NG.sh script and see the ignore/tmp.X
directory. Does something like this work?
After running RootStock-NG.sh;
sudo chroot /path/to/ignore/tmp.XXX /bin/bash
(I get a
On Tue, Apr 27, 2021 at 12:47 PM John Allwine wrote:
>
> The image-builder scripts (https://github.com/beagleboard/image-builder) are
> great for putting together a Beaglebone image. Is there a mechanism in there
> to build specific packages from source? I see some references to qemu in
>
The image-builder scripts (https://github.com/beagleboard/image-builder)
are great for putting together a Beaglebone image. Is there a mechanism in
there to build specific packages from source? I see some references to qemu
in various places. Is it set up to cross compile?
Any tips are
