Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 16 Jan 2010 19:49:03 +0100
From:      Marc Fonvieille <blackend@freebsd.org>
To:        CeDeROM <tomek.cedro@gmail.com>
Cc:        doc@freebsd.org, Marius Strobl <marius@alchemy.franken.de>
Subject:   Re: cdrecord and burning disks on FreeBSD with filesize over 4GB
Message-ID:  <20100116184903.GA3235@gothic.blackend.org>
In-Reply-To: <3fcfb0ba1001160754v6f52ea9eyfc609cbee6889efa@mail.gmail.com>
References:  <3fcfb0ba1001160513s260a798cl76cf7b1cf45ac6cb@mail.gmail.com> <20100116144420.GC1272@gothic.blackend.org> <20100116153838.GE18141@alchemy.franken.de> <3fcfb0ba1001160754v6f52ea9eyfc609cbee6889efa@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jan 16, 2010 at 03:54:07PM +0000, CeDeROM wrote:
> On Sat, Jan 16, 2010 at 3:38 PM, Marius Strobl
> <marius@alchemy.franken.de> wrote:
> >> We can add a note to the Handbook but it'd a better idea to have the fix in
> >> default cdrtools port, I mean the one used by all burning applications.
> >>
> >> I let marius@ (the port maintainer) choosing the best solution.
> >
> > Patching cdrtools is a complicated topic as the author is very strict
> > about the license so it typically means creating an unsupported fork
> > which needs to be compiled with -DSOURCE_MODIFIED etc. Backporting
> > features to 2.01 also isn't easily possible as for most parts it's
> > GPL in 2.01 versus CDDL in 2.01.01. As long a the release engineering
> > depends on a working mkisofs I'm also reluctant to change the version
> > tracked by sysutils/cdrtools to the alpha releases. If a port requires
> > features from 2.01.01 it should just depend on sysutils/cdrtools-devel
> > explicitly. There are some differences in pkg-plist files of the two
> > cdrtools ports which should make this actually possible.
> 
> Thank you Marius, my opinion is the same. I will try to ask author of
> the cdrtools for some explict date of the new release.
> 
> Marc - I still think there is a need to add info about "-iso-level 3"
> and the "-udf -iso-level 3" switch of mkisofs to the Handbook, as this
> option allows burning files with per-file-size limit >4GB and use
> level 3 of the ISO-9660. This option must be applied to mkisofs and
> dvd+rw-tools, neverthless of the mkisofs release, so giving this hint
> explictly in a Handbook will help commandline users. The other thing
> is that it works only in releases older than 2.01.01aXXX and should
> work with nearest stable release.
> 
> Please follow discussion on the usenet - there are all of the details
> necessary to acknowlege my point of view.
>

So, does the following is Ok for addition to the Handbook?

--
Note:
If you need to burn files larger than 4.38 GB, for example in the case
of a double layer media, the -iso-level 3 option must be passed to
mkisofs(8).  Therefore this option has to be added to any growisofs(1)
command line, e.g.:

# growisofs -dvd-compat -Z /dev/cd0 -iso-level 3 -J -R /path/to/data

or 

# growisofs -dvd-compat -Z /dev/cd0=imagefile.iso -iso-level 3

Be sure to have the sysutils/cdrtools-devel port installed instead of
sysutils/cdrtools.  This later comes with a mkisofs(8) version that does
not work very well with the -iso-level 3 option.
--


-- 
Marc



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100116184903.GA3235>