In a message dated: Wed, 31 Jan 2001 19:53:36 EST
Benjamin Scott said:
>On Wed, 31 Jan 2001, Kenneth E. Lussier wrote:
>> This only addresses the "workstaion install". Does this mean that if you
>> do a server install, or a custom install, then the services will still be
>> on?
>
> Dunno, I don't work for Red Hat. But that does seem a reasonable conclusion
>to draw from the words provided. Perhaps they figure if one is doing a server
>installation, one will want services enabled (otherwise, what's the point?),
>and that one is also smart enough to keep the box secure. Sadly, that is
>often a false assumption, and not one I agree with, but I could see where that
>reasoning would come from.
The problem I have with the "server" charaterization is that it's little
different from the "workstation" mentality.
Let me clarify (Completely disregarding the fact that you can
"pick individual packages"). When you perform a "workstation"
installation, usually you install "everything". "Everything"
meaning everything a workstation could ever need without being
a server. This isn't bad, regardless of the fact that
it probably installs a bunch of crap no one will ever likely use.
The "server" install seems to be the "workstation" everything plus the stuff
that's needed to be a server. Unlike a workstation though, servers usually
have a very specific purpose; mail, web, file/print, etc. However, they don't
ask what kind of server you want to install, do they (I can't actually
remember if I've ever chosen that option)? So, they just install everything,
plus all server packages.
It seems to me that the logic flow should be something like:
- Workstation
- Server
- Mail
- News
- WWW
- File
- Print
- DNS
- NIS
- etc.
Then allow you to choose which type of server you want to install. You might
want to create a very specified server that just does mail, or maybe choose a
combination of services like Mail, News, and Print all on one system.
For some reason I don't think they go that far, it's either Workstation,
in which case you choose between Custom Install or Default to everything;
or Server, in which case you choose between Custom or Default.
Granted, the Custom allows you the choices, but you kind of have to know what
you're doing first. The poor newbie setting up a serer for his company may
have little idea what NIS is, or care. All he wants is a Samba server for his
Windows users. He's likely going to choose Default, in which case, he gets
everything. I don't think this is good. Rather than only a choice between
custom and default, they should provide some "Default Types" to choose
between. That way this poor guy can set up a Samba server and not have named,
innd, and sendmail running needlessly. Or, set up a mail server, but not be
running smbd/nmbd and nfsd!
Oh well, that's my $.02 :)
--
Seeya,
Paul
----
It may look like I'm just sitting here doing nothing,
but I'm really actively waiting for all my problems to go away.
If you're not having fun, you're not doing it right!
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
