[linuxconf] Re: First impression of LinuxConf

[aurelio marinho jargas - ctba]

hi!

> Yes, all messages from *linuxconf* (and the tools which it runs) are
> stored in these logs but not the boot-messages of the linux kernel
> (harddisks found, status of fsck, SCSI bus, etc). Isn't it possible that
> linuxconf just skips the "clear screen" ?

yeah, on the boot log do you see the same as you see on the
dmesg comand. (/var/log/dmesg)
HDs & SCSI are stored on that...

i tried here a `dmesg -n 8` but nothing has changed... &:(

> Doesn't this disable linuxconf completely ? Also, I think this wouldn't
> help: what I'm refering to is the message "There were some errors"
> which you get right before you can login.

no it's just the askrunlevel module.
if you disable it, your machine gets back to "normal" boot,
but Linuxconf is still there, called normally.
this module just "takes control" of the boot process and let
you do some changes/fixes before logging.

just disable it to take out this behaviour.

> Can you please add a list of all extra modules on the WWW page (including
> info where they can be found, please :-)

well, there is a link for it on the Linuxconf homepage:
http://www.solucorp.qc.ca/linuxconf/modules.html
maybe it's not totally updated, but it's a start.

well, one thing you can try is to execute this comand:
ls /usr/lib/linuxconf/modules
&:)

then you'll see all the modules that are a part of the
linuxconf package

ah! managerpm is a separated module that have it's own rpm.
you can get it on:
ftp://ftp.solucorp.qc.ca/pub/linuxconf/modules/


[]s - s/&:(/&:)/g
aurelio


---
You are currently subscribed to linuxconf as: [archive@jab.org]
To unsubscribe, forward this message to [EMAIL PROTECTED]