July 2004 - Packet Writing - openSUSE Mailing Lists

Linux-2.6.0
by Richard A Downing FBCS 30 Dec '04

30 Dec '04

I was about to update my kernel to the new stable 2.6.0, but notice Jens has added some changes since test11. Is there any reason to suppost the test11 patch wouldn't work? I guess this is just a way of saying 'Can we have a 2.6.0 patch please Peter?' -- Richard A Downing FBCS http://www.freewebs.com/109bean/ Anyone sending unwanted advertising e-mail to this address will be charged $25 for network traffic and computing time. By extracting my address from this message or its header, you agree to these terms.

5 6

Packet-writing with kernel 2.6.3
by falolaf 01 Aug '04

01 Aug '04

Hello, I have for some time now tried to get packet-writing to work with kernel 2.6.3. I can get it to work if I add scsi-emulation for my cd-rw, but I recieve a message that it's deprecated to do so and I should use ide-cd. So I try to do this without emulation. No problem with: cdrwtool -d /dev/cdrom -q No problem with: pktsetup /dev/pktcdvd0 /dev/cdrom No problem with: mount /dev/pktcdvd0 /mnt/cdrw -t udf -o rw,noatime When I copy a file to the disk the led is flashing as usual, but when I try to copy another file nothing happens. It doesn't matter how long I wait, I can't unmount or eject the device. Does anyone have any sugestions?

3 6

trying to change type of multiple extents
by XMANN 01 Aug '04

01 Aug '04

Hello, that was a long time I haven't problem with this patch, one = year I think, sign of a good job :-) . This is my config: -debian kernel sources 2.6.7 patch 2.6.7 (patch the debain kernel sources without any pro= blem) -dell gx270 with a CDRW/DVD samsung SN-324F with the U204 fi= rmware (it's not a dvd burner) After installing my new patched debian 2.6.7 kernel, I would= like to format a cdrw.=20 The installation is all right (all modules and devices installed,pktsetup is mapped on /dev/hdc). i tried to format a verbatim 8-10X writing compatible: $cdrwtool -t 10 -d /dev/hdc -q setting speed to 10 using device /dev/hdc 1914KB internal buffer setting write speed to 10x Settings for /dev/hdc: Fixed packets, size 32 Mode-2 disc I'm going to do a quick setup of /dev/hdc. The disc is going= to be blanked and formatted with one big track. All data on the de= vice will be lost!! Press CTRL-C to cancel now. ENTER to continue. Initiating quick disc blank Disc capacity is 295264 blocks (590528KB/576MB) Formatting track start=3D0, blocks=3D16, type=3DRESERVED start=3D16, blocks=3D3, type=3DVRS start=3D19, blocks=3D237, type=3DUSPACE start=3D256, blocks=3D1, type=3DANCHOR start=3D257, blocks=3D31, type=3DUSPACE start=3D288, blocks=3D32, type=3DPVDS start=3D320, blocks=3D32, type=3DLVID start=3D352, blocks=3D32, type=3DSTABLE start=3D384, blocks=3D1024, type=3DSSPACE start=3D1408, blocks=3D293568, type=3DPSPACE start=3D294976, blocks=3D31, type=3DUSPACE start=3D295007, blocks=3D1, type=3DANCHOR start=3D295008, blocks=3D160, type=3DUSPACE start=3D295168, blocks=3D32, type=3DSTABLE start=3D295200, blocks=3D32, type=3DRVDS start=3D295232, blocks=3D31, type=3DUSPACE start=3D295263, blocks=3D1, type=3DANCHOR Writing UDF structures to disc wait_cmd: Input/output error Command failed: 2a 00 00 00 00 00 00 00 20 00 00 00 - sense = 02.04.04 wait_cmd: Input/output error Command failed: 2a 00 00 00 00 00 00 00 20 00 00 00 - sense = 02.04.04 Quick setup complete! -------------------------------------------- After this, the disc always turn in the drive and I can not = get it out without force it. This the dmesg: pktcdvd: v0.1.5a 2004-06-26 Jens Axboe (axboe(a)suse.de) and petero2(a)telia.com cdrom: This disc doesn't have any tracks I recognize! cdrom: This disc doesn't have any tracks I recognize! cdrom: This disc doesn't have any tracks I recognize! So it can blank the cdrw in fast or full method, but it can = not format it with UDF. If I try to manually format it, I have this message: $mkudffs /dev/hdc trying to change type of multiple extents That's all.=20 Thanks for your help. _____________________________________________________________________ Envie de discuter en "live" avec vos amis ? T�l�charger MSN Messenger http://www.ifrance.com/_reloc/m la 1�re messagerie instantan�e de France

2 2

when will we be ready for prime time?
by John Sowden 27 Jul '04

27 Jul '04

It seems that dvd and cd packet writing is a technology whose time came about 5 years ago, and there certainly is demand. It also seems that the patching of the operating system tells us that the technology is not yet ready for prime time. Is there a word from the suse people when this will be made part of the operating system? Possibly our (suse) standard might be used in windows to allow us to transfer data from our windows machines to our linux machines and back. John Sowden American Sentry Systems. Inc. 1221 Andersen Drive San Rafael, CA 94901 U.L. Listed Central Station Alarm Service Serving the San Francisco Bay Area Since 1967 mail(a)americansentry.net http://www.americansentry.net

