[elbe-devel] [PATCH v2 4/6] debinstaller: implement download of vmlinuz and initrd.gz
Manuel Traut
manut at linutronix.de
Mon Oct 15 14:02:27 CEST 2018
On Mon, Oct 15, 2018 at 01:18:01PM +0200, Torben Hohn wrote:
> On Fri, Oct 12, 2018 at 05:19:34PM +0200, Manuel Traut wrote:
> > On Wed, Sep 26, 2018 at 12:13:50PM +0200, Torben Hohn wrote:
> > > the debinstaller module shall replace elbe-bootstrap.
> > > it downloads debian installer linux kernel and initrd.gz from
> > > a debian mirror. It does that in a secure manner, iE validating
> > > Release.gpg and SHA256SUMS on the way.
> > >
> > > filenames on the mirror:
> > > /debian/dists/jessie/main/installer-amd64/current/images/netboot/debian-installer/amd64/linux
> > > /debian/dists/jessie/main/installer-amd64/current/images/netboot/debian-installer/amd64/initrd.gz
> > > /debian/dists/jessie/main/installer-amd64/current/images/cdrom/initrd.gz
> > >
> > > Although this functionality is also provided by apt,
> > > we implement it here in pure python, because outside
> > > of the initvm, we can not rely on apt being available.
> > >
> > > The initrd and vmlinuz are stored in the initvm in /var/cache/elbe/installer.
> > > Also put them on bin-cdrom.iso, and reuse them, when an elbe build
> > > is run from cdrom.
> > >
> > > With this code in Place, we can remove the fallback
> > > Code in pkgutils. We also will never see initvm build
> > > failures due to new debian Releases requiring new
> > > installer/elbe-bootstrap versions.
>
> [...]
> >
> > > try:
> > > - copy_kinitrd(xml.node("/initvm"), out_path, defs, arch="amd64")
> > > + copy_kinitrd(xml.node("/initvm"), out_path)
> >
> > shouldn't we keep arch? I still dream about an arm64 initvm :/
>
> it was hardcoded to arch="amd64", i have just removed a codepath,
> that never gets called.
>
> we can add that later, if we have a usecase.
> for arm64 it looks like just replaceing amd64 with arm64 is ok.
>
> see:
> http://ftp.de.debian.org/debian/dists/jessie/main/installer-arm64/current/images/netboot/debian-installer/
>
> but for armhf its already different...
>
> http://ftp.de.debian.org/debian/dists/jessie/main/installer-armhf/current/images/netboot/
>
> so without adding a map from arch to URLs this seems rather useless.
> and that starts to go out of scope of this queue here.
i think an arm64 initvm would be a real use-case. armhf not.
If it's not 'easy' to handle, just go on with the removal of the codepath.
More information about the elbe-devel
mailing list