Re: write to dvd ram

Re: write to dvd ram

[cacook]

No one has a minute to help me with this (compile?) problem?  Linus ?





-------- Original Message --------
Subject: Re: write to dvd ram
Date: Fri, 11 May 2001 07:57:56 -0600
From: @.
To: linux-kernel@vger.kernel.org
In-Reply-To: <91FD33983070D21188A10008C728176C09421202@LDMS6003> <20010508145400Z132655-406+505@vger.kernel.org> <20010508100129.19740@dragon.linux.ix.netcom.com> <20010508195030.J505@suse.de>

Only udf I could find that was compatible with kernel 2.4.2 was the udf-0.9.3 tarball.  It does have a 2.4 directory.  I am restricted in which kernel I can use, as I must have a patch for fibrechannel.  My compile craps out with the listing below; I can't make any sense out of it.

I have used Linux for several years as my firewall, and in December 2k I decided to make it my workstation.  Since that time I have worked on configuring it at least a few hours each workday afternoon. (RedHat Fisher, then Wolverine)  Now I am not a dummy, but I'm not a coder either, and I have just not been able to get this system running, and am now up against two problems I cannot solve: this DVDRAM | UDF issue corrupting my disks (Why is udf-0.9.1 in Wolverine, wrecking my DVDRAM data?  And how can I install udf as a module when it's already in kernel?), and Wine setup.  No one has
answered my questions on the kernel IRCs nor Wine mailinglist -- they're fairly cross with newbies who have actually  read/followed the docs.  Often when I ask a question I get taken down like an elk by a lion.  This isn't supposed to be natural selection people.  Supposed to =bring= ppl to Linux;  don't they know the damage they do to Linux by blowing off their steam?  Most newbies won't slap them back down;  they'll just go away quietly & then put down Linux to others.

I haven't even yet gotten to learning/configuring Sane, LDAP, Postfix, IPTables, VPN, nor intrusion detection, much less database & production functions.

I just don't know how I'm going to make this work =practically=  as much as I want it;  RedHat just seems to require unlimited volumes of time.  After months I am precisely nowhere, and stuck with Windows, and discouraged; looks like I have at least another year of =configuring= at this rate.
--
C.

The best way out is always through.
      - Robert Frost  A Servant to Servants, 1914


Linux UDF Configuration Script

The default responses for each question are correct for most users.

Linux source directory [/usr/src/linux]: /usr/src/linux-2.4.2-temp
Alternate target install directory []: /lib/modules/2.4.2-0.1.49
C compiler name [gcc]:
Linker name [ld -m elf_i386]:
UDF Write Support (y/n) [y]:
Compiler flags for debugging [-g]:

The UDF driver needs to be compiled to match the kernel it will be used with, or it may fail to load.  If you are not sure what to do, please consult the UDF manual.

How would you like to set kernel-specific options?
    1 - Read from the currently running kernel
    2 - Read from the Linux source tree
Enter option (1-2) [1]: 2

Kernel configuration options:
    Symmetric multiprocessing support is disabled.
    Max physical memory in MB is
    Advanced Power Management (APM) support is enabled.
    Networking support is enabled.
    Module version checking is enabled.

The kernel source tree is version 2.4.2-0.1.49.
The current kernel build date is Wed Apr 18 20:53:37 MDT 2001.

Your module utilities are version 2.4.2.
make[1]: Entering directory `/usr/send-rec/download/udf-0.9.3/module'
gcc -MD -O2 -Wall -Wstrict-prototypes -pipe -DMODVERSIONS -include /usr/src/linux-2.4.2-temp/include/linux/modversions.h -g -D__KERNEL__ -DMODULE -I../include -I. -I/usr/src/linux-2.4.2-temp/include  -DUDFFS_RW=1 -DCONFIG_UDF_FS_EXT -c -o balloc.o ../linux-2.4/balloc.c
../linux-2.4/balloc.c:115:17: warning: pasting "(" and ""block_group (%d) > nr_groups (%d)\n"" does not give a valid preprocessing token
../linux-2.4/balloc.c:160:17: warning: pasting "(" and ""nonexistent device"" does not give a valid preprocessing token
../linux-2.4/balloc.c:168:17: warning: pasting "(" and ""%d < %d || %d + %d > %d\n"" does not give a valid preprocessing token
../linux-2.4/balloc.c:198:25: warning: pasting "(" and ""bit %ld already set\n"" does not give a valid preprocessing token
../linux-2.4/balloc.c:199:25: warning: pasting "(" and ""byte=%2x\n"" does not give a valid preprocessing token
../linux-2.4/balloc.c:203:54: macro "DQUOT_FREE_BLOCK" passed 3 arguments, but takes just 2
../linux-2.4/balloc.c:239:17: warning: pasting "(" and ""nonexistent device\n"" does not give a valid preprocessing token
../linux-2.4/balloc.c:268:59: macro "DQUOT_PREALLOC_BLOCK" passed 3 arguments, but takes just 2
../linux-2.4/balloc.c:272:25: warning: pasting "(" and ""bit already cleared for
 block %d\n"" does not give a valid preprocessing token
../linux-2.4/balloc.c:273:54: macro "DQUOT_FREE_BLOCK" passed 3 arguments, but takes just 2
../linux-2.4/balloc.c:310:17: warning: pasting "(" and ""nonexistent device\n""
does not give a valid preprocessing token
../linux-2.4/balloc.c:407:43: macro "DQUOT_ALLOC_BLOCK" passed 3 arguments, but takes just 2
../linux-2.4/balloc.c:420:17: warning: pasting "(" and ""bit already cleared for
 block %d\n"" does not give a valid preprocessing token
../linux-2.4/balloc.c:454:9: warning: pasting "(" and ""ino=%ld, bloc=%d, offset
=%d, count=%d\n"" does not give a valid preprocessing token
../linux-2.4/balloc.c:460:17: warning: pasting "(" and ""nonexistent device"" do
es not give a valid preprocessing token
../linux-2.4/balloc.c:471:17: warning: pasting "(" and ""%d < %d || %d + %d > %d
\n"" does not give a valid preprocessing token
../linux-2.4/balloc.c:479:42: macro "DQUOT_FREE_BLOCK" passed 3 arguments, but takes just 2
../linux-2.4/balloc.c: In function `udf_bitmap_free_blocks':
../linux-2.4/balloc.c:203: `DQUOT_FREE_BLOCK' undeclared (first use in this func
tion)
../linux-2.4/balloc.c:203: (Each undeclared identifier is reported only once
../linux-2.4/balloc.c:203: for each function it appears in.)
../linux-2.4/balloc.c: In function `udf_bitmap_prealloc_blocks':
../linux-2.4/balloc.c:268: `DQUOT_PREALLOC_BLOCK' undeclared (first use in this function)
../linux-2.4/balloc.c:273: `DQUOT_FREE_BLOCK' undeclared (first use in this func
tion)
../linux-2.4/balloc.c: In function `udf_bitmap_new_block':
../linux-2.4/balloc.c:407: `DQUOT_ALLOC_BLOCK' undeclared (first use in this fun
ction)
../linux-2.4/balloc.c: In function `udf_table_free_blocks':
../linux-2.4/balloc.c:479: `DQUOT_FREE_BLOCK' undeclared (first use in this func
tion)
../linux-2.4/balloc.c:705:9: warning: pasting "(" and ""ino=%ld, partition=%d, f
irst_block=%d, block_count=%d\n"" does not give a valid preprocessing token
../linux-2.4/balloc.c:711:17: warning: pasting "(" and ""nonexistent device\n""
does not give a valid preprocessing token
../linux-2.4/balloc.c:739:17: warning: pasting "(" and ""eloc=%d, elen=%d, first
_block=%d\n"" does not give a valid preprocessing token
../linux-2.4/balloc.c:772:9: warning: pasting "(" and ""alloc_count=%d\n"" does
not give a valid preprocessing token
../linux-2.4/balloc.c:787:9: warning: pasting "(" and ""ino=%ld, partition=%d, g
oal=%d\n"" does not give a valid preprocessing token
../linux-2.4/balloc.c:794:17: warning: pasting "(" and ""nonexistent device\n""
does not give a valid preprocessing token
../linux-2.4/balloc.c:875:17: warning: pasting "(" and ""cannot get block %d\n""
 does not give a valid preprocessing token