1 0

Re: Re: dvd-rw packet writing howto???
by Jeff Lia 26 Jul '04

26 Jul '04

Thanks Carl, I tried exactly what you said and after cdrwtool -d /dev/hdc -q churned away for around an hour (1x write speed) the mount command gave the error "trying to change type of multiple extents". I've seen this many times before and don't know what to do about it. Again, I remind you I am trying to write to DVD-RW media. I found this link of Dyson's progress... http://lists.suse.com:80/archive/packet-writing/2003-Nov/0001.html which I tried to imitate but had no luck. I wasn't sure what kind of 4.2GB_image_file to use so I made 3 using dd ----------------------- -rw-r--r-- 1 root root 1048576000 Jul 21 12:13 1GB_image_file_cdrw -rw-r--r-- 1 root root 1048576000 Jul 21 12:15 1GB_image_file_dvd -rw-r--r-- 1 liaj users 209715200 Jul 21 13:12 200MB_image_file_empty ----------------------- in which the empty one is just zeros and the cdrw and dvd ones are made with mkudffs as shown in my outputs below empty ----------------------- bash-2.05b$ dvd+rw-format -f /dev/dvd * DVD±RW format utility by <appro(a)fy.chalmers.se>, version 4.9. * 4.7GB DVD-RW media in Sequential mode detected. * formatting 47.2% bash-2.05b$ growisofs -Z /dev/dvd=200MB_image_file_empty Executing 'builtin_dd if=200MB_image_file_empty of=/dev/dvd obs=32k seek=0' /dev/dvd: "Current Write Speed" is 1.0x1385KBps. 7143424/209715200 ( 3.4%) @1.5x, remaining 2:50 11796480/209715200 ( 5.6%) @1.0x, remaining 2:31 16449536/209715200 ( 7.8%) @1.0x, remaining 2:20 . . (etc) . 197361664/209715200 (94.1%) @1.0x, remaining 0:08 201981952/209715200 (96.3%) @1.0x, remaining 0:05 206635008/209715200 (98.5%) @1.0x, remaining 0:02 builtin_dd: 102400*2KB out @ average 1.0x1385KBps /dev/dvd: flushing cache /dev/dvd: writing lead-out bash-2.05b# modprobe pktcdvd bash-2.05b# pktsetup /dev/pktcdvd0 /dev/hdd bash-2.05b# mkudffs --spartable=2 --media-type=cdrw /dev/pktcdvd0 trying to change type of multiple extents ----------------------- cdrw ----------------------- bash-2.05b# mkudffs -r 0x0102 --media-type=cdrw 1GB_image_file_cdrw start=0, blocks=16, type=RESERVED start=16, blocks=3, type=VRS start=19, blocks=237, type=USPACE start=256, blocks=1, type=ANCHOR start=257, blocks=31, type=USPACE start=288, blocks=32, type=PVDS start=320, blocks=32, type=LVID start=352, blocks=32, type=STABLE start=384, blocks=1024, type=SSPACE start=1408, blocks=510304, type=PSPACE start=511712, blocks=31, type=USPACE start=511743, blocks=1, type=ANCHOR start=511744, blocks=160, type=USPACE start=511904, blocks=32, type=STABLE start=511936, blocks=32, type=RVDS start=511968, blocks=31, type=USPACE start=511999, blocks=1, type=ANCHOR bash-2.05b$ dvd+rw-format -f /dev/dvd * DVD±RW format utility by <appro(a)fy.chalmers.se>, version 4.9. * 4.7GB DVD-RW media in Sequential mode detected. * formatting .:-[ START UNIT failed with SK=3h/ASC=31h/ACQ=00h]: Input/output error 34.6% bash-2.05b$ growisofs -Z /dev/dvd=1GB_image_file_cdrw Executing 'builtin_dd if=1GB_image_file_cdrw of=/dev/dvd obs=32k seek=0' /dev/dvd: "Current Write Speed" is 1.0x1385KBps. 7831552/1048576000 ( 0.7%) @1.7x, remaining 11:04 12451840/1048576000 ( 1.2%) @1.0x, remaining 11:05 17104896/1048576000 ( 1.6%) @1.0x, remaining 12:03 21725184/1048576000 ( 2.1%) @1.0x, remaining 11:48 . . (etc) . 1034584064/1048576000 (98.7%) @1.0x, remaining 0:10 1039204352/1048576000 (99.1%) @1.0x, remaining 0:06 1043857408/1048576000 (99.5%) @1.0x, remaining 0:03 1048477696/1048576000 (100.0%) @1.0x, remaining 0:00 builtin_dd: 512000*2KB out @ average 1.0x1385KBps /dev/dvd: flushing cache /dev/dvd: writing lead-out bash-2.05b# modprobe pktcdvd bash-2.05b# pktsetup /dev/pktcdvd0 /dev/dvd bash-2.05b# mkudffs --spartable=2 --media-type=cdrw /dev/pktcdvd0 trying to change type of multiple extents bash-2.05b# mount -t udf -o rw,noatime /dev/pktcdvd0 /mnt/dvd mount: wrong fs type, bad option, bad superblock on /dev/pktcdvd0, or too many mounted file systems ----------------------- dvd ----------------------- bash-2.05b# mkudffs -r 0x0102 --media-type=dvd 1GB_image_file_dvd start=0, blocks=16, type=RESERVED start=16, blocks=3, type=VRS start=19, blocks=237, type=USPACE start=256, blocks=1, type=ANCHOR start=257, blocks=16, type=PVDS start=273, blocks=1, type=LVID start=274, blocks=511469, type=PSPACE start=511743, blocks=1, type=ANCHOR start=511744, blocks=239, type=USPACE start=511983, blocks=16, type=RVDS start=511999, blocks=1, type=ANCHOR bash-2.05b# dvd+rw-format -f /dev/dvd * DVD±RW format utility by <appro(a)fy.chalmers.se>, version 4.9. * 4.7GB DVD-RW media in Restricted Overwrite mode detected. * formatting 28.3% bash-2.05b# growisofs -Z /dev/dvd=1GB_image_file_dvd Executing 'builtin_dd if=1GB_image_file_dvd of=/dev/dvd obs=32k seek=0' /dev/dvd: "Current Write Speed" is 1.0x1385KBps. 5242880/1048576000 ( 0.5%) @1.1x, remaining 9:57 9863168/1048576000 ( 0.9%) @1.0x, remaining 12:17 14516224/1048576000 ( 1.4%) @1.0x, remaining 11:52 . . (etc) . 1038188544/1048576000 (99.0%) @1.0x, remaining 0:07 1042841600/1048576000 (99.5%) @1.0x, remaining 0:04 1047461888/1048576000 (99.9%) @1.0x, remaining 0:00 builtin_dd: 512000*2KB out @ average 1.0x1385KBps /dev/dvd: flushing cache /dev/dvd: writing lead-out bash-2.05b# modprobe pktcdvd bash-2.05b# pktsetup /dev/pktcdvd0 /dev/dvd ioctl: Device or resource busy bash-2.05b# mkudffs --media-type=dvd /dev/pktcdvd0 trying to change type of multiple extents bash-2.05b# mount -t udf -o rw,noatime /dev/pktcdvd0 /mnt/dvd mount: wrong fs type, bad option, bad superblock on /dev/pktcdvd0, or too many mounted file systems ----------------------- In doing these tests I've been using kernel 2.6.7 with the 2.6.6 packet writing patch and 2.6.4 dvd-rw patch. After no success, i tried kernel 2.6.7-bk20 with the 2.6.7 packet patch found at http://w1.894.telia.com/~u89404340/patches/packet/2.6/ and the dvd rw patches found at http://w1.894.telia.com/~u89404340/patches/packet/2.6/extra/2.6.7/ and came up with the exact same errors. My modules.conf file looks like below when packet writing is a module ----------------------- bash-2.05b# cat /etc/modules.conf # This is for DVD options ide-cd ignore=hdb options ide-cd ignore=hdc options ide-cd ignore=hdd pre-install sg modprobe ide-scsi pre-install sr_mod modprobe ide-scsi pre-install ide-scsi modprobe ide-cd alias block-major-97 pktcdvd ----------------------- However I've also tried building the kernel with it as part of the kernel instead of as a module and put the "alias block-major-97 pktcdvd" line in that file as well then before and after attempting to do this whole process with a reboot in between. At one point a few days ago (and I've been unable to repeat this and can't remember how I did it or in what kernel etc.) I was able to "mkudffs /dev/pktcdvd0" and it gave me some output similar to that above when I mkudffs'd the files, so it appeared as though I actually created the udf filesystem on the dvd-rw media, but I was never able to mount it with "mount /dev/pktcdvd0 /mnt/dvd -t udf -o rw,noatime" or as read only either. Does this sound like I was close? Am I chasing shadows? Please anyone help! I appreciate the response so far but unfortunately they do not help or I am missing some key ingrediant! Thanks, Jeff >Subject: Re: dvd-rw packet writing howto??? >From: Carl Luescher <wc.luescher(a)insightbb.com> >Message-Id: <1090381721.17202.50.camel(a)citialin.local> >Date: Tue, 20 Jul 2004 23:48:41 -0400 > >Jeff, > >This is what I have done. I downloaded the stable (at that time) 2.6.7 >kernel. I downloaded the 2.6.6 packet patches (if 2.6.7 patch was available >at the time I would have used these) from >http://w1.894.telia.com/~u89404340/patches/packet/2.6/ (big thanks to Peter >Osterlund!). I then downloaded the linux-2.6.6_dvd+rw-rc1.patch from >http://www.lbsd.net//display.php?page=downloads (big thanks to Nigel >Kukard!). After applying the patches and selecting the associated options >in the kernel .configure (I'm guessing you know which this is), I compiled >the kernel, built and installed the modules and did all the other good >stuff in grub. No need for you to create the pktcdvd0 device, looks the >same as mine. > >I added the following entry into the /etc/modprobe.conf file: alias >block-major-97* pktcdvd > >Reboot to the new kernel. > >Set up the packet driver: pktsetup /dev/pktcdvd0 /dev/hdc > >I formatted a cdrw with: cdrwtool -d /dev/hdc -q > >Once formatted, you should be able to mount with: mount /dev/pktcdvd0 -t >udf <mount point> -o rw,noatime _________________________________________________________________ Express yourself instantly with MSN Messenger! Download today - it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

