On 4/14/19 9:14 PM, Eero Tamminen wrote: > On 4/12/19 12:34 PM, John Paul Adrian Glaubitz wrote: >> I just uploaded updated installation images 2019-04-12 for the >> following Debian Ports architectures: > > Is there any other change than > - choose-mirror 2.98 all > - choose-mirror-bin 2.98 m68k > + choose-mirror 2.99 all > + choose-mirror-bin 2.99 m68k > > for nativehd/initrd.gz?
I cannot really answer that as that would mean having to parse the changelogs for all packages found on the installation CDs which is not feasible. Debian installation media is assembled from existing packages from the FTP mirrors and these packages are maintained by individual maintainers within Debian and get regularly updated, albeit less frequent during feature freeze which is the case for now. What I did is updating debian-cd - the CD building software - to the latest version in git and pulling the latest debian-installer images from the FTP archives instead of building them manually as there was just a new release of debian-installer. >> Please test those images and report back over the mailing list for >> the corresponding architecture. > > Any comment on things I asked with previous m68k debian-installer: > > * adding System.map along with kernel > (to help debugging installer issues) System.map is part of the normal linux-image Debian package: root@elgar:~> dpkg -L linux-image-4.2.0-1-m68k |grep System.map /boot/System.map-4.2.0-1-m68k root@elgar:~> Since it's usually not required for installation, it's not shipped on the installation media. It will get automatically installed by debian-installer though. Installation media is not really intended for debugging kernel or emulator bugs, so I'm not sure the other maintainers of the debian- installer project would accept such a change. > * s/CONFIG_CRYPTO_DH=y/CONFIG_CRYPTO_DH=m/ > (to speed up boot when one doesn't use inicall_blacklist=dh_init) This change would have to be made to the linux-image package thus filing a bug report to src:linux with that request is necessary. But again, if you're solely interested in these changes for debugging kernel or emulator bugs, it doesn't make much sense to implement these changes. I'm not generally opposed to changing this option from "built-in" to "module" but we would have to make sure this change doesn't break anything else. I haven't checked what CONFIG_CRYPTO_DH is used for. Please note that you can just create a chroot for m68k using debootstrap without the need for using debian-installer. debootstrap has the parameters "--foreign --arch=$ARCH" for that matter. Thanks, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
