From: Pavel Zaitsev <pavel@md5.ca>
To: linux-kernel@vger.kernel.org
Subject: kernel changes
Date: Fri, 28 Sep 2001 14:32:05 -0700 [thread overview]
Message-ID: <20010928143205.B3669@md5.ca> (raw)
[-- Attachment #1: Type: text/plain, Size: 979 bytes --]
Hey guys,
I have been watching development of 2.4 since 2.4.2, I wonder wether
there would be reversion to old process where kernel source will be
solidified before starting development branch. Sysadmins where I work
are uneasy to move to linux from solaris, because of erratic changes
to the kernel such as replacement of the hardware monitoring code, rewriting
of network card drivers - all of which broke some or other software,
or simply did not work. I myself update kernel as time permits,
usually every 0.0.2+ I have spent nearly two days tracing problem
of my network, that ended up in source code of the driver that have
been radically changed for "better". Now I don't trust 2.4 line
kernel to work *at all*, so cautiously keep all old kernels in the /boot,
when upgrading.
It seems I am not only one and wonder if something will be done about that.
Regards,
p.
--
Research causes cancer in rats.
110461387
http://gpg.md5.ca
http://perlpimp.com
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next reply other threads:[~2001-09-28 21:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-28 21:32 Pavel Zaitsev [this message]
2001-09-28 22:04 ` kernel changes Mark Frazer
2001-09-28 22:31 ` Ben Greear
2001-09-28 22:33 ` Alan Cox
2001-10-01 9:07 ` Paul Larson
2001-09-28 22:06 ` Alan Cox
2001-09-29 13:43 ` Andrew Ebling
2001-09-29 7:25 ` Mika Liljeberg
2001-09-29 10:19 ` Ville Herva
2001-09-29 16:45 ` John Alvord
2001-09-29 17:23 ` arjan
2001-09-30 8:17 ` John Alvord
2001-10-01 17:07 ` Martin J. Bligh
[not found] <fa.b97kd6v.8j2vhi@ifi.uio.no>
[not found] ` <fa.hmvo4bv.l2gsaj@ifi.uio.no>
2001-09-29 7:29 ` Dan Maas
2001-10-04 0:36 ` bill davidsen
2001-10-04 9:43 ` John Alvord
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=20010928143205.B3669@md5.ca \
--to=pavel@md5.ca \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.