From: Matthias Andree <matthias.andree@gmx.de>
To: Joerg Schilling <schilling@fokus.fraunhofer.de>
Cc: matthias.andree@gmx.de, linux-kernel@vger.kernel.org,
cdwrite@other.debian.org
Subject: Re: Request to stop cdrecord's bogus accusations of Linux.
Date: Mon, 30 Jan 2006 19:03:27 +0100 [thread overview]
Message-ID: <20060130180327.GA15332@merlin.emma.line.org> (raw)
In-Reply-To: <43DE511A.nail2DG117NWT@burner>
Joerg Schilling schrieb am 2006-01-30:
> Matthias Andree <matthias.andree@gmx.de> wrote:
>
> > with this open letter, I officially request that you stop your
> > misrepresentations in cdrecord that claim Linux were noncompliant in a
> > place where it is conforming to POSIX.
> >
> > I am not speaking on behalf of any other party here, this is purely my
> > personal opinion that is supposed to make sure both sides play fair.
> >
> > <ftp://ftp.berlios.de/pub/cdrecord/alpha/AN-2.01.01a05>
> > (dated 2006-01-29 20:20" states
>
> I am sorry to see that you still insist in claiming things that are not in this
> announcement.
>
> You did inform me about this Linux "self non-compliance" and you are the only
> person who did claim that there is a problem. I spend a lot of time in trying
> to find a work around for this problem and I am in hope that I did find a
> working solution.
Compliance is a term used in contexts such as "standards" compliance.
Even "self compliance" is given, the Linux manpage matches observed
behavior, too.
Fact however is that I approached you with a patch that moved the
allocation into root-mode code, and later with a patch that reset
RLIMIT_MEMLOCK to RLIM_INFINITY, and we tested several variants forth
and back until you settled for raising RLIMIT_MEMLOCK to some 6 MB.
...
> For this reason it is apropriate to call the code that deals with the problem
> "a workaround".
Which was not at all my point, but "compliance" is. I don't mind you
calling it workaround or call 2.6.9 incompatible with 2.6.8.1.
Re-read my message - and I find it interesting to read this NOW, after
I'd mailed this and discussed this earlier.
--
Matthias Andree
prev parent reply other threads:[~2006-01-30 18:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-30 17:37 Matthias Andree
2006-01-30 17:47 ` Joerg Schilling
2006-01-30 18:03 ` Matthias Andree [this message]
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=20060130180327.GA15332@merlin.emma.line.org \
--to=matthias.andree@gmx.de \
--cc=cdwrite@other.debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=schilling@fokus.fraunhofer.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
all inboxes | Powered by JetHome®