Yeah!
I know that it's a pain, and probably considered outmoded and tacky these
days, but how about a "real expert" mode?
I find myself often building relatively simple single-purpose servers.
You know, dhcp, dns, proxy, NAT, that kind of stuff. I find that I'm
spending more time turning stuff off and recompiling kernels without
various fancy modules than I am doing installs. I know about tomsrtbt
etc. But I think that y'all are overlooking a big marketplace: experienced linux
network admins that need dirt simple, small servers, but like the convenience
of rpm management and consistent startup/network script placement. (It's
so much easier to explain to the new linux admins and techs around here.)
Also a good document that goes over ALL the possible statements in the
sysconfig and network-scripts files would be nice;) (Yup, IPX, too!) Nothing
too complicated, just a list of variable names and possible values.
(and you can stuff that buggy, overcomplicated linuxconf crap. I'm being
somewhat unfair, as it's been getting better over time, but dammit! well-
documented text files are simple to configure, and can be script-manipulated.
They are not to be treated as some kind of necessary evil.)
I've bought every version of RedHat since 4.2, and have never used any of the
provided premium support even though entitled to it, as it's just been easier
to go to this list and the mirrors for whatever I've needed. On the whole I've
been happy, so please pardon my rant.
ps. How about listing the actual mirrors in the "busy message"? It'd save those
of us using commandline ftp clients on terminal emulators plugged into serial
ports of infrastructure devices (nat-routers, application proxies, dns servers)
a lot of time. More important on updates than on initial installs. Easier, too,
as updates are fewer than installs.
Juha Saarinen wrote:
>
> >
> %-> > And that makes perfect sense. Nobody will ever need both an
> %-> SMP kernel and
> %-> > a UP kernel at the same time. Many people don't need the PCMCIA stuff
> %-> > (which, by the way, is not part of the standard kernel - if
> %-> you compile
> %-> > from source, it's a separate package as well).
>
> On the top of my wishlist for future RHL (and other Linux distros) would be
> a kernel configuration phase during installation/setup. The stock kernel is
> pretty bloated -- it comes with RAID, ISDN, SCSI and lots of different and
> esoteric modules.
>
> It would be nice to be able to pick'n'choose what hardware etc. support you
> want in your kernel during the install.
>
> -- Juha
>
> --
> To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
> as the Subject.
--
-------------------------------------
Sam Bayne - System Administrator
North Seattle Community College
[EMAIL PROTECTED] (206)527-3762
=====================================
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
