🚀 go-pugleaf

In article <Bz882q.L2.2@cs.cmu.edu>, cline+@cs.cmu.edu (Kenneth Cline) writes:
|> A user logged into a Sun4 was unable to extract tarred files (created
|> by another user) to a disk mounted on our SGI machine.  Apparently,
|> SunOs tar chowns the new file to the old user before reading its
|> contents, and subsequent operations fail due to ownership conflict.
|> 
|> The fix was to build a new kernel for the SGI with restricted_chown
|> set to 1.  Now, "tar x..." works fine, but I would like to know if
|> this is a bug in SunOs tar (maybe, calling chown prematurely), an SGI
|> bug (which doesn't seem as likely), or simply conflicting features.
|> 
|> I ask, because it is annoying to ship tar archives to other sites and
|> require the recipient to be super-user to extract the files, but in
|> general that seems to be necessary.  (n.b. rebuilding the kernel is a
|> bit much to ask the recipient).  Is there another solution short of
|> running homogeneous networks?
|> 
|> Ken

I happened to encounter the problem once before, and the way I did to
go around it was to login to a SGI machine(obviously, this
SGI box has to have access to that SGI bound disk) to do the untar.
Normaly it works because the user who has the access to the SGI bound disk
should have access to some SGI machines that accesses the disk, and is
easier than rebuilding the kernel, not to mention you may not always have the
source. I would be very interested to know who should be blamed for 
the problem, though.

Tom
-- 
---------------------------------------------------------------------------
|-                                                                       -|
|-- tzheng@cs              Room: CS G016        O.Phone: (317)494-0813  --|
---------------------------------------------------------------------------