Kernel 2.4.26 brings us up to date with the latest stable 2.4 kernel. It also contains the fix for the recently announced kernel vulnerability:

http://isec.pl/vulnerabilities/isec-0015-msfilter.txt

2.4.26-linode26-1um is built using the -1um stable UML patch, not the buggy -2um patch from the linode25 kernel.

How to Upgrade

See if you're already running 2.4.26-linode26-1um by viewing the output of "uname -a" inside your Linode. If not, follow this procedure:

Log into the Linode Platform Manager (LPM)
Configuration Profiles --> Click on your configuration profile
Make sure the Kernel drop-down has "Latest 2.4 Series" selected and Save
Reboot your Linode

Thanks and enjoy!
-Chris

Just wanted to say I upgraded without a problem. Thanks for the new kernel!

It works fine!

It works OK for me too.

I get the impression that over the past 6 months, the various impovements have greatly improved system responsiveness.

Wouldn't boot...

Oddly enough, I tried the 2.4.26 kernel first, and it wouldn't boot... even tried twice. Swtiched to 2.6.4, and everything looks good now. Very strange.

_________________
----
Ed/Bones.

Yeah -- There's still a bug I'm chasing on hosts running 2.6. It has nothing to do with the kernel version you're running on your Linode.

br0: port 12(necrobones_0) entering disabled state
unregister_netdevice: waiting for necrobones_0 to become free. Usage count = 4

Something isn't releasing the network device on the host, so a reboot fails. After a while (30 seconds?) it clears up and you're able to boot again...

-Chris

How come we don't get notified via email (the linode-announce group) whenever there's a new kernel?

_________________
http://understroem.dk/
http://findhim.com/

my postfix broke and gave the following log messages about the time I upgraded to this newer kernel. any chance its kernel related?

and if not, anyone have any other ideas?

postfix/smtp[14388]: fatal: unknown service: smtp/tcp
postfix/qmgr[14380]: warning: premature end-of-input on private/smtp socket while reading input attribute name
postfix/qmgr[14380]: warning: private/smtp socket: malformed response
postfix/qmgr[14380]: warning: transport smtp failure -- see a previous warning/fatal/panic logfile record for the problem description
postfix/master[14376]: warning: process /usr/lib/postfix/smtp pid 14388 exit status 1
postfix/master[14376]: warning: /usr/lib/postfix/smtp: bad command startup -- throttling

It doesn't look kernel-related to me; it looks like your /etc/services file got hosed.

thanks, but /etc/services looks fine:
...
smtp 25/tcp mail
...

oh... and i'm using postfix 2.0.16 on Debian Sarge... anyone else on this system experience anything similar?

For postfix, "private/smtp" is a Unix domain socket. It probably lives in /var/spool/postfix/private/smtp

On my (own compiled) postfix package:

% ls -l /var/spool/postfix/private/smtp
srw-rw-rw- 1 postfix postfix 0 Apr 29 15:16 /var/spool/postfix/private/smtp

Check you haven't filled up your root disk, and other standard file system stuff

_________________
Rgds
Stephen
(Linux user since kernel version 0.11)

mine's in the same place and looks identical...

plenty of free space on the drive... the postfix user has good permissions everywhere it needs to (i think)...

i am using postfix + mysql, and i haven't gotten sasl to work yet, so my postfix has been delivering and forwarding only (only to accepted networks...)

thanks for the help... i've been reading everything on postfix i can, but nothing seems to talk about this sort of error. (except some people said to remove smtp from the chroot, which i tested, but had the same result)

You're running postfix chrooted? In that case you need to check stuff in /path/to/chroot/.... instead of in /

I've never done chroot'd postfix, but postfix (own compiled from snapshot) is running on my Fedora linode with the latest stable kernel quite happily.

_________________
Rgds

Stephen

(Linux user since kernel version 0.11)