Re: [cobalt-users] RaQ3 & 2.4 kernel (link to unofficial release dead)

["E.B. Dreger" <eddy+public+spam@xxxxxxxxxxxxxxxxx>]

FJ> Date: Mon, 7 Apr 2003 15:21:28 +0200
FJ> From: Frank Joerdens


FJ> ftp://ftp.cobaltnet.com/pub/users/thockin/2.4/
FJ>
FJ> which is dead however. Does anyone know if/where it can be
FJ> found still?  Any ideas as to upgrading glibc?

Huh?  I was at that FTP site last night. :-)  As for glibc, I'd
just install a standard glibc... AFAIK, the Cobalt funkiness is
contained in the kernel.


FJ> Why do I think that I need a 2.4 kernel? - I'd like to have
FJ> stateful firewalling via iptables, advanced (policy) routing
FJ> (a.k.a. traffic shaping), and might like to put ipsec into
FJ> the kernel. I also want a custom kernel anyway since I'd like
FJ> to disable loadable modules for security reasons.

All sound good.

FWIW, I'd like to point out that policy routing is different from
traffic shaping.


FJ> What do I intend to do with it? - Run Apache, PHP, PostgreSQL
FJ> mostly.

If you upgrade the kernel to 2.4, read the instructions.  Tim
Hockin's info explains things well... just make certain you use
_III images (NOT _V) and run ROM revision 2.3.x, where x >= 38;
2.3.40 is currently available, although I've not tried it.

I'm considering moving a RaQ4 to 2.4 kernel, due to what I'm
certain is a kernel bug in 2.2.16C33_III.  I had no luck
attempting to merge Cobalt patches with 2.2.17; I've not tried
newer kernels.

Finally, STW for a general "upgrading 2.2 to 2.4" guide.  Some
other elements, such as binutils, need to be at least a certain
version.


HTH,
Eddy
--
Brotsman & Dreger, Inc. - EverQuick Internet Division
Bandwidth, consulting, e-commerce, hosting, and network building
Phone: +1 (785) 865-5885 Lawrence and [inter]national
Phone: +1 (316) 794-8922 Wichita

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Date: Mon, 21 May 2001 11:23:58 +0000 (GMT)
From: A Trap <blacklist@xxxxxxxxx>
To: blacklist@xxxxxxxxx
Subject: Please ignore this portion of my mail signature.

These last few lines are a trap for address-harvesting spambots.
Do NOT send mail to <blacklist@xxxxxxxxx>, or you are likely to
be blocked.