Jonathan Marsden writes:
>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.
Good! :-)
>Paul G., do you know why RedHat chose not to include any info
>on adding Linuxconf modules in the install guide?
Please read the list archives; I answered this question yesterday
several hours before you asked. :-)
>could this be added to the
>online version of the Guide, and so included in any 'second edition'
>reprintings of the paper version??
No.
>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... :-)
Maybe because it was intentionally not a target of our QA team?
If you had read my earlier email, you would have discovered the
reasons. They are valid, and the only promise I can make you about
an update to fix this is that if we release an updated linuxconf, it
will not be to fix this bug in a module which we do not support.
It might or might not get fixed collaterally if we release a fix for
other bugs.
The linuxconf core appears to be stable on 5.2. That was all we
could do; we had enough to do to make that be the case without
getting to the modules. As we are able to certify modules as
working, they will normally be installed by default. We already
do that for treemenu in Red Hat Linux 5.2.
michaelkjohnson
"Magazines all too frequently lead to books and should be regarded by the
prudent as the heavy petting of literature." -- Fran Lebowitz
Linux Application Development http://www.redhat.com/~johnsonm/lad/
---
You are currently subscribed to linuxconf as: [[email protected]]
To unsubscribe, forward this message to [EMAIL PROTECTED]