On 8 Nov 1998, Dino Nardini writes:
> (1) Red Hat's Linux package seems to be getting more
> install-friendly with every version. The latest 5.2 detected all of
> my hardware (except Logitech mouse, which I chose from a displayed
> menu). The "Disk Druid" feature is a step in the right direction but
> still requires some movement towards "user-friendly" for the average
> non-techie installer. Being a creature of habit, I used fdisk.
Grin! If you just pick the 'Server' install the thing consumes your
entire HD in a fairly reasonable way, no need for user education about
partitioning at all. Definitely a step in the right direction.
> The installation guide is getting better (and thicker). And I like
> the new section on Linuxconf, although there is still no reference
> to the modules (an oversight?). I found the neccessary module
> information in "Jonathan's FAQ". Is there some reason why this
> module information is so hard to locate?
I don't think so.
It's really time we (a) made the module names be a pick list in
Linuxconf and (b) documented the available modules and how to add them
better. Paul G., do you know why RedHat chose not to include any info
on adding Linuxconf modules in the install guide? It seems a real
pity that the opportunity was missed... could this be added to the
online version of the Guide, and so included in any 'second edition'
reprintings of the paper version??
> (2) Linuxconf loaded just fine from the command prompt but it
> couldn't find a makemap reference in
> "/usr/lib/linuxconf/redhat/DIST/conf.daemons", which didn't
> exist. The closest I could find was
> "/usr/lib/linuxconf/redhat/linuxconf.daemons". After adding a
> reference to makemap the error (and core dumps) disappeared.
Right. This is a known problem my FAQ tries to document (maybe I need
to make it clearer?)... I'd like to see RH put out an updated
linuxconf RPM with this fixed ASAP. It would also be of interest to
find out how this problem got by their internal QA processes... :-)
> I immediately upgraded to Linuxconf 1.13 subrev 4 and added the
> dnsconf and mailconf modules. I had some problems rebuilding my dns
> server... linuxconf didn't appear to reboot named when I made dns
> changes. Doing a manual boot of named worked. I like the new tree
> interface, although found myself jumping back to the "classic text
> interface". :) Also, linuxconf wants to reboot httpd every time I
> exit... is there a reason for this?
I believe it is a buglet in dnsconf, but others know more about that
module than I do. Like you, I see linuxconf wanting to do
root@jmarsden /usr/local/home/jonathan#linuxconf --status
List of things required to activate current configuration
Executing: /etc/rc.d/rc3.d/S10network reload
every time, once I have a primary DNS domain defined in Linuxconf.
I'll try to take a look at the code, but I bet someone else will find
the problem and the fix before I do!
Jonathan
--
Jonathan Marsden | Internet: [EMAIL PROTECTED] | Making electronic
1849 N. Wabash Ave.| Phone: +1 (909) 794 1151 | communications work
Redlands, CA 92374 | FAX: +1 (909) 794 3016 | reliably for Christian
USA | http://www.xc.org/jonathan | missions worldwide
---
You are currently subscribed to linuxconf as: [[email protected]]
To unsubscribe, forward this message to [EMAIL PROTECTED]
