I eventually bit the bullet and recompiled my kernel to version 2.4.4, and guess what, IT WORKED, well I was surprised Having done this I have some questions.
0)I missed a module out when I compiled the kernel, how do I compile just that module?
1)Would people recommend a 2.2 or 2.4 kernel for mission critical systems which need high availability?
2)What would people recommend in the way of journelling file systems?
I think that was all. Thanks to all who advised me on my earlier kernel thread.
Thanks
D
PS Mark: are all the admin messages archived in some shape or form?
__________________________________________________ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/
David Freeman wrote:
I eventually bit the bullet and recompiled my kernel to version 2.4.4, and guess what, IT WORKED, well I was surprised Having done this I have some questions.
0)I missed a module out when I compiled the kernel, how do I compile just that module?
1)Would people recommend a 2.2 or 2.4 kernel for mission critical systems which need high availability?
if you are talking about systems which need 500+ days of uptime, then It has to be 2.2 as 2.4 hasn't been tested for that long ;)..
2)What would people recommend in the way of journelling file systems?
I use reiserfs, but it really depends on what you want to do... Neill
--- Neill Newman neill@entora.co.uk wrote:
David Freeman wrote:
I eventually bit the bullet and recompiled my kernel to version
2.4.4,
and guess what, IT WORKED, well I was surprised Having done this I
have
some questions.
0)I missed a module out when I compiled the kernel, how do I
compile
just that module?
1)Would people recommend a 2.2 or 2.4 kernel for mission critical systems which need high availability?
if you are talking about systems which need 500+ days of uptime, then It has to be 2.2 as 2.4 hasn't been tested for that long ;)..
It only has to last 90 days. But it needs to be reliable and boot quickly. Also it needs to have a journelling filesystem of somekind.
2)What would people recommend in the way of journelling file
systems?
I use reiserfs, but it really depends on what you want to do... Neill
How well does that take to being shat upon, i.e. have reboots/powerloss during writes etc...?
Thanks
D
-- Open Source Specialists http://www.entora.co.uk/ Tel: +44 (0)701 0723686 Fax: +44 (0)870 3214368
__________________________________________________ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/
David Freeman wrote:
if you are talking about systems which need 500+ days of uptime, then It has to be 2.2 as 2.4 hasn't been tested for that long ;)..
It only has to last 90 days. But it needs to be reliable and boot quickly. Also it needs to have a journelling filesystem of somekind.
one of our production servers had 2.4.2 on with over 60 days uptime, then we had to reboot to stick in another disk.. I suspect 2.4.x (where x >= 2) will last 90 days without any problems... reiserfs is in 2.4.x
2)What would people recommend in the way of journelling file
systems?
I use reiserfs, but it really depends on what you want to do... Neill
How well does that take to being shat upon, i.e. have reboots/powerloss during writes etc...?
imho, it copes very well, I'm no journeling expert, but it seems to do the job well enough for our machines. A reboot after a powerfailure takes only a few seconds longer than a reboot without a powerfailure ;)..
Neill
On Fri, May 25, 2001 at 01:34:59AM -0700, David Freeman wrote:
2)What would people recommend in the way of journelling file systems?
I just moved /usr and /home over to reiserfs last night. No problems yet....
XFS seems a bit too new to trust, I'm not sure about ext3.