home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.sys.sun.admin:8202 comp.sys.hp:12847
- Path: sparky!uunet!auspex-gw!guy
- From: guy@Auspex.COM (Guy Harris)
- Newsgroups: comp.sys.sun.admin,comp.sys.hp
- Subject: Re: Mounting /usr/spool/mail from HP?
- Message-ID: <15466@auspex-gw.auspex.com>
- Date: 12 Nov 92 19:56:50 GMT
- References: <1992Nov11.221801.2738@elroy.jpl.nasa.gov> <TML.92Nov12030940@hemuli.tik.vtt.fi> <1992Nov12.160404.12312@elroy.jpl.nasa.gov>
- Sender: news@auspex-gw.auspex.com
- Followup-To: comp.sys.sun.admin
- Organization: Auspex Systems, Santa Clara
- Lines: 14
- Nntp-Posting-Host: auspex.auspex.com
-
- >Now let me tell you what happens when you extract from a Tar archive
- >containing directories you do not own, onto a non-Sun file system.
- >Sun's `tar' proceeds to chown the parent directories before putting
- >anything into them (figuring that this will fail if not root).
- >Surprise, it cannot write the files into the directory...
-
- "Sun's `tar'" is 4.3BSD's "tar", with some additional flags added and
- some miscellaneous cleanup. The notion that a user should be allowed to
- give files away is an S3/SV-ism; you can probably *ask* for that
- behavior in Solaris 2.x, but I think SVR4 also allows you to configure
- the system *not* to allow it, e.g. if you're using disk quotas.
-
- Yes, differing file system semantics can be annoying, but be *very*
- careful before assigning blame; Sun isn't always the outlier here....
-