2 1

RE: packet sector/block location?
by Jeff Lia 22 Jul '04

22 Jul '04

And if specifically defining where I want to place certain files via block address, could I instead write a dummy FILE_1 before all other files, and then go back and overwrite FILE_1 with the regenerated FILE_1? I suppose the question would more be how does UDF handle overwriting of files on disc? By literally writing the new data over the old data on the same block address (provided it is of course the exact same size) or by just writing to a new block address and changing where to look for it in the udf filesystem information? Thanks! Jeff >From: "Jeff Lia" <jeffreyallenlia(a)hotmail.com> >To: packet-writing(a)suse.com >Subject: packet sector/block location? >Date: Thu, 22 Jul 2004 17:26:58 -0400 > >Is there any prog for viewing udf info of a cd to verify block locations of >files written using packet writing software similar to that of isoinfo used >on an iso9660 iso image? > >You can stop reading here if you want, but if you are curious, the >reasoning behind my query is for testing purposes for my quest described >below... > >Thanks, > >Jeff > >------ > >I want to packet write files to a DVD-RW disc in a specific physical order. >It's important that the first file on the disc is FILE_1 however, I can't >write FILE_1 until files 2-X have been written. The DVD drive will seek >FILE_1 and from it get the information on which sectors the other files >start and end. > >The trickiness occurs because I want to write the files to disc while being >created but the files required at the beginning of the disc will be the >last ones written because they are dependent upon the files written first. > >In a perfect world, the data on my disc would be physically seen on the >disc in the following order... > >FILE_1 >FILE_2 >FILE_3 >FILE_4 >... > >However the order the files are created is... > >FILE_2 >FILE_3 >FILE_4 >... >FILE_1 > >If an image is made with mkisofs with the files in the correct order, using >isoinfo the image should appear similar to this... > >bash-2.05b# isoinfo -i dvd.iso -l > >Directory listing of / >d--------- 0 0 0 2048 Jun 16 2004 [ 275] . >d--------- 0 0 0 2048 Jun 16 2004 [ 275] .. >d--------- 0 0 0 2048 Jun 16 2004 [ 277] DIR_1 >d--------- 0 0 0 2048 Jun 16 2004 [ 276] DIR_2 > >Directory listing of /DIR_1/ >d--------- 0 0 0 2048 Jun 16 2004 [ 277] . >d--------- 0 0 0 2048 Jun 16 2004 [ 275] .. > >Directory listing of /DIR_2/ >d--------- 0 0 0 2048 Jun 16 2004 [ 276] . >d--------- 0 0 0 2048 Jun 16 2004 [ 275] .. >---------- 0 0 0 12288 Jun 16 2004 [ 300] FILE_3;1 >---------- 0 0 0 12288 Jun 16 2004 [ 278] FILE_1;1 >---------- 0 0 0 32768 Jun 16 2004 [ 284] FILE_2;1 >---------- 0 0 0 12288 Jun 16 2004 [ 9828] FILE_6;1 >---------- 0 0 0 12288 Jun 16 2004 [ 306] FILE_4;1 >---------- 0 0 0 19488768 Jun 16 2004 [ 312] FILE_5;1 > >The numbers between the brackets tells us the start sector of each file. >FILE_1 must have the lowest sector number of all files! > >I believe this strategy of using packet writing is best because as I >understand generation of udf superblock and directory stucture will be >handled by the packet writing and all that will need to be done (I hope) >would be to allow files to have a desired destination on the disc >fulfilling the reserved space requirement for the files generated later on >which go first. Thus, once files FILE_2 through FILE_X have finished >writing, the only thing left to be written is FILE_1 and lead-out. > >The only alternative I can think of would be to burn files FILE_2 through >FILE_X to disc, note their locations, create FILE_1 based on the other >files on the disc, write FILE_1 in the reserved space on the disk in front >of all the other files, and finally generate the UDF superblock and file >structure data and write that in the space reserved before everything else >already written. This sounds too complicated due to all the calculations >needed to be made based on stored info gathered based on prior written >data. This approach as would require not only FILE_1 and lead-out to be >written after the other files finished writing, but also the UDF data would >be left to write. This is not favorable because I'd like the disc to be >ready to take out of the dvd-rw drive asap. > >_________________________________________________________________ >Dont just search. Find. Check out the new MSN Search! >http://search.msn.click-url.com/go/onm00200636ave/direct/01/ > > >-- >To unsubscribe, e-mail: packet-writing-unsubscribe(a)suse.com >For additional commands, e-mail: packet-writing-help(a)suse.com > _________________________________________________________________ Dont just search. Find. Check out the new MSN Search! http://search.msn.click-url.com/go/onm00200636ave/direct/01/

