On Wed, Jun 21, 2023 at 03:57:15PM +0200, Mario Marietto wrote:
> I've got an idea to perform the first and the second debootstrap stages on
> my X64 pc. What I need to know is where I can find the packages for the
> armhf architecture. Basically I did the first part of the bootstrap on my
> X64 PC with the following command :
>
> debootstrap --foreign --arch armhf chimaera /mnt
> http://deb.devuan.org/merged/ chimaera
>
> and now I should perform the 2 stage directly on the arm board,but I can't
> install an OS on that board,so,AFAIK the only method that I have is to
> install some basic packages necessary to get the other ones. For sure the
> most important package is apt. Below there is the version of amd64 :
>
> http://deb.devuan.org/merged/pool/DEVUAN/main/a/apt/apt_2.6.1devuan1_amd64.deb
>
> but I need the corrispective package for armh. After having installed apt
> and every dependency using the pre-installed dpkg package,I will try to get
> the other packages by playing a little bit with the web paths. Thanks.
If you set up your host for multi-arch, say, armhf then "apt-get
update" will bring in the Packages files for armhf, and in fact you
can accomplish the two stages with the single command:
# debootstrap --arch armhf chimaera /mnt
http://deb.devuan.org/merged
That command will set up a chimaera filesystem under /mnt using armhf
software, and then it will chroot into that and perform the stage 2
within that filesystem (using armhf emulation). You may then later use
the same:
# chroot /mnt /bin/bash
to enter that filesystem and continue adding packages etc; debootstrap
will have set up /etc/apt/sources.list within that filesystem and you
might edit that as per normal. There would also be a kernel meta
package named linux-kernel-armhf to install which will prepare an
initrd etc in /boot as per normal. Later you will also need to have
the appropriate dtb file (device tree blob) for you actual target
hardware in order to run that kernel there. Many arm systems also has
a different (uboot-based) boot system that may require a boot image to
be prepared separate from the root filesystem.
Ralph.
>
> On Wed, Jun 21, 2023 at 3:22 PM Ralph Ronnquist <rrq@???> wrote:
>
> > On Wed, Jun 21, 2023 at 02:45:28PM +0200, Didier Kryn wrote:
> > > Le 21/06/2023 à 14:27, Ralph Ronnquist a écrit :
> > > > (I messed up and sent a direct reply :()
> > > >
> > > > ----- Forwarded message from Ralph Ronnquist <rrq@???>
> > -----
> > > >
> > > > Date: Wed, 21 Jun 2023 22:25:54 +1000
> > > > From: Ralph Ronnquist <rrq@???>
> > > > To: Didier Kryn <kryn@???>
> > > > Subject: Re: [DNG] Devuan armhf / armel for my Samsung / Google
> > Chromebook
> > > > model XE303C12 "Snow" ?
> > > > Message-ID: <ZJLsUNhj9sZ4GlT2@localhost>
> > > >
> > > > On Wed, Jun 21, 2023 at 02:09:53PM +0200, Didier Kryn wrote:
> > > > > Le 21/06/2023 à 12:13, Ralph Ronnquist a écrit :
> > > > > > It also works fine using "multiarch" (in which case the
> > architecture
> > > > > > transition is seamless). I.e., set up your system to have armhf
> > > > > > (and/or armel) as additional "foreign" architecture(s) and then a
> > > > > > plain debootstrap will be fine.
> > > > > multiarch makes sense for i386 and x86-64 (amd64) and for
> > powerpc 32 and
> > > > > 64, because the cpus are able to execute instructions of both
> > arches. I
> > > > > would be extermely surprised if it worked for amd64 and armhf.
> > > > Yes it did surprise me too :) Works fine for my amd6 laptop; a bit
> > > > slow, but that's no different from a "proper" qemu VM. (The multiarch
> > > > approach is basically the same as running a foreign qemu-static within
> > > > a foreign filesystem). But "seamless"; doesn;t need chroot.
> > > >
> > > > Ralph.
> > > >
> > > >
> > > Yes, an amd64 can run i386 instructions (by design) and a ppc64 can
> > run
> > > ppc32 instructions, also by design. I dunno if there are multiarch
> > > capibilities within arm architectures, but you can certainly not mix a
> > > random combination of architectures, like amd64 and armhf. Hence the need
> > > for qemu.
> >
> > Note that I have:
> > % dpkg --print-architecture
> > amd64
> > % dpkg --print-foreign-architectures
> > i386
> > arm64
> > armhf
> > armel
> > ppc64el
> >
> > and I have used them all and it has been very useful for preparing
> > filesystems and compiling kernel(s) for arm on my amd64 laptop; I've
> > done that for all three variants as well as for ppc64el.
> >
> > Ralph.
> >
> > >
> > > -- Didier
> > >
> > > _______________________________________________
> > > Dng mailing list
> > > Dng@???
> > > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
> > _______________________________________________
> > Dng mailing list
> > Dng@???
> > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
> >
>
>
> --
> Mario.
::
Re: [DNG] [rrq@mail.rrq.id.au: Re: …