make[1]: *** [balloc.o] Error 1
make[1]: Leaving directory `/usr/send-rec/download/udf-0.9.3/module'
make: *** [udf.o] Error 2


Jens Axboe wrote:

> On Tue, May 08 2001, Ben Fennema wrote:
> > > The log is:
> > > Apr 15 20:58:27 hydra kernel: UDF-fs INFO UDF 0.9.1 (2000/02/29) Mounting
> > > volume 'UDF Volume', timestamp 2001/03/02 11:55 (1e98)
> >
> > At the very least, run 0.9.3 from sourceforce (or the cvs version) and
> > see if it works any better.
>
> I was just about to say the same thing, 0.9.3 works well for me. In fact
> so well, that I made a patch to bring 2.4.5-pre1 UDF up to date with
> current CVS earlier this afternoon (hint hint, Ben :-).
>
> *.kernel.org/pub/linux/kernel/people/axboe/patches/2.4.5-pre1/
>
> udf-0.9.3-2.4.5p1-1.bz2
>
> --
> Jens Axboe

Re: write to dvd ram

[Helge Hafting]

cacook@freedom.net wrote:
> 
> OK, I've asked this question four weeks in a row and received no response whatsoever.  
This happens.  So what?  Nobody _promised_ you anything.
> Linux is supposed to be the OS where you can turn to the newsgroups/IRC and get able help.
Linux is the os where you often, but not necessarily will get help form
newsgroups and mailinglists.  Particularly, try finding the _right_
list.
 
> This is to those who couldn't lift a finger to help with this compile/driver problem:
Why would anyone lift a finger for you?  Did _you_ ever help someone?
I (and many others) couldn't help because we don't know anything about
your driver and havent used UDF.  Seek out those few who knows.
> Thanks for nothing, you arrogant snots.  You don't know how much damage you do.

Damage?  Nobody did any damage by not helping you.  That's impossible
per definition.  There are tasks for which linux aren't ready, maybe you
found one of them.

Helge Hafting

Re: write to dvd ram

[Rafael Herrera]

I tried to give you some pointers in a personal email. So it's not true
you didn't receive any response. Also reminded you of the best place to
look for info, namely, that driver's mailing list. You don't seem to
have made any additional attempts at resolving it yourself since you
reposted your original message. Get newer kernel sources, read the
driver's documentation more thoroughly.
-- 
     Rafael

Re: write to dvd ram

[David Weinehall]

On Tue, May 22, 2001 at 10:38:49AM -0600, cacook@freedom.net wrote:
> OK, I've asked this question four weeks in a row and received no response
> whatsoever.  Linux is supposed to be the OS where you can turn to the
> newsgroups/IRC and get able help.
> 
> This is to those who couldn't lift a finger to help with this compile/driver
> problem:

Ignoring your obvious attitude problem for now (you haven't ever
considered the fact that (almost) all the people on this list develop
Linux voluntarily, in their spare-time?!), I suggest you try
at #kernelnewbies on irc if you want response. Or you could try to
download a newer version of the kernel. You know, the bug might've been
fixed since v2.4.2...


/David Weinehall
  _                                                                 _
 // David Weinehall <tao@acc.umu.se> /> Northern lights wander      \\
//  Project MCA Linux hacker        //  Dance across the winter sky //
\>  http://www.acc.umu.se/~tao/    </   Full colour fire           </

Re: write to dvd ram

[cacook]

OK, I've asked this question four weeks in a row and received no response whatsoever.  Linux is supposed to be the OS where you can turn to the newsgroups/IRC and get able help.

This is to those who couldn't lift a finger to help with this compile/driver problem:
Thanks for nothing, you arrogant snots.  You don't know how much damage you do.



-------- Original Message --------
Subject: Re: write to dvd ram
Date: Tue, 15 May 2001 10:32:21 -0600
From: @.
To: linux-kernel@vger.kernel.org

No one has a minute to help me with this (compile?) problem?  Linus ?





-------- Original Message --------
Subject: Re: write to dvd ram
Date: Fri, 11 May 2001 07:57:56 -0600
From: @.
To: linux-kernel@vger.kernel.org
In-Reply-To: <91FD33983070D21188A10008C728176C09421202@LDMS6003> <20010508145400Z132655-406+505@vger.kernel.org> <20010508100129.19740@dragon.linux.ix.netcom.com> <20010508195030.J505@suse.de>

Only udf I could find that was compatible with kernel 2.4.2 was the udf-0.9.3 tarball.  It does have a 2.4 directory.  I am restricted in which kernel I can use, as I must have a patch for fibrechannel.  My compile craps out with the listing below; I can't make any sense out of it.

I have used Linux for several years as my firewall, and in December 2k I decided to make it my workstation.  Since that time I have worked on configuring it at least a few hours each workday afternoon. (RedHat Fisher, then Wolverine)  Now I am not a dummy, but I'm not a coder either, and I have just not been able to get this system running, and am now up against two problems I cannot solve: this DVDRAM | UDF issue corrupting my disks (Why is udf-0.9.1 in Wolverine, wrecking my DVDRAM data?  And how can I install udf as a module when it's already in kernel?), and Wine setup.  No one has
answered my questions on the kernel IRCs nor Wine mailinglist -- they're fairly cross with newbies who have actually  read/followed the docs.  Often when I ask a question I get taken down like an elk by a lion.  This isn't supposed to be natural selection people.  Supposed to =bring= ppl to Linux;  don't they know the damage they do to Linux by blowing off their steam?  Most newbies won't slap them back down;  they'll just go away quietly & then put down Linux to others.

I haven't even yet gotten to learning/configuring Sane, LDAP, Postfix, IPTables, VPN, nor intrusion detection, much less database & production functions.

I just don't know how I'm going to make this work =practically=  as much as I want it;  RedHat just seems to require unlimited volumes of time.  After months I am precisely nowhere, and stuck with Windows, and discouraged; looks like I have at least another year of =configuring= at this rate.
--
C.

The best way out is always through.
      - Robert Frost  A Servant to Servants, 1914


Linux UDF Configuration Script

The default responses for each question are correct for most users.

Linux source directory [/usr/src/linux]: /usr/src/linux-2.4.2-temp
Alternate target install directory []: /lib/modules/2.4.2-0.1.49
C compiler name [gcc]:
Linker name [ld -m elf_i386]:
UDF Write Support (y/n) [y]:
Compiler flags for debugging [-g]:

The UDF driver needs to be compiled to match the kernel it will be used with, or it may fail to load.  If you are not sure what to do, please consult the UDF manual.

How would you like to set kernel-specific options?
    1 - Read from the currently running kernel
    2 - Read from the Linux source tree
Enter option (1-2) [1]: 2

Kernel configuration options:
    Symmetric multiprocessing support is disabled.
    Max physical memory in MB is
    Advanced Power Management (APM) support is enabled.
    Networking support is enabled.
    Module version checking is enabled.

The kernel source tree is version 2.4.2-0.1.49.
The current kernel build date is Wed Apr 18 20:53:37 MDT 2001.

Your module utilities are version 2.4.2.
make[1]: Entering directory `/usr/send-rec/download/udf-0.9.3/module'
gcc -MD -O2 -Wall -Wstrict-prototypes -pipe -DMODVERSIONS -include /usr/src/linux-2.4.2-temp/include/linux/modversions.h -g -D__KERNEL__ -DMODULE -I../include -I. -I/usr/src/linux-2.4.2-temp/include  -DUDFFS_RW=1 -DCONFIG_UDF_FS_EXT -c -o balloc.o ../linux-2.4/balloc.c
../linux-2.4/balloc.c:115:17: warning: pasting "(" and ""block_group (%d) > nr_groups (%d)\n"" does not give a valid preprocessing token
../linux-2.4/balloc.c:160:17: warning: pasting "(" and ""nonexistent device"" does not give a valid preprocessing token
../linux-2.4/balloc.c:168:17: warning: pasting "(" and ""%d < %d || %d + %d > %d\n"" does not give a valid preprocessing token
../linux-2.4/balloc.c:198:25: warning: pasting "(" and ""bit %ld already set\n"" does not give a valid preprocessing token
../linux-2.4/balloc.c:199:25: warning: pasting "(" and ""byte=%2x\n"" does not give a valid preprocessing token
../linux-2.4/balloc.c:203:54: macro "DQUOT_FREE_BLOCK" passed 3 arguments, but takes just 2
../linux-2.4/balloc.c:239:17: warning: pasting "(" and ""nonexistent device\n"" does not give a valid preprocessing token
../linux-2.4/balloc.c:268:59: macro "DQUOT_PREALLOC_BLOCK" passed 3 arguments, but takes just 2
../linux-2.4/balloc.c:272:25: warning: pasting "(" and ""bit already cleared for
 block %d\n"" does not give a valid preprocessing token
