Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.misc > #3615 > unrolled thread
| Started by | Todd <Todd@invalid.invalid> |
|---|---|
| First post | 2012-01-07 20:15 -0800 |
| Last post | 2013-03-21 14:06 +0000 |
| Articles | 20 on this page of 147 — 22 participants |
Back to article view | Back to comp.os.linux.misc
Why are mkisofs ISO's so large? Todd <Todd@invalid.invalid> - 2012-01-07 20:15 -0800
Re: Why are mkisofs ISO's so large? unruh <unruh@invalid.ca> - 2012-01-08 06:03 +0000
Re: Why are mkisofs ISO's so large? Todd <Todd@invalid.invalid> - 2012-01-07 23:33 -0800
Re: Why are mkisofs ISO's so large? Todd <Todd@invalid.invalid> - 2012-01-07 23:40 -0800
Re: Why are mkisofs ISO's so large? unruh <unruh@invalid.ca> - 2012-01-08 22:10 +0000
Re: Why are mkisofs ISO's so large? unruh <unruh@invalid.ca> - 2012-01-08 22:07 +0000
Re: Why are mkisofs ISO's so large? Joerg.Schilling@fokus.fraunhofer.de - 2013-03-21 14:07 +0000
Re: Why are mkisofs ISO's so large? Todd <Todd@invalid.invalid> - 2012-01-23 10:08 -0800
Re: Why are mkisofs ISO's so large? unruh <unruh@invalid.ca> - 2012-01-24 05:04 +0000
Re: Why are mkisofs ISO's so large? Todd <Todd@invalid.invalid> - 2012-01-24 11:04 -0800
Re: Why are mkisofs ISO's so large? Loki Harfagr <l0k1@thedarkdesign.free.fr.INVALID> - 2012-01-25 18:33 +0000
Re: Why are mkisofs ISO's so large? unruh <unruh@invalid.ca> - 2012-01-25 20:17 +0000
Re: Why are mkisofs ISO's so large? Richard Kettlewell <rjk@greenend.org.uk> - 2012-01-25 21:37 +0000
Re: Why are mkisofs ISO's so large? unruh <unruh@invalid.ca> - 2012-01-25 22:32 +0000
Re: Why are mkisofs ISO's so large? Richard Kettlewell <rjk@greenend.org.uk> - 2012-01-26 01:33 +0000
Re: Why are mkisofs ISO's so large? unruh <unruh@invalid.ca> - 2012-01-26 07:56 +0000
Re: Why are mkisofs ISO's so large? Baho Utot <baho-utot@invlaid.com> - 2012-01-26 09:26 -0500
Re: Why are mkisofs ISO's so large? unruh <unruh@invalid.ca> - 2012-01-26 22:43 +0000
Re: Why are mkisofs ISO's so large? J G Miller <miller@yoyo.ORG> - 2012-01-27 00:43 +0000
Re: Why are mkisofs ISO's so large? Richard Kettlewell <rjk@greenend.org.uk> - 2012-01-26 20:08 +0000
Re: Why are mkisofs ISO's so large? unruh <unruh@invalid.ca> - 2012-01-26 22:55 +0000
Re: Why are mkisofs ISO's so large? Baho Utot <baho-utot@invlaid.com> - 2012-01-26 18:15 -0500
Re: Why are mkisofs ISO's so large? The Natural Philosopher <tnp@invalid.invalid> - 2012-01-27 07:55 +0000
Re: Why are mkisofs ISO's so large? Baho Utot <baho-utot@invlaid.com> - 2012-01-27 07:51 -0500
Re: Why are mkisofs ISO's so large? Richard Kettlewell <rjk@greenend.org.uk> - 2012-01-27 09:29 +0000
Re: Why are mkisofs ISO's so large? unruh <unruh@invalid.ca> - 2012-01-27 20:35 +0000
Re: Why are mkisofs ISO's so large? Peter Köhlmann <peter-koehlmann@t-online.de> - 2012-01-27 22:45 +0100
Re: Why are mkisofs ISO's so large? Baho Utot <baho-utot@invlaid.com> - 2012-01-26 18:58 -0500
Re: Why are mkisofs ISO's so large? John Hasler <jhasler@newsguy.com> - 2012-01-27 07:22 -0600
Re: Why are mkisofs ISO's so large? Joerg.Schilling@fokus.fraunhofer.de - 2013-03-21 14:47 +0000
Re: Why are mkisofs ISO's so large? unruh <unruh@invalid.ca> - 2012-01-27 20:47 +0000
Re: Why are mkisofs ISO's so large? Peter Köhlmann <peter-koehlmann@t-online.de> - 2012-01-27 22:03 +0100
Re: Why are mkisofs ISO's so large? unruh <unruh@invalid.ca> - 2012-01-27 21:38 +0000
Re: Why are mkisofs ISO's so large? The Natural Philosopher <tnp@invalid.invalid> - 2012-01-27 21:54 +0000
Re: Why are mkisofs ISO's so large? unruh <unruh@invalid.ca> - 2012-01-28 00:00 +0000
Re: Why are mkisofs ISO's so large? The Natural Philosopher <tnp@invalid.invalid> - 2012-01-28 01:32 +0000
Re: Why are mkisofs ISO's so large? unruh <unruh@invalid.ca> - 2012-01-28 01:54 +0000
Re: Why are mkisofs ISO's so large? Baho Utot <baho-utot@invlaid.com> - 2012-01-29 08:01 -0500
Re: Why are mkisofs ISO's so large? unruh <unruh@invalid.ca> - 2012-01-29 19:09 +0000
Re: Why are mkisofs ISO's so large? Darren Salt <news@youmustbejoking.demon.cu.invalid> - 2012-01-31 17:57 +0000
Re: Why are mkisofs ISO's so large? unruh <unruh@invalid.ca> - 2012-01-31 21:12 +0000
Re: Why are mkisofs ISO's so large? Dan Espen <despen@verizon.net> - 2012-01-27 16:44 -0500
Re: Why are mkisofs ISO's so large? Baho Utot <baho-utot@invlaid.com> - 2012-01-27 16:39 -0500
Re: Why are mkisofs ISO's so large? lynxuser@mouse-potato.com - 2012-01-27 14:17 +0000
Re: Why are mkisofs ISO's so large? Baho Utot <baho-utot@invlaid.com> - 2012-01-27 09:44 -0500
Re: Why are mkisofs ISO's so large? Feranija <feranija@mouse-potato.com> - 2012-01-27 07:02 -0800
Re: Why are mkisofs ISO's so large? unruh <unruh@invalid.ca> - 2012-01-27 20:53 +0000
Re: Why are mkisofs ISO's so large? Joerg.Schilling@fokus.fraunhofer.de - 2013-03-21 14:54 +0000
Re: Why are mkisofs ISO's so large? Joerg.Schilling@fokus.fraunhofer.de - 2013-03-21 14:43 +0000
Re: Why are mkisofs ISO's so large? unruh <unruh@invalid.ca> - 2013-03-21 18:02 +0000
Re: Why are mkisofs ISO's so large? Octothorpe <Octothorpe@invalid.com> - 2013-03-21 17:30 -0400
Re: Why are mkisofs ISO's so large? unruh <unruh@invalid.ca> - 2013-03-21 23:01 +0000
Re: Why are mkisofs ISO's so large? Robert Riches <spamtrap42@jacob21819.net> - 2013-03-22 04:10 +0000
Re: Why are mkisofs ISO's so large? Octothorpe <Octothorpe@invalid.com> - 2013-03-22 07:19 -0400
Re: Why are mkisofs ISO's so large? unruh <unruh@invalid.ca> - 2013-03-22 17:48 +0000
Re: Why are mkisofs ISO's so large? Octothorpe <Octothorpe@invalid.com> - 2013-03-22 17:51 -0400
Re: Why are mkisofs ISO's so large? unruh <unruh@invalid.ca> - 2013-03-22 17:46 +0000
Re: Why are mkisofs ISO's so large? Robert Riches <spamtrap42@jacob21819.net> - 2013-03-23 04:45 +0000
Re: Why are mkisofs ISO's so large? Robert Riches <spamtrap42@jacob21819.net> - 2013-03-23 04:47 +0000
Re: Why are mkisofs ISO's so large? Balwinder S Dheeman <bsd.SANSPAM@anu.homelinux.net> - 2013-03-23 21:26 +0530
Re: Why are mkisofs ISO's so large? Joerg.Schilling@fokus.fraunhofer.de - 2013-03-22 18:05 +0000
Re: Why are mkisofs ISO's so large? Octothorpe <Octothorpe@invalid.com> - 2013-03-22 17:57 -0400
Re: Why are mkisofs ISO's so large? Octothorpe <Octothorpe@invalid.com> - 2013-03-22 07:17 -0400
Re: Why are mkisofs ISO's so large? Roger Blake <rogblake@iname.invalid> - 2013-03-23 01:30 +0000
Re: Why are mkisofs ISO's so large? Bit Twister <BitTwister@mouse-potato.com> - 2013-03-23 02:40 +0000
Re: Why are mkisofs ISO's so large? Roger Blake <rogblake@iname.invalid> - 2013-03-23 13:33 +0000
Re: Why are mkisofs ISO's so large? Octothorpe <Octothorpe@invalid.com> - 2013-03-23 10:41 -0400
Re: Why are mkisofs ISO's so large? Roger Blake <rogblake@iname.invalid> - 2013-03-23 15:29 +0000
Re: Why are mkisofs ISO's so large? Octothorpe <Octothorpe@invalid.com> - 2013-03-23 11:57 -0400
Re: Why are mkisofs ISO's so large? J G Miller <miller@yoyo.ORG> - 2013-03-23 17:24 +0000
Re: Why are mkisofs ISO's so large? Roger Blake <rogblake@iname.invalid> - 2013-03-23 19:02 +0000
Re: Why are mkisofs ISO's so large? J G Miller <miller@yoyo.ORG> - 2013-03-23 20:00 +0000
Re: Why are mkisofs ISO's so large? Roger Blake <rogblake@iname.invalid> - 2013-03-23 23:22 +0000
Re: Why are mkisofs ISO's so large? Octothorpe <Octothorpe@invalid.com> - 2013-03-23 19:44 -0400
Re: Why are mkisofs ISO's so large? Roger Blake <rogblake@iname.invalid> - 2013-03-23 23:56 +0000
Re: Why are mkisofs ISO's so large? Octothorpe <Octothorpe@invalid.com> - 2013-03-23 20:36 -0400
Re: Why are mkisofs ISO's so large? Roger Blake <rogblake@iname.invalid> - 2013-03-24 00:54 +0000
Re: Why are mkisofs ISO's so large? Joerg.Schilling@fokus.fraunhofer.de - 2013-03-22 18:02 +0000
Re: Why are mkisofs ISO's so large? Dan Espen <despen@verizon.net> - 2013-03-22 14:34 -0400
Re: Why are mkisofs ISO's so large? Joerg.Schilling@fokus.fraunhofer.de - 2013-03-23 11:48 +0000
Re: Why are mkisofs ISO's so large? Roger Blake <rogblake@iname.invalid> - 2013-03-23 13:35 +0000
Re: Why are mkisofs ISO's so large? Dan Espen <despen@verizon.net> - 2013-03-23 11:59 -0400
Re: Why are mkisofs ISO's so large? Joerg.Schilling@fokus.fraunhofer.de - 2013-03-23 16:35 +0000
Re: Why are mkisofs ISO's so large? Dan Espen <despen@verizon.net> - 2013-03-23 13:09 -0400
Re: Why are mkisofs ISO's so large? unruh <unruh@invalid.ca> - 2013-03-23 17:14 +0000
Re: Why are mkisofs ISO's so large? Dan Espen <despen@verizon.net> - 2013-03-23 13:33 -0400
Re: Why are mkisofs ISO's so large? Bit Twister <BitTwister@mouse-potato.com> - 2013-03-23 17:58 +0000
Re: Why are mkisofs ISO's so large? Dan Espen <despen@verizon.net> - 2013-03-23 14:19 -0400
Re: Why are mkisofs ISO's so large? Joerg.Schilling@fokus.fraunhofer.de - 2013-03-23 19:18 +0000
Re: Why are mkisofs ISO's so large? Roger Blake <rogblake@iname.invalid> - 2013-03-23 19:18 +0000
Re: Why are mkisofs ISO's so large? Dan Espen <despen@verizon.net> - 2013-03-23 17:25 -0400
Re: Why are mkisofs ISO's so large? <nunojsilva@invalid.invalid> (Nuno Silva) - 2013-03-24 00:05 +0200
Re: Why are mkisofs ISO's so large? unruh <unruh@invalid.ca> - 2013-03-23 23:39 +0000
Re: Why are mkisofs ISO's so large? <nunojsilva@invalid.invalid> (Nuno Silva) - 2013-03-24 09:00 +0200
Re: Why are mkisofs ISO's so large? J G Miller <miller@yoyo.ORG> - 2013-03-24 16:04 +0000
Re: Why are mkisofs ISO's so large? Dan Espen <despen@verizon.net> - 2013-03-24 13:46 -0400
Re: Why are mkisofs ISO's so large? J G Miller <miller@yoyo.ORG> - 2013-03-24 19:07 +0000
Re: Why are mkisofs ISO's so large? Dan Espen <despen@verizon.net> - 2013-03-24 17:06 -0400
Re: Why are mkisofs ISO's so large? "Nuno J. Silva (aka njsg)" <njsg@invalid.invalid> - 2013-03-24 21:20 +0000
Re: Why are mkisofs ISO's so large? Fedora bug tracking Dan Espen <despen@verizon.net> - 2013-03-24 20:08 -0400
Re: Why are mkisofs ISO's so large? Fedora bug tracking Joerg.Schilling@fokus.fraunhofer.de - 2013-03-25 09:59 +0000
Re: Why are mkisofs ISO's so large? Joerg.Schilling@fokus.fraunhofer.de - 2013-03-24 22:17 +0000
Re: Why are mkisofs ISO's so large? "Nuno J. Silva (aka njsg)" <njsg@invalid.invalid> - 2013-03-24 23:07 +0000
Re: Why are mkisofs ISO's so large? Joerg.Schilling@fokus.fraunhofer.de - 2013-03-25 09:57 +0000
Re: Why are mkisofs ISO's so large? Joerg.Schilling@fokus.fraunhofer.de - 2013-03-24 22:35 +0000
Re: Why are mkisofs ISO's so large? "Nuno J. Silva (aka njsg)" <njsg@invalid.invalid> - 2013-03-24 23:03 +0000
Re: Why are mkisofs ISO's so large? Joerg.Schilling@fokus.fraunhofer.de - 2013-03-24 21:42 +0000
Re: Why are mkisofs ISO's so large? Joerg.Schilling@fokus.fraunhofer.de - 2013-03-24 21:31 +0000
Re: Why are mkisofs ISO's so large? <nunojsilva@invalid.invalid> (Nuno Silva) - 2013-03-24 09:00 +0200
Re: Why are mkisofs ISO's so large? Joerg.Schilling@fokus.fraunhofer.de - 2013-03-24 11:29 +0000
Re: Why are mkisofs ISO's so large? unruh <unruh@invalid.ca> - 2013-03-23 23:34 +0000
Re: Why are mkisofs ISO's so large? Octothorpe <Octothorpe@invalid.com> - 2013-03-23 19:58 -0400
Re: Why are mkisofs ISO's so large? Joerg.Schilling@fokus.fraunhofer.de - 2013-03-24 11:31 +0000
Re: Why are mkisofs ISO's so large? Octothorpe <Octothorpe@invalid.com> - 2013-03-24 08:56 -0400
Re: Why are mkisofs ISO's so large? Joerg.Schilling@fokus.fraunhofer.de - 2013-03-30 12:06 +0000
Re: Why are mkisofs ISO's so large? Octothorpe <Octothorpe@invalid.com> - 2013-03-30 13:24 -0400
Re: Why are mkisofs ISO's so large? unruh <unruh@invalid.ca> - 2013-03-24 17:46 +0000
Re: Why are mkisofs ISO's so large? Octothorpe <Octothorpe@invalid.com> - 2013-03-24 15:53 -0400
Re: Why are mkisofs ISO's so large? Joerg.Schilling@fokus.fraunhofer.de - 2013-03-24 21:45 +0000
Re: Why are mkisofs ISO's so large? Octothorpe <Octothorpe@invalid.com> - 2013-03-24 21:51 -0400
Re: Why are mkisofs ISO's so large? Joerg.Schilling@fokus.fraunhofer.de - 2013-03-24 20:53 +0000
Re: Why are mkisofs ISO's so large? Richard Kettlewell <rjk@greenend.org.uk> - 2013-03-25 08:32 +0000
Re: Why are mkisofs ISO's so large? Peter Köhlmann <peter-koehlmann@t-online.de> - 2013-03-23 17:22 +0100
Re: Why are mkisofs ISO's so large? unruh <unruh@invalid.ca> - 2013-03-23 17:13 +0000
Re: Why are mkisofs ISO's so large? Joerg.Schilling@fokus.fraunhofer.de - 2013-03-23 18:44 +0000
Re: Why are mkisofs ISO's so large? Robert Riches <spamtrap42@jacob21819.net> - 2013-03-24 04:15 +0000
Re: Why are mkisofs ISO's so large? Joerg.Schilling@fokus.fraunhofer.de - 2013-03-24 11:34 +0000
Re: Why are mkisofs ISO's so large? Joerg.Schilling@fokus.fraunhofer.de - 2013-03-22 17:56 +0000
Re: Why are mkisofs ISO's so large? Richard Kettlewell <rjk@greenend.org.uk> - 2013-03-22 18:39 +0000
Re: Why are mkisofs ISO's so large? unruh <unruh@invalid.ca> - 2013-03-22 22:14 +0000
Re: Why are mkisofs ISO's so large? Joerg.Schilling@fokus.fraunhofer.de - 2013-03-23 16:25 +0000
Re: Why are mkisofs ISO's so large? Octothorpe <Octothorpe@invalid.com> - 2013-03-23 13:03 -0400
Re: Why are mkisofs ISO's so large? Joerg.Schilling@fokus.fraunhofer.de - 2013-03-23 18:39 +0000
Re: Why are mkisofs ISO's so large? Octothorpe <Octothorpe@invalid.com> - 2013-03-23 16:37 -0400
Re: Why are mkisofs ISO's so large? Octothorpe <Octothorpe@invalid.com> - 2013-03-21 17:23 -0400
Re: Why are mkisofs ISO's so large? Joerg.Schilling@fokus.fraunhofer.de - 2013-03-22 17:58 +0000
Re: Why are mkisofs ISO's so large? Octothorpe <Octothorpe@invalid.com> - 2013-03-22 17:53 -0400
Re: Why are mkisofs ISO's so large? The Natural Philosopher <tnp@invalid.invalid> - 2013-03-23 09:20 +0000
Re: Why are mkisofs ISO's so large? Joerg.Schilling@fokus.fraunhofer.de - 2013-03-21 14:35 +0000
Re: Why are mkisofs ISO's so large? Peter Köhlmann <peter-koehlmann@t-online.de> - 2012-01-25 23:28 +0100
Re: Why are mkisofs ISO's so large? unruh <unruh@invalid.ca> - 2012-01-26 07:41 +0000
Re: Why are mkisofs ISO's so large? Joerg.Schilling@fokus.fraunhofer.de - 2013-03-21 14:31 +0000
Re: Why are mkisofs ISO's so large? Joerg.Schilling@fokus.fraunhofer.de - 2013-03-21 14:23 +0000
Re: Why are mkisofs ISO's so large? Joerg.Schilling@fokus.fraunhofer.de - 2013-03-21 14:21 +0000
Re: Why are mkisofs ISO's so large? Todd <Todd@invalid.invalid> - 2012-01-26 10:38 -0800
Re: Why are mkisofs ISO's so large? root <NoEMail@home.org> - 2012-01-08 15:50 +0000
Re: Why are mkisofs ISO's so large? Joerg.Schilling@fokus.fraunhofer.de - 2013-03-21 14:06 +0000
Page 6 of 8 — ← Prev page 1 2 3 4 5 [6] 7 8 Next page →
| From | Joerg.Schilling@fokus.fraunhofer.de |
|---|---|
| Date | 2013-03-25 09:59 +0000 |
| Subject | Re: Why are mkisofs ISO's so large? Fedora bug tracking |
| Message-ID | <kip76n$gea$2@news.albasani.net> |
| In reply to | #7649 |
In article <icr4j4nxy1.fsf_-_@home.home>,
Dan Espen <despen@verizon.net> wrote:
>>>> Fedora is released regardless of whether the bug was ever
>>>> acknowledged or fixed.
>>>
>>> I've reported Fedora bugs. Nothing like that ever happened to me.
>>>
>>> In general, problems get fixed when they affect someone that can fix
>>> them. I've fixed a few, but haven't had any of those CD or DVD problems
>>> so I haven't tried to fix any of them.
>>
>> And, just like all this "wodim works" thing, that it never happened to
>> you does not mean it doesn't happen. Fedora is to bug tracking systems
>> like some web fora moderators are to webfora: "oh it's old you can't
>> reply to it".
>
>I've reported bugs more than once.
>I gotten replies, action and fixes too.
>
>Sorry you didn't have the same experience.
>
>Fedora bug tracking is free in both senses of the word.
>I can't see criticizing it under any circumstance.
You can't blame the bug tracking system for that problem, because it was caused
by humans.
In fact, there have been aprox. 100 bugs in the system related to "cdrkit".
Most of them have been closed because it is easier to close bug entries than to
fix the related bugs.
--
EMail:joerg@schily.net (home) Jörg Schilling D-13353 Berlin
js@cs.tu-berlin.de (uni)
joerg.schilling@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily
[toc] | [prev] | [next] | [standalone]
| From | Joerg.Schilling@fokus.fraunhofer.de |
|---|---|
| Date | 2013-03-24 22:17 +0000 |
| Message-ID | <kinu2f$88e$1@news.albasani.net> |
| In reply to | #7634 |
In article <icd2uopkwt.fsf@home.home>, Dan Espen <despen@verizon.net> wrote:
>J G Miller <miller@yoyo.ORG> writes:
>
>> On Sun, 24 Mar 2013 13:46:04 -0400, Dan Espen wrote:
>>
>>> Can you provide a link? I don't see them.
>>
>> I was referring specifically to all Debian packages related to cdrkit source.
>>
>> <http://bugs.debian.ORG/cgi-bin/pkgreport.cgi?ordering=normal;archive=0;src=cdrkit;dist=unstable;repeatmerged=0>
>>
>> It is interesting to note that a bug was reported in November, 2008
>> and a patch supplied to fix it --
>
>Here's an interesting one:
>
>k3b: Burns coasters when copying audio CDs
>
> As I understand, you needn't RAW mode if you write audio tracks from .wav
> files (possibly you never need it for CDDA tracks, if it's usual CDDA?).
> And so -raw96r option in second code is wrong.
> If k3b does this, possibly this cause a problem. Then, may be for RAW mode
> app needs priviledges, but k3b does not supply cdrecord piece with them
> for copying audio. So, you got a permissions error.
k3b prefers cdrecord over wodim - the authors know why ;-)
On the other side, this may be a typical problem caused by not being root.
Eduard Bloch, who has no clue on SCSI (in special on Linux) is responsible for
not installing wodim suid root. He did even remove warnings that are usually
written by cdrecord in case that there are permission problems.
Before 2004, Linux did require a program to be root when opening the SCSI
devices in order to be able to send any SCSI command.
After that time, Linux requires a program to be root while sending the related
commands.
If you use an unmodified cdrecord, you will see a warning when cdrecord is
missing the needed privileges - cdrecord abort then. As Bloch did remove these
warnings, cdrecord tries to continue instead of aborting but may fail later
with unexplainable problems.
--
EMail:joerg@schily.net (home) Jörg Schilling D-13353 Berlin
js@cs.tu-berlin.de (uni)
joerg.schilling@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily
[toc] | [prev] | [next] | [standalone]
| From | "Nuno J. Silva (aka njsg)" <njsg@invalid.invalid> |
|---|---|
| Date | 2013-03-24 23:07 +0000 |
| Message-ID | <kio0vi$u1f$2@news.datemas.de> |
| In reply to | #7640 |
On 2013-03-24, Joerg.Schilling@fokus.fraunhofer.de <Joerg.Schilling@fokus.fraunhofer.de> wrote: > In article <icd2uopkwt.fsf@home.home>, Dan Espen <despen@verizon.net> wrote: >>J G Miller <miller@yoyo.ORG> writes: >> >>> On Sun, 24 Mar 2013 13:46:04 -0400, Dan Espen wrote: >>> >>>> Can you provide a link? I don't see them. >>> >>> I was referring specifically to all Debian packages related to cdrkit source. >>> >>> <http://bugs.debian.ORG/cgi-bin/pkgreport.cgi?ordering=normal;archive=0;src=cdrkit;dist=unstable;repeatmerged=0> >>> >>> It is interesting to note that a bug was reported in November, 2008 >>> and a patch supplied to fix it -- >> >>Here's an interesting one: >> >>k3b: Burns coasters when copying audio CDs >> >> As I understand, you needn't RAW mode if you write audio tracks from .wav >> files (possibly you never need it for CDDA tracks, if it's usual CDDA?). >> And so -raw96r option in second code is wrong. >> If k3b does this, possibly this cause a problem. Then, may be for RAW mode >> app needs priviledges, but k3b does not supply cdrecord piece with them >> for copying audio. So, you got a permissions error. > > k3b prefers cdrecord over wodim - the authors know why ;-) > > On the other side, this may be a typical problem caused by not being root. > > Eduard Bloch, who has no clue on SCSI (in special on Linux) is responsible for > not installing wodim suid root. He did even remove warnings that are usually > written by cdrecord in case that there are permission problems. > > Before 2004, Linux did require a program to be root when opening the SCSI > devices in order to be able to send any SCSI command. > > After that time, Linux requires a program to be root while sending the related > commands. Having write permissions on the device is not enough? > If you use an unmodified cdrecord, you will see a warning when cdrecord is > missing the needed privileges - cdrecord abort then. As Bloch did remove these > warnings, cdrecord tries to continue instead of aborting but may fail later > with unexplainable problems. Either linux is not signaling errors or he did actually break the program, because I'd really expect an error to be triggered in this case... -- Nuno Silva (aka njsg) http://njsg.sdf-eu.org/
[toc] | [prev] | [next] | [standalone]
| From | Joerg.Schilling@fokus.fraunhofer.de |
|---|---|
| Date | 2013-03-25 09:57 +0000 |
| Message-ID | <kip72k$gea$1@news.albasani.net> |
| In reply to | #7645 |
In article <kio0vi$u1f$2@news.datemas.de>,
Nuno J. Silva (aka njsg) <njsg@invalid.invalid> wrote:
>> Before 2004, Linux did require a program to be root when opening the SCSI
>> devices in order to be able to send any SCSI command.
>>
>> After that time, Linux requires a program to be root while sending the related
>> commands.
>
>Having write permissions on the device is not enough?
It was before 2004, but then a novice programmer (Douglas Gilbert) "enhanced"
the driver to permit to send SCSI commands even in case that only read
permissions are hold.
A few months later, Linus Torvalds did not fix this bug but rather broke the
interface..... now we have to live with this situation.
>> If you use an unmodified cdrecord, you will see a warning when cdrecord is
>> missing the needed privileges - cdrecord abort then. As Bloch did remove these
>> warnings, cdrecord tries to continue instead of aborting but may fail later
>> with unexplainable problems.
>
>Either linux is not signaling errors or he did actually break the
>program, because I'd really expect an error to be triggered in this
>case...
He did actually break the program.
--
EMail:joerg@schily.net (home) Jörg Schilling D-13353 Berlin
js@cs.tu-berlin.de (uni)
joerg.schilling@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily
[toc] | [prev] | [next] | [standalone]
| From | Joerg.Schilling@fokus.fraunhofer.de |
|---|---|
| Date | 2013-03-24 22:35 +0000 |
| Message-ID | <kinv42$88e$2@news.albasani.net> |
| In reply to | #7634 |
In article <icd2uopkwt.fsf@home.home>, Dan Espen <despen@verizon.net> wrote:
>k3b: Burns coasters when copying audio CDs
>
> As I understand, you needn't RAW mode if you write audio tracks from .wav
> files (possibly you never need it for CDDA tracks, if it's usual CDDA?).
> And so -raw96r option in second code is wrong.
Maybe I should add a short note: you need to use -raw96r if you are using a
LiteON drive. The firmware in these drives is buggy and would otherwise create
defective audio CDs, that e.g. have wrong pregaps and time stamps that count
backwards.
K3b is correct in being careful and using -raw96r.
--
EMail:joerg@schily.net (home) Jörg Schilling D-13353 Berlin
js@cs.tu-berlin.de (uni)
joerg.schilling@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily
[toc] | [prev] | [next] | [standalone]
| From | "Nuno J. Silva (aka njsg)" <njsg@invalid.invalid> |
|---|---|
| Date | 2013-03-24 23:03 +0000 |
| Message-ID | <kio0ni$u1f$1@news.datemas.de> |
| In reply to | #7641 |
On 2013-03-24, Joerg.Schilling@fokus.fraunhofer.de <Joerg.Schilling@fokus.fraunhofer.de> wrote: > In article <icd2uopkwt.fsf@home.home>, Dan Espen <despen@verizon.net> wrote: >>k3b: Burns coasters when copying audio CDs >> >> As I understand, you needn't RAW mode if you write audio tracks from .wav >> files (possibly you never need it for CDDA tracks, if it's usual CDDA?). >> And so -raw96r option in second code is wrong. > > Maybe I should add a short note: you need to use -raw96r if you are using a > LiteON drive. The firmware in these drives is buggy and would otherwise create > defective audio CDs, that e.g. have wrong pregaps and time stamps that count > backwards. > > K3b is correct in being careful and using -raw96r. And here we are, from my little knowledge this may as well as be why some people don't believe wodim has issues, and why it does have issues. "Oh, it shouldn't need RAW mode.", then someone has a drive that actually needs it even if it shouldn't. Sadly I don't have DVD-Rs to volunteer, but IIRC, with my desktop burner, I had problems with wodim/cdrkit, and nowadays I use cdrtools with no problems. If I get my hands on some DVD-Rs, I may as well as try to test this again, so that proper bug reports can be filled. -- Nuno Silva (aka njsg) http://njsg.sdf-eu.org/
[toc] | [prev] | [next] | [standalone]
| From | Joerg.Schilling@fokus.fraunhofer.de |
|---|---|
| Date | 2013-03-24 21:42 +0000 |
| Message-ID | <kins0r$2sv$2@news.albasani.net> |
| In reply to | #7631 |
In article <kiniu3$l9h$2@dont-email.me>, J G Miller <miller@yoyo.ORG> wrote:
>On Sun, 24 Mar 2013 13:46:04 -0400, Dan Espen wrote:
>http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=505381
This is a _very_ minor bug only. There are plenty of real bugs that
cause defective filesystem images.
>One of the maintainers, Steve McIntyre, replied 9 days later
>
> "Cool, thanks. I'll take a look."
>
>Over 4 years later and no further action has been taken on the bug
>in reviewing or applying the patch or any further action on it.
Many other bugs reports did not see a reply at all.
>This behavior can be observed in bug reports for a number
>of other packages, eg
>
><http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=302907>
Well, I would not care about problems in other packages in this discussion.
>In April 2005, a user reports a bug and supplies a patch to
>fix the problem. 7 years later people are still asking for
>the patch to be applied and the response from Debian person
>responsible is that they should get Debian privileges to
>apply the patch to the package if they want it fixed
>because, obviously, "he ain't gonna do it."
>
>Users may start to get the feeling of "What is the point
>in reporting a bug to Debian (or providing a fix" if it
>is just going to be ignored.
Reporting problems should be done to the authors. You cannot expect any effect
if you report things to Debian.
>> Here's a Fedora list of cdrkit bugs:
>>
>> https://admin.fedoraproject.org/pkgdb/acls/bugs/cdrkit
>
>Fedora have a habit of closing bugs when a new version of
>Fedora is released regardless of whether the bug was ever
>acknowledged or fixed.
You will need to make closed but unfixed bugs visible to understand
the problem.
--
EMail:joerg@schily.net (home) Jörg Schilling D-13353 Berlin
js@cs.tu-berlin.de (uni)
joerg.schilling@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily
[toc] | [prev] | [next] | [standalone]
| From | Joerg.Schilling@fokus.fraunhofer.de |
|---|---|
| Date | 2013-03-24 21:31 +0000 |
| Message-ID | <kinrb3$2sv$1@news.albasani.net> |
| In reply to | #7627 |
In article <kin86d$n2h$6@dont-email.me>, J G Miller <miller@yoyo.ORG> wrote:
>On Sunday, March 24th, 2013, at 09:00:02h +0200, Nuno Silva wrote:
>
>> If wodim has no real upstream, I guess that would explain part of the
>> problem...
>
>The "upstream" is the Debian package maintainers.
Do not expect upstream actions from people who don't know the basics for the
related software.
> Joerg Jaspert
> Eduard Bloch
> Steve McIntyre
>
>Here is the relevant information from
>
> <http://packages.debian.ORG/changelogs/pool/main/c/cdrkit/cdrkit_1.1.11-2/copyright>
>
>QUOTE
>
> This package was first debianized by Erik Andersen andersee@debian.org.
> The current Debian maintainer is Joerg Jaspert <joerg@debian.org>.
> Co-maintainers: Eduard Bloch <blade@debian.org>,
> Steve McIntyre <93sam@debian.org>
Eduard Bloch is the person that started to send repeated personal attacks
in May 2004 and that later tried to create a red herring of a
so called license problems in hope people would forget about
his non-social action.
He has no clue on SCSI but is responsible for changes that
introduced a lot of problems in that program.
Joerg Jaspert is not a maintainer at all. He does not write code or fix bugs
but he is the main supporter of the Debian iniated dispute.
Steve McIntire is responsible for the new bugs in "genisoimage", I don't
remember that he did ever fix a bug.
> Upstream maintainers:
> The upstream author of zisofs-tools is H. Peter Anvin <hpa@zytor.com>.
> The rest is maintained by the Debian maintainers; see above.
Not part of cdrtools.
> Other authors:
> Joerg Schilling <schilling@fokus.fraunhofer.de>, Eric Youngdale and many
> others.
Eric Youngdale is the initial author of mkisofs. He did contribute code between
September 1993 and early Spring 1997. I am the main author of this program
since Spring 1997. While Eric did contribute less than 25% of the amount of
code I wrote for mkisofs, I beleive that James Pearson did contribute more code
than Eric did.
> Names of relevant binary program(s) and copyright info have been adapted to
> avoid the violation of the GPL license (as offered by Joerg Schilling) and the
> obligations created by German laws.
Edurard Bloch did remove Copyright messes from me in December 2006 - this
introduced a Copyright violation.....Debian was immediately informed about the
Copyright violation but did not fix their fault.
>UNQUOTE
>
>As it takes some Debian developers all their time just to maintain
>their packages, so I seriously doubt whether these Debian developers
>are doing or have done any significant new development on the software
>over the years since the fork.
Eduard Bloch did stop contributing to Debian on May 6th 2007.
>cdrkit currently has 19 bugs (out of a total of 99), the oldest dated
>December 12th, 2011 which have not even been "classified" (initial sorting
>and response) by the cdrkit maintainers.
>
>Surely this indicates a lack of activity in keeping the package
>well maintained.
There are more than 150 documented bugs, if you add up all non-overlapping
bugs from various Linux distributors. Fedora did however remove most if the
bugs without fixing anything.
Many of the bugs have been introduced in 2004 by Edurad Bloch already, many
others have been introduced in December 2006 - none of these bugs has been
fixed so far.
--
EMail:joerg@schily.net (home) Jörg Schilling D-13353 Berlin
js@cs.tu-berlin.de (uni)
joerg.schilling@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily
[toc] | [prev] | [next] | [standalone]
| From | <nunojsilva@invalid.invalid> (Nuno Silva) |
|---|---|
| Date | 2013-03-24 09:00 +0200 |
| Message-ID | <8738vle0zd.fsf@invalid.invalid> |
| In reply to | #7604 |
On 2013-03-24, unruh wrote: > On 2013-03-23, <nunojsilva@invalid.invalid> (Nuno Silva) > <nunojsilva@invalid.invalid> wrote: > >> Hardware *is* in the mix, because Debian's tools seem to be unable to >> work with a set of optical burners. Joerg's mention of the media size >> would make sense. >> >> I am also used to see a lot of "drive returns wrong startsec, using ..." >> (sic?) when using cdrtools. That has always made me wonder if Debian's >> incarnation is using the wrong value. (A childish assumption, as there >> are so many other things that may go wrong.) >> >> Anyone knows what is the upstream's opinion on these issues? > > Well, the original upstream is Jorg and you know what his opinion is. > Wodim is cdrtools from 2006 plus > some changes. AFAIK it has received very little attention since then, so > upstream does not exist anymore. If wodim has no real upstream, I guess that would explain part of the problem... -- Nuno Silva (aka njsg) http://njsg.sdf-eu.org/
[toc] | [prev] | [next] | [standalone]
| From | Joerg.Schilling@fokus.fraunhofer.de |
|---|---|
| Date | 2013-03-24 11:29 +0000 |
| Message-ID | <kimo38$l2o$1@news.albasani.net> |
| In reply to | #7604 |
In article <c3r3t.293365$Q91.161101@newsfe26.iad>,
unruh <unruh@invalid.ca> wrote:
>> Anyone knows what is the upstream's opinion on these issues?
>
>Well, the original upstream is Jorg and you know what his opinion is.
> Wodim is cdrtools from 2006 plus
>some changes. AFAIK it has received very little attention since then, so
>upstream does not exist anymore.
In late 2006, some people picked a cdrtools version from September 2004 and
started to "work" on the code.
- They removed the working DVD support code and replaced it with something
half baken is a result of the trace actions of a french guy from
Mandriva on a cdrecord-ProDVD version from Autumn 2001. This however
only contains SCSI commands that have been understood by this person...
- The working autoconfiguration and build system has been removed and
replaced by something that does not even work for all Linux platforms.
Note that there is more than x86.
- Instead of fixing bugs, a lot of new bugs have been introduced.
- Copyright notices have been removed from the code. Note that these
removed notes did help to identify many illegal closed source projects
in the past that have been based on cdrtools.
- Unlike the original source, the Debian based source cannot be called
"complete source" (as required by the GPL) anymore and it does not
compile on some Linux systems because of this missing code.
- 7 months lather (on May 6th 2007) all development action stopped.
Well, there have been some typo fixes later to create the attempt of
a maintained project, but bug reports are ignored.
But note that this is OSS and nobody is foced by the enemies of OpenSource
in Debian or other Linux distros to use the Debian code.
...meanwhile, the original code has been improved a lot. The code base and the
features did more than double since 2004.
The code has been checked by several lawyers and none of them could detect any
legal problem in the original code.
--
EMail:joerg@schily.net (home) Jörg Schilling D-13353 Berlin
js@cs.tu-berlin.de (uni)
joerg.schilling@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily
[toc] | [prev] | [next] | [standalone]
| From | unruh <unruh@invalid.ca> |
|---|---|
| Date | 2013-03-23 23:34 +0000 |
| Message-ID | <A_q3t.20190$N52.16294@newsfe01.iad> |
| In reply to | #7589 |
On 2013-03-23, Dan Espen <despen@verizon.net> wrote: > unruh <unruh@invalid.ca> writes: > >> On 2013-03-23, Dan Espen <despen@verizon.net> wrote: >>> Joerg.Schilling@fokus.fraunhofer.de writes: >>> >>>> In article <icli9fcmgm.fsf@home.home>, Dan Espen <despen@verizon.net> wrote: >>>>>Joerg.Schilling@fokus.fraunhofer.de writes: >>>> >>>>>> If you like people to get > 50% spoiled media, continue to recommend wodim... >>>>> >>>>>50% failure rate? >>>> >>>> This what typical users report as the reason for switching to cdrtools >>>> after discovering that their distributor did not ship the real software. >>>> >>>> There are of cause other people who do not have problems with wodim because they >>>> don't use it. >>> >>> I'm still not buying it. >>> >>> I don't know who this "typical user" was but I suspect he had a bad >>> drive or bad media. >> >> You heard from Blake. His failure rate dropped from high (tens of >> percent) to almost zero on the switch. That is evidence that your >> suspected reason is wrong. > > Sorry, didn't see that. Maybe you could re-post it so we can > see how many variables were controlled for. > > Is tens of percent close to >50%? No. So what. > > I've burned at last 25 DVDs. They all played. > I know anecdotes are not data, but 25 good burns in a row > just isn't compatible with claims of 50% failure. > Fine. For you wodim works. For others it does not. You want us to listen to you but not to others? They anecdotes are useless, but yours are useful? No, you have not experienced the problems. Others have. Open your mind. You accuse Jorg of cherry picking evidence but so you are justified for doing the same? Noone is forcing you to change. YOu are happy with wodim. Keep using it. But do not elevate your experience to the generic. Remember that you are using Jorg's software. If it works it is because of him.
[toc] | [prev] | [next] | [standalone]
| From | Octothorpe <Octothorpe@invalid.com> |
|---|---|
| Date | 2013-03-23 19:58 -0400 |
| Message-ID | <s5s12a-ao7.ln1@crazy-horse.bildanet.com> |
| In reply to | #7603 |
On Sat, 23 Mar 2013 23:34:56 +0000, unruh wrote: [putolin] >> > Fine. For you wodim works. For others it does not. You want us to listen > to you but not to others? They anecdotes are useless, but yours are > useful? No, you have not experienced the problems. Others have. Open > your mind. You accuse Jorg of cherry picking evidence but so you are > justified for doing the same? Noone is forcing you to change. YOu are > happy with wodim. Keep using it. But do not elevate your experience to > the generic. > > Remember that you are using Jorg's software. If it works it is because > of him. Ah so it is OK for him to take things out of context and twist them into non-sense. When one lies and miss-represents the truth on purpose to elevate their cause ( what cause he seems to think he has) they should be called on it. You see he did it again he comes here to introduce a battle and we now have one. No I don't worship at the feet of jorg like you do Thanks but no thanks I'll use libburn and cdrskin, those have nothing to do with him.
[toc] | [prev] | [next] | [standalone]
| From | Joerg.Schilling@fokus.fraunhofer.de |
|---|---|
| Date | 2013-03-24 11:31 +0000 |
| Message-ID | <kimo6i$l2o$2@news.albasani.net> |
| In reply to | #7607 |
In article <s5s12a-ao7.ln1@crazy-horse.bildanet.com>,
Octothorpe <Octothorpe@invalid.com> wrote:
>Thanks but no thanks I'll use libburn and cdrskin, those have nothing to
>do with him.
This is of cource complete nonsense!
This code has been created from the knowledge aquired by looking into the
cdrtools source code.
--
EMail:joerg@schily.net (home) Jörg Schilling D-13353 Berlin
js@cs.tu-berlin.de (uni)
joerg.schilling@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily
[toc] | [prev] | [next] | [standalone]
| From | Octothorpe <Octothorpe@invalid.com> |
|---|---|
| Date | 2013-03-24 08:56 -0400 |
| Message-ID | <1p932a-kn8.ln1@crazy-horse.bildanet.com> |
| In reply to | #7617 |
On Sun, 24 Mar 2013 11:31:30 +0000, Joerg.Schilling wrote: > In article <s5s12a-ao7.ln1@crazy-horse.bildanet.com>, > Octothorpe <Octothorpe@invalid.com> wrote: > >>Thanks but no thanks I'll use libburn and cdrskin, those have nothing to >>do with him. > > This is of cource complete nonsense! > > This code has been created from the knowledge acquired by looking into > the cdrtools source code. How do you know this... Show then evidence of this and not just clueless accusations. This could have been a clean room effort. You are not the only one that can come up with a solution to CD/DVD burning. You are ridiculous. This is just more postering by you.... When are you going to quit making a complete ass of yourself.
[toc] | [prev] | [next] | [standalone]
| From | Joerg.Schilling@fokus.fraunhofer.de |
|---|---|
| Date | 2013-03-30 12:06 +0000 |
| Message-ID | <kj6kfa$m38$3@news.albasani.net> |
| In reply to | #7620 |
In article <1p932a-kn8.ln1@crazy-horse.bildanet.com>,
Octothorpe <Octothorpe@invalid.com> wrote:
>On Sun, 24 Mar 2013 11:31:30 +0000, Joerg.Schilling wrote:
>
>> In article <s5s12a-ao7.ln1@crazy-horse.bildanet.com>,
>> Octothorpe <Octothorpe@invalid.com> wrote:
>>
>>>Thanks but no thanks I'll use libburn and cdrskin, those have nothing to
>>>do with him.
>>
>> This is of cource complete nonsense!
>>
>> This code has been created from the knowledge acquired by looking into
>> the cdrtools source code.
>
>How do you know this...
>Show then evidence of this and not just clueless accusations.
>This could have been a clean room effort.
Your claim is ridiculous - a clean room implementation would be _vevry_
different from cdrecord. This is obviously not the case...
It seems that they recently started with a re-implementation of the Reed
Solomon code for RAW CD writing, but former versions of "libburn" et. al.
did even incorporate original code from cdrtools.
Note that for many years Heiko Eißfeldt's Reed Solomon implementation was the
only free implementation available. This code has been in use by several "GNU
projects" that were unwilling to honor the license conditions.
Given the fact that there was no other free Reed Solomon implementation for
CDs, I assume that even other newer Reed Solomon implementations did benefit
from Heiko's implementation. The code that now is in cdrdao is definitely
derived from Heiko's code even though it's author claims something different.
--
EMail:joerg@schily.net (home) Jörg Schilling D-13353 Berlin
js@cs.tu-berlin.de (uni)
joerg.schilling@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily
[toc] | [prev] | [next] | [standalone]
| From | Octothorpe <Octothorpe@invalid.com> |
|---|---|
| Date | 2013-03-30 13:24 -0400 |
| Message-ID | <vmjj2a-skj.ln1@crazy-horse.bildanet.com> |
| In reply to | #7704 |
On Sat, 30 Mar 2013 12:06:02 +0000, Joerg.Schilling wrote:
> In article <1p932a-kn8.ln1@crazy-horse.bildanet.com>,
> Octothorpe <Octothorpe@invalid.com> wrote:
>>On Sun, 24 Mar 2013 11:31:30 +0000, Joerg.Schilling wrote:
>>
>>> In article <s5s12a-ao7.ln1@crazy-horse.bildanet.com>,
>>> Octothorpe <Octothorpe@invalid.com> wrote:
>>>
>>>>Thanks but no thanks I'll use libburn and cdrskin, those have nothing
>>>>to do with him.
>>>
>>> This is of cource complete nonsense!
>>>
>>> This code has been created from the knowledge acquired by looking into
>>> the cdrtools source code.
>>
>>How do you know this...
>>Show then evidence of this and not just clueless accusations.
>>This could have been a clean room effort.
>
> Your claim is ridiculous - a clean room implementation would be _vevry_
> different from cdrecord. This is obviously not the case...
>
> It seems that they recently started with a re-implementation of the Reed
> Solomon code for RAW CD writing, but former versions of "libburn" et.
> al.
> did even incorporate original code from cdrtools.
>
Really?
Would that explain that cdrskin interfaces the libburn api to the cdrecord
interface...
I have the source code for libburn and cdrskin... Now give me the line
number(s) of the code that was taken from your cdrtools.
If you can not then I will know that all you do is to talk out your ass,
Now that I would need more prove that.
A grep on the code has this which by the way the code was not written by
you.
/* The following two functions were implemented according to
doc/boot_sectors.txt section "SUN Disk Label and boot images" which
was derived by Thomas Schmitt from
cdrtools-2.01.01a77/mkisofs/sunlabel.h
cdrtools-2.01.01a77/mkisofs/mkisofs.8
by Joerg Schilling
Both functions are entirely under copyright (C) 2010 Thomas Schmitt.
*/
So the libburn has NO CODE authored by you!
Prove me wrong!
From the AUTHORS text file
Vreixo Formoso
Mario Danic
Vladimir Serbinenko
Thomas Schmitt
Oh look your name is missing!
Yap Yap Yap.
Now go way. I need to burn a dvd without your nose up my ass, I think I
will use libburn.
[toc] | [prev] | [next] | [standalone]
| From | unruh <unruh@invalid.ca> |
|---|---|
| Date | 2013-03-24 17:46 +0000 |
| Message-ID | <AZG3t.171578$O52.57703@newsfe10.iad> |
| In reply to | #7607 |
On 2013-03-23, Octothorpe <Octothorpe@invalid.com> wrote: > On Sat, 23 Mar 2013 23:34:56 +0000, unruh wrote: > > [putolin] > >>> >> Fine. For you wodim works. For others it does not. You want us to listen >> to you but not to others? They anecdotes are useless, but yours are >> useful? No, you have not experienced the problems. Others have. Open >> your mind. You accuse Jorg of cherry picking evidence but so you are >> justified for doing the same? Noone is forcing you to change. YOu are >> happy with wodim. Keep using it. But do not elevate your experience to >> the generic. >> >> Remember that you are using Jorg's software. If it works it is because >> of him. > > Ah so it is OK for him to take things out of context and twist them into So it is OK for you to do so? > non-sense. When one lies and miss-represents the truth on purpose to > elevate their cause ( what cause he seems to think he has) they should be > called on it. Yes, what cause is it? He states that the user should try the cdrtools to solve his problem. Apparently it did. He also states that cdrkit uses and ancient (7 year old) version of cdrtools. It does. He states that people have trouble with cdrkit. This thread bears testament to that. If at times he overstates his case ( he does) that differentiates him little from you. > You see he did it again he comes here to introduce a battle and we now > have one. He is NOT introduce the battle. He came here to help someone who was having trouble. He did. You are the key one who has decided to come riding onto the field to do battle with him. Why? You admit to using his software (cdrkit) but then state you would never use his software. Why? > > No I don't worship at the feet of jorg like you do Worship at his feet? Another exageration from you. I believe that he writes good software (as apparently do you as well. Even 7 year old software works well for you) but stated that you would never use his software because you do not like him. I will use good software no matter who writes it, and will defend it as software. > > Thanks but no thanks I'll use libburn and cdrskin, those have nothing to > do with him. Fine.
[toc] | [prev] | [next] | [standalone]
| From | Octothorpe <Octothorpe@invalid.com> |
|---|---|
| Date | 2013-03-24 15:53 -0400 |
| Message-ID | <q6242a-099.ln1@crazy-horse.bildanet.com> |
| In reply to | #7630 |
On Sun, 24 Mar 2013 17:46:08 +0000, unruh wrote: > On 2013-03-23, Octothorpe <Octothorpe@invalid.com> wrote: >> On Sat, 23 Mar 2013 23:34:56 +0000, unruh wrote: >> >> [putolin] >> >> >>> Fine. For you wodim works. For others it does not. You want us to >>> listen to you but not to others? They anecdotes are useless, but yours >>> are useful? No, you have not experienced the problems. Others have. >>> Open your mind. You accuse Jorg of cherry picking evidence but so you >>> are justified for doing the same? Noone is forcing you to change. YOu >>> are happy with wodim. Keep using it. But do not elevate your >>> experience to the generic. >>> >>> Remember that you are using Jorg's software. If it works it is because >>> of him. >> >> Ah so it is OK for him to take things out of context and twist them >> into > > So it is OK for you to do so? I did not I first responded to his non sense that wodim doesn't burn DVDs. > >> non-sense. When one lies and miss-represents the truth on purpose to >> elevate their cause ( what cause he seems to think he has) they should >> be called on it. > > Yes, what cause is it? He states that the user should try the cdrtools > to solve his problem. Apparently it did. He also states that cdrkit uses > and ancient (7 year old) version of cdrtools. It does. He states that > people have trouble with cdrkit. This thread bears testament to that. > > If at times he overstates his case ( he does) that differentiates him > little from you. Every time in interjects into a conversation he starts his non sense just like here. > >> You see he did it again he comes here to introduce a battle and we now >> have one. > > He is NOT introduce the battle. He came here to help someone who was > having trouble. He did. > You are the key one who has decided to come riding onto the field to do > battle with him. Why? You admit to using his software (cdrkit) but then > state you would never use his software. Why? > No he came here to continue his rant against wodim. If you look at my first post to him I simply state that he is not telling the truth, after which he starts his attacks. For other rants see his nonsense he posted to the arch linux mailing list, where he was promptly handed his ass. He is well known as you should be aware that he always gets into dick size wars where ever he shows up. > >> No I don't worship at the feet of jorg like you do > > Worship at his feet? Another exageration from you. I believe that he > writes good software (as apparently do you as well. Even 7 year old > software works well for you) but stated that you would never use his > software because you do not like him. I will use good software no matter > who writes it, and will defend it as software. No you are one to defend him no matter what. That is very plain. I did not say I would never use his software that is a fabrication by you. I said that I have used wodim and it is supplied by fedora in place of cdrtools. Again if cdrkit (wodim) is as bad as you and him make it out to be then why do they ship it? Surely they would not ship it if it was badly broken, BTW they are not the only one shipping cdrkit as the default package, so are they all wrong too? > > >> Thanks but no thanks I'll use libburn and cdrskin, those have nothing >> to do with him. > > Fine.
[toc] | [prev] | [next] | [standalone]
| From | Joerg.Schilling@fokus.fraunhofer.de |
|---|---|
| Date | 2013-03-24 21:45 +0000 |
| Message-ID | <kins6d$2sv$3@news.albasani.net> |
| In reply to | #7632 |
In article <q6242a-099.ln1@crazy-horse.bildanet.com>,
Octothorpe <Octothorpe@invalid.com> wrote:
>I said that I have used wodim and it is supplied by fedora in place of
>cdrtools. Again if cdrkit (wodim) is as bad as you and him make it out
>to be then why do they ship it? Surely they would not ship it if it was
Wodim is shipped by enemies of OpenSource, distributions that do not care about
the problems of their users.
--
EMail:joerg@schily.net (home) Jörg Schilling D-13353 Berlin
js@cs.tu-berlin.de (uni)
joerg.schilling@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily
[toc] | [prev] | [next] | [standalone]
| From | Octothorpe <Octothorpe@invalid.com> |
|---|---|
| Date | 2013-03-24 21:51 -0400 |
| Message-ID | <j6n42a-rl9.ln1@crazy-horse.bildanet.com> |
| In reply to | #7638 |
On Sun, 24 Mar 2013 21:45:49 +0000, Joerg.Schilling wrote: > In article <q6242a-099.ln1@crazy-horse.bildanet.com>, > Octothorpe <Octothorpe@invalid.com> wrote: > >>I said that I have used wodim and it is supplied by fedora in place of >>cdrtools. Again if cdrkit (wodim) is as bad as you and him make it out >>to be then why do they ship it? Surely they would not ship it if it was > > Wodim is shipped by enemies of OpenSource, distributions that do not > care about the problems of their users. Where do you come up with this non sense?
[toc] | [prev] | [next] | [standalone]
Page 6 of 8 — ← Prev page 1 2 3 4 5 [6] 7 8 Next page →
Back to top | Article view | comp.os.linux.misc
csiph-web