From: "Nils O. =?ISO-8859-1?Q?Sel=E5sdal=22?= <noselasd@Utel.no>"@vax.home.local
To: linux-kernel@vger.kernel.org
Subject: Re: Linux v2.5.40 - and a feature freeze reminder
Date: Tue, 1 Oct 2002 09:41:47 +0200 [thread overview]
Message-ID: <200210010741.g917flO15927@utelsystems.dyndns.org> (raw)
In-Reply-To: <fa.hu1gd9v.fku81p@ifi.uio.no>
In fa.linux.kernel, you wrote:
>> > And if it wasn't clear to the non-2.5-development people out there, yes
>> > you _should_ also test this code out even before the freeze. The IDE layer
>> > shouldn't be all that scary any more, and while there are still silly
>> > things like trivially non-compiling setups etc, it's generally a good idea
>> > to try things out as widely as possible before it's getting too late to
>> > complain about things..
>>
>> Basically: I would _love_ to test this kernel on my laptop here, but -
>> unfortunately - i need the laptop for my work. Which means i need it to work.
>>
>> So how much chance IS there to trash the filesystems? I guess a lot of ppl
>> like me are just waiting to test it out, but aren't willing to screw their
>> systems over it...
>
> There is not much chance.
>
> The only thing that can be guaranteed is that if nobody tests 2.5.x out, then 2.6.x
> will definitely have trivial bugs in it.
Which reminds me, I was testing 2.5.39 yesterday on a 433MHz x86, 224Mb ram.
I felt this was abit like some of the 2.4.7-2.4.9 kernels i once ran:
too happy swapping things out. Having mozilla and evolution in the background
while compiling some large projects, or doing lots of file copying
caused most of mozilla and evolution to be swapped out, and thus the desktop felt
alot slower than e.g. 2.4.19.
Other issue, it took me about 2 hours to figure out that it was enabling preemtion
that caused the kernel not to boot.
--
Vennlig hilsen/Best Regards
Nils Olav Selåsdal
System Engineer
UtelSystems a/s
Tlf: +47 370 45 431
w w w . u t e l s y s t e m s . c o m
next parent reply other threads:[~2002-10-01 8:46 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.mpta6av.960ggh@ifi.uio.no>
[not found] ` <fa.hu1gd9v.fku81p@ifi.uio.no>
2002-10-01 7:41 ` Nils O. =?ISO-8859-1?Q?Sel=E5sdal=22?= <noselasd@Utel.no> [this message]
[not found] <96096729@toto.iv>
2002-10-01 23:06 ` Linux v2.5.40 - and a feature freeze reminder Peter Chubb
2002-10-02 0:26 ` Chris Wedgwood
2002-10-01 11:39 Markus Weiss
2002-10-01 16:35 ` James H. Cloos Jr.
-- strict thread matches above, loose matches on Subject: below --
2002-10-01 7:32 Linus Torvalds
2002-10-01 7:39 ` DevilKin
2002-10-01 8:00 ` jbradford
2002-10-01 8:04 ` Linus Torvalds
2002-10-01 8:23 ` Thomas Molina
2002-10-01 8:27 ` DevilKin
2002-10-01 10:28 ` Jens Axboe
2002-10-01 8:49 ` Gregoire Favre
2002-10-01 10:42 ` Alan Cox
2002-10-01 12:25 ` jlnance
2002-10-01 15:34 ` Dave Jones
2002-10-01 17:02 ` Vojtech Pavlik
2002-10-01 14:48 ` Denis Vlasenko
2002-10-01 17:29 ` Adrian Bunk
2002-10-01 17:44 ` Kai Germaschewski
2002-10-01 21:14 ` Christoph Hellwig
2002-10-01 22:51 ` Chris Wedgwood
2002-10-02 0:35 ` Linus Torvalds
2002-10-02 0:52 ` Alexander Viro
2002-10-02 3:12 ` Linus Torvalds
2002-10-02 12:11 ` Andries Brouwer
2002-10-02 6:51 ` Jens Axboe
2002-10-05 22:28 ` Peter Osterlund
2002-10-05 22:39 ` Kai Germaschewski
2002-10-05 23:06 ` Peter Osterlund
2002-10-06 0:09 ` Linus Torvalds
2002-10-08 21:56 ` Hans Reiser
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=200210010741.g917flO15927@utelsystems.dyndns.org \
--to="nils o. =?iso-8859-1?q?sel=e5sdal=22?= <noselasd@utel.no>"@vax.home.local \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).