[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#925084: marked as done (di-netboot-assistant: debian-installer-xxx-netboot-yyy are wrongly configured)

Your message dated Sun, 31 Mar 2019 09:51:57 +0300
with message-id <20190331065156.GA19818@fuzi>
and subject line Re: Bug#925084: di-netboot-assistant: debian-installer-xxx-netboot-yyy are wrongly configured
has caused the Debian Bug report #925084,
regarding di-netboot-assistant: debian-installer-xxx-netboot-yyy are wrongly configured
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
925084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925084
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: di-netboot-assistant
Version: 0.60~bpo9+1
Severity: normal
Tags: d-i

Dear Maintainer,


I've just discovered and then set-up di-netboot-assistant to manage several
debian netboot versions.
It works great when it manages setup di-netboot-assistant installed by itself,
but it fails to configure correctly already installed installers from official
packages.
I get a "No DEFAULT or UI configuration directive found!" when the PXE client
boots on one of these installer.

(Other system information are not relevant as I'm not writing from the PXE boot
server)

Best regards,
Jérémy VIES



-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-3-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages di-netboot-assistant depends on:
ii  curl  7.64.0-1
ii  wget  1.20.1-1

Versions of packages di-netboot-assistant recommends:
ii  grub-efi-amd64-bin            2.02+dfsg1-12
pn  tftpd-hpa | atftpd | dnsmasq  <none>

Versions of packages di-netboot-assistant suggests:
pn  dnsmasq | isc-dhcp-server | udhcpd  <none>
pn  syslinux                            <none>
pn  vim-addon-manager                   <none>

--- End Message ---
--- Begin Message --- 
Hi Jérémy,

thanks for reporting back!

On Sat, Mar 30, 2019 at 09:34:37PM +0100, Jérémy Viès wrote:
> 
> sorry for the delay, your emails went to my spam folder.
 
No problem.

> I thought I was more smart than the doc... I didn't mount/bind the installer
> folder, instead I linked it to the correct place.
> I've just tried mounting the folder, and all is OK !

That's good to hear, of course! Accordingly, I am closing this bug.

> so sorry again for the disturbing !

No problem again, I am happy to see di-netboot-assistant working in
the wild.  ;-)

> by curiosity, why does it work using mount/bind and not with a simple symbolic
> link ?

The reason is that symlinks allow nasty things, concerning security.
Depending on the TFTP-server you use, it might run in a chroot jail,
where only the file system below the TFTP-root is accessible and/or
apply other restrictions.
By using appropriate options for the server, you can probably make it
work with symlinks too, but I wouldn't recommend that.

If you search the www for 'TFTP symlink' you'll find a lot of hits
and more thorough explanations.

Best regards,

  Andi

--- End Message ---
Reply to: