On Mon, 13 Dec 2004 07:53:28 +0100, Frank Steiner wrote:

Yes, browsing the list archives before asking, and you will find a lot of messages telling you should use "pktsetup whatevername /dev/cdrom" instead of "pktsetup /dev/pkt... /dev/cdrom". Then mount with "mount /dev/pktcdvd/whatevername -o udf <mount-point>" etc.

To write your reply, it took only two minutes of your time; to search the archives, it took me much longer than 15 minutes and with no success, as I did search the archives... Maybe, you are an expert and, because of that, you go through the messages of the list straight to the point, but, please, do not ignore that there are many people (like me) not as computer literate as you are... So, please, do not treat everybody who asks something as a lazy boy... Below is the intriguing result of your suggestion: [root@localhost psmith]# mount /dev/pktcdvd/whatevername -o udf /mnt mount: wrong fs type, bad option, bad superblock on /dev/pktcdvd/whatevername, or too many mounted file systems [root@localhost psmith]# Paul

On Mon, 13 Dec 2004 17:18:19 +0000, Chris Clayton wrote:

...

Below is the intriguing result of your suggestion:

[root@localhost psmith]# mount /dev/pktcdvd/whatevername -o udf /mnt mount: wrong fs type, bad option, bad superblock on /dev/pktcdvd/whatevername, or too many mounted file systems [root@localhost psmith]#

I think your problem will be something to do with the packet writing driver having changed recently - see Documentation/cdrom/packet-writing.txt in the kernel sources for details of how packet device setup is now achieved. If you don't have the sources, mail me off-list and I'll mail the document to you.

You will also need to patch and rebuild udftools. the patch is available at http://w1.894.telia.com/~u89404340/patches/packet/udftools-1.0.0b3.patch.bz2

Thanks, Chris. I did not build from the source the binary with udftools; I just installed it with a rpm provided on a mirror of Mandrake, under /contrib. So, I believe that the mentioned rpm was build already with the patch... otherwise, it would not make any sense to build a non-usable rpm for the Mandrake 10.1 community. Am I missing the point? Paul

On Mon, 13 Dec 2004 18:39:02 +0000, Chris Clayton wrote:

...

...

...

Below is the intriguing result of your suggestion:

[root@localhost psmith]# mount /dev/pktcdvd/whatevername -o udf /mnt mount: wrong fs type, bad option, bad superblock on /dev/pktcdvd/whatevername, or too many mounted file systems [root@localhost psmith]#

I think your problem will be something to do with the packet writing driver having changed recently - see Documentation/cdrom/packet-writing.txt in the kernel sources for details of how packet device setup is now achieved. If you don't have the sources, mail me off-list and I'll mail the document to you.

You will also need to patch and rebuild udftools. the patch is available at http://w1.894.telia.com/~u89404340/patches/packet/udftools-1.0.0b3.patch. bz2

Thanks, Chris. I did not build from the source the binary with udftools; I just installed it with a rpm provided on a mirror of Mandrake, under /contrib. So, I believe that the mentioned rpm was build already with the patch... otherwise, it would not make any sense to build a non-usable rpm for the Mandrake 10.1 community. Am I missing the point?

You are probably right, but a surefire way to tell is to run pktsetup without any arguments.

[chris:~]$ pktsetup For pktcdvd < 0.2.0: pktsetup /dev/pktcdvd0 /dev/cdrom setup device pktsetup -d /dev/pktcdvd0 tear down device For pktcdvd >= 0.2.0: pktsetup dev_name /dev/cdrom setup device pktsetup -d dev_name tear down device pktsetup -d major:minor tear down device pktsetup -s

Mine, Chris, is: [root@localhost psmith]# pktsetup For pktcdvd < 0.2.0: pktsetup /dev/pktcdvd0 /dev/cdrom setup device pktsetup -d /dev/pktcdvd0 tear down device For pktcdvd >= 0.2.0: pktsetup dev_name /dev/cdrom setup device pktsetup -d dev_name tear down device pktsetup -d major:minor tear down device pktsetup -s show device mappings [root@localhost psmith]# Same as yours, is not it? Paul

On Monday 13 Dec 2004 19:43, Chris Clayton wrote:

On Monday 13 Dec 2004 18:48, Paul Smith wrote:

...

On Mon, 13 Dec 2004 18:39:02 +0000, Chris Clayton

wrote:

...

...

...

...

Below is the intriguing result of your suggestion:

[root@localhost psmith]# mount /dev/pktcdvd/whatevername -o udf /mnt mount: wrong fs type, bad option, bad superblock on /dev/pktcdvd/whatevername, or too many mounted file systems [root@localhost psmith]#