1 0

RE: packet sector/block location?
by Jeff Lia 22 Jul '04

22 Jul '04

And if specifically defining where I want to place certain files via block address, could I instead write a dummy FILE_1 before all other files, and then go back and overwrite FILE_1 with the regenerated FILE_1? I suppose the question would more be how does UDF handle overwriting of files on disc? By literally writing the new data over the old data on the same block address (provided it is of course the exact same size) or by just writing to a new block address and changing where to look for it in the udf filesystem information? Thanks! Jeff >From: "Jeff Lia" <jeffreyallenlia(a)hotmail.com> >To: packet-writing(a)suse.com >Subject: packet sector/block location? >Date: Thu, 22 Jul 2004 17:26:58 -0400 > >Is there any prog for viewing udf info of a cd to verify block locations of >files written using packet writing software similar to that of isoinfo used >on an iso9660 iso image? > >You can stop reading here if you want, but if you are curious, the >reasoning behind my query is for testing purposes for my quest described >below... > >Thanks, > >Jeff > >------ > >I want to packet write files to a DVD-RW disc in a specific physical order. >It's important that the first file on the disc is FILE_1 however, I can't >write FILE_1 until files 2-X have been written. The DVD drive will seek >FILE_1 and from it get the information on which sectors the other files >start and end. > >The trickiness occurs because I want to write the files to disc while being >created but the files required at the beginning of the disc will be the >last ones written because they are dependent upon the files written first. > >In a perfect world, the data on my disc would be physically seen on the >disc in the following order... > >FILE_1 >FILE_2 >FILE_3 >FILE_4 >... > >However the order the files are created is... > >FILE_2 >FILE_3 >FILE_4 >... >FILE_1 > >If an image is made with mkisofs with the files in the correct order, using >isoinfo the image should appear similar to this... > >bash-2.05b# isoinfo -i dvd.iso -l > >Directory listing of / >d--------- 0 0 0 2048 Jun 16 2004 [ 275] . >d--------- 0 0 0 2048 Jun 16 2004 [ 275] .. >d--------- 0 0 0 2048 Jun 16 2004 [ 277] DIR_1 >d--------- 0 0 0 2048 Jun 16 2004 [ 276] DIR_2 > >Directory listing of /DIR_1/ >d--------- 0 0 0 2048 Jun 16 2004 [ 277] . >d--------- 0 0 0 2048 Jun 16 2004 [ 275] .. > >Directory listing of /DIR_2/ >d--------- 0 0 0 2048 Jun 16 2004 [ 276] . >d--------- 0 0 0 2048 Jun 16 2004 [ 275] .. >---------- 0 0 0 12288 Jun 16 2004 [ 300] FILE_3;1 >---------- 0 0 0 12288 Jun 16 2004 [ 278] FILE_1;1 >---------- 0 0 0 32768 Jun 16 2004 [ 284] FILE_2;1 >---------- 0 0 0 12288 Jun 16 2004 [ 9828] FILE_6;1 >---------- 0 0 0 12288 Jun 16 2004 [ 306] FILE_4;1 >---------- 0 0 0 19488768 Jun 16 2004 [ 312] FILE_5;1 > >The numbers between the brackets tells us the start sector of each file. >FILE_1 must have the lowest sector number of all files! > >I believe this strategy of using packet writing is best because as I >understand generation of udf superblock and directory stucture will be >handled by the packet writing and all that will need to be done (I hope) >would be to allow files to have a desired destination on the disc >fulfilling the reserved space requirement for the files generated later on >which go first. Thus, once files FILE_2 through FILE_X have finished >writing, the only thing left to be written is FILE_1 and lead-out. > >The only alternative I can think of would be to burn files FILE_2 through >FILE_X to disc, note their locations, create FILE_1 based on the other >files on the disc, write FILE_1 in the reserved space on the disk in front >of all the other files, and finally generate the UDF superblock and file >structure data and write that in the space reserved before everything else >already written. This sounds too complicated due to all the calculations >needed to be made based on stored info gathered based on prior written >data. This approach as would require not only FILE_1 and lead-out to be >written after the other files finished writing, but also the UDF data would >be left to write. This is not favorable because I'd like the disc to be >ready to take out of the dvd-rw drive asap. > >_________________________________________________________________ >Dont just search. Find. Check out the new MSN Search! >http://search.msn.click-url.com/go/onm00200636ave/direct/01/ > > >-- >To unsubscribe, e-mail: packet-writing-unsubscribe(a)suse.com >For additional commands, e-mail: packet-writing-help(a)suse.com > _________________________________________________________________ Dont just search. Find. Check out the new MSN Search! http://search.msn.click-url.com/go/onm00200636ave/direct/01/

1 0

packet sector/block location?
by Jeff Lia 22 Jul '04

22 Jul '04

Is there any prog for viewing udf info of a cd to verify block locations of files written using packet writing software similar to that of isoinfo used on an iso9660 iso image? You can stop reading here if you want, but if you are curious, the reasoning behind my query is for testing purposes for my quest described below... Thanks, Jeff ------ I want to packet write files to a DVD-RW disc in a specific physical order. It's important that the first file on the disc is FILE_1 however, I can't write FILE_1 until files 2-X have been written. The DVD drive will seek FILE_1 and from it get the information on which sectors the other files start and end. The trickiness occurs because I want to write the files to disc while being created but the files required at the beginning of the disc will be the last ones written because they are dependent upon the files written first. In a perfect world, the data on my disc would be physically seen on the disc in the following order... FILE_1 FILE_2 FILE_3 FILE_4 ... However the order the files are created is... FILE_2 FILE_3 FILE_4 ... FILE_1 If an image is made with mkisofs with the files in the correct order, using isoinfo the image should appear similar to this... bash-2.05b# isoinfo -i dvd.iso -l Directory listing of / d--------- 0 0 0 2048 Jun 16 2004 [ 275] . d--------- 0 0 0 2048 Jun 16 2004 [ 275] .. d--------- 0 0 0 2048 Jun 16 2004 [ 277] DIR_1 d--------- 0 0 0 2048 Jun 16 2004 [ 276] DIR_2 Directory listing of /DIR_1/ d--------- 0 0 0 2048 Jun 16 2004 [ 277] . d--------- 0 0 0 2048 Jun 16 2004 [ 275] .. Directory listing of /DIR_2/ d--------- 0 0 0 2048 Jun 16 2004 [ 276] . d--------- 0 0 0 2048 Jun 16 2004 [ 275] .. ---------- 0 0 0 12288 Jun 16 2004 [ 300] FILE_3;1 ---------- 0 0 0 12288 Jun 16 2004 [ 278] FILE_1;1 ---------- 0 0 0 32768 Jun 16 2004 [ 284] FILE_2;1 ---------- 0 0 0 12288 Jun 16 2004 [ 9828] FILE_6;1 ---------- 0 0 0 12288 Jun 16 2004 [ 306] FILE_4;1 ---------- 0 0 0 19488768 Jun 16 2004 [ 312] FILE_5;1 The numbers between the brackets tells us the start sector of each file. FILE_1 must have the lowest sector number of all files! I believe this strategy of using packet writing is best because as I understand generation of udf superblock and directory stucture will be handled by the packet writing and all that will need to be done (I hope) would be to allow files to have a desired destination on the disc fulfilling the reserved space requirement for the files generated later on which go first. Thus, once files FILE_2 through FILE_X have finished writing, the only thing left to be written is FILE_1 and lead-out. The only alternative I can think of would be to burn files FILE_2 through FILE_X to disc, note their locations, create FILE_1 based on the other files on the disc, write FILE_1 in the reserved space on the disk in front of all the other files, and finally generate the UDF superblock and file structure data and write that in the space reserved before everything else already written. This sounds too complicated due to all the calculations needed to be made based on stored info gathered based on prior written data. This approach as would require not only FILE_1 and lead-out to be written after the other files finished writing, but also the UDF data would be left to write. This is not favorable because I'd like the disc to be ready to take out of the dvd-rw drive asap. _________________________________________________________________ Dont just search. Find. Check out the new MSN Search! http://search.msn.click-url.com/go/onm00200636ave/direct/01/