../linux-2.4/balloc.c:273:54: macro "DQUOT_FREE_BLOCK" passed 3 arguments, but takes just 2
../linux-2.4/balloc.c:310:17: warning: pasting "(" and ""nonexistent device\n""
does not give a valid preprocessing token
../linux-2.4/balloc.c:407:43: macro "DQUOT_ALLOC_BLOCK" passed 3 arguments, but takes just 2
../linux-2.4/balloc.c:420:17: warning: pasting "(" and ""bit already cleared for
 block %d\n"" does not give a valid preprocessing token
../linux-2.4/balloc.c:454:9: warning: pasting "(" and ""ino=%ld, bloc=%d, offset
=%d, count=%d\n"" does not give a valid preprocessing token
../linux-2.4/balloc.c:460:17: warning: pasting "(" and ""nonexistent device"" do
es not give a valid preprocessing token
../linux-2.4/balloc.c:471:17: warning: pasting "(" and ""%d < %d || %d + %d > %d
\n"" does not give a valid preprocessing token
../linux-2.4/balloc.c:479:42: macro "DQUOT_FREE_BLOCK" passed 3 arguments, but takes just 2
../linux-2.4/balloc.c: In function `udf_bitmap_free_blocks':
../linux-2.4/balloc.c:203: `DQUOT_FREE_BLOCK' undeclared (first use in this func
tion)
../linux-2.4/balloc.c:203: (Each undeclared identifier is reported only once
../linux-2.4/balloc.c:203: for each function it appears in.)
../linux-2.4/balloc.c: In function `udf_bitmap_prealloc_blocks':
../linux-2.4/balloc.c:268: `DQUOT_PREALLOC_BLOCK' undeclared (first use in this function)
../linux-2.4/balloc.c:273: `DQUOT_FREE_BLOCK' undeclared (first use in this func
tion)
../linux-2.4/balloc.c: In function `udf_bitmap_new_block':
../linux-2.4/balloc.c:407: `DQUOT_ALLOC_BLOCK' undeclared (first use in this fun
ction)
../linux-2.4/balloc.c: In function `udf_table_free_blocks':
../linux-2.4/balloc.c:479: `DQUOT_FREE_BLOCK' undeclared (first use in this func
tion)
../linux-2.4/balloc.c:705:9: warning: pasting "(" and ""ino=%ld, partition=%d, f
irst_block=%d, block_count=%d\n"" does not give a valid preprocessing token
../linux-2.4/balloc.c:711:17: warning: pasting "(" and ""nonexistent device\n""
does not give a valid preprocessing token
../linux-2.4/balloc.c:739:17: warning: pasting "(" and ""eloc=%d, elen=%d, first
_block=%d\n"" does not give a valid preprocessing token
../linux-2.4/balloc.c:772:9: warning: pasting "(" and ""alloc_count=%d\n"" does
not give a valid preprocessing token
../linux-2.4/balloc.c:787:9: warning: pasting "(" and ""ino=%ld, partition=%d, g
oal=%d\n"" does not give a valid preprocessing token
../linux-2.4/balloc.c:794:17: warning: pasting "(" and ""nonexistent device\n""
does not give a valid preprocessing token
../linux-2.4/balloc.c:875:17: warning: pasting "(" and ""cannot get block %d\n""
 does not give a valid preprocessing token
make[1]: *** [balloc.o] Error 1
make[1]: Leaving directory `/usr/send-rec/download/udf-0.9.3/module'
make: *** [udf.o] Error 2


