Quoting cout at eircom.net (cout at eircom.net):
[Debian network-daemon packages tend to be built to auto-start
if installed.]
> Of course the difficulty I have with this, is that sometimes I might
> like to install things that I may (or may not) use later, which is ok
> for some 'useful' cli utils, but for me is a real waste of space for
> gui stuff which ends up taking up lots and lots of space on my
> harddisk... sort of like Gnome and KDE.
Yes, I consider it a minor flaw. You just get into the habit of
checking your sysvinit scripts and processes after installing or
upgrading network daemons.
> I don't really remember the install process, except that working
> through all of the dependancies from the 3 disks I was attempting to
> install was a real nightmare, even OpenBSD 3.0 didn't seem quite as
> bad for this dependancy issue, but I might just be trolling.
Reiterating the earlier point: You can avoid the nightmare entirely by
curing yourself of the bad RedHat-type habit of installing the kitchen
sink. It's the classic Debian-newcomer's mistake.
> I got a little tired of Debian which had no obvious way of telling
> it to get an ip via dhcp...
You can have your choice of either dhcp-client or pump. Either one
works in the usual way.
--
Cheers, "Why is the alphabet in that order? Is it because of that song?"
Rick Moen -- Steven Wright
rick at linuxmafia.com
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!