On Tue, 10 Nov 1998, Jonathan Marsden wrote:
> On 10 Nov 1998, Jacques Gelinas writes:
>
> > On Sat, 7 Nov 1998, Jonathan Marsden wrote:
>
> >> I recommend upgrading to 1.13r4. This seems to cure the problem for
> >> me. Apparently (?) the DIST is not being substituted for redhat, so
> >> the file is not being seen?
>
> > This is a generic error message. this is why the DIST is not replaced.
>
> It would be nice if it *were* replaced, perhaps at run time??
> Otherwise it is quite confusing for novice users, and even for some
> more experienced users. Especially as there is no file called
> /usr/lib/linuxconf/redhat/conf.daemons... the 'conf' also needs
> substituting for the actual filename, maybe?
I will change the error message completly. Originally, there was a single
file called conf.daemons. Now, each module may contribute one file. So the
message should read something like
can't find information about a command in one of the *.daemons
file in /usr/lib/linuxconf/redhat
Or something readable in that sens :-)
> > The bug above is a packaging problem from the redhat rpm. They forgot two
> > files
> >
> > /usr/lib/linuxconf/redhat/mailconf.daemons
> >
> > sendmail /usr/sbin/sendmail -bd
> > smrsh /usr/sbin/smrsh
> > makemap /usr/bin/makemap
> >
> > /usr/lib/linuxconf/redhat/dialout.daemons
> >
> > chat /usr/sbin/chat
> > pppd /usr/sbin/pppd
> > diald /usr/sbin/diald
>
> Great! I'll add this to my FAQ. Michael K.: if this is a genuine
> RedHat 5.2 packaging bug, and not a direct Linuxconf problem, can we
> consider it officially reported, and so expect an updated linuxconf
> package to appear on updates.redhat.com soon <grin>?
yes this is a packaging problem. But Michael's statement about modules is
more or less this (as seen on this mailing list)
-redhat has tested and validated some parts of linuxconf. Not all
-to please the early linuxconf adopters, redhat delivers the
modules as is.
So if redhat do an update for linuxconf (they probably will for other
reasons such as the netmask feature of the IP aliases), the fix will be
included (I guess).
> If there is a similar problem making dialout connections we/RedHat/the
> Linux community will probably get plenty of questions about it,
> because RH 5.2 does recommend using Linuxconf for that purpose... or
> does the dialout.daemons file only matter if you load the dialout
> module??
Right, the dialout.daemons is only useful to the dialout module. Linuxconf
on redhat provides a PPP/SLIP/PLIP configuration facility compatible with
netcfg (built in the linuxconf redhat module).
So the dialout modules is offered for the following reasons
-compatibility for those who were using it before redhat 5.1
-for those who wants diald supports
-and few extra features (routing, ssh tunelling, ipx
configuration,...)
which is the idea about modules. For one, it allows competing solution to
coexist in linuxconf.
---------------------------------------------------------
Jacques Gelinas <[EMAIL PROTECTED]>
Check out Linuxconf at http://www.solucorp.qc.ca/linuxconf
New modules: mgettyconf, managerpm
---
You are currently subscribed to linuxconf as: [[email protected]]
To unsubscribe, forward this message to [EMAIL PROTECTED]