Jens Axboe wrote:

> On Tue, May 08 2001, Ben Fennema wrote:
> > > The log is:
> > > Apr 15 20:58:27 hydra kernel: UDF-fs INFO UDF 0.9.1 (2000/02/29) Mounting
> > > volume 'UDF Volume', timestamp 2001/03/02 11:55 (1e98)
> >
> > At the very least, run 0.9.3 from sourceforce (or the cvs version) and
> > see if it works any better.
>
> I was just about to say the same thing, 0.9.3 works well for me. In fact
> so well, that I made a patch to bring 2.4.5-pre1 UDF up to date with
> current CVS earlier this afternoon (hint hint, Ben :-).
>
> *.kernel.org/pub/linux/kernel/people/axboe/patches/2.4.5-pre1/
>
> udf-0.9.3-2.4.5p1-1.bz2
>
> --
> Jens Axboe

Re: write to dvd ram

[quantum7]

OK, I've asked this question four weeks in a row and received no response whatsoever.  Linux is supposed to be the OS where you can turn to the newsgroups/IRC and get able help.

This is to those who couldn't lift a finger to help with this compile/driver problem:
Thanks for nothing, you arrogant snots.  You don't know how much damage you do.



-------- Original Message --------
Subject: Re: write to dvd ram
Date: Tue, 15 May 2001 10:32:21 -0600
From: @.
To: linux-kernel@vger.kernel.org

No one has a minute to help me with this (compile?) problem?  Linus ?





-------- Original Message --------
Subject: Re: write to dvd ram
Date: Fri, 11 May 2001 07:57:56 -0600
From: @.
To: linux-kernel@vger.kernel.org
In-Reply-To: <91FD33983070D21188A10008C728176C09421202@LDMS6003> <20010508145400Z132655-406+505@vger.kernel.org> <20010508100129.19740@dragon.linux.ix.netcom.com> <20010508195030.J505@suse.de>

Only udf I could find that was compatible with kernel 2.4.2 was the udf-0.9.3 tarball.  It does have a 2.4 directory.  I am restricted in which kernel I can use, as I must have a patch for fibrechannel.  My compile craps out with the listing below; I can't make any sense out of it.

I have used Linux for several years as my firewall, and in December 2k I decided to make it my workstation.  Since that time I have worked on configuring it at least a few hours each workday afternoon. (RedHat Fisher, then Wolverine)  Now I am not a dummy, but I'm not a coder either, and I have just not been able to get this system running, and am now up against two problems I cannot solve: this DVDRAM | UDF issue corrupting my disks (Why is udf-0.9.1 in Wolverine, wrecking my DVDRAM data?  And how can I install udf as a module when it's already in kernel?), and Wine setup.  No one has
answered my questions on the kernel IRCs nor Wine mailinglist -- they're fairly cross with newbies who have actually  read/followed the docs.  Often when I ask a question I get taken down like an elk by a lion.  This isn't supposed to be natural selection people.  Supposed to =bring= ppl to Linux;  don't they know the damage they do to Linux by blowing off their steam?  Most newbies won't slap them back down;  they'll just go away quietly & then put down Linux to others.

I haven't even yet gotten to learning/configuring Sane, LDAP, Postfix, IPTables, VPN, nor intrusion detection, much less database & production functions.

I just don't know how I'm going to make this work =practically=  as much as I want it;  RedHat just seems to require unlimited volumes of time.  After months I am precisely nowhere, and stuck with Windows, and discouraged; looks like I have at least another year of =configuring= at this rate.
--
C.

The best way out is always through.
      - Robert Frost  A Servant to Servants, 1914


Linux UDF Configuration Script

The default responses for each question are correct for most users.

Linux source directory [/usr/src/linux]: /usr/src/linux-2.4.2-temp
Alternate target install directory []: /lib/modules/2.4.2-0.1.49
C compiler name [gcc]:
Linker name [ld -m elf_i386]:
UDF Write Support (y/n) [y]:
Compiler flags for debugging [-g]:

The UDF driver needs to be compiled to match the kernel it will be used with, or it may fail to load.  If you are not sure what to do, please consult the UDF manual.

How would you like to set kernel-specific options?
    1 - Read from the currently running kernel
    2 - Read from the Linux source tree
Enter option (1-2) [1]: 2

Kernel configuration options:
    Symmetric multiprocessing support is disabled.
    Max physical memory in MB is
    Advanced Power Management (APM) support is enabled.
    Networking support is enabled.
    Module version checking is enabled.

The kernel source tree is version 2.4.2-0.1.49.
The current kernel build date is Wed Apr 18 20:53:37 MDT 2001.

