From: Martin Dalecki <dalecki@evision-ventures.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linus Torvalds <torvalds@transmeta.com>,
"H. Peter Anvin" <hpa@transmeta.com>,
Andries.Brouwer@cwi.nl, linux-kernel@vger.kernel.org,
tytso@MIT.EDU
Subject: Re: Larger dev_t
Date: Tue, 03 Apr 2001 14:13:38 +0200 [thread overview]
Message-ID: <3AC9BE72.9C2D3C9@evision-ventures.com> (raw)
In-Reply-To: <E14kPmQ-0007vt-00@the-village.bc.nu>
Alan Cox wrote:
>
> > If anything I'm a *SERIOUS* production user. And I wouldn't allow
> > *ANYBODY* here to run am explicitly tagged as developement kernel
> > here anyway in an production enviornment. That's what releases are for
> > damn.
> > Or do you think that Linux should still preserve DOS compatibility
> > in to the eternity as other "popular" systems do?
>
> You still break 2.4-2.6. Thats a production release jump. Right now I can
> and do run 2.0->2.4 on the same box. If you dont understand why to many
> people that is a requirement please talk to folks who run real business on
> Linux
You have possible no imagination about how real the business is I do
:-).
What's worth it to be able running 2.0 and 2.4 on the same box?
I just intendid to tell you that there are actually people in the
REAL BUSINESS out there who know about and are willing to sacifier
compatibility until perpetuum for contignouus developement.
BTW we don't run much of Cyrix486 hardware anymore here.. More like
boxes with few gigs of ram 4 CPU's RAID and so on...
The single biggest memmory hog here is currently the Oracle 9i AS.
next prev parent reply other threads:[~2001-04-03 12:28 UTC|newest]
Thread overview: 95+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-27 9:29 Larger dev_t Andries.Brouwer
2001-03-27 18:48 ` Linus Torvalds
2001-03-27 19:28 ` H. Peter Anvin
2001-03-27 19:51 ` Linus Torvalds
2001-03-27 21:21 ` Alan Cox
2001-03-27 21:35 ` Linus Torvalds
2001-03-27 22:02 ` Andre Hedrick
2001-03-27 23:57 ` Linus Torvalds
2001-03-28 21:23 ` Martin Dalecki
2001-03-28 21:40 ` H. Peter Anvin
2001-03-28 21:44 ` Andre Hedrick
2001-03-27 22:16 ` Alan Cox
2001-03-27 22:16 ` H. Peter Anvin
2001-03-27 22:43 ` Russell King
2001-03-28 16:59 ` Jeff Randall
2001-03-28 0:07 ` Linus Torvalds
2001-03-28 0:10 ` H. Peter Anvin
2001-03-28 0:24 ` Linus Torvalds
2001-03-28 2:19 ` Alan Cox
2001-03-28 7:08 ` Andre Hedrick
2001-03-28 21:32 ` Martin Dalecki
2001-03-29 3:53 ` Alan Cox
2001-03-29 11:02 ` Martin Dalecki
2001-04-02 20:02 ` Alan Cox
2001-04-03 7:25 ` Martin Dalecki
2001-04-03 12:19 ` Alan Cox
2001-04-03 12:13 ` Martin Dalecki [this message]
2001-04-03 12:38 ` Alan Cox
2001-04-04 8:08 ` Rogier Wolff
2001-03-30 6:54 ` Kai Henningsen
2001-03-28 21:18 ` Martin Dalecki
2001-03-27 22:13 ` H. Peter Anvin
2001-03-27 22:55 ` Dan Hollis
2001-03-27 22:58 ` H. Peter Anvin
2001-03-27 23:42 ` Richard Gooch
2001-03-28 1:03 ` Paul Jakma
2001-03-28 1:35 ` Alexander Viro
2001-03-27 23:44 ` Andrew Pimlott
2001-03-28 0:28 ` Albert D. Cahalan
2001-03-28 3:58 ` Johan Kullstam
2001-03-28 4:23 ` Alexander Viro
2001-03-28 11:57 ` Jesse Pollard
2001-03-28 18:13 ` Oliver Neukum
2001-03-28 19:05 ` Jesse Pollard
2001-03-28 19:50 ` Oliver Neukum
2001-03-28 21:36 ` Martin Dalecki
2001-03-28 21:09 ` Martin Dalecki
2001-03-28 21:24 ` H. Peter Anvin
2001-03-28 21:46 ` Alexander Viro
2001-03-28 20:54 ` Martin Dalecki
2001-03-28 11:52 ` Pjotr Kourzanoff
2001-03-28 12:11 ` Tim Jansen
2001-03-27 19:27 ` Albert D. Cahalan
-- strict thread matches above, loose matches on Subject: below --
2001-04-03 14:48 Wayne.Brown
2001-04-03 15:34 ` Bart Trojanowski
2001-04-02 21:59 Andries.Brouwer
2001-04-02 20:17 Andries.Brouwer
2001-04-02 21:45 ` Alan Cox
2001-04-03 7:28 ` Martin Dalecki
2001-04-03 10:09 ` Ingo Oeser
2001-04-03 12:06 ` Alan Cox
2001-04-03 12:20 ` Ingo Oeser
2001-04-03 12:15 ` Martin Dalecki
2001-04-03 12:53 ` Alan Cox
2001-04-03 16:05 ` Richard Gooch
2001-04-03 16:34 ` Alexander Viro
2001-04-03 16:58 ` Richard Gooch
2001-04-03 16:54 ` Alan Cox
2001-04-03 17:02 ` Richard Gooch
2001-04-03 12:41 ` Alan Cox
2001-04-03 23:28 ` Tim Wright
2001-03-27 22:38 Jesse Pollard
2001-03-27 22:44 ` H. Peter Anvin
2001-03-26 21:18 John Byrne
2001-03-26 22:12 ` Linus Torvalds
2001-03-26 23:41 ` Guest section DW
2001-03-25 12:31 Andries.Brouwer
2001-03-25 15:35 ` Wichert Akkerman
2001-03-25 16:15 ` Mitchell Blank Jr
2001-03-25 16:54 ` Michel Wilson
2001-03-25 17:12 ` Jeff Garzik
2001-03-25 17:00 ` Jamie Lokier
2001-03-25 17:07 ` Anton Altaparmakov
2001-03-25 17:37 ` Michel Wilson
2001-03-25 18:21 ` Guest section DW
2001-03-25 20:50 ` diego
2001-03-25 17:55 ` Gerry
2001-03-27 6:03 ` Linus Torvalds
2001-03-24 16:13 Andries.Brouwer
2001-03-24 14:25 Andries.Brouwer
2001-03-24 14:40 ` Jeff Garzik
2001-03-24 15:00 ` Alexander Viro
2001-03-25 14:22 ` Martin Dalecki
2001-03-25 3:24 ` Linus Torvalds
2001-03-25 14:35 ` Martin Dalecki
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=3AC9BE72.9C2D3C9@evision-ventures.com \
--to=dalecki@evision-ventures.com \
--cc=Andries.Brouwer@cwi.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hpa@transmeta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=tytso@MIT.EDU \
/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