Thanks for your response.
On Sun, 26 Mar 2017 18:31:45 +0200 Philipp Kern wrote:
> IOW: Is there a way to guarantee that
> (dist)/main/installer-amd64/current/images/netboot/netboot.tar.gz does not
> contain a kernel that has no modules package IN THAT SAME mirror?
>
> Or maybe even an automate
On Tue, Mar 14, 2017 at 08:39:31PM +, Ben Hutchings wrote:
> On Tue, 2017-03-14 at 11:36 -0700, Nye Liu wrote:
> > The only apparent solution is to have the kernel maintainers coordinate
> > with the d-i maintainers so that whatever kernel is used in d-i is NOT
> > rem
The only apparent solution is to have the kernel maintainers coordinate
with the d-i maintainers so that whatever kernel is used in d-i is NOT
removed from the package repository and its mirrors.
With DCHP ENABLED:
I have tried:
Null string:
d-i netcfg/hostname string
d-i netcfg/get_hostname string
Seen false:
d-i netcfg/hostname seen false
d-i netcfg/get_hostname seen false
The only workaround seems to be to remove priority=critical from the kernel
command line (annoying, since there
This really should be marked grave or serious because it means net
install is completely broken.
HP ProLiant DL390 Gen 9, redscreen with
testing/main/installer-amd64/20150813/images/netboot:
debian-installer/amd64/pxelinux.0
If I replace ONLY pxelinux.0 with
stable/main/installer-amd64/20150422+deb8u1/images/netboot:
debian-installer/amd64/pxelinux.0
(but use all of the rest of testing)
It
6 matches
Mail list logo
