From: "Theodore Y. Ts'o" <tytso@MIT.EDU>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: michael@linuxmagic.com, alan@lxorguk.ukuu.org.uk,
linux-kernel@vger.kernel.org
Subject: Re: Signal 11
Date: Fri, 15 Dec 2000 11:12:20 -0500 [thread overview]
Message-ID: <200012151612.LAA11746@tsx-prime.MIT.EDU> (raw)
In-Reply-To: Alan Cox's message of Fri, 15 Dec 2000 01:09:29 +0000 (GMT), <E146jNL-0000SN-00@the-village.bc.nu>
Date: Fri, 15 Dec 2000 01:09:29 +0000 (GMT)
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
> > o We tell vendors to build RPMv3 , glibc 2.1.x
> Curious HOW do you tell vendors??
When they ask. More usefully Dan Quinlann and most vendors put together a
recommended set of things to build with and use. It warns about library
pitfalls, kernel changes and what packaging is supported. It is far from
perfect and nothing like the LSB goals but its a start and following it does
give you applications that with a bit of care run on everything.
In the interests of making sure everyone understands the history:
The Linux Development Platform Specification (LDPS) was started as a
result of an informal evening post-LSB-meeting gathering in June --- to
which by the way Red Hat didn't send any representatives(*) --- the
discussion at the restaurant started along the lines of "Oh, my *GOD*
RedHat is about to do something stupid --- they're releasing Red Hat 7.0
with beta/snapshots of just about every single critical system component
except the kernel --- and vendors who fall into the trap developing
against Red Hat 7.0 won't work with any other distribution. This is
going to be *bad* for Linux."
So yes, the reason why LDPS was formed was to recommend to vendors what
they should build and use --- but while Alan gave comments about the
LDPS once it was announced that a group of people were working on the
LDPS , there is no way that the LDPS could even vaguely be considered a
Red Hat initiative. (The LDPS is a separate work group which is part of
the FSG, so it is a sister group to the LSB effort.)
- Ted
(*) Ever since Jim Kingdon left Red Hat (he was at VA Linux for a while,
and is now at SGI), as far as I know no one at Red Hat is actively
participating in the LSB activities --- they haven't sent anyone to the
physical LSB meetings, or participated in the bi-weekly phone
conferences, or taken work items to help finish the LSB. Alan does
participate on the mailing lists, and makes quite helpful comments, but
as far as I know that's about the limit to Red Hat's participation to
either the LSB or the LDPS specification work. Speaking as someone who
has been contributing time and effort to the LSB, it would be great if
Red Hat were to become more fully involved in the LSB; I (and I'm sure
all the other LSB volunteers) would welcome a greater level of
participation by Red Hat.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-15 16:43 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-14 12:42 Clayton Weaver
2000-12-14 19:11 ` Linus Torvalds
2000-12-14 22:35 ` Alan Cox
2000-12-14 22:45 ` Linus Torvalds
2000-12-14 22:58 ` Bernhard Rosenkraenzer
2000-12-14 23:11 ` Linus Torvalds
2000-12-15 0:10 ` Miquel van Smoorenburg
2000-12-15 0:32 ` Alan Cox
2000-12-15 0:42 ` Miquel van Smoorenburg
2000-12-15 2:07 ` Michael Peddemors
2000-12-15 1:09 ` Alan Cox
2000-12-15 16:12 ` Theodore Y. Ts'o [this message]
2000-12-14 23:24 ` Alan Cox
2000-12-14 23:35 ` Jakub Jelinek
2000-12-14 23:51 ` Linus Torvalds
2000-12-15 0:11 ` Dan Egli
2000-12-16 1:28 ` Signal 11gy Alan Cox
2000-12-14 22:46 ` Signal 11 Jakub Jelinek
-- strict thread matches above, loose matches on Subject: below --
2000-12-09 5:32 davej
2000-12-08 0:27 Linux 2.2.18pre25 Alan Cox
2000-12-08 0:44 ` Signal 11 Rainer Mager
2000-12-08 1:05 ` Jeff V. Merkey
2000-12-08 1:09 ` Michel LESPINASSE
2000-12-08 2:14 ` Rainer Mager
2000-12-08 1:20 ` Andi Kleen
2000-12-08 1:24 ` Jeff V. Merkey
2000-12-08 1:40 ` Andi Kleen
2000-12-08 1:43 ` Jeff V. Merkey
2000-12-08 1:55 ` Jeff V. Merkey
2000-12-08 19:20 ` Dr. Kelsey Hudson
2000-12-08 2:28 ` davej
2000-12-08 3:13 ` Jeff V. Merkey
2000-12-08 3:25 ` davej
2000-12-08 16:44 ` Matthew Vanecek
2000-12-08 19:43 ` Dr. Kelsey Hudson
2000-12-08 13:52 ` Alan Cox
2000-12-15 0:11 ` lamont
2000-12-08 1:58 ` Richard B. Johnson
2000-12-08 2:04 ` Peter Samuelson
2000-12-08 16:36 ` Matthew Vanecek
2000-12-08 16:49 ` Richard B. Johnson
2000-12-08 17:40 ` Peter Samuelson
2000-12-08 19:36 ` Dr. Kelsey Hudson
2000-12-08 9:46 ` David Woodhouse
2000-12-08 14:06 ` Alan Cox
2000-12-09 19:01 ` Matthew Vanecek
2000-12-09 19:20 ` davej
2000-12-09 23:31 ` Matthew Vanecek
2000-12-11 0:58 ` Rainer Mager
2000-12-11 9:05 ` Rainer Mager
2000-12-11 13:33 ` Mike Galbraith
2000-12-11 23:24 ` Rainer Mager
2000-12-11 14:14 ` davej
2000-12-08 16:21 ` Horst von Brand
2000-12-08 19:34 ` Mark Vojkovich
2000-12-08 23:16 ` Jeff V. Merkey
2000-12-08 22:24 ` David Woodhouse
2000-12-09 0:56 ` Jeff V. Merkey
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=200012151612.LAA11746@tsx-prime.MIT.EDU \
--to=tytso@mit.edu \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@linuxmagic.com \
/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®