I think your problem will be something to do with the packet writing driver having changed recently - see Documentation/cdrom/packet-writing.txt in the kernel sources for details of how packet device setup is now achieved. If you don't have the sources, mail me off-list and I'll mail the document to you.

You will also need to patch and rebuild udftools. the patch is available at http://w1.894.telia.com/~u89404340/patches/packet/udftools-1.0.0b3. pa tch. bz2

Thanks, Chris. I did not build from the source the binary with udftools; I just installed it with a rpm provided on a mirror of Mandrake, under /contrib. So, I believe that the mentioned rpm was build already with the patch... otherwise, it would not make any sense to build a non-usable rpm for the Mandrake 10.1 community. Am I missing the point?

You are probably right, but a surefire way to tell is to run pktsetup without any arguments.

[chris:~]$ pktsetup For pktcdvd < 0.2.0: pktsetup /dev/pktcdvd0 /dev/cdrom setup device pktsetup -d /dev/pktcdvd0 tear down device For pktcdvd >= 0.2.0: pktsetup dev_name /dev/cdrom setup device pktsetup -d dev_name tear down device pktsetup -d major:minor tear down device pktsetup -s

Mine, Chris, is:

[root@localhost psmith]# pktsetup For pktcdvd < 0.2.0: pktsetup /dev/pktcdvd0 /dev/cdrom setup device pktsetup -d /dev/pktcdvd0 tear down device For pktcdvd >= 0.2.0: pktsetup dev_name /dev/cdrom setup device pktsetup -d dev_name tear down device pktsetup -d major:minor tear down device pktsetup -s show device mappings [root@localhost psmith]#

Same as yours, is not it?

Paul

Paul,

Yes it is. I guess it's time to go into a bit more detail. Everything to do with my cd rewriter (/dev/hdc) is called cdrw:

/dev/cdrw is a symbolic link to /dev/hdc I pass the string cdrw as the first argument to pktsetup I mount on /cdrw.

So, setting up packet writing on that drive needs this sequence of commands:

[chris:~]$ su - Password: [root:~]$ pktsetup cdrw /dev/cdrw [root:~]$ chmod a+rw /dev/pktcdvd/cdrw [root:~]$ mount -t udf -o \ rw,noauto,noatime,user,exec,umask=0000 /dev/pktcdvd/cdrw /cdrw [root:~]$ exit

Whilst clutching at straws, it might be worth making sure that your kernel has the latest driver. When the pktcdvd module loads, I get:

pktcdvd: v0.2.0a 2004-07-14 Jens Axboe (axboe@suse.de) and petero2@telia.com

shows up in the output from dmesg.

If these suggestions don't solve your problem, I'm afraid it's got me beaten :(

Good luck

Chris

Drat, replying to my own email's now :) Thinko in my last message - the string after the -o command line switch should contain neither ,noauto nor ,user. They would only be appropriate to an entry in /etc/fstab, of course. The noatime is important though, otherwise you could wear out your media quite quickly :(( Chris

That last command should read: pksetup -d cdrw The device name is the same that you use to setup the device. Don't give the full path. Ingo

Thanks, Chris. Everything works fine now, except the last command of the sequence below:

[root@localhost psmith]# pktsetup cdrw /dev/cdrom [root@localhost psmith]# mount -t udf -o rw,noatime,exec,umask=0000 /dev/pktcdvd/cdrw /cdrom [root@localhost psmith]# chmod a+rw /cdrom [root@localhost psmith]# umount /dev/pktcdvd/cdrw [root@localhost psmith]# pktsetup -d /dev/pktcdvd/cdrw ioctl: Inappropriate ioctl for device [root@localhost psmith]#

Any ideas?

Paul

Paul Smith wrote

To write your reply, it took only two minutes of your time; to search the archives, it took me much longer than 15 minutes and with no success, as I did search the archives... Maybe, you are an expert and,

Well, 8 threads earlier "Device problems", the problem was explained. Anyway...

because of that, you go through the messages of the list straight to the point, but, please, do not ignore that there are many people (like me) not as computer literate as you are... So, please, do not treat everybody who asks something as a lazy boy...

... I did answer instead of just telling to search, right? :-)

Below is the intriguing result of your suggestion:

[root@localhost psmith]# mount /dev/pktcdvd/whatevername -o udf /mnt mount: wrong fs type, bad option, bad superblock on /dev/pktcdvd/whatevername, or too many mounted file systems [root@localhost psmith]#

Yes, was answered now already, should have been -t udf instead of -o udf. However, that was completely unrelated to packet writing, but just mount syntax. As I read from the thread, looks like everything is running well now for you. cu, Fank -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr. 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: +49 89 2180-99-4049 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *