<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
	>
<channel>
	<title>Comments on: Packet Writing on CDRW and DVDRW media</title>
	<atom:link href="http://www.g-loaded.eu/2005/11/10/packet-writing-on-cdrw-and-dvdrw-media/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.g-loaded.eu/2005/11/10/packet-writing-on-cdrw-and-dvdrw-media/</link>
	<description>An open-source software and technology related journal</description>
	<lastBuildDate>Sun, 28 Feb 2010 05:55:55 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: GNot</title>
		<link>http://www.g-loaded.eu/2005/11/10/packet-writing-on-cdrw-and-dvdrw-media/#comment-8070</link>
		<dc:creator>GNot</dc:creator>
		<pubDate>Thu, 15 Mar 2007 05:48:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.g-loaded.eu/2005/11/10/packet-writing-on-cdrw-and-dvdrw-media/#comment-8070</guid>
		<description>I haven&#039;t used any rewriteable media for a while. I guess it&#039;s time for a test (soon). There might be bugs that need to be reported.
Thanks for your feedback.</description>
		<content:encoded><![CDATA[<p>I haven&#8217;t used any rewriteable media for a while. I guess it&#8217;s time for a test (soon). There might be bugs that need to be reported.<br />
Thanks for your feedback.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Laszlo</title>
		<link>http://www.g-loaded.eu/2005/11/10/packet-writing-on-cdrw-and-dvdrw-media/#comment-7990</link>
		<dc:creator>Laszlo</dc:creator>
		<pubDate>Tue, 13 Mar 2007 01:45:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.g-loaded.eu/2005/11/10/packet-writing-on-cdrw-and-dvdrw-media/#comment-7990</guid>
		<description>When trying to mount, I have the same computer lock-up problems jimmy martin mentioned. What&#039;s the fix?</description>
		<content:encoded><![CDATA[<p>When trying to mount, I have the same computer lock-up problems jimmy martin mentioned. What&#8217;s the fix?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: GNot</title>
		<link>http://www.g-loaded.eu/2005/11/10/packet-writing-on-cdrw-and-dvdrw-media/#comment-6295</link>
		<dc:creator>GNot</dc:creator>
		<pubDate>Fri, 16 Feb 2007 11:06:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.g-loaded.eu/2005/11/10/packet-writing-on-cdrw-and-dvdrw-media/#comment-6295</guid>
		<description>I would recommend testing it from a console, for example by using the &lt;strong&gt;cp&lt;/strong&gt; command to transfer files to the rewritable medium.
Was the medium mounted when you run the chmod command? Maybe you should include the &lt;strong&gt;-R&lt;/strong&gt; (recursive) chmod option.
If you have used the UDEV rule as is, does the user who tries to write to the medium belong to the group &lt;strong&gt;disk&lt;/strong&gt;?</description>
		<content:encoded><![CDATA[<p>I would recommend testing it from a console, for example by using the <strong>cp</strong> command to transfer files to the rewritable medium.<br />
Was the medium mounted when you run the chmod command? Maybe you should include the <strong>-R</strong> (recursive) chmod option.<br />
If you have used the UDEV rule as is, does the user who tries to write to the medium belong to the group <strong>disk</strong>?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jimmy martin</title>
		<link>http://www.g-loaded.eu/2005/11/10/packet-writing-on-cdrw-and-dvdrw-media/#comment-6191</link>
		<dc:creator>jimmy martin</dc:creator>
		<pubDate>Tue, 13 Feb 2007 20:15:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.g-loaded.eu/2005/11/10/packet-writing-on-cdrw-and-dvdrw-media/#comment-6191</guid>
		<description>Thanks for the great article. I followed all the steps but when it came to mounting the RW media for packet writing using this command:   mount -t udf -o rw,noatime /dev/pktcdvd/pktcdvd0 /media/cdvdrw/

My computer would always freeze up needing a reboot. But I now have a desktop icon  that says DVD-RW LinuxUDF. In Nautilus when I click on the RW icon there is a folder there called lost+found.

When I try to drag and drop a file to the disc in Nautius file manager I get an error message: 
&quot;Error while copying to &quot;/media/LinuxUDF&quot; You do not have permissions to write to this folder.

Even when I log in as root I get the same message.
Is there a workaround way to remove any root permissions while using a GUI file manager.

I tried this comand:  &quot;chmod 777 /media/cdvdrw&quot; but it didn&#039;t work.

Jimmy</description>
		<content:encoded><![CDATA[<p>Thanks for the great article. I followed all the steps but when it came to mounting the RW media for packet writing using this command:   mount -t udf -o rw,noatime /dev/pktcdvd/pktcdvd0 /media/cdvdrw/</p>
<p>My computer would always freeze up needing a reboot. But I now have a desktop icon  that says DVD-RW LinuxUDF. In Nautilus when I click on the RW icon there is a folder there called lost+found.</p>
<p>When I try to drag and drop a file to the disc in Nautius file manager I get an error message:<br />
&#8220;Error while copying to &#8220;/media/LinuxUDF&#8221; You do not have permissions to write to this folder.</p>
<p>Even when I log in as root I get the same message.<br />
Is there a workaround way to remove any root permissions while using a GUI file manager.</p>
<p>I tried this comand:  &#8220;chmod 777 /media/cdvdrw&#8221; but it didn&#8217;t work.</p>
<p>Jimmy</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Claudio</title>
		<link>http://www.g-loaded.eu/2005/11/10/packet-writing-on-cdrw-and-dvdrw-media/#comment-1734</link>
		<dc:creator>Claudio</dc:creator>
		<pubDate>Tue, 18 Jul 2006 02:37:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.g-loaded.eu/2005/11/10/packet-writing-on-cdrw-and-dvdrw-media/#comment-1734</guid>
		<description>Thank&#039;s for this great tutorial. I am new in Linux and it helped a lot! I am using this to make Autobackups for important files with rsync and cron in Fedora 4. Fedora has released the new Kernel 2.6.17 and the module pktcdvd is gone. I am getting this message: &quot;FATAL: Module pktcdvd not found.
Can&#039;t find pktcdvd character device.&quot; I have tried to load the module with modprobe (is it right?) and got the same message. What now? I went back to the 2.6.16 kernel but the update is labeled as &quot;security&quot;.
Thank&#039;s for any help.</description>
		<content:encoded><![CDATA[<p>Thank&#8217;s for this great tutorial. I am new in Linux and it helped a lot! I am using this to make Autobackups for important files with rsync and cron in Fedora 4. Fedora has released the new Kernel 2.6.17 and the module pktcdvd is gone. I am getting this message: &#8220;FATAL: Module pktcdvd not found.<br />
Can&#8217;t find pktcdvd character device.&#8221; I have tried to load the module with modprobe (is it right?) and got the same message. What now? I went back to the 2.6.16 kernel but the update is labeled as &#8220;security&#8221;.<br />
Thank&#8217;s for any help.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gnot</title>
		<link>http://www.g-loaded.eu/2005/11/10/packet-writing-on-cdrw-and-dvdrw-media/#comment-139</link>
		<dc:creator>Gnot</dc:creator>
		<pubDate>Tue, 24 Jan 2006 16:59:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.g-loaded.eu/2005/11/10/packet-writing-on-cdrw-and-dvdrw-media/#comment-139</guid>
		<description>It&#039;s always good to hear that things work! Thanks for the comment, walwat. :-)</description>
		<content:encoded><![CDATA[<p>It&#8217;s always good to hear that things work! Thanks for the comment, walwat. :-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: walwat</title>
		<link>http://www.g-loaded.eu/2005/11/10/packet-writing-on-cdrw-and-dvdrw-media/#comment-135</link>
		<dc:creator>walwat</dc:creator>
		<pubDate>Sun, 22 Jan 2006 15:41:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.g-loaded.eu/2005/11/10/packet-writing-on-cdrw-and-dvdrw-media/#comment-135</guid>
		<description>Thank You Raul for very helpful page!!! It works.
Maybe I have solution of Francesco&#039;s problem.
Tray as root: pktsetup -d pktcdvd0 &amp;&amp; rm -f /dev/pktcdvd &amp;&amp; pktsetup pktcdvd0 /dev/hdd
(of course replace hdd with your writing device).
This first create wrong pktcdvd, than remove it and again create but the proper one.
It has to be done after every reboot, so proposed by Raul script in the line creating device mapping can be:
su -l root -c &quot;pktsetup -d pktcdvd0 &amp;&amp; rm -f /dev/pktcdvd &amp;&amp; pktsetup pktcdvd0 /dev/hdd&quot;
insted of: su -l root -c &quot;pktsetup pktcdvd0 /dev/hdd&quot;.
You can also do: pktsetup pktcdvd0 /dev/hdd &amp;&amp; rm -f /dev/pktcdvd &amp;&amp; pktsetup pktcdvd0 /dev/hdd.
Obviously there is a bug in pktsetup.
I hope it will help and thanks again Raul.</description>
		<content:encoded><![CDATA[<p>Thank You Raul for very helpful page!!! It works.<br />
Maybe I have solution of Francesco&#8217;s problem.<br />
Tray as root: pktsetup -d pktcdvd0 &amp;&amp; rm -f /dev/pktcdvd &amp;&amp; pktsetup pktcdvd0 /dev/hdd<br />
(of course replace hdd with your writing device).<br />
This first create wrong pktcdvd, than remove it and again create but the proper one.<br />
It has to be done after every reboot, so proposed by Raul script in the line creating device mapping can be:<br />
su -l root -c &#8220;pktsetup -d pktcdvd0 &amp;&amp; rm -f /dev/pktcdvd &amp;&amp; pktsetup pktcdvd0 /dev/hdd&#8221;<br />
insted of: su -l root -c &#8220;pktsetup pktcdvd0 /dev/hdd&#8221;.<br />
You can also do: pktsetup pktcdvd0 /dev/hdd &amp;&amp; rm -f /dev/pktcdvd &amp;&amp; pktsetup pktcdvd0 /dev/hdd.<br />
Obviously there is a bug in pktsetup.<br />
I hope it will help and thanks again Raul.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gnot</title>
		<link>http://www.g-loaded.eu/2005/11/10/packet-writing-on-cdrw-and-dvdrw-media/#comment-86</link>
		<dc:creator>Gnot</dc:creator>
		<pubDate>Tue, 03 Jan 2006 16:37:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.g-loaded.eu/2005/11/10/packet-writing-on-cdrw-and-dvdrw-media/#comment-86</guid>
		<description>Unfortunately I cannot provide any more help. I am out of ideas... Perhaps you should also try adding one of the following lines to &lt;code&gt;/etc/modprobe.conf&lt;/code&gt; or &lt;code&gt;/etc/modules.conf&lt;/code&gt;:

&lt;code&gt;alias block-major-97 pktcdvd&lt;/code&gt;
or
&lt;code&gt;alias block-major-252 pktcdvd&lt;/code&gt;

I believe that you need a newer kernel version.</description>
		<content:encoded><![CDATA[<p>Unfortunately I cannot provide any more help. I am out of ideas&#8230; Perhaps you should also try adding one of the following lines to <code>/etc/modprobe.conf</code> or <code>/etc/modules.conf</code>:</p>
<p><code>alias block-major-97 pktcdvd</code><br />
or<br />
<code>alias block-major-252 pktcdvd</code></p>
<p>I believe that you need a newer kernel version.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Francesco</title>
		<link>http://www.g-loaded.eu/2005/11/10/packet-writing-on-cdrw-and-dvdrw-media/#comment-83</link>
		<dc:creator>Francesco</dc:creator>
		<pubDate>Mon, 02 Jan 2006 19:53:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.g-loaded.eu/2005/11/10/packet-writing-on-cdrw-and-dvdrw-media/#comment-83</guid>
		<description>Slackware 10.1 uses by default the kernel 2.4.29 and in testing the 2.6.10 (even if a lot of person find this more stable than the 2.4). The two kernels are vanilla ones. For this reason it seems there is a mix between udev and devfs. In /etc/udev/rules.d the file for the rules isn&#039;t 50-udev.rules but conf-udev.rules or something similar that I had already renamed in 50-udev.rules and I had already tried to put your rules in 10-udev.rules but unfortunately nothing changes. I have said that probably there is a mix between devfs and udev since there are some files in /etc/udev/rules.d called &quot;devfs.rules.unsupported&quot; and &quot;/etc/udev/rules.d/compat.rules.unsupported&quot;. Anyway these files don&#039;t deal with pktcdvd and when I give the command &quot;pktsetup pktcdvd0 /dev/hdc&quot; are correctly created the two file /dev/pktcdvd/pktcdvd0 and /dev/pktcdvd/control.
The version of pktcdvd is &quot;0.2 a&quot; and the kernel I&#039;m using is the 2.6.13.2 compiled by myself with abilitated the udf fs and the pktcdvd (not as modules. They are in the kernel). I&#039;ve tried to use the dvd but there is the same problem: altough the cp command has finished the led of the dvd-writer is always on since I&#039;have copied the files. I&#039;ll try to post to the packetwriting mailing list. Thank you anyway...</description>
		<content:encoded><![CDATA[<p>Slackware 10.1 uses by default the kernel 2.4.29 and in testing the 2.6.10 (even if a lot of person find this more stable than the 2.4). The two kernels are vanilla ones. For this reason it seems there is a mix between udev and devfs. In /etc/udev/rules.d the file for the rules isn&#8217;t 50-udev.rules but conf-udev.rules or something similar that I had already renamed in 50-udev.rules and I had already tried to put your rules in 10-udev.rules but unfortunately nothing changes. I have said that probably there is a mix between devfs and udev since there are some files in /etc/udev/rules.d called &#8220;devfs.rules.unsupported&#8221; and &#8220;/etc/udev/rules.d/compat.rules.unsupported&#8221;. Anyway these files don&#8217;t deal with pktcdvd and when I give the command &#8220;pktsetup pktcdvd0 /dev/hdc&#8221; are correctly created the two file /dev/pktcdvd/pktcdvd0 and /dev/pktcdvd/control.<br />
The version of pktcdvd is &#8220;0.2 a&#8221; and the kernel I&#8217;m using is the 2.6.13.2 compiled by myself with abilitated the udf fs and the pktcdvd (not as modules. They are in the kernel). I&#8217;ve tried to use the dvd but there is the same problem: altough the cp command has finished the led of the dvd-writer is always on since I&#8217;have copied the files. I&#8217;ll try to post to the packetwriting mailing list. Thank you anyway&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gnot</title>
		<link>http://www.g-loaded.eu/2005/11/10/packet-writing-on-cdrw-and-dvdrw-media/#comment-82</link>
		<dc:creator>Gnot</dc:creator>
		<pubDate>Mon, 02 Jan 2006 03:15:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.g-loaded.eu/2005/11/10/packet-writing-on-cdrw-and-dvdrw-media/#comment-82</guid>
		<description>Hi, Francesco. I am not surprised that the kernel pktcdvd module has got you into trouble. I had many issues, until it worked properly.

The first thing that needs to be settled is the proper creation of the device nodes in &lt;code&gt;/dev/&lt;/code&gt;. If there are no &lt;code&gt;UDEV&lt;/code&gt; rules, then it&#039;s most probable that the necessary device nodes will be created in the wrong place. The creation of the &lt;code&gt;/dev/pktcdvd/&lt;/code&gt; directory is handled by &lt;code&gt;UDEV&lt;/code&gt;, so creating this directory in &lt;code&gt;rc.local&lt;/code&gt; is not needed.
You should also check if there are any default &lt;code&gt;UDEV&lt;/code&gt; rules for &lt;code&gt;pktcdvd&lt;/code&gt;. Maybe you will need to rename the file with the rules I have suggested to &lt;code&gt;40-udev.rules&lt;/code&gt; or anything that will be read &lt;strong&gt;before&lt;/strong&gt; the default &lt;code&gt;50-udev.rules&lt;/code&gt; file.

You have written that you have resolved your issues with the device node creation, but I just added this info.

Now, for the other problems you have encountered:
Make sure, through a Slackware mailing list or by any other means, that the version of the pktcdvd module that is included in your running kernel version is functioning properly and that no issues have been reported about it. This is critical. I had encountered the same problem (the drive led wouldn&#039;t stop blinking), probably to malfunctioning &lt;code&gt;pktcdvd&lt;/code&gt; module. This had happened only once, but I cannot remember the version of the kernel...
Second, make sure that your kernel has support for the &lt;code&gt;UDF&lt;/code&gt; filesystem. If the &lt;code&gt;udf&lt;/code&gt; module does not get loaded together with the &lt;code&gt;pktcdvd&lt;/code&gt; module when you setup the device mapping, then try to load it in &lt;code&gt;rc.local&lt;/code&gt;.
About &lt;code&gt;cdrwtool&lt;/code&gt;, as I have written in this article, I could not make it prepare my CDRW media for packet writing. I do not know which exactly is the problem, but I guess that it does not work well with my DVD writer. I can tell you, that I had almost quit due to these damn &lt;code&gt;cdrwtool&lt;/code&gt; malfuctions and its non-informative error messages. I would suggest that you try some DVD rewritable media instead. &lt;code&gt;dvd+rw-tools&lt;/code&gt; seem to be much more stable, but you can use them only with DVDRWs. I currently do not use any CDRWs because of the little storage space they provide.
A last thing I would suggest is to try to copy some files to the rewritable medium using &lt;code&gt;cp&lt;/code&gt;, instead of &lt;code&gt;konqueror&lt;/code&gt; or any other graphical file manager, just to make sure that it works.

I hope these will help. It is very difficult to tell what exactly is wrong. It may need some time until you investigate your issue.</description>
		<content:encoded><![CDATA[<p>Hi, Francesco. I am not surprised that the kernel pktcdvd module has got you into trouble. I had many issues, until it worked properly.</p>
<p>The first thing that needs to be settled is the proper creation of the device nodes in <code>/dev/</code>. If there are no <code>UDEV</code> rules, then it&#8217;s most probable that the necessary device nodes will be created in the wrong place. The creation of the <code>/dev/pktcdvd/</code> directory is handled by <code>UDEV</code>, so creating this directory in <code>rc.local</code> is not needed.<br />
You should also check if there are any default <code>UDEV</code> rules for <code>pktcdvd</code>. Maybe you will need to rename the file with the rules I have suggested to <code>40-udev.rules</code> or anything that will be read <strong>before</strong> the default <code>50-udev.rules</code> file.</p>
<p>You have written that you have resolved your issues with the device node creation, but I just added this info.</p>
<p>Now, for the other problems you have encountered:<br />
Make sure, through a Slackware mailing list or by any other means, that the version of the pktcdvd module that is included in your running kernel version is functioning properly and that no issues have been reported about it. This is critical. I had encountered the same problem (the drive led wouldn&#8217;t stop blinking), probably to malfunctioning <code>pktcdvd</code> module. This had happened only once, but I cannot remember the version of the kernel&#8230;<br />
Second, make sure that your kernel has support for the <code>UDF</code> filesystem. If the <code>udf</code> module does not get loaded together with the <code>pktcdvd</code> module when you setup the device mapping, then try to load it in <code>rc.local</code>.<br />
About <code>cdrwtool</code>, as I have written in this article, I could not make it prepare my CDRW media for packet writing. I do not know which exactly is the problem, but I guess that it does not work well with my DVD writer. I can tell you, that I had almost quit due to these damn <code>cdrwtool</code> malfuctions and its non-informative error messages. I would suggest that you try some DVD rewritable media instead. <code>dvd+rw-tools</code> seem to be much more stable, but you can use them only with DVDRWs. I currently do not use any CDRWs because of the little storage space they provide.<br />
A last thing I would suggest is to try to copy some files to the rewritable medium using <code>cp</code>, instead of <code>konqueror</code> or any other graphical file manager, just to make sure that it works.</p>
<p>I hope these will help. It is very difficult to tell what exactly is wrong. It may need some time until you investigate your issue.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