Your module utilities are version 2.4.2.
make[1]: Entering directory `/usr/send-rec/download/udf-0.9.3/module'
gcc -MD -O2 -Wall -Wstrict-prototypes -pipe -DMODVERSIONS -include /usr/src/linux-2.4.2-temp/include/linux/modversions.h -g -D__KERNEL__ -DMODULE -I../include -I. -I/usr/src/linux-2.4.2-temp/include  -DUDFFS_RW=1 -DCONFIG_UDF_FS_EXT -c -o balloc.o ../linux-2.4/balloc.c
../linux-2.4/balloc.c:115:17: warning: pasting "(" and ""block_group (%d) > nr_groups (%d)\n"" does not give a valid preprocessing token
../linux-2.4/balloc.c:160:17: warning: pasting "(" and ""nonexistent device"" does not give a valid preprocessing token
../linux-2.4/balloc.c:168:17: warning: pasting "(" and ""%d < %d || %d + %d > %d\n"" does not give a valid preprocessing token
../linux-2.4/balloc.c:198:25: warning: pasting "(" and ""bit %ld already set\n"" does not give a valid preprocessing token
../linux-2.4/balloc.c:199:25: warning: pasting "(" and ""byte=%2x\n"" does not give a valid preprocessing token
../linux-2.4/balloc.c:203:54: macro "DQUOT_FREE_BLOCK" passed 3 arguments, but takes just 2
../linux-2.4/balloc.c:239:17: warning: pasting "(" and ""nonexistent device\n"" does not give a valid preprocessing token
../linux-2.4/balloc.c:268:59: macro "DQUOT_PREALLOC_BLOCK" passed 3 arguments, but takes just 2
../linux-2.4/balloc.c:272:25: warning: pasting "(" and ""bit already cleared for
 block %d\n"" does not give a valid preprocessing token
../linux-2.4/balloc.c:273:54: macro "DQUOT_FREE_BLOCK" passed 3 arguments, but takes just 2
../linux-2.4/balloc.c:310:17: warning: pasting "(" and ""nonexistent device\n""
does not give a valid preprocessing token
../linux-2.4/balloc.c:407:43: macro "DQUOT_ALLOC_BLOCK" passed 3 arguments, but takes just 2
../linux-2.4/balloc.c:420:17: warning: pasting "(" and ""bit already cleared for
 block %d\n"" does not give a valid preprocessing token
../linux-2.4/balloc.c:454:9: warning: pasting "(" and ""ino=%ld, bloc=%d, offset
=%d, count=%d\n"" does not give a valid preprocessing token
../linux-2.4/balloc.c:460:17: warning: pasting "(" and ""nonexistent device"" do
es not give a valid preprocessing token
../linux-2.4/balloc.c:471:17: warning: pasting "(" and ""%d < %d || %d + %d > %d
\n"" does not give a valid preprocessing token
../linux-2.4/balloc.c:479:42: macro "DQUOT_FREE_BLOCK" passed 3 arguments, but takes just 2
../linux-2.4/balloc.c: In function `udf_bitmap_free_blocks':
../linux-2.4/balloc.c:203: `DQUOT_FREE_BLOCK' undeclared (first use in this func
tion)
../linux-2.4/balloc.c:203: (Each undeclared identifier is reported only once
../linux-2.4/balloc.c:203: for each function it appears in.)
../linux-2.4/balloc.c: In function `udf_bitmap_prealloc_blocks':
../linux-2.4/balloc.c:268: `DQUOT_PREALLOC_BLOCK' undeclared (first use in this function)
../linux-2.4/balloc.c:273: `DQUOT_FREE_BLOCK' undeclared (first use in this func
tion)
../linux-2.4/balloc.c: In function `udf_bitmap_new_block':
../linux-2.4/balloc.c:407: `DQUOT_ALLOC_BLOCK' undeclared (first use in this fun
ction)
../linux-2.4/balloc.c: In function `udf_table_free_blocks':
../linux-2.4/balloc.c:479: `DQUOT_FREE_BLOCK' undeclared (first use in this func
tion)
../linux-2.4/balloc.c:705:9: warning: pasting "(" and ""ino=%ld, partition=%d, f
irst_block=%d, block_count=%d\n"" does not give a valid preprocessing token
../linux-2.4/balloc.c:711:17: warning: pasting "(" and ""nonexistent device\n""
does not give a valid preprocessing token
../linux-2.4/balloc.c:739:17: warning: pasting "(" and ""eloc=%d, elen=%d, first
_block=%d\n"" does not give a valid preprocessing token
../linux-2.4/balloc.c:772:9: warning: pasting "(" and ""alloc_count=%d\n"" does
not give a valid preprocessing token
../linux-2.4/balloc.c:787:9: warning: pasting "(" and ""ino=%ld, partition=%d, g
oal=%d\n"" does not give a valid preprocessing token
../linux-2.4/balloc.c:794:17: warning: pasting "(" and ""nonexistent device\n""
does not give a valid preprocessing token
../linux-2.4/balloc.c:875:17: warning: pasting "(" and ""cannot get block %d\n""
 does not give a valid preprocessing token
