On Fri, Jan 15, 2016 at 09:37:31AM +0200, Alkis Georgopoulos wrote: > The "manual" stanza isn't there just for network-manager. LTSP chroots don't > have network-manager installed by default. > A netbooted system needs these 2 things from ifupdown: > 1) the scripts at /etc/network/if-up.d to get executed for the boot > interface, > 2) while preventing the boot interface from being DOWNed at shutdown. > > You mention that using "manual" is the wrong approach to accomplish this. > Could you please advise us on how to notify ifupdown to do those 2 things in > a backwards/forward compatible way?
Which scripts in /etc/network/if-up.d are required for the system to
work?
If the network has been brought up by other means before mounting the
root filesystem, I don't see why ifupdown needs to be used at all. If it
does need to be used, can you explain in more detail what is happening
during the boot of an LTSP client?
The best way to prevent the boot interface from being downed at shutdown
is not to have it managed by ifupdown in the first place. Ifupdown will
only touch interfaces that are defined in /etc/network/interfaces.
--
Met vriendelijke groet / with kind regards,
Guus Sliepen <g...@debian.org>
signature.asc
Description: Digital signature
