Prev: Fixed: help for LILO with "too many" drives
Next: Slack 11.0 postfix from SlackBuilds - problem
From: fred on 7 Dec 2009 22:36
Upgrading from 10.2 to 13.0 and have some "burning" questions.
1) Is growisofs still the best method for burning data DVD's?
2) Does it still need the ide-scsi trick?
3) Does the ide-scsi trick work on serial-ata drives?

Thanks in advance,
Fred
From: Michael Black on 7 Dec 2009 23:13
On Mon, 7 Dec 2009, fred(a)vcoms.net wrote:

> Upgrading from 10.2 to 13.0 and have some "burning" questions.
> 1) Is growisofs still the best method for burning data DVD's?
> 2) Does it still need the ide-scsi trick?
No, that went out some releases back.
> 3) Does the ide-scsi trick work on serial-ata drives?
>
Not likely, since it's not needed for pata drives.

Michael

> Thanks in advance,
> Fred
>
From: Douglas Mayne on 8 Dec 2009 00:02
On Mon, 07 Dec 2009 21:36:34 -0600, fred wrote:

> Upgrading from 10.2 to 13.0 and have some "burning" questions.
> 1) Is growisofs still the best method for burning data DVD's?
> 2) Does it still need the ide-scsi trick?
> 3) Does the ide-scsi trick work on serial-ata drives?
>
> Thanks in advance,
> Fred
>
The cdrecord command now supports the features which previously required
growisofs. cdrecord even supports dual layer DVD's now, very large files,
etc. Those changes have allowed me to switch to using cdrecord as my
preferred command line burning tool. YMMV.
Also, AFAIK, ide-scsi is not necessary (beginning with 11.0 or 12.0 ?).

Although, I am just running 12.2 for now, and have limited experience
with 13.0, I know that there have been major changes that you will likely
notice when moving from 10.x to 13.0. The big changes include:
1. the default kernel requires an initrd,
2. the device directory uses automatic allocation (udev),
3. wireless support is working a lot better, and for a lot more devices.
4. Suspend and hibernate is working (via pm-utils)
5. Printing is managed by cups. HP devices have special support.

Probably, there are more things, too. The above is off the cuff. Of course
there is a lot of buzz about KDE, but I don't use it, so I'll leave
that alone.

--
Douglas Mayne
From: Eef Hartman on 8 Dec 2009 09:16
fred(a)vcoms.net wrote:
> Upgrading from 10.2 to 13.0 and have some "burning" questions.
> 1) Is growisofs still the best method for burning data DVD's?

It still works, if it's the BEST way I wouldn't know

> 2) Does it still need the ide-scsi trick?

No, that hasn't been needed for some time

> 3) Does the ide-scsi trick work on serial-ata drives?

No, but it isn't needed anyway as S-ATA drives use the SCSI handling
and addressing anyway, so all programs written FOR scsi will work
on S-ATA as well.
--
*******************************************************************
** Eef Hartman, Delft University of Technology, dept. SSC/ICT **
** e-mail: E.J.M.Hartman(a)tudelft.nl - phone: +31-15-278 82525 **
*******************************************************************
From: Douglas Mayne on 15 Dec 2009 18:52
On Tue, 15 Dec 2009 18:48:52 +0000, Joerg Schilling wrote:

> In article <pan.2009.12.08.05.02.57.342168(a)sl12.localnet>, Douglas Mayne
> <doug(a)sl12.localnet> wrote:
>
>>The cdrecord command now supports the features which previously required
>>growisofs. cdrecord even supports dual layer DVD's now, very large
>>files, etc. Those changes have allowed me to switch to using cdrecord as
>>my
>
> FYI:
>
> cdrecord writes DVDs since February 1998, this is 5 months after the
> first DVD writer was build and this was at a time when less than 50
> drives existed.....
>
> growisofs started to exist 4 years later.
>
> I was never forced to use growisofs in my life.
>
> Since 3.5 years, cdrecord supports auto-target mode and in case there is
> only one CD/DVD drive in the system, you do not need to specify the dev=
> parameter.
>
I meant no offense. The only problems I had with previous versions of
cdrecord was the inability to record files over 2G in size, and that made
it necessary for me to use alternate tools. The last time I discussed
this on this newsgroup with you, you pointed out that it made no sense
for me to record cd's with one tool, and to record dvd's with another.
After that discussion, I took another look at mkisofs and cdrecord and
decided you were right. Your toolset had the features that I needed,
including files over 4G in size (for dual layer media and using the iso-
level 3).

That, in fact, was my point to the OP: your tools work.

I see your other post and I will respond to that shortly.

--
Douglas Mayne
 |  Next  |  Last
Pages: 1 2
Prev: Fixed: help for LILO with "too many" drives
Next: Slack 11.0 postfix from SlackBuilds - problem