make[1]: *** [balloc.o] Error 1
make[1]: Leaving directory `/usr/send-rec/download/udf-0.9.3/module'
make: *** [udf.o] Error 2


Jens Axboe wrote:

> On Tue, May 08 2001, Ben Fennema wrote:
> > > The log is:
> > > Apr 15 20:58:27 hydra kernel: UDF-fs INFO UDF 0.9.1 (2000/02/29) Mounting
> > > volume 'UDF Volume', timestamp 2001/03/02 11:55 (1e98)
> >
> > At the very least, run 0.9.3 from sourceforce (or the cvs version) and
> > see if it works any better.
>
> I was just about to say the same thing, 0.9.3 works well for me. In fact
> so well, that I made a patch to bring 2.4.5-pre1 UDF up to date with
> current CVS earlier this afternoon (hint hint, Ben :-).
>
> *.kernel.org/pub/linux/kernel/people/axboe/patches/2.4.5-pre1/
>
> udf-0.9.3-2.4.5p1-1.bz2
>
> --
> Jens Axboe

Re: write to dvd ram

[cacook]

Only udf I could find that was compatible with kernel 2.4.2 was the udf-0.9.3 tarball.  It does have a 2.4 directory.  I am restricted in which kernel I can use, as I must have a patch for fibrechannel.  My compile craps out with the listing below; I can't make any sense out of it.

I have used Linux for several years as my firewall, and in December 2k I decided to make it my workstation.  Since that time I have worked on configuring it at least a few hours each workday afternoon. (Fisher, then Wolverine)  Now I am not a dummy, but I'm not a coder either, and I have just not been able to get this system running, and am now up against two problems I cannot solve: this DVDRAM | UDF issue corrupting my disks (Why is udf-0.9.1 in Wolverine, wrecking my DVDRAM data?  And how can I install udf as a module when it's already in kernel?), and Wine setup.  No one has answered my
questions on the kernel IRCs nor Wine mailinglist -- they're fairly cross with newbies who have actually  read/followed the docs.  Often when I ask a question I get taken down like an elk by a lion.  This isn't supposed to be natural selection people.  Supposed to =bring= ppl to Linux;  don't they know the damage they do to Linux by blowing off their steam?  Most newbies won't slap them back down;  they'll just go away quietly & then put down Linux to others.

I haven't even yet gotten to learning/configuring Sane, LDAP, Postfix, IPTables, VPN, nor intrusion detection, much less database.

I just don't know how I'm going to make this work =practically=  as much as I want it;  RedHat just seems to require unlimited volumes of time.  After months I am precisely nowhere, and stuck with Windows, and discouraged; looks like I have at least another year of =configuring= at this rate.
--
C.

The best way out is always through.
      - Robert Frost  A Servant to Servants, 1914


Linux UDF Configuration Script

The default responses for each question are correct for most users.

Linux source directory [/usr/src/linux]: /usr/src/linux-2.4.2-temp
Alternate target install directory []: /lib/modules/2.4.2-0.1.49
C compiler name [gcc]:
Linker name [ld -m elf_i386]:
UDF Write Support (y/n) [y]:
Compiler flags for debugging [-g]:

The UDF driver needs to be compiled to match the kernel it will be used with, or it may fail to load.  If you are not sure what to do, please consult the UDF manual.

How would you like to set kernel-specific options?
    1 - Read from the currently running kernel
    2 - Read from the Linux source tree
Enter option (1-2) [1]: 2

Kernel configuration options:
    Symmetric multiprocessing support is disabled.
    Max physical memory in MB is
    Advanced Power Management (APM) support is enabled.
    Networking support is enabled.
    Module version checking is enabled.

The kernel source tree is version 2.4.2-0.1.49.
The current kernel build date is Wed Apr 18 20:53:37 MDT 2001.

Your module utilities are version 2.4.2.
make[1]: Entering directory `/usr/send-rec/download/udf-0.9.3/module'
gcc -MD -O2 -Wall -Wstrict-prototypes -pipe -DMODVERSIONS -include /usr/src/linux-2.4.2-temp/include/linux/modversions.h -g -D__KERNEL__ -DMODULE -I../include -I. -I/usr/src/linux-2.4.2-temp/include  -DUDFFS_RW=1 -DCONFIG_UDF_FS_EXT -c -o balloc.o ../linux-2.4/balloc.c
../linux-2.4/balloc.c:115:17: warning: pasting "(" and ""block_group (%d) > nr_groups (%d)\n"" does not give a valid preprocessing token
../linux-2.4/balloc.c:160:17: warning: pasting "(" and ""nonexistent device"" does not give a valid preprocessing token
../linux-2.4/balloc.c:168:17: warning: pasting "(" and ""%d < %d || %d + %d > %d\n"" does not give a valid preprocessing token
../linux-2.4/balloc.c:198:25: warning: pasting "(" and ""bit %ld already set\n"" does not give a valid preprocessing token
../linux-2.4/balloc.c:199:25: warning: pasting "(" and ""byte=%2x\n"" does not give a valid preprocessing token
../linux-2.4/balloc.c:203:54: macro "DQUOT_FREE_BLOCK" passed 3 arguments, but takes just 2
../linux-2.4/balloc.c:239:17: warning: pasting "(" and ""nonexistent device\n"" does not give a valid preprocessing token
../linux-2.4/balloc.c:268:59: macro "DQUOT_PREALLOC_BLOCK" passed 3 arguments, but takes just 2
../linux-2.4/balloc.c:272:25: warning: pasting "(" and ""bit already cleared for
 block %d\n"" does not give a valid preprocessing token
../linux-2.4/balloc.c:273:54: macro "DQUOT_FREE_BLOCK" passed 3 arguments, but takes just 2
../linux-2.4/balloc.c:310:17: warning: pasting "(" and ""nonexistent device\n""
does not give a valid preprocessing token
../linux-2.4/balloc.c:407:43: macro "DQUOT_ALLOC_BLOCK" passed 3 arguments, but takes just 2
../linux-2.4/balloc.c:420:17: warning: pasting "(" and ""bit already cleared for
 block %d\n"" does not give a valid preprocessing token
../linux-2.4/balloc.c:454:9: warning: pasting "(" and ""ino=%ld, bloc=%d, offset
=%d, count=%d\n"" does not give a valid preprocessing token
../linux-2.4/balloc.c:460:17: warning: pasting "(" and ""nonexistent device"" do
es not give a valid preprocessing token
../linux-2.4/balloc.c:471:17: warning: pasting "(" and ""%d < %d || %d + %d > %d
\n"" does not give a valid preprocessing token
../linux-2.4/balloc.c:479:42: macro "DQUOT_FREE_BLOCK" passed 3 arguments, but takes just 2
../linux-2.4/balloc.c: In function `udf_bitmap_free_blocks':
../linux-2.4/balloc.c:203: `DQUOT_FREE_BLOCK' undeclared (first use in this func
tion)
../linux-2.4/balloc.c:203: (Each undeclared identifier is reported only once
../linux-2.4/balloc.c:203: for each function it appears in.)
../linux-2.4/balloc.c: In function `udf_bitmap_prealloc_blocks':
../linux-2.4/balloc.c:268: `DQUOT_PREALLOC_BLOCK' undeclared (first use in this function)
../linux-2.4/balloc.c:273: `DQUOT_FREE_BLOCK' undeclared (first use in this func
tion)
../linux-2.4/balloc.c: In function `udf_bitmap_new_block':
../linux-2.4/balloc.c:407: `DQUOT_ALLOC_BLOCK' undeclared (first use in this fun
ction)
../linux-2.4/balloc.c: In function `udf_table_free_blocks':
../linux-2.4/balloc.c:479: `DQUOT_FREE_BLOCK' undeclared (first use in this func
tion)
../linux-2.4/balloc.c:705:9: warning: pasting "(" and ""ino=%ld, partition=%d, f
irst_block=%d, block_count=%d\n"" does not give a valid preprocessing token
../linux-2.4/balloc.c:711:17: warning: pasting "(" and ""nonexistent device\n""
does not give a valid preprocessing token
../linux-2.4/balloc.c:739:17: warning: pasting "(" and ""eloc=%d, elen=%d, first
_block=%d\n"" does not give a valid preprocessing token
../linux-2.4/balloc.c:772:9: warning: pasting "(" and ""alloc_count=%d\n"" does
not give a valid preprocessing token
../linux-2.4/balloc.c:787:9: warning: pasting "(" and ""ino=%ld, partition=%d, g
oal=%d\n"" does not give a valid preprocessing token
../linux-2.4/balloc.c:794:17: warning: pasting "(" and ""nonexistent device\n""
does not give a valid preprocessing token
../linux-2.4/balloc.c:875:17: warning: pasting "(" and ""cannot get block %d\n""
 does not give a valid preprocessing token
make[1]: *** [balloc.o] Error 1
make[1]: Leaving directory `/usr/send-rec/download/udf-0.9.3/module'
make: *** [udf.o] Error 2


