Network Manager dependencies
Jordon Bedwell
jordon at envygeeks.com
Thu Aug 23 00:40:58 UTC 2012
On Wed, Aug 22, 2012 at 7:27 PM, Dale Amon <amon at vnl.com> wrote:
> I usually de-install it on servers. A server has the interfaces
> and static IP addresses I tell it has and it should never, ever
> even consider overriding those settings.
>
> NM is okay (usually) for portable luser devices, but not for
> the rack.
I think I would be a little bit upset if Ubuntu started defaulting to
NM on servers. It brings nothing better or new to the table and as
everybody already mentioned it's focus is primarily mobile users. I
have it on my laptop, wouldn't live without it, but on my desktop I
remove it and use ifupdown because removing NM allows me to remove
dependencies I'll never need or use and ones that I wouldn't file a
ticket over because so many other users need it.
I guess this whole NM issue might fall under the tasksel issue, I
prefer not to use it but a friend of mine does...you prefer NM I
prefer to stay away from it, preference perhaps? But with preference
comes the problem that NM relies on wpasupplicant and a couple of
other wireless tools that we would absolutely never need on a server,
unless we are crazy or there is some one-off sysadmin who has some
crazy ideas.
More information about the Ubuntu-devel-discuss
mailing list