1 0

packet sector/block location?
by Jeff Lia 22 Jul '04

22 Jul '04

Is there any prog for viewing udf info of a cd to verify block locations of files written using packet writing software similar to that of isoinfo used on an iso9660 iso image? You can stop reading here if you want, but if you are curious, the reasoning behind my query is for testing purposes for my quest described below... Thanks, Jeff ------ I want to packet write files to a DVD-RW disc in a specific physical order. It's important that the first file on the disc is FILE_1 however, I can't write FILE_1 until files 2-X have been written. The DVD drive will seek FILE_1 and from it get the information on which sectors the other files start and end. The trickiness occurs because I want to write the files to disc while being created but the files required at the beginning of the disc will be the last ones written because they are dependent upon the files written first. In a perfect world, the data on my disc would be physically seen on the disc in the following order... FILE_1 FILE_2 FILE_3 FILE_4 ... However the order the files are created is... FILE_2 FILE_3 FILE_4 ... FILE_1 If an image is made with mkisofs with the files in the correct order, using isoinfo the image should appear similar to this... bash-2.05b# isoinfo -i dvd.iso -l Directory listing of / d--------- 0 0 0 2048 Jun 16 2004 [ 275] . d--------- 0 0 0 2048 Jun 16 2004 [ 275] .. d--------- 0 0 0 2048 Jun 16 2004 [ 277] DIR_1 d--------- 0 0 0 2048 Jun 16 2004 [ 276] DIR_2 Directory listing of /DIR_1/ d--------- 0 0 0 2048 Jun 16 2004 [ 277] . d--------- 0 0 0 2048 Jun 16 2004 [ 275] .. Directory listing of /DIR_2/ d--------- 0 0 0 2048 Jun 16 2004 [ 276] . d--------- 0 0 0 2048 Jun 16 2004 [ 275] .. ---------- 0 0 0 12288 Jun 16 2004 [ 300] FILE_3;1 ---------- 0 0 0 12288 Jun 16 2004 [ 278] FILE_1;1 ---------- 0 0 0 32768 Jun 16 2004 [ 284] FILE_2;1 ---------- 0 0 0 12288 Jun 16 2004 [ 9828] FILE_6;1 ---------- 0 0 0 12288 Jun 16 2004 [ 306] FILE_4;1 ---------- 0 0 0 19488768 Jun 16 2004 [ 312] FILE_5;1 The numbers between the brackets tells us the start sector of each file. FILE_1 must have the lowest sector number of all files! I believe this strategy of using packet writing is best because as I understand generation of udf superblock and directory stucture will be handled by the packet writing and all that will need to be done (I hope) would be to allow files to have a desired destination on the disc fulfilling the reserved space requirement for the files generated later on which go first. Thus, once files FILE_2 through FILE_X have finished writing, the only thing left to be written is FILE_1 and lead-out. The only alternative I can think of would be to burn files FILE_2 through FILE_X to disc, note their locations, create FILE_1 based on the other files on the disc, write FILE_1 in the reserved space on the disk in front of all the other files, and finally generate the UDF superblock and file structure data and write that in the space reserved before everything else already written. This sounds too complicated due to all the calculations needed to be made based on stored info gathered based on prior written data. This approach as would require not only FILE_1 and lead-out to be written after the other files finished writing, but also the UDF data would be left to write. This is not favorable because I'd like the disc to be ready to take out of the dvd-rw drive asap. _________________________________________________________________ Dont just search. Find. Check out the new MSN Search! http://search.msn.click-url.com/go/onm00200636ave/direct/01/

