As you can see on beowulf it works as intended. Not in the chimaera. Please
fix it on chimaera.

# qemu-debootstrap --arch armhf beowulf beowulf-armhf
http://deb.devuan.org/merged
<https://l.facebook.com/l.php?u=http%3A%2F%2Fdeb.devuan.org%2Fmerged%3Ffbclid%3DIwAR0uBMDxVi1AdvD7m2sI7HHdMlIGngHP6dFXe98IOOPb6rRdMJKM6wbXsw8&h=AT3LPoIKykWq1izys9y7rhP2t2TXyUwJbF8TkmRnMy3-M2l-cQOxsYabILZmWhkmbtOdE41N-5gqJLZ0IP1Xqtwriju6mKnXIig0fh1y9TEI5jKxNcLAgW6PQg&__tn__=-UK-R&c[0]=AT0-AoC4ka65JWIAnkXdQ5SMOaDq8dPrYY7_CjrFSPr9wgsz4fgSmUR6W4PAO-9m5VMkEY1PSHZaL0dQggWaA5Acn41hXycBgTPspvJcuca4-KfcS6R8zFo5RFM5J-_49uQzLn-vg4qcLOeGjZbhaB-pem5Yw6UbZmcZp9qUAgnSnF1OSJaWqg>
beowulf

I: Running command: debootstrap --arch armhf --foreign beowulf
beowulf-armhf http://deb.devuan.org/merged
<http://deb.devuan.org/merged?fbclid=IwAR1GrspARbDWFWAiG8MbAq99h2EKBERMygF1SbFazIpHviI2_pkg7u_u8rI>
beowulf
I: Retrieving InRelease
I: Checking Release signature
I: Valid Release signature (key id 72E3CB773315DFA2E464743D94532124541922FB)

......

# chroot beowulf-armhf

# uname -a
Linux marietto-Z87-HD3 4.19.0-24-amd64 #1 SMP Debian 4.19.282-1
(2023-04-29) armv7l GNU/Linux

# uname -r
4.19.0-24-amd64

# apt update

Hit:1 http://deb.devuan.org/merged
<https://l.facebook.com/l.php?u=http%3A%2F%2Fdeb.devuan.org%2Fmerged%3Ffbclid%3DIwAR2i_TwxeNW8h3Y5cBQQ42oJlQam1w91afZgE0Fee_3EUpZDibbNfb8eUlw&h=AT3LPoIKykWq1izys9y7rhP2t2TXyUwJbF8TkmRnMy3-M2l-cQOxsYabILZmWhkmbtOdE41N-5gqJLZ0IP1Xqtwriju6mKnXIig0fh1y9TEI5jKxNcLAgW6PQg&__tn__=-UK-R&c[0]=AT0-AoC4ka65JWIAnkXdQ5SMOaDq8dPrYY7_CjrFSPr9wgsz4fgSmUR6W4PAO-9m5VMkEY1PSHZaL0dQggWaA5Acn41hXycBgTPspvJcuca4-KfcS6R8zFo5RFM5J-_49uQzLn-vg4qcLOeGjZbhaB-pem5Yw6UbZmcZp9qUAgnSnF1OSJaWqg>
beowulf InRelease
Get:2 http://deb.devuan.org/merged
<https://l.facebook.com/l.php?u=http%3A%2F%2Fdeb.devuan.org%2Fmerged%3Ffbclid%3DIwAR0FRfUlJ8mkQAPLXgIVh-Sx5d5HntIQwHyqkcWkcxxmiMT0Gm2o-yPqkiU&h=AT3LPoIKykWq1izys9y7rhP2t2TXyUwJbF8TkmRnMy3-M2l-cQOxsYabILZmWhkmbtOdE41N-5gqJLZ0IP1Xqtwriju6mKnXIig0fh1y9TEI5jKxNcLAgW6PQg&__tn__=-UK-R&c[0]=AT0-AoC4ka65JWIAnkXdQ5SMOaDq8dPrYY7_CjrFSPr9wgsz4fgSmUR6W4PAO-9m5VMkEY1PSHZaL0dQggWaA5Acn41hXycBgTPspvJcuca4-KfcS6R8zFo5RFM5J-_49uQzLn-vg4qcLOeGjZbhaB-pem5Yw6UbZmcZp9qUAgnSnF1OSJaWqg>
beowulf/main Translation-en [6295 kB]
Fetched 6295 kB in 6s (1026 kB/s)
Reading package lists... Done
Building dependency tree... Done
All packages are up to date.

On Wed, Jun 21, 2023 at 3:51 PM Mario Marietto <marietto2008@???>
wrote:

> ----> I doubt you can do anything without an armhf kernel. Because what
> debootstrap --second stage does is run dpkg on the target arch, to install
> the downloaded packages and then apt-get install a minimal OS. And all this
> is made by executables meant to be run by an armhf cpu, obviously.
>
> yeah,it works like this with qemu-debootstrap. there isn't any 2 stage.
> the os is configured totally on the first stage.
>
> ----> Could you remind us why you don't install a ready-made armhf image?
>
> Please elaborate more.
>
> On Wed, Jun 21, 2023 at 3:41 PM Mario Marietto <marietto2008@???>
> wrote:
>
>> ---> This means you must install an armhf kernel under your qemu virtual
>> machine; and this virtual machine will then execute the binaries downloaded
>> by debootstrap's first stage
>>
>> ok. Thanks for explaining to me what happens under the hood. In the end
>> qemu-debootstrap does all that is needed to run as I want. I would like to
>> try to run qemu-deboostrap instead of debootstrap. Can you explain to me
>> how to do that ? I don't want to install beowulf to have its functionality.
>>
>> On Wed, Jun 21, 2023 at 2:19 PM Didier Kryn <kryn@???> wrote:
>>
>>> Le 21/06/2023 à 13:55, Mario Marietto a écrit :
>>> > ---> The principle is that the executable downlaoded by the first
>>> > stage of debootstrap is not executable by the x86, but by the armhf.
>>> >
>>> > it does not work like this if qemu-debootstrap is used. I've posted
>>> > two tutorials that show that it works like this. Even me,after the
>>> > first stage of the bootstrapping,I configure the rest of the os
>>> > (armhf) directly on my PC x64 bit. There is even no need for a second
>>> > stage. What I don't understand is why the chimaera version removed
>>> > qemu-debootstrap and it forces users to have an arm board to finish
>>> > the setup. It does not even try to run debootstrap. On the screen I
>>> > see that the executable bootstrap is executed,instead. But,on the
>>> > previous version of devuan,called beowulf it works exactly like I have
>>> > explained. It does the first stage and the second stage on the X64 pc
>>> > running the command qemu-debootstrap and not the command bootstrap.
>>>

>>>      Sorry, I didn't read your tutorials. Here is the intention of
>>> quemu: emulate the instruction set of a foreign architecture. This means
>>> you must install an armhf kernel under your qemu virtual machine; and
>>> this virtual machine will then execute the binaries downladed by
>>> debootstrap's first stage. I doubt you can do anything without an armhf
>>> kernel. Because what debootstrap --second stage does is run dpkg on the
>>> target arch, to install the downloaded packages and then apt-get install
>>> a minimal OS. And all this is made by executabes meant to be run by an
>>> armhf cpu, obviously.

>>>

>>>      Couls you remind us why you don't install a ready-made armhf image?

>>>

>>> --     Didier

>>>
>>> _______________________________________________
>>> Dng mailing list
>>> Dng@???
>>> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
>>>
>>
>>
>> --
>> Mario.
>>
>
>
> --
> Mario.
>


--
Mario.