First allow me to explain something. When you cd into the mount point where the CD or DVD is mounted, you will not be able to make changes there. This is because commands like mkdir, cp, rm mv, etc uses the file system as an interface for making changes to the underlying disk, and the file system is mounted as read-only
In contrast with this, the GUIs uses CD-writing APIs for making changes to the disk. In particular when you drag-and-drop to create files there, you will find that the files are in fact written somewhere else in a temporary location. Later once you have all the changes you want to make "ready", you tell the CD-writing application to compile a CD, combining what is on the disk now with what you want to change, and then writing those changes, together with a new Table-of-contents, to the media. The important thing here is to realize that metacity or whatever tool you use, do not directly write to the disk. You can do this from the command line, but it is not a one-step process. You will stell need to "prepare" a temporary space with the files, make an image file (ISO file) and then write (or merge) this to the CD or DVD media. The GUI tools automate the process of programming the options on cdrecord / cdrw / growisofs / mkisofs / etc. In any case, as far as doing this on the command line: cdrecord: 131 options (including sub-options) documented in man page. cdrw: 18 options documented. And you realy only need to use one: cdrw -i image.iso However, creating the iso image can be non-trivial. In particular if you want to deal with long file names and cater for your resulting disk being usable on various OSes, and have strange characters in the file names.... Though if you want to just dump a few files: mkisofs -o image.iso /path/to_files Followed by: cdrw -i image.iso _Johan On Wed, Jun 25, 2008 at 2:28 PM, Joerg Schilling < Joerg.Schilling at fokus.fraunhofer.de> wrote: > Danek Duvall <danek.duvall at sun.com> wrote: > > > - burn that image with cdrw (Solaris specific, but very easy to use) > or > > cdrecord (common on many unix platforms, but has a stunningly > > complicated set of commandline options, most of which you can > > probably ignore) > > Well my experineces say that cdrw is the command with a complex interface > while > cdrecord is easy to use ;-) > > If you did not yet use cdrecord, you should try it and see that it would be > hard to make cdrecord easier to use than it is now. The advantage of > cdrecord > is that it supports more features and that it writes human readable error > messages while cdrw does not say more than just "it did not work". > > > > J?rg > > -- > EMail:joerg at schily.isdn.cs.tu-berlin.de<EMail%3Ajoerg at > schily.isdn.cs.tu-berlin.de>(home) J?rg Schilling D-13353 Berlin > js at cs.tu-berlin.de (uni) > schilling at fokus.fraunhofer.de (work) Blog: > http://schily.blogspot.com/ > URL: http://cdrecord.berlios.de/old/private/ > ftp://ftp.berlios.de/pub/schily > _______________________________________________ > laptop-discuss mailing list > laptop-discuss at opensolaris.org > -- Any sufficiently advanced technology is indistinguishable from magic. Arthur C. Clarke Afrikaanse Stap Website: http://www.bloukous.co.za My blog: http://initialprogramload.blogspot.com ICQ = 193944626 YahooIM = johan_hartzenberg GoogleTalk = jhartzen at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/laptop-discuss/attachments/20080625/268f5237/attachment.html>
