From: Joerg Schilling <schilling@fokus.fraunhofer.de>
To: schilling@fokus.fraunhofer.de, matthias.andree@gmx.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: CD writing in future Linux try #2
Date: Fri, 03 Feb 2006 17:43:50 +0100 [thread overview]
Message-ID: <43E38846.nail5CASXQDG1@burner> (raw)
In-Reply-To: <20060203131550.GA14819@merlin.emma.line.org>
Matthias Andree <matthias.andree@gmx.de> wrote:
> Joerg Schilling schrieb am 2006-02-03:
>
> > Bill Davidsen <davidsen@tmr.com> wrote:
> >
> > > Free, but not open source, and that's an issue with a mission critical
> > > application. For home use it doesn't matter, for business use it really
> >
> > Since when is mission critical requiring OpenSource?
>
> Now this is really offensive. Bill stated the reason, yet you jump at
> him before even reading his message through the end.
It would really help it you try to understand first....
Today many companies buy closed source software from small companies that
may just disappear one day. So where is your point?
Jörg
--
EMail:joerg@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
js@cs.tu-berlin.de (uni)
schilling@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily
next prev parent reply other threads:[~2006-02-03 16:44 UTC|newest]
Thread overview: 88+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-27 16:37 CD writing in future Linux try #2 [ was: Re: CD writing in future Linux (stirring up a hornets' nest) ] Bartlomiej Zolnierkiewicz
2006-01-29 11:01 ` Joerg Schilling
2006-01-29 11:15 ` Jan Engelhardt
2006-01-29 11:28 ` Matthias Andree
2006-01-30 15:24 ` Joerg Schilling
2006-02-05 12:03 ` Jan Engelhardt
2006-02-06 16:29 ` Joerg Schilling
2006-02-06 17:17 ` René Rebe
2006-02-06 18:02 ` Matthias Andree
2006-01-29 11:26 ` Matthias Andree
2006-01-29 20:41 ` Jan Engelhardt
2006-01-29 20:50 ` Joerg Schilling
2006-01-29 21:28 ` Albert Cahalan
2006-01-30 16:11 ` Joerg Schilling
2006-01-30 16:31 ` Albert Cahalan
2006-01-30 16:35 ` Joerg Schilling
2006-01-30 17:08 ` Matthias Andree
2006-01-30 17:14 ` Joerg Schilling
2006-01-30 17:30 ` Matthias Andree
2006-01-30 17:37 ` Joerg Schilling
2006-01-30 17:49 ` Matthias Andree
2006-01-30 20:22 ` James Courtier-Dutton
2006-01-31 10:17 ` Andreas Jellinghaus
2006-01-30 20:24 ` Phillip Susi
2006-01-31 10:47 ` Joerg Schilling
2006-01-31 11:22 ` Matthias Andree
2006-02-01 0:15 ` Bill Davidsen
2006-02-01 7:45 ` Tejun Heo
2006-02-01 16:41 ` Joerg Schilling
2006-01-31 23:55 ` Bill Davidsen
2006-02-01 15:06 ` Joerg Schilling
2006-01-30 15:25 ` Joerg Schilling
2006-01-30 17:09 ` Matthias Andree
2006-01-30 17:15 ` Joerg Schilling
2006-01-30 23:26 ` Pavel Machek
2006-02-01 15:51 ` Jan Engelhardt
2006-01-31 1:43 ` Patrick McFarland
2006-01-31 1:47 ` CD writing in future Linux try #2 David S. Miller
2006-01-31 11:13 ` Gerhard Mack
2006-01-31 11:18 ` David S. Miller
2006-02-01 0:28 ` Bill Davidsen
2006-02-01 15:12 ` Joerg Schilling
2006-02-01 15:25 ` Matthias Andree
2006-02-01 16:32 ` Joerg Schilling
2006-02-02 16:24 ` Jan Engelhardt
2006-02-02 16:29 ` Jan Engelhardt
2006-02-02 18:37 ` Bill Davidsen
2006-02-03 12:58 ` Joerg Schilling
2006-02-03 13:15 ` Matthias Andree
2006-02-03 16:43 ` Joerg Schilling [this message]
2006-02-03 13:30 ` linux-os (Dick Johnson)
2006-02-03 19:27 ` Bill Davidsen
2006-02-01 4:49 ` Albert Cahalan
2006-02-01 7:56 ` jerome lacoste
2006-02-01 16:42 ` Joerg Schilling
2006-02-02 0:30 ` Kurt Wall
2006-02-01 11:33 ` Rene Herman
2006-02-01 16:21 ` Jon Agirre
2006-02-02 16:35 ` Jan Engelhardt
2006-02-06 23:15 ` Peter Chubb
2006-02-07 5:00 ` Albert Cahalan
2006-02-01 16:36 ` Joerg Schilling
2006-02-01 17:01 ` Matthias Andree
2006-02-02 19:17 ` Bill Davidsen
2006-01-31 16:46 ` Lennart Sorensen
2006-01-31 14:15 ` linux-os (Dick Johnson)
[not found] ` <515e525f0601302205h4a845f36u12b946515759239a@mail.gmail.com>
2006-01-31 6:46 ` CD writing in future Linux try #2 [ was: Re: CD writing in future Linux (stirring up a hornets' nest) ] Kyle Moffett
2006-01-31 8:55 ` Pekka Enberg
2006-02-01 0:25 ` Jesper Juhl
2006-02-02 16:45 ` Jan Engelhardt
2006-02-10 17:58 ` CD-blanking leads to machine freeze with current -git [was: Re: CD writing in future Linux try #2 [ was: Re: CD writing in future Linux (stirring up a hornets' nest) ]] Marc Koschewski
2006-02-10 19:19 ` Phillip Susi
2006-02-10 19:39 ` Gene Heskett
2006-02-10 20:12 ` Kyle Moffett
2006-02-10 21:00 ` Gene Heskett
2006-02-10 21:00 ` Marc Koschewski
2006-02-10 21:26 ` Phillip Susi
2006-02-10 21:35 ` Lennart Sorensen
2006-02-11 15:16 ` CD-blanking leads to machine freeze with current -git Jan Engelhardt
2006-02-11 15:25 ` Marc Koschewski
2006-02-11 15:35 ` Doug McNaught
2006-02-11 15:44 ` Marc Koschewski
2006-02-10 23:23 ` CD-blanking leads to machine freeze with current -git [was: Re: CD writing in future Linux try #2 [ was: Re: CD writing in future Linux (stirring up a hornets' nest) ]] Alan Cox
2006-02-10 23:41 ` Marc Koschewski
2006-02-10 23:50 ` CD-blanking leads to machine freeze with current -git Doug McNaught
2006-02-10 23:56 ` CD-blanking leads to machine freeze with current -git [was: Re: CD writing in future Linux try #2 [ was: Re: CD writing in future Linux (stirring up a hornets' nest) ]] Alan Cox
2006-02-11 1:03 ` hackmiester (Hunter Fuller)
2006-02-11 1:08 ` Marc Koschewski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43E38846.nail5CASXQDG1@burner \
--to=schilling@fokus.fraunhofer.de \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.andree@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox