Ralph Shumaker wrote:
> I just discovered a gotcha (*before* it got me).
>
> I just noticed the ownership of the files in my backups. Everything in
> my backups are owned by root and belong to group root. That's not
> *completely* surprising since I always did my backups while logged in as
> root (to avoid permission issues). What I never realized until now is
> that ownerships are not being protected.
The problem is that the ISO-9660 spec does not allow for owner/user
groups. It is in the Rock Ridge extensions.
>From the mkisofs man page:
-R Generate SUSP and RR records using the Rock Ridge protocol to
further describe the files on the iso9660 filesystem.
-r This is like the -R option, but file ownership and modes are set to
more useful values. The uid and gid are set to zero, because
they are usually only useful on the author's system, and not
useful to the client. All the file read bits are set true, so
that files and directories are globally readable on the client. If
any execute bit is set for a file, set all of the execute bits, so
that executables are globally executable on the client. If any
search bit is set for a directory, set all of the search bits, so
that directories are globally searchable on the client. All write
bits are cleared, because the CD-Rom will be mounted read-only in
any case. If any of the special mode bits are set, clear them,
because file locks are not useful on a read-only file system, and
set-id bits are not desirable for uid 0 or gid 0. When used on
Win32, the exe- cute bit is set on all files. This is a result of
the lack of file permissions on Win32 and the Cygwin POSIX emulation
layer. See also -uid -gid, -dir-mode, -file-mode and -new-dir-mode.
Besides the ownership, you may also want to verify that the permssion
bts are as you expect them to be. It may be easier to ensure that your
iso generation procedure is using the -R option vice -r. I could not
tell you how to do that.
-john
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-newbie
