On Wed Sep 08 1999 at 00:13, Bill Nottingham wrote:
> Subject: Re: Lorax
> Tony Nugent ([EMAIL PROTECTED]) said:
> > Is there a CHANGELOG file? Or preferably two... one for "general"
> > features and improvements, and one for system administrators.
>
> Well, as to new 'general' features, those were pretty much covered
> in the announcement.
But not all together in the one file in the main distribution. Not
that I could see, anyway. [I haven't had a chance to look at the html
manual yet, hopefully in the next couple of days.]
> As to other random changed things...
>
> Some services don't run by default if installed anymore, such as
> bind, inn, samba, knfsd.
>
> jikes is included instead of guavac.
>
> There are packages for some clustering support.
>
> Lots of updated packages. New versions with new features
> and new fixes. :)
All well and good and way way cool, but what I'm saying (and what
others have also said) is that these changes features really need to
be properly and systematically documented in a file that accompanies
each distribution. Same for *every* distribution, including rawhide
etc.
Documentation - yes, I know... a right PITA and "time out when other
things also need to be done". But unfortunately it is badly needed.
RedHat distributions are being widely used for very serious purposes,
especially in corporate environments. And rightly so, it's a
brilliant distribution, and with the explosion of linux this trend is
only going to continue. You guys are on a winner.
[My "hobby interest" in linux and experience with redhat has now
made me a winner too... I now have a career for life and people with
this sort of experience are only going to become more and more
employable and valuable.]
But as was shown with the problem of the rh6.0 changes to the range of
system UID/GID that were being used, it is important for system
administrators to have some sort of "definitive reference" about these
things so they know what to expect when deploying new versions of
distributions on desktops and servers in corporate networked
environments.
One thing I've learned when working as a system/network administrator
in this sort of environment is that you don't suprise people with
"nifty" changes. And if suprises are there, then warn them about it
first, loudly.
Doesn't this make sense?
Cheers
Tony
(Not for much longer -->>
-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-
Tony Nugent <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
Computer Systems Officer Faculty of Science
University of Southern Queensland, Toowoomba Oueensland Australia
-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-
--
To unsubscribe:
mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
