[nSLUG] Debian 3.1 (sarge) is released

bdavidso at supercity.ns.ca bdavidso at supercity.ns.ca
Wed Jun 8 20:44:35 ADT 2005


Hi:

On Wed, 8 Jun 2005, Ben Armstrong wrote:
[snip]
> So if Libranet really does force you to use its own GUI-based admin
> tools rather than...
> editing simple conf files and running simple command-line commands, then
> it certainly lowers my opinion of Libranet.

I have to agree here.  Nice graphical or curses-based, menu-driven admin 
tools that *supplement* traditional tools, or provide an optional 
front-end to traditional tools, are all very nice.  But sometimes you need 
to work with a system when those tools aren't available (say, on a 
non-mounted partition) or aren't working for some reason.  To suggest that 
one should not directly edit config files because it will break some admin 
tool says that said admin tool is already broken and probably shouldn't be 
used.

> file(s) should be modified instead.  In such cases, the conf file is
> clearly marked with comments at the top about this situation, e.g. at
> the top of /etc/modules.conf:
>
> ### This file is automatically generated by update-modules

Yes, and I am glad they at least put that warning there so anyone 
accustomed to administering any other ("normal") linux distro isn't 
completely sandbagged.  Now, of course, they have to read at least one 
extra man page (which might not be available, see above) and figure out 
what the heck is going on in /etc/modutils.  I guess there is some Debian 
developer who can explain why this non-standard way of doing things is a 
Good Thing, but as far as I am concerned it is a brain-dead annoyance.

However, the good news is that in an emergency one actually could edit 
/etc/modules.conf (or /etc/modprobe.conf in modern distributions) and it 
would work at least until update-modules was run again.

-- 
Bill Davidson
bdavidso at supercity.ns.ca


!DSPAM:42a782e4193629262120473!




More information about the nSLUG mailing list