Jens Axboe wrote:

> On Tue, May 08 2001, Ben Fennema wrote:
> > > The log is:
> > > Apr 15 20:58:27 hydra kernel: UDF-fs INFO UDF 0.9.1 (2000/02/29) Mounting
> > > volume 'UDF Volume', timestamp 2001/03/02 11:55 (1e98)
> >
> > At the very least, run 0.9.3 from sourceforce (or the cvs version) and
> > see if it works any better.
>
> I was just about to say the same thing, 0.9.3 works well for me. In fact
> so well, that I made a patch to bring 2.4.5-pre1 UDF up to date with
> current CVS earlier this afternoon (hint hint, Ben :-).
>
> *.kernel.org/pub/linux/kernel/people/axboe/patches/2.4.5-pre1/
>
> udf-0.9.3-2.4.5p1-1.bz2
>
> --
> Jens Axboe

Re: write to dvd ram

[Jens Axboe]

On Tue, May 08 2001, Thiago Vinhas de Moraes wrote:
> 
> Hi!
> 
> Can this new UDF driver do cd-rewriting ?

No not in itself, but you can give the pktcdvd module a shot. It can do
rw CD-RW mount so far, at least.

*.kernel.org/pub/linux/kernel/people/axboe/packet/

There's a packet-writing mailing list for the above patch, there is more
info in the tar file above (subscribe info, archives, resources, etc).

-- 
Jens Axboe

Re: write to dvd ram

[Thiago Vinhas de Moraes]

Hi!

Can this new UDF driver do cd-rewriting ?



Em Ter 08 Mai 2001 14:50, Jens Axboe escreveu:
> On Tue, May 08 2001, Ben Fennema wrote:
> > > The log is:
> > > Apr 15 20:58:27 hydra kernel: UDF-fs INFO UDF 0.9.1 (2000/02/29)
> > > Mounting volume 'UDF Volume', timestamp 2001/03/02 11:55 (1e98)
> >
> > At the very least, run 0.9.3 from sourceforce (or the cvs version) and
> > see if it works any better.
>
> I was just about to say the same thing, 0.9.3 works well for me. In fact
> so well, that I made a patch to bring 2.4.5-pre1 UDF up to date with
> current CVS earlier this afternoon (hint hint, Ben :-).
>
> *.kernel.org/pub/linux/kernel/people/axboe/patches/2.4.5-pre1/
>
> udf-0.9.3-2.4.5p1-1.bz2

-- 
________________________________
 Thiago Vinhas de Moraes
 NetWorx - A SuaCompanhia.com

Re: write to dvd ram

[cacook]

Thanks, I'll try it.  Didn't get the prior response.
--
C.

The best way out is always through.
      - Robert Frost  A Servant to Servants, 1914



Jens Axboe wrote:

> On Tue, May 08 2001, Ben Fennema wrote:
> > > The log is:
> > > Apr 15 20:58:27 hydra kernel: UDF-fs INFO UDF 0.9.1 (2000/02/29) Mounting
> > > volume 'UDF Volume', timestamp 2001/03/02 11:55 (1e98)
> >
> > At the very least, run 0.9.3 from sourceforce (or the cvs version) and
> > see if it works any better.
>
> I was just about to say the same thing, 0.9.3 works well for me. In fact
> so well, that I made a patch to bring 2.4.5-pre1 UDF up to date with
> current CVS earlier this afternoon (hint hint, Ben :-).
>
> *.kernel.org/pub/linux/kernel/people/axboe/patches/2.4.5-pre1/
>
> udf-0.9.3-2.4.5p1-1.bz2
>
> --
> Jens Axboe

Re: write to dvd ram

[Jens Axboe]

On Tue, May 08 2001, Ben Fennema wrote:
> > The log is:
> > Apr 15 20:58:27 hydra kernel: UDF-fs INFO UDF 0.9.1 (2000/02/29) Mounting
> > volume 'UDF Volume', timestamp 2001/03/02 11:55 (1e98)
> 
> At the very least, run 0.9.3 from sourceforce (or the cvs version) and
> see if it works any better.

I was just about to say the same thing, 0.9.3 works well for me. In fact
so well, that I made a patch to bring 2.4.5-pre1 UDF up to date with
current CVS earlier this afternoon (hint hint, Ben :-).

*.kernel.org/pub/linux/kernel/people/axboe/patches/2.4.5-pre1/

udf-0.9.3-2.4.5p1-1.bz2

-- 
Jens Axboe

Re: write to dvd ram

[Ben Fennema]

> The log is:
> Apr 15 20:58:27 hydra kernel: UDF-fs INFO UDF 0.9.1 (2000/02/29) Mounting
> volume 'UDF Volume', timestamp 2001/03/02 11:55 (1e98)

At the very least, run 0.9.3 from sourceforce (or the cvs version) and
see if it works any better.

Ben

Re: write to dvd ram

[cacook]

Many thanks Jim.  Now at least I have a way.

But I caution others that Linux modifies the UDF filesystem somehow, so that Winders can no longer understand it.  I nearly lost all my music & photo archives to this.  And attempts to rm or mv on a DVDRAM with UDF cause it to segfault & jam up.  There doesn't seem to be an answer to this.  (yes, I have written to the developer of cddriver; no response at all after two weeks)  UDF2 is just nonfunctional in Linux and I don't know why.

To recap: running Panasonic LF-D101 DVDRAM drive on SCSI (AHA2940) and
getting segfaults.  On-disk format is UDF2.0, as 2.1 won't mount.

