> discs created with mkudffs do work fine on windows XP but not on 2000 or less.
Interesting. I was wondering whether I should shift from ext2 to udf,
quick tests show that mkudffs is fine. mkisofs -udf produces rubbish. Is
there another alternative? (I'm only really interested in Linux.)
Volker
Hi,
> If you only want to store files >2GB (or udf, with mkudffs), and the disk can be mounted in the usual
> fashion (hint: loop mount). Whether it can be read on Microshite is
> none of my concern, if you use DVDs as tar tapes it sounds like it's
> none of yours either.
discs created with mkud
On Sat, 14 Jun 2003, Volker Kuhlmann wrote:
> On Sat 14 Jun 2003 14:00:07 NZST +1200, Robert M. Stockmann wrote:
>
> > this mkisofs is a component of cdrtools-2.0 which i patched see :
> >
> > ftp://crashrecovery.org/pub/linux/cdrtools/
>
> I wish people would give some useful information with
Quoting Volker Kuhlmann <[EMAIL PROTECTED]>:
> Are you sure? Joliet is an optional extra, on unix it's just a waste
> of space.
Joliet extensions have various limitations on file paths and names. I run
into them regularly. Not using Joliet fixes the issue (bare ISO9660 or
ISO9660+RockRidge-onl
On Sat 14 Jun 2003 14:00:07 NZST +1200, Robert M. Stockmann wrote:
> this mkisofs is a component of cdrtools-2.0 which i patched see :
>
> ftp://crashrecovery.org/pub/linux/cdrtools/
I wish people would give some useful information with their patches,
like some basic info, e.g. what the patch ac
> Is there a good "par" HOWTO somewhere?
Do you need one? There's a lot of info on the sourceforge site, and with
the version 2 source code. Version 1 seems pretty simple and just
compiles. Version 2 doesn't compile with current versiosn of
automake/autoconf gcc 3.3.
> > What I can't do, is repai
Quoting Volker Kuhlmann <[EMAIL PROTECTED]>:
> Are you sure? Joliet is an optional extra, on unix it's just a waste
> of space.
Joliet extensions have various limitations on file paths and names. I run into them
regularly. Not
using Joliet fixes the issue (bare ISO9660 or ISO9660+RockRidge-on
Quoting André Dalle <[EMAIL PROTECTED]>:
> What I did myself, was to split my large files into smaller chunks.
> I use GNU 'split' to split it into 50MB chunks, then I use parity
> archives ('par' utility) to generate redundancy data for my split
> volumes.
> This way I can recover the large file
On Fri, 13 Jun 2003, André Dalle wrote:
I can make upto 4.7 Gig udf iso's without problems here and possibly even
bigger upto the filesize limit on current ext2/ext3 filesystems in
linux systems running kernel 2.4.18 and higher :
/usr/bin/mkisofs -o /mnt/backup/disc1.raw
-l \# Allow
Thanks for posting that! I was wondering what other people do.
> I was trying to save multi gigabyte database dumps to dvd, but
> limitations withing mkisofs (more specifically the joliet file system)
Are you sure? Joliet is an optional extra, on unix it's just a waste of
space.
> The workaround
What I did myself, was to split my large files into smaller chunks.
I use GNU 'split' to split it into 50MB chunks, then I use parity
archives ('par' utility) to generate redundancy data for my split
volumes.
This way I can recover the large file even if data errors on the disc
prevent me from re
While this is not a mkisofs related topic, it does relate to dvdrecord.
I see so many problems, and few solutions on this list that I decided to
post a solution, of sorts.
I was trying to save multi gigabyte database dumps to dvd, but
limitations withing mkisofs (more specifically the joliet file
12 matches
Mail list logo
