DVD+RW support
Hi, I've just updated my http://fy.chalmers.se/~appro/linux/DVD+RW/ significantly enough (IMHO:-) to notify the list. The major (unfortunately not exactly good) news are that even though it should be possible to lay arbitrary file system down on DVD+RW media, it is not quite working yet:-( Further details provided in technical ramblings, second paragraph. Even growisofs was suffering from this problem. Updated version 1.1 working the problem around from user-land is now posted on the page. Cheers. A. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
long joliet filenames missing file extensions
hello, i have the following problem when using the joliet extension with mkisofs: Joliet is limited to 64 char long filenames but a lot mp3's i burn on CD are longer. mkisofs simply cuts the rest of the filename off - including the extension! This is no problem with linux and rock ridge. but if you put the cd in a windows pc the files are no longer recognized as mp3s because the extension is missing. Although i don't care about windows, i care about my hardware mp3 player which skips those files too :( tia, michael msg02503/pgp0.pgp Description: PGP signature
kernel panic with cdrw
I understand this is a development list, but I've not located other list resources so I apologize if this is OT. I've got a Philips cdrw that was working for a while just fine. I've since upgraded kernels a couple of times as well as distributions. When I've attempted to use it lately I get a kernel panic and the box locks up. Some folks have indicated that they think the drive's gone bad, but I wouldn't expect that to cause a kernel panic. Anyway, anyone have any insights into what this might be an indicator of? Since I've moved through a couple of kernels since my last cd creation, I want to be sure this thing is junk before I go out and replace it. Currently running Mandrake 8.1 with kernel 2.4.12. Last time I used this drive it was kernel 2.2.18 and I believe the distro was Mandrake 7.2??? Insights and/or pointers to this problem or a more appropriate forum would be greatly appreciated. -- Until later: Geoffrey [EMAIL PROTECTED] ...the system (Microsoft passport) carries significant risks to users that are not made adequately clear in the technical documentation available. - David P. Kormann and Aviel D. Rubin, ATT Labs - Research - http://www.avirubin.com/passport.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel panic with cdrw
From: Geoffrey [EMAIL PROTECTED] I understand this is a development list, but I've not located other list resources so I apologize if this is OT. I've got a Philips cdrw that was working for a while just fine. I've since upgraded kernels a couple of times as well as distributions. When I've attempted to use it lately I get a kernel panic and the box locks up. Some folks have indicated that they think the drive's gone bad, but I wouldn't expect that to cause a kernel panic. Anyway, anyone have any insights into what this might be an indicator of? Since I've moved through a couple of kernels since my last cd creation, I want to be sure this thing is junk before I go out and replace it. Currently running Mandrake 8.1 with kernel 2.4.12. Last time I used this drive it was kernel 2.2.18 and I believe the distro was Mandrake 7.2??? If you get a panic, then you found a Kernel bug. Kernel bugs should be reported to Kernel people Jörg EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED] (uni) If you don't have iso-8859-1 [EMAIL PROTECTED] (work) chars I am Jorg Schilling URL: http://www.fokus.gmd.de/usr/schilling ftp://ftp.fokus.gmd.de/pub/unix -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: long joliet filenames missing file extensions
i have the following problem when using the joliet extension with mkisofs: Joliet is limited to 64 char long filenames but a lot mp3's i burn on CD are longer. mkisofs simply cuts the rest of the filename off - including the extension! This is no problem with linux and rock ridge. but if you put the cd in a windows pc the files are no longer recognized as mp3s because the extension is missing. Although i don't care about windows, i care about my hardware mp3 player which skips those files too :( Have a look at my patch at ftp://ftp.ge.ucl.ac.uk/pub/mkhfs/testing/ called mkisofs-1.14-jext-2.patch.gz and the file README.jext James Pearson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Copying a bootable cdrom
Copying a bootable cdrom. I have a cdrom that I am trying to copy. It is a bootable cdrom. I can make a copy of it, but I can't boot off of it. I am assuming that I need to do something different in the mkisofs command. I even tried to to point the iso creation process at /dev/hda, but that did not work either. -- Mike Cannon Infrastructure Systems Administrator Vice President for Information Technology Purdue University 1061 Freehafer Hall (FREH) West Lafayette, IN 47907-1061 office phone: 765.494.6357 office fax: 765.496.1380 email: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
new user - solaris driver problem
I've been trying to get cdrecord to talk to my RICOH RW7060S as SCSI target 6 on a Sun Ultra 2 with Solaris 2.8. The following reflects how far I have gotten to date: --- # /usr/local/bin/cdrecord dev=6,0 -inq Cdrecord release 1.6.1 Copyright (C) 1995-1998 Jörg Schilling scsidev: '6,0' scsibus: 0 target: 6 lun: 0 /usr/local/bin/cdrecord: No such file or directory. Cannot open SCSI driver. --- I had done a pkgadd of SCHILYscg, but received the following messages on bootup: --- /kernel/drv/scg: undefined symbol 'wakeup' WARNING: mod_load: MT-unsafe module 'scg' rejected --- I then tried replacing /kernel/drv/scg with scg-sparc-sol2.4.beta2 and continue to see the same error (although I do not get the mod_load error). Note that I can read files from the drive fine. So, which part of the FAQ did I skip? Thanks for any help, --Gary -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: new user - solaris driver problem
From: Gary Delong [EMAIL PROTECTED] The following reflects how far I have gotten to date: --- # /usr/local/bin/cdrecord dev=6,0 -inq Cdrecord release 1.6.1 Copyright (C) 1995-1998 Jörg Schilling Outdated for ages! Get a recent version and read the recent instructions to install the driver http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/problems.html Jörg EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED] (uni) If you don't have iso-8859-1 [EMAIL PROTECTED] (work) chars I am Jorg Schilling URL: http://www.fokus.gmd.de/usr/schilling ftp://ftp.fokus.gmd.de/pub/unix -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: long joliet filenames missing file extensions
On Mon, 2001-12-17 at 16:33, James Pearson wrote: Have a look at my patch at ftp://ftp.ge.ucl.ac.uk/pub/mkhfs/testing/ called mkisofs-1.14-jext-2.patch.gz and the file README.jext thanks - that helped a lot! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Copying a bootable cdrom
On Mon, 17 Dec 2001, Mike R. Cannon wrote: I have a cdrom that I am trying to copy. It is a bootable cdrom. I can make a copy of it, but I can't boot off of it. I am assuming that I need to do something different in the mkisofs command. I even tried to to point the iso creation process at /dev/hda, but that did not work either. Why do you use mkisofs if you're just copying a cdrom? I usually use 'dd if=/dev/cdrom of=/tmp/filename.iso' to create an ISO image from the original cdrom and then 'cdrecord /tmp/filename.iso' to burn a new cdrom from that image. This method works well for data only and has no problems with bootable cdroms. D. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Copying a bootable cdrom
On Mon, 17 Dec 2001, Mike R. Cannon wrote: Copying a bootable cdrom. I have a cdrom that I am trying to copy. It is a bootable cdrom. I can make a copy of it, but I can't boot off of it. I am assuming that I need to do something different in the mkisofs command. I even tried to to point the iso creation process at /dev/hda, but that did not work either. I can't understand what's your problem. Why do you use mkisofs at all? The data on the original cdrom is an ISO9660 image, isn't it? So if you can boot the original CD you will be able to boot a copy of it. Kind regards Carsten -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Copying a bootable cdrom
Carsten Neumann wrote: On Mon, 17 Dec 2001, Mike R. Cannon wrote: Copying a bootable cdrom. I have a cdrom that I am trying to copy. It is a bootable cdrom. I can make a copy of it, but I can't boot off of it. I am assuming that I need to do something different in the mkisofs command. I even tried to to point the iso creation process at /dev/hda, but that did not work either. I can't understand what's your problem. Why do you use mkisofs at all? The data on the original cdrom is an ISO9660 image, isn't it? So if you can boot the original CD you will be able to boot a copy of it. Well the mkisofs didn't work! I'm not an expert but as I understand it: When you mount a cdrom you can't/don't see the boot information. Therefore when making an iso, you don't get the boot information. I ended up using xdxroast, thank someone for that. Kind regards Carsten -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Mike Cannon Infrastructure Systems Administrator Management Information Purdue University 1061 Freehafer Hall (FREH) West Lafayette, IN 47907-1061 office phone: 765.494.6357 office fax: 765.496.1380 email: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Copying a bootable cdrom
On Mon, 17 Dec 2001, Mike R. Cannon wrote: Carsten Neumann wrote: On Mon, 17 Dec 2001, Mike R. Cannon wrote: Copying a bootable cdrom. I have a cdrom that I am trying to copy. It is a bootable cdrom. I can make a copy of it, but I can't boot off of it. I am assuming that I need to do something different in the mkisofs command. I even tried to to point the iso creation process at /dev/hda, but that did not work either. I can't understand what's your problem. Why do you use mkisofs at all? The data on the original cdrom is an ISO9660 image, isn't it? So if you can boot the original CD you will be able to boot a copy of it. Well the mkisofs didn't work! I'm not an expert but as I understand it: Could you please explain why you want to use mkisofs at all? What I understood from your 1st mail is that you want to make a simple copy of it. I.e.: simply write the data from the original CD to a blank CD-R. If you want to make changes to the file system, e.g. add/replace/change/delete files you need of course to make a new iso-image via mkisofs. For all these cases there are README files in the cdrtools package. So, please RTFM. When you mount a cdrom you can't/don't see the boot information. Therefore when making an iso, you don't get the boot information. I ended up using xdxroast, thank someone for that. Kind regards Carsten Kind regards Carsten -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