Mount, ls, umount, mount, ls, umount, etc - no problem except filestructure is now no longer available to Winders. (CAUTION! Save data using Linux for recovery in Winders)

Mount, cp <20Mfile>, umount, mount, ls, (20Mfile), umount, mount, ls, (20Mfile),
rpm -q 20Mfile, umount, etc - no problem except filestructure no longer available to Winders.

Mount, rm <20Mfile>, Segmentation Fault, umount, (device busy), umount, (device busy), etc.  Reboot without reset and bootup hangs at Running Linuxconf hooks. Reset & system boots fine.  Mount, ls, (no files), umount, mount, ls, (no files), umount, etc.

Running RedHat Wolverine with HelixGnome & Nautilus.
--
C.

The best way out is always through.
      - Robert Frost  A Servant to Servants, 1914

Keywords: DVDRAM DVD-RAM LF-D101 LFD101 cdrecord


The log is:
Apr 15 20:58:27 hydra kernel: UDF-fs INFO UDF 0.9.1 (2000/02/29) Mounting
volume 'UDF Volume', timestamp 2001/03/02 11:55 (1e98)
Apr 15 20:59:31 hydra kernel: UDF-fs INFO UDF 0.9.1 (2000/02/29) Mounting
volume 'UDF Volume', timestamp 2001/03/02 11:55 (1e98)
Apr 15 20:59:50 hydra last message repeated 3 times
Apr 15 21:00:17 hydra mon[1258]: failure for servers http 987390017 localhost
Apr 15 21:01:11 hydra kernel: UDF-fs INFO UDF 0.9.1 (2000/02/29) Mounting
volume 'UDF Volume', timestamp 2001/03/02 11:55 (1e98)
Apr 15 21:03:25 hydra last message repeated 2 times
Apr 15 21:03:40 hydra kernel: kernel BUG at inode.c:890!
Apr 15 21:03:40 hydra kernel: invalid operand: 0000
Apr 15 21:03:40 hydra kernel: CPU:    0
Apr 15 21:03:40 hydra kernel: EIP:    0010:[iput_free+216/352]
Apr 15 21:03:40 hydra kernel: EIP:    0010:[<c01461c8>]
Apr 15 21:03:40 hydra kernel: EFLAGS: 00010286
Apr 15 21:03:40 hydra kernel: eax: 0000001b   ebx: cb1ad640   ecx: 00000004
edx: c5508840
Apr 15 21:03:40 hydra kernel: esi: c0319560   edi: cb4f2740   ebp: bffff678 esp:
c9d5ff20
Apr 15 21:03:40 hydra kernel: ds: 0018   es: 0018   ss: 0018
Apr 15 21:03:40 hydra kernel: Process rm (pid: 2254, stackpage=c9d5f000)
Apr 15 21:03:40 hydra kernel: Stack: c02a1610 c02a16f3 0000037a 00000000
00000012 c3920000 cffb3560 cb4f2740
Apr 15 21:03:40 hydra kernel:        cb1ad640 c0144a3c cb1ad640 00000184
fffffff0 c39229c0 cb4f2740 00000000
Apr 15 21:03:40 hydra kernel:        c39229c0 c013e31c cb4f2740 cfc83d40
c9d5ff9c 00000000 ffffffeb cb4f2740
Apr 15 21:03:40 hydra kernel: Call Trace: [error_table+39488/42452]
[error_table+39715/42452] [d_delete+76/112] [vfs_unlink+316/368]
[sys_unlink+150/272] [do_page_fault+0/1088] [system_call+51/56]
Apr 15 21:03:40 hydra kernel: Call Trace: [<c02a1610>] [<c02a16f3>]
[<c0144a3c>] [<c013e31c>] [<c013e3e6>] [<c0112de0>] [<c0108ffb>]
Apr 15 21:03:40 hydra kernel:
Apr 15 21:03:40 hydra kernel: Code: 0f 0b 83 c4 0c eb 69 90 39 1b 74 3c f6 83 f8 00 00 00 07 75
Apr 15 21:04:18 hydra mon[1258]: failure for servers http 987390258 localhost


ver_linux
Linux hydra.darkmatter.com 2.4.2-0.1.49 #1 Sun Apr 15 18:12:33 MDT 2001 i686 unknown

Gnu C                  2.96
Gnu make               3.79.1
binutils               2.10.91.0.2
util-linux             2.10r
modutils               2.4.2
e2fsprogs              1.19
reiserfsprogs          3.x.0b
PPP                    2.4.0
isdn4k-utils           3.1pre1
Linux C Library        2.2.2
Dynamic linker (ldd)   2.2.2
Procps                 2.0.7
Net-tools              1.57
Console-tools          0.3.3
Sh-utils               2.0
Modules Loaded         via82cxxx_audio ac97_codec binfmt_misc autofs
nls_iso8859-1 nls_cp437
cdrecord             1.9-6


"Hawthorne, Jim J SSI-ISEA" wrote:

> No problem with ext2 file system -- I have been using LM 7.2 with kernel
> 2.2.14 and it works straight out of the box. Newer kernel 2.4.x should also
> work .
> Have Toshiba w1101 scsi dvd ram and initio wide scsi card. I also use
> WINDOZE 2000 and use UDF for DVD RAM on WINDOZE 2000 (Instant Write from VOB
> at www.vob.de -- came with the drive).
>
> I use BRUBACK for backup to backup both Linux and W2K (Bruback will backup
> windoze filesystem from Linux -- no problem)
>
> format your media with mke2fs /dev/scd1 (or wherever your dvd ram is
> detected) -- just use defaults  takes about 1 min to format a 2.6 GB media.
>
> create a directory under /   say /dvdram
>
> then simply mount -t ext2 /dev/scd1 /dvdram      hey presto you should get
> read/write access to your drive
>
> your fstab entry should look something like this
>
> /dev/scd1 /dvdram ext2 noauto,rw,user,nosuid,sync
>
> I haven't played around with the UDF file system on LM 7.2 yet but if you
> keep separate media for Windoze and Linux then using ext2 for linux should
> not be a problem.
>
> BTW you can actually create a FAT32 file system on your device as well ( use
> DOSUTILS package) but perversely Windoze will not allow you to write to the
> device in this case ---- no driver available).  I understand that Windoze XP
> (or Whistler) will have native FAT32 support for DVD RAM drives.
>
> Hope this helps a bit
>
> cheers
> jim