9438 |
@c Ian said: ``I don't think -p or -r are portable''!!! How can you live |
@c Ian said: ``I don't think -p or -r are portable''!!! How can you live |
9439 |
@c without -r??? |
@c without -r??? |
9440 |
|
|
9441 |
|
Bob Proulx notes that @samp{cp -p} always @emph{tries} to copy |
9442 |
|
ownerships. But whether it actually does copy ownerships or not is a |
9443 |
|
system dependent policy decision implemented by the kernel. If the |
9444 |
|
kernel allows it then it happens. If the kernel does not allow it then |
9445 |
|
it does not happen. It is not something @command{cp} itself has control |
9446 |
|
over. |
9447 |
|
|
9448 |
|
In SysV any user can chown files to any other user, and also had a |
9449 |
|
non-sticky @file{/tmp}. That undoubtedly derives from the heritage of |
9450 |
|
SysV in a business environment without hostile users. BSD changed this |
9451 |
|
to be a more secure model where only root can @command{chown} files, and |
9452 |
|
used a sticky @file{/tmp}. That undoubtedly derives from the heritage |
9453 |
|
of BSD in a campus environment. |
9454 |
|
|
9455 |
|
Linux by default follows BSD, but it can be configured to allow |
9456 |
|
@command{chown}. HP-UX as an alternate example follows SysV, but it can |
9457 |
|
be configured to use the modern security model and disallow |
9458 |
|
@command{chown}. Since it is an administrator configurable parameter |
9459 |
|
you can't use the name of the kernel as an indicator of the behavior. |
9460 |
|
|
9461 |
|
|
9462 |
|
|
9463 |
@item @command{date} |
@item @command{date} |
9464 |
@c ----------------- |
@c ----------------- |