Todd Lyons writes:
: There's no need to put a warning in every rpm postinstall script about
: all the possible gotchas. That's what man pages are for. Your job as
: an experienced sysadmin is to read the documentation before you start
: configuring stuff, then configure everything before you start testing.
: Admittedly, that is something that is VERY hard for all of us to do. We
: all get burned by it quite frequently. IOW, we can't blame our own lack
: of discipline on the rpm package. That's like blaming gun deaths on the
: gun instead of the guy holding it. (Guess how I feel about gun control)
I am not a sysadmin, experienced or otherwise. I happen to have a Linux
box at my former office---I've retired so its no longer my office,
but I have permission to keep the machine there---that has a highspeed
connection to the Internet. And I maintain some mailing lists there
for some of the local Buddhist organizations, and one related to my
interests in free speech and computer programming.
I don't even know any sysadmins.
So your comments are hardly pertinent to my predicament. Especially since
I could find no documentation that covered the point. In fact, it was the
lack of documentation that I was commenting on.
--
Peter D. Junger--Case Western Reserve University Law School--Cleveland, OH
EMAIL: junger@samsara.law.cwru.edu URL: http://samsara.law.cwru.edu
NOTE: junger@pdj2-ra.f-remote.cwru.edu no longer exists
Follow-Ups:
References:
|
|
