Newsgroups: comp.os.linux.development
Path: gmd.de!newsserver.jvnc.net!darwin.sura.net!howland.reston.ans.net!
math.ohio-state.edu!magnus.acs.ohio-state.edu!cis.ohio-state.edu!
news.sei.cmu.edu!bb3.andrew.cmu.edu!honeydew.srv.cs.cmu.edu!ddj
From: d...@cs.cmu.edu (Doug DeJulio)
Subject: Linux v1.0: what's in it?
Message-ID: < CJw66t.I0t.3@cs.cmu.edu>
Sender: n...@cs.cmu.edu (Usenet News System)
Nntp-Posting-Host: itc.cs.cmu.edu
Organization: School of Computer Science, Carnegie Mellon
Date: Wed, 19 Jan 1994 19:30:29 GMT
Lines: 9
So, what's going to be in the 1.0 kernel? I'm wondering if my
favorate patches will be included. They are the CLUSTER SCSI I/O
performance patches, and the acct/quota patches. The first doubles my
disk performance, and the second makes me feel better about letting
random internet users use my guest accounts.
--
Doug DeJulio
d...@cmu.edu
Newsgroups: comp.os.linux.development
Path: gmd.de!newsserver.jvnc.net!howland.reston.ans.net!pipex!
uknet!EU.net!sun4nl!rnzll3!pe1chl!rob
From: r...@pe1chl.ampr.org (Rob Janssen)
Subject: Re: Linux v1.0: what's in it?
References: < CJw66t.I0t.3@cs.cmu.edu>
Organization: PE1CHL
Date: Wed, 19 Jan 1994 22:26:19 GMT
Message-ID: <1994Jan19.222619.8580@pe1chl.ampr.org>
Reply-To: pe1...@rabo.nl
Lines: 18
In < CJw66t.I0...@cs.cmu.edu> d...@cs.cmu.edu (Doug DeJulio) writes:
>So, what's going to be in the 1.0 kernel? I'm wondering if my
>favorate patches will be included. They are the CLUSTER SCSI I/O
>performance patches, and the acct/quota patches. The first doubles my
>disk performance, and the second makes me feel better about letting
>random internet users use my guest accounts.
Those will not be in it. Only features currently in the distributed kernel
will be in 1.0
Rob
--
-------------------------------------------------------------------------
| Rob Janssen | AMPRnet: r...@pe1chl.ampr.org |
| e-mail: pe1...@rabo.nl | AX.25 BBS: PE1CHL@PI8UTR.#UTR.NLD.EU |
-------------------------------------------------------------------------
Newsgroups: comp.os.linux.development
Path: gmd.de!xlink.net!howland.reston.ans.net!cs.utexas.edu!uunet!
news.sprintlink.net!connected.com!inex!carlb
From: ca...@inex.com (Carl Boernecke)
Subject: Re: Linux v1.0: what's in it?
References: < CJw66t.I0t.3@cs.cmu.edu>
<1994Jan19.222619.8580@pe1chl.ampr.org> < COE.94Jan19204650@leopard.bert.cs.byu.edu>
Organization: InEx Net, Seattle, Washington
Date: Thu, 20 Jan 1994 13:17:36 GMT
Message-ID: <1994Jan20.131736.6031@inex.com>
Lines: 33
c...@bert.cs.byu.edu (Mike Coe) writes:
> Those will not be in it. Only features currently in the distributed kernel
> will be in 1.0
> Rob
[cheap Amoeba shot removed...]
I must say that I'm glad Linus and folks are doing the freeze on
the code. This will give it a chance to settle-down, thus giving
us a uniform place to base all future development on. Only big
thing that holds me back from fully endorsing 1.0 is the network
code; how is it holding up? I know my 0.99pl14o stuff with both
PPP and SLIP runs better than any previous release, but it does
ocasionally 'hang.' I'm not sure if it's due to the machines I
have that run NOS (KA9Q), or my Linux boxes, though I would assume
that it's the latter.
So, is the networking code stable, or not? Will we ('we' being
the thousands of loyal Linux users) finally be able to compare our
systems to those that run NetBSD or FreeBSD? Their only real
bragging point has been the networking code. Will this realase
effectively remove that point from the 'my system is better than
your system' discussions? I don't really care, though, just
curious.
Finally, Linus said the freeze would happen when pl15 was released,
but I didn't see a date. Did I just miss it, or was it not mentioned?
--
-- Carl Boernecke (ca...@inex.com [MIME-ready])
"Remember, rive carefully. 90% of all people are caused by
accidents."
Newsgroups: comp.os.linux.development
Path: gmd.de!xlink.net!howland.reston.ans.net!pipex!uknet!cf-cm!
cybaswan!iiitac
From: iii...@swan.pyr (Alan Cox)
Subject: Re: Linux v1.0: what's in it?
Message-ID: <1994Jan21.163734.9473@swan.pyr>
Organization: Swansea University College
References: <1994Jan19.222619.8580@pe1chl.ampr.org>
< COE.94Jan19204650@leopard.bert.cs.byu.edu> <1994Jan20.131736.6031@inex.com>
Date: Fri, 21 Jan 1994 16:37:34 GMT
Lines: 43
In article <1994Jan20.131736.6...@inex.com> ca...@inex.com
(Carl Boernecke) writes:
>I must say that I'm glad Linus and folks are doing the freeze on
>the code. This will give it a chance to settle-down, thus giving
>us a uniform place to base all future development on. Only big
>thing that holds me back from fully endorsing 1.0 is the network
>code; how is it holding up? I know my 0.99pl14o stuff with both
>PPP and SLIP runs better than any previous release, but it does
>ocasionally 'hang.' I'm not sure if it's due to the machines I
>have that run NOS (KA9Q), or my Linux boxes, though I would assume
>that it's the latter.
Pl14t has a collection of major TCP write side fixes contributed by
people. It would have more for closing down too but time runs out
before I can get them all in....
PPP won't be in 1.0 because the developers choose to class it as ALPHA.
It's awfully stable for alpha test software 8-). Bear in mind most of the
distributors add some of the alpha/beta pieces either directly (grrr!) or
as patch kits in /usr/src (which I much prefer). So I'd expect PPP to
at least be on the CD-ROM distributions even if it has WARNING ALPHA TEST
stamped all over it.
What I'm looking forward to then is the finished version of SLS everything
as loadable modules....
>So, is the networking code stable, or not? Will we ('we' being
>the thousands of loyal Linux users) finally be able to compare our
>systems to those that run NetBSD or FreeBSD? Their only real
It's better than it was. The BSD bods have had 15 years to get their
code stable in various environments, which helps no end. if it annoys
you ask them about DOS emulation, choice of network cards, and things.
It's all a bit pointless this comparing lark. If it does what you want
use it.
>bragging point has been the networking code. Will this realase
>effectively remove that point from the 'my system is better than
>your system' discussions? I don't really care, though, just
>curious.
Why go down to their level ?
Alan
iii...@pyr.swan.ac.uk