1 0

Problems with 2.6.7 kernel compiling pktcdvd.o
by The Wizard 22 Jul '04

22 Jul '04

All - I am runnning SuSE 9.1 with the 2.6.5-7.95-default kernel. I downloaded the 2.6.7 patches from http://w1.894.telia.com/~u89404340/patches/packet/2.6/ and they all applied fine. Did make cloneconfig make and get these errors CC [M] drivers/block/pktcdvd.o drivers/block/pktcdvd.c:312: warning: `struct packet_command' declared inside parameter list drivers/block/pktcdvd.c:312: warning: its scope is only this definition or declaration, which is probably not what you want drivers/block/pktcdvd.c: In function `pkt_generic_packet': drivers/block/pktcdvd.c:327: error: dereferencing pointer to incomplete type drivers/block/pktcdvd.c:334: error: dereferencing pointer to incomplete type drivers/block/pktcdvd.c:335: error: dereferencing pointer to incomplete type drivers/block/pktcdvd.c:340: error: dereferencing pointer to incomplete type drivers/block/pktcdvd.c:342: error: dereferencing pointer to incomplete type drivers/block/pktcdvd.c:342: error: dereferencing pointer to incomplete type drivers/block/pktcdvd.c: At top level: drivers/block/pktcdvd.c:364: warning: `struct packet_command' declared inside parameter list drivers/block/pktcdvd.c: In function `pkt_dump_sense': drivers/block/pktcdvd.c:370: error: dereferencing pointer to incomplete type drivers/block/pktcdvd.c:374: error: dereferencing pointer to incomplete type drivers/block/pktcdvd.c: In function `pkt_flush_cache': drivers/block/pktcdvd.c:397: error: storage size of `cgc' isn't known drivers/block/pktcdvd.c:397: warning: unused variable `cgc' drivers/block/pktcdvd.c: In function `pkt_set_speed': drivers/block/pktcdvd.c:418: error: storage size of `cgc' isn't known drivers/block/pktcdvd.c:418: warning: unused variable `cgc' drivers/block/pktcdvd.c: At top level: drivers/block/pktcdvd.c:1291: warning: `struct packet_command' declared inside parameter list drivers/block/pktcdvd.c: In function `pkt_mode_sense': drivers/block/pktcdvd.c:1293: error: dereferencing pointer to incomplete type drivers/block/pktcdvd.c:1293: error: dereferencing pointer to incomplete type drivers/block/pktcdvd.c:1293: error: dereferencing pointer to incomplete type drivers/block/pktcdvd.c:1293: error: dereferencing pointer to incomplete type drivers/block/pktcdvd.c:1293: error: dereferencing pointer to incomplete type drivers/block/pktcdvd.c:1293: error: dereferencing pointer to incomplete type drivers/block/pktcdvd.c:1293: error: dereferencing pointer to incomplete type drivers/block/pktcdvd.c:1293: error: dereferencing pointer to incomplete type drivers/block/pktcdvd.c:1293: error: dereferencing pointer to incomplete type drivers/block/pktcdvd.c:1293: error: dereferencing pointer to incomplete type drivers/block/pktcdvd.c:1295: error: dereferencing pointer to incomplete type drivers/block/pktcdvd.c:1296: error: dereferencing pointer to incomplete type drivers/block/pktcdvd.c:1297: error: dereferencing pointer to incomplete type drivers/block/pktcdvd.c:1297: error: dereferencing pointer to incomplete type drivers/block/pktcdvd.c:1298: error: dereferencing pointer to incomplete type drivers/block/pktcdvd.c:1298: error: dereferencing pointer to incomplete type drivers/block/pktcdvd.c:1299: error: dereferencing pointer to incomplete type drivers/block/pktcdvd.c:1300: warning: passing arg 2 of `pkt_generic_packet' from incompatible pointer type drivers/block/pktcdvd.c: At top level: drivers/block/pktcdvd.c:1303: warning: `struct packet_command' declared inside parameter list drivers/block/pktcdvd.c: In function `pkt_mode_select': drivers/block/pktcdvd.c:1305: error: dereferencing pointer to incomplete type drivers/block/pktcdvd.c:1305: error: dereferencing pointer to incomplete type drivers/block/pktcdvd.c:1305: error: dereferencing pointer to incomplete type drivers/block/pktcdvd.c:1305: error: dereferencing pointer to incomplete type drivers/block/pktcdvd.c:1305: error: dereferencing pointer to incomplete type drivers/block/pktcdvd.c:1305: error: dereferencing pointer to incomplete type drivers/block/pktcdvd.c:1305: error: dereferencing pointer to incomplete type drivers/block/pktcdvd.c:1305: error: dereferencing pointer to incomplete type drivers/block/pktcdvd.c:1305: error: dereferencing pointer to incomplete type drivers/block/pktcdvd.c:1305: error: dereferencing pointer to incomplete type drivers/block/pktcdvd.c:1306: error: dereferencing pointer to incomplete type drivers/block/pktcdvd.c:1306: error: dereferencing pointer to incomplete type drivers/block/pktcdvd.c:1306: error: dereferencing pointer to incomplete type drivers/block/pktcdvd.c:1306: error: dereferencing pointer to incomplete type drivers/block/pktcdvd.c:1307: error: dereferencing pointer to incomplete type drivers/block/pktcdvd.c:1308: error: dereferencing pointer to incomplete type drivers/block/pktcdvd.c:1309: error: dereferencing pointer to incomplete type drivers/block/pktcdvd.c:1309: error: dereferencing pointer to incomplete type drivers/block/pktcdvd.c:1310: error: dereferencing pointer to incomplete type drivers/block/pktcdvd.c:1310: error: dereferencing pointer to incomplete type drivers/block/pktcdvd.c:1311: error: dereferencing pointer to incomplete type drivers/block/pktcdvd.c:1312: warning: passing arg 2 of `pkt_generic_packet' from incompatible pointer type drivers/block/pktcdvd.c: In function `pkt_get_disc_info': drivers/block/pktcdvd.c:1317: error: storage size of `cgc' isn't known drivers/block/pktcdvd.c:1317: warning: unused variable `cgc' drivers/block/pktcdvd.c: In function `pkt_get_track_info': drivers/block/pktcdvd.c:1344: error: storage size of `cgc' isn't known drivers/block/pktcdvd.c:1344: warning: unused variable `cgc' drivers/block/pktcdvd.c: In function `pkt_set_write_settings': drivers/block/pktcdvd.c:1407: error: storage size of `cgc' isn't known drivers/block/pktcdvd.c:1407: warning: unused variable `cgc' drivers/block/pktcdvd.c: In function `pkt_probe_settings': drivers/block/pktcdvd.c:1566: error: storage size of `cgc' isn't known drivers/block/pktcdvd.c:1566: warning: unused variable `cgc' drivers/block/pktcdvd.c: In function `pkt_write_caching': drivers/block/pktcdvd.c:1662: error: storage size of `cgc' isn't known drivers/block/pktcdvd.c:1662: warning: unused variable `cgc' drivers/block/pktcdvd.c: In function `pkt_lock_door': drivers/block/pktcdvd.c:1694: error: storage size of `cgc' isn't known drivers/block/pktcdvd.c:1694: warning: unused variable `cgc' drivers/block/pktcdvd.c: In function `pkt_get_max_speed': drivers/block/pktcdvd.c:1707: error: storage size of `cgc' isn't known drivers/block/pktcdvd.c:1707: warning: unused variable `cgc' drivers/block/pktcdvd.c: In function `pkt_media_speed': drivers/block/pktcdvd.c:1768: error: storage size of `cgc' isn't known drivers/block/pktcdvd.c:1768: warning: unused variable `cgc' drivers/block/pktcdvd.c: In function `pkt_perform_opc': drivers/block/pktcdvd.c:1840: error: storage size of `cgc' isn't known drivers/block/pktcdvd.c:1840: warning: unused variable `cgc' make[2]: *** [drivers/block/pktcdvd.o] Error 1 make[1]: *** [drivers/block] Error 2 make: *** [drivers] Error 2 It appears that the packet_command struct is not properly declared anywhere? I looked in /usr/src/linux/include/linux/pktcdvd.h but don't see it there; am I missing something? Mark Almeida -- Powered by SuSE Linux Pro 9.1/Evolution 1.4.6 This is a Microsoft-free computer

2 1