Hi Don, Don Wright writes:
> Olaf Meeuwissen wrote: > >>Installing a desktop, by default, pulls in wicd (or network-manager). >>You can prevent this by using apt-get's --no-install-recommend option. > > Not an option within the de??an installer - which was the context of the > original post. I understand your point. Yet, you stated in your original post >>> Installed ASCII using Expert (text) from devuan_ascii_2.0.0_amd64_dvd-1.iso. >>> I'm very familiar with the Debian Installer interface from years of using >>> it. Considering that, I think this is an option, even though it is not necessarily an easy one. After you've configured the mirror and proxy settings for APT, execute a shell, chroot into the installer's target directory, from memory that's /target, and run the command. >>Whether either package blatantly ignores your static IP configuration >>from when you installed, I cannot tell for sure (zapped wicd) but I >>vaguely remember that you can tell wicd to leave certain interfaces >>unmolested. That may even be its default behaviour for interfaces that >>are configured in /etc/network/interfaces. >> > [Steve Litt] >>>I would sure find this behavior surprising. >> >>If wicd breaks static IP address configurations out-of-the-box I'd be >>surprised too. I've mainly used it in DHCP settings. On my server's >>wicd was never installed so any static IP configurations just worked as >>intended. > > However surprising to any of you, this is my testimony. A statically > configured interface present in /etc/network/interfaces was ignored **as > installed by Devuan ASCII.iso**. Removing wicd fixed the problem. What other > conclusion can reasonably be drawn but that wicd is the one doing the > ignoring? My use of 'surprised' meant to imply that I consider it a bug (in the 'WTF' category). Understatement didn't make it through :-(( and in hindsight I should have been clearer. Sorry. >># Veteran Unix Administrator's are free to cobble together their own >># solution and `apt purge wicd` goes a long ways towards that end ;-P > > But that's only an option after the fault, which only shows up after > restarting. If the device is not within easy reach, how will you get a > command line at the random assigned IP address in the first place? Although I haven't found myself in that situation, I'd say one of: - not :-( - with a lot of effort - by using the hostname (assuming that your DHCP server's register their leases with your DNS servers) > Background: My situation, which you so deride, I did not mean to deride your situation. Apologies if my follow-up sounded that way. > is a test install of a server with changing products *and management > tools* which is where the desktop comes in. When a configuration is > finally settled upon, the server will be wiped and reinstalled in a > production configuration without desktop as all my other servers have > been, and the management tools installed on a management > workstation. Until then the churn will be limited to this one system. May I suggest you do your test install in a setup that more closely resembles your production configuration. That is, test installs for both the server and the management workstation. You could do either or both on a suitable VM that runs someplace you have physical access. Hope this helps, -- Olaf Meeuwissen, LPIC-2 FSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Software https://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join _______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
