Carl Lowenstein wrote:
On Dec 29, 2007 1:09 AM, Ralph Shumaker <[EMAIL PROTECTED]> wrote:
[snip]
Any hints on whether I need to be $ or #? (I'd really prefer not to
make any coasters.) The man page talks about avoiding sudo, but doesn't
specify further, at least not that I could tell.
It depends on details of your system setup. In my system, the cd
writer is owned by group "disk"
and I am a member of group "disk". So it works without having to be root.
[EMAIL PROTECTED] ~]$ ls -l /dev/hdc
brw------- 1 cdl disk 22, 0 Dec 5 15:22 /dev/hdc
I think that if you don't have the privilege to use the cd writer, you
will get an error message and nothing else will happen. So you won't
make a coaster.
And does the command, as stated by you, automatically take care of
making it bootable? Is that something that is already built into the
ISO that I downloaded or must it be specified? The man page mentions
options for Rock-Ridge and Joliet, which IIRC are boot conventions.
The part of the man page that is relevant here is:
- - - - - - - -
To use growisofs to write a pre-mastered ISO-image to a DVD:
growisofs -dvd-compat -Z /dev/dvd=image.iso
where image.iso represents an arbitrary object in the filesystem, such
as file, named pipe or device entry. Nothing is growing here and com-
mand name is not intuitive in this context.
- - - - - - - -
As it says, "the command name is not intuitive in this context". And
the exact command usage is not intuitive either. But it works.
Again, the key word to notice is "pre-mastered".
The token name "/dev/dvd" in the command above may need to be replaced
by something else. In my system, the physical connection to the
CD/DVD writer is /dev/hdc. But there are several symbolic links.
cdrom -> hdc
cdwriter -> hdc
dvd -> hdc
dvdwriter -> hdc
So you can call it by any of those four names, and still get the same result.
carl
Thanks for mentioning that, Carl. I wasn't seeing anything when doing:
$ ll /dev | grep hdc
$ ll /dev | grep hda
$ ll /dev | grep hdb
So then I tried:
$ ll /dev
and was surprised that the listing was so much shorter than I remember
it having been in the past. From this listing I got some clues, and
basically ended up getting a summary listing by:
$ ll /dev | grep disk
which was still long, and:
$ ll /dev | grep rafael
which was shorter, but still long, and finally:
$ ll /dev | grep sr[0-9]
lrwxrwxrwx 1 root root 3 2007-12-25 15:19 cdrom -> sr0
lrwxrwxrwx 1 root root 3 2007-12-25 15:19 cdrom1 -> sr1
lrwxrwxrwx 1 root root 3 2007-12-25 15:19 cdrw1 -> sr1
lrwxrwxrwx 1 root root 3 2007-12-25 15:19 dvd1 -> sr1
lrwxrwxrwx 1 root root 3 2007-12-25 15:19 scd0 -> sr0
lrwxrwxrwx 1 root root 3 2007-12-25 15:19 scd1 -> sr1
brw-rw----+ 1 rafael disk 11, 0 2007-12-25 15:19 sr0
brw-rw----+ 1 rafael disk 11, 1 2007-12-25 15:19 sr1
Does it make a difference if the link's owner and group are root? More
to the point, would /dev/dvd1 work differently than /dev/sr1 since
ownership and group are different between the two? Or does the link
inherit the ownership and group of what they are linked to?
You did not show a long listing of your 4 links that all point to your
/dev/hdc, but if I understand correctly, your links probably all say
their owner and group is root also. Therefor, I should be able to use
any of:
/dev/sr1
/dev/cdrom1
/dev/cdrw1
/dev/dvd1
/dev/scd1
Thanks again, Carl.
--
Ralph
--------------------
How do you test an uncooperative intelligence when it's smarter than you?
--Stewart Stremler
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
