home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!cs.utexas.edu!asuvax!asuacad!aubxg
- Organization: Arizona State University
- Date: Saturday, 2 Jan 1993 13:24:20 MST
- From: Ben Goren <AUBXG@ASUACAD.BITNET>
- Message-ID: <93002.132420AUBXG@ASUACAD.BITNET>
- Newsgroups: comp.unix.aux
- Subject: Re: shlib in /usr/spool/ftp
- References: <92364.145827AUBXG@ASUACAD.BITNET> <1342@jagubox.gsfc.nasa.gov>
- <1993Jan1.173450.7264@panix.com>
- Lines: 23
-
- (Again apologies for the primitive newsreader. I think this is enough
- incentive for me to make sure that my next A/UX project will be rn or
- something like that.)
-
- Regarding disagreement with my gripe about Apple not talking about
- /shlib:
-
- I don't expect Apple to go to such lengths in general, but I think it
- was warrented in this case. *Every* other file and directory in /usr/\
- spool/ftp was described, in most cases even giving the mode and owner/
- group information. ~/ftp/bin/ls was described as being necesary for
- ftp to function correctly; why couldn't they also mention that ~/shlib
- is necessary for the whole machine to fuction? With the care with which
- they described the potential security problems, I'd expect them to at
- least mention this potentially deadly one.
-
- Ah, well. Live and learn. At least I've got a (more) sensible partitioning
- scheme now.
-
- Trust all had a happy and safe New Year's, and that all headaches
- are beginning to subside....
-
- b&
-