netenv doesn't come up initializing via systemd

Elimar Riesebieter riesebie at lxtec.de
Sun Jun 1 09:19:52 BST 2014


* Michael Biebl <biebl at debian.org> [2014-05-31 15:46 +0200]:

> Am 31.05.2014 15:09, schrieb Michael Biebl:
> > That leaves netdev.
> > Tbh I don't know what to do about that. The password agents [2] were
> > designed to prompt for passphrases, not to select from a list from
> > pre-defined values. So they are not applicable to the case.
> > 
> > 
> > While you can change a service file's StandardInput= setting so it
> > actually get's access to the console during boot, a "systemctl start
> > netdev.service" in you terminal emulator does not work with that either
> > afair. But for this case you could simply provide a command-line tool
> > like netenv-select or so
> > 
> > As a closing remark, let me add that it is generally discouraged to
> > prompt for input during boot.
> 
> netenv let's you choose a network configuration via an interactiva
> dialog during boot.

This is the default

> It also supports a mode though where you specify the network profile via
> a kernel command line argument.
> I would make that the only supported modus operandi under systemd.

Well this works. But I have always have to edit the "linux" line in the
grubmenu by appending "NETENV=blo". I can define different kernel
args via /etc/grub.d/40_custom. But those AFAIK are not updated by
un/installing new kernels. There is no way to influence
GRUB_CMDLINE_LINUX for each Kernel via /etc/default/grub, though.

Elimar
-- 
  Alles was viel bedacht wird ist bedenklich!;-)
         Friedrich Nietzsche



More information about the Pkg-systemd-maintainers mailing list