Sure you could do the same things to the bigger displacement engine (whether or not its American German or whaterver). But you won't get 37mpg out of those huge engines with the same performance.
You're forgetting the two tools of the trade which are used daily to pump put huge amounts of power:
Turbo's and Superchargers.
Let's say your 1.6l Civic makes 130hp stock. Throw on some bolt on aftermarket parts, you might get it up to 145hp. Really do to town on it, tear it down and build it back up with the intention of making lots of horsepower and you'll get close to 200hp.
Now throw on your typical turbo kit with ~6-7 lbs of boost. Instant 60hp gain. Now you're pushing close to 200hp with just about no loss of mileage under normal driving conditions. Yes, you'll still get 37mpg cruising the freeways!
Now that little Civic is a real threat to your big Dodge with a weight/hp ratio just about equal. And you don't have to feel guilty about burning a gallon of gas on the way to the grocery store.
Or you could leave yourself open to the security holes which existed in previous kernels to local users.
If you don't have anyone that uses your system, then staying on 2.4.5 might not be a bad idea, but at the very least you should be testing the latest releases in case you find a problem that forces you to upgrade.
Do what I did, send out a message on my local LUG saying you have a bunch of old hardware laying around, that's free for pickup.
Before you know it, you'll have dozens of Linux Users clamoring at your door to pick it up for their various projects. You'll get rid of all your stuff, and someone else might actually end up using it!
After installing any distro, you want to update all the software to the latest bugfixes.
For RedHat, this means FTPing to updates.redhat.com and downloading all errata for your distribution release and running a rpm -Fvh *.rpm. You will notice that this includes a kernel update as well, bumping it up to 2.4.9-something.
Running a distro kernel is the best thing to do for most users. The QA process the distribution goes through is part of what you're paying for when you buy the shiny box!
Re:What are YOU doing to help test the pre release
on
Linux 2.4.16 Released
·
· Score: 1
I'm not sure where you think I say Nobody uses pre-release versions, I said most.
If you run pre-release kernels on mission-critical servers, why are you complaining about the quality of the so-called release kernels? Obviously you know what you're doing and know enough to not trust a kernel until you can test it under your workload and hardware.
I can't argue with the fact that a full-regression test-suite for the kernel is a good idea. In fact, people are already working on it over at the Linux Test Project.
What are YOU doing to help test the pre releases?
on
Linux 2.4.16 Released
·
· Score: 2, Insightful
You know what? As Linus posted to LKML[1], it doesn't matter if there are a million pre releases, as long as it's a pre release, most people don't download it and run it on their hardware and workloads. Not to mention the fact that Linus doesn't like to maintain kernels and turns them over to other maintainers (Alan and Marcelo) for maintenance.
Hence, bugs don't turn up until after real releases are made.
Anyone who goes out and runs a shiny new kernel on a mission critical machine which was released 20 minutes ago is just asking for trouble. These kernels simply don't get the QA they need to be determined to be stable for a number of days after they're released.
If you want a QA tested kernel, go to RedHat, Suse or any of the other Linux distributions, shell out whatever they charge for bundling it up and use their kernel. When that kernel breaks, go whine to the distribution maintainers. (I've done this personally with RedHat, and found them to be very responsive to bug reports.)
Its either that, or fix it yourself, it's that simple. What, you want something for nothing? That's not how free software works.
Whining about the problem will not fix it. Going out and fixing it yourself, will.
1. See posts about Linus and maintaining stable kernels here and here.
If they're doing a lot of I/O device control directly with the app, they're going to have to code different versions for Unix and NT with C/C++, too. Your argument doesn't help here unless there's a cross-platform I/O device control library, in which case you can still use JNI to interface with that.
Why not use Java JNI to help give a clean interface between the code which needs to be platform dependant?
Re:Which releases are production stable?
on
Linux 2.4.13
·
· Score: 1
Lots of good comments here, and I'll throw in my 2c and experience with them:
The entire 2.4 series is called stable. Whether or not that is actually true for you is a different story.
For every stable kernel, there is someone out there where something doesn't work quite right in it and that person will call it unstable.
If you want a highly tested kernel, don't use Linus' or Alan's kernel, instead use a kernel from a distribution such as Redhat, Debian, Suse or Mandrake. Linus' kernel is stable for Linus, Alan's kernel is stable for Alan, and each distribution's kernel is stable for them.
Linus's and Alan's kernels receive less testing than a distributions kernel, so unless their kernel's have some feature or bugfix that you can't live without, stick with a distribution's kernel.
Of course, if you just want to be l33t and say that you're running the latest kernel 2.4.45-ac32, go ahead. Just don't cry if it doesn't work on your setup and workload.
You're thinking of inexpensive ATA RAID, while they explicitly wanted a SCSI solution for speed. But SCSI RAID is _expensive_ - it's professional workstation class hardware, not within the budget for a personal machine (no matter that they say "cost is no object" - clearly there are limits here).
Hmm, have you looked at the price of SCSI RAID cards lately? Certainly not out of the bugdet, you can pick up an Adaptec single channel RAID card for $333.95 at mwave.com. This card supports raid 0, 1, 0/1, and 5.
Having redundant disks is important enough to me to spend the ~$350 + extra disk that I would consider it on any machine where I consider uptime to be important.
4-5 months ago I put 3 15GB 75GXP drives into a Linux server. 1 month ago, 2 of them started failing reporting bad sectors and bad clicking noises.
Both of these drives were made in Thailand, so it's not just the Made in Hungary drives.
I also had a 40GB 40GV (a 5400 RPM drive!) completely die after 3-4 months at about the same time the 75GXP drives died. It would no longer get detected by the BIOS in any machine I tried. This drive was also Made in Thailand.
All three drives were RMAd and now I have 3 new IBM drives sitting here, but I'm scared to put them back into any mission critical machine.
Apache Projects have got to be some of the most collaborative and open projects out there. Go read
the Apache Jakarta's Getting Involved document to see how to get involved there. It's the same for all Apache projects.
Which translates into people willing to pay roughly ZERO for anything less than a 500Mhz improvemen. ZERO dollars for which Intel may have invested billions of dollars to generate.
What makes you think that a 500MHz increase in CPU speed today is harder to achieve than a 50MHz increase 5 years ago?
5 years ago when the Pentium 200s were hot, another 50MHz would have been as big a deal as 500MHz today. It will take the same amount of time, too.
Let me point you to Moore's Law clearly shows that CPU speeds increase at the same rate.
Let me tell you also, that if I'm running a maching on CPU bound tasks, even a 5% speed increase is worth buying. Especially if those tasks I'm running take large amounts of time to complete (weeks for scientific calculations!).
Umm... Do you EVEN know what you're talking about?
on
Linux 2.4.7 Released
·
· Score: 1
Have you been paying attention to 2.4 kernel development at all?
If you've watched linux-kernel at all, you will know that there are several potentially system-crippling bugs which were fixed in 2.4.7.
If you NEED your 2.4.x kerneled Linux machine running, I would recommend one of the following before upgrading any mission critical servers:
1. Stick with RedHat's official 2.4.3-12 kernel if you don't know what you're doing.
2. Else wait a couple days for the guinea pigs to find any serious bugs and any patches you run to be ported to 2.4.7.
3. If it all looks OK, then download, config, compile and install.
Besides, using the newest kernel DOES make you more 1337. Ask anyone. You don't see Linus running old kernels do you, and no-one gets more 1337 than him!
Lots of obscure deadlocks fixed.
A number of Reiserfs patches (including one to make exporting NFS shares work properly).
Lots of driver updates.
Lots of platform updates (s390, sparc, mips)
I love their silencer cooling fans ($9 each), open up your power supply and swap this fan in place of it, works great. A lot cheaper than the ~$100 for a new PSU.
Throw this fan in the front of your case too, to get extra airflow lost when moving to this quiet fan.
Their CPU coolers also work well and are very quiet.
After switching my K6-2 450 to their 275W silencer power supply, a silencer fan in the front, their CPU fan, the loudest thing in my case was the hard-drive.
Modern 5400 RPM drives are a LOT quieter than 7200 RPM and older 5400/7200 RPM drives. Pick up one of the new inexpensive Seagate, Fujitsu or Quantum drives, they run just about silent.
After all these changes, I can finally sleep in peace (only a very slight whirring left) with my PC on all the time.
If you have a faster CPU, the CPU coolers that PC power and cooling sells aren't up to the job IMO. In that case, you'll want to look at water cooling your CPU. Cheap, and a lot quieter than most CPU fans, since this one uses a 120mm fan spinning slowly at ~2K RPM instead of the normal 60mm fan spinning at 5-8K RPM.
Velocity 1.0 has been officially released, check it out.
It's more than a web based template engine, it also works wonders for generating any type of text-based content from templates.
The Velocity engine can be loaded in stand alone apps as well as Java Servlets, so it's very flexible!
It also performs great, I found it significantly faster than JSP for some simple pages.
Re:Upgrading from 1.3.x & preserving configuration
on
Apache 2.0 Goes Beta
·
· Score: 1
Well, if you want SSL support, I would stay away from the Apache 2.0.x series, I would consider mod_tls alpha quality since they only recently got it's SSL support working.
Upgrading to Apache 1.3.19 and mod_ssl is the way to go for now, unless you feel the need to pay for Stronghold.
There really isn't any easy way to merge the configuration file to 1.3.19. My best suggestion is to set up the new server running on an alternate port (like 8080/8443) and move the configuration over bit by bit, testing as you go.
I haven't run it on any 486/66s, but I have run it on a P133/64MB. Comparing to 2.2.18, 2.4.0 feels very good. Memory management is improved as there is less swapping and programs feel like they run faster.
There's no reason not to at least try it out, (except that it'll take a couple hours to compile the kernel on your 486!), so go for it.
Domain names in the.com,.net, and.org domains can now be registered
with many different competing registrars. Go to http://www.internic.net
for detailed information.
MICROSOFT.COM.WILL.LIVE.FOREVER.BUT.LUNIX.SUCKS- BY BIRTH.ARTISTICCHEESE.COM
MICROSOFT.COM.SHOULD.GIVE.UP.BECAUSE.LINUXISGOD. CO M
MICROSOFT.COM.SE.FAIT.HAX0RIZER.PAR.TOUT.LE.ZOY. OR G
MICROSOFT.COM.OWNED.BY.MAT.HACKSWARE.COM
MICROSOFT.COM.N-AIME.BILL.QUE.QUAND.IL.N-EST.PAS .N U
MICROSOFT.COM.MUST.STOP.TAKEDRUGS.ORG
MICROSOFT.COM.IS.SOON.GOING.TO.THE.DEATHCORPORAT IO N.COM
MICROSOFT.COM.IS.SECRETLY.RUN.BY.ILLUMINATI.TERR OR ISTS.NET
MICROSOFT.COM.IS.NOTHING.BUT.A.MONSTER.ORG
MICROSOFT.COM.IS.NO.MATCH.FOR.THE.UEBER-GEEKS.AT .J IMPHILLIPS.ORG
MICROSOFT.COM.IS.GOD.BUT.LINUX.SUCKS-FOREVER.ART IS TICCHEESE.COM
MICROSOFT.COM.IS.BORING.COMPARED.TO.TEENEXTREME. CO M
MICROSOFT.COM.IS.AT.THE.MERCY.OF.DETRIMENT.ORG
MICROSOFT.COM.INSPIRES.COPYCAT.WANNABE.SUBVERSIV ES.NET
MICROSOFT.COM.HAS.NO.LINUXCLUE.COM
MICROSOFT.COM.HACKED.BY.PSYKOJOKO.ON.A.ROOT-NETW OR K.COM
MICROSOFT.COM.HACKED.BY.HACKSWARE.COM
MICROSOFT.COM.GUTS.NL
MICROSOFT.COM.FAIT.VRAIMENT.DES.LOGICIELS.A.TROI S. FRANCS.DOUZE.ORG
MICROSOFT.COM.ER.IKKE.NO.I.FORHOLD.TIL.LATHANS.N ET
MICROSOFT.COM.AINT.WORTH.SHIT.KLUGE.ORG
MICROSOFT.COM
To single out one record, look it up with "xxx", where xxx is one of the
of the records displayed above. If the records are the same, look them up
with "=xxx" to receive a full display for each record.
>>> Last update of whois database: Tue, 23 Jan 2001 10:55:29 EST
The Registry database contains ONLY.COM,.NET,.ORG,.EDU domains and
Registrars.
There was a thread when 2.4.0 came out on linux-kernel that some (or all?) 386s had problems booting. You should be able to find the thread from a list archive. (Try here). The bug was found when some guy was trying to boot 2.4.0 on a 386 with 4 or 5MB of ram.
It's fixed in the latest pre-patches, so you just might want to wait until 2.4.1 to try it out since it'll take forever for it to compile on a 386. By the time it is done compiling, you 2.4.1 might be out, anyway!;-)
FWIW, I am using 2.4.0 on a P133/64MB and it runs great. This would be way overkill for just a firewall, we're using it as a development machine running Apache.
Your 486/100 32MB machine will be overkill for a firewall.
Slashdot Mirror
Would love to, but support for many modules including PHP is flaky at best at this time.
Thanks for the complement.
But did you even read what I wrote?
Sure you could do the same things to the bigger displacement engine (whether or not its American German or whaterver). But you won't get 37mpg out of those huge engines with the same performance.
You're forgetting the two tools of the trade which are used daily to pump put huge amounts of power:
Turbo's and Superchargers.
Let's say your 1.6l Civic makes 130hp stock. Throw on some bolt on aftermarket parts, you might get it up to 145hp. Really do to town on it, tear it down and build it back up with the intention of making lots of horsepower and you'll get close to 200hp.
Now throw on your typical turbo kit with ~6-7 lbs of boost. Instant 60hp gain. Now you're pushing close to 200hp with just about no loss of mileage under normal driving conditions. Yes, you'll still get 37mpg cruising the freeways!
Now that little Civic is a real threat to your big Dodge with a weight/hp ratio just about equal. And you don't have to feel guilty about burning a gallon of gas on the way to the grocery store.
Or you could leave yourself open to the security holes which existed in previous kernels to local users.
If you don't have anyone that uses your system, then staying on 2.4.5 might not be a bad idea, but at the very least you should be testing the latest releases in case you find a problem that forces you to upgrade.
Do what I did, send out a message on my local LUG saying you have a bunch of old hardware laying around, that's free for pickup.
Before you know it, you'll have dozens of Linux Users clamoring at your door to pick it up for their various projects. You'll get rid of all your stuff, and someone else might actually end up using it!
Hey, it worked for me!
You've almost got it.
After installing any distro, you want to update all the software to the latest bugfixes.
For RedHat, this means FTPing to updates.redhat.com and downloading all errata for your distribution release and running a rpm -Fvh *.rpm. You will notice that this includes a kernel update as well, bumping it up to 2.4.9-something.
Running a distro kernel is the best thing to do for most users. The QA process the distribution goes through is part of what you're paying for when you buy the shiny box!
I'm not sure where you think I say Nobody uses pre-release versions, I said most.
If you run pre-release kernels on mission-critical servers, why are you complaining about the quality of the so-called release kernels? Obviously you know what you're doing and know enough to not trust a kernel until you can test it under your workload and hardware.
I can't argue with the fact that a full-regression test-suite for the kernel is a good idea. In fact, people are already working on it over at the Linux Test Project.
You know what? As Linus posted to LKML[1], it doesn't matter if there are a million pre releases, as long as it's a pre release, most people don't download it and run it on their hardware and workloads. Not to mention the fact that Linus doesn't like to maintain kernels and turns them over to other maintainers (Alan and Marcelo) for maintenance.
Hence, bugs don't turn up until after real releases are made.
Anyone who goes out and runs a shiny new kernel on a mission critical machine which was released 20 minutes ago is just asking for trouble. These kernels simply don't get the QA they need to be determined to be stable for a number of days after they're released.
If you want a QA tested kernel, go to RedHat, Suse or any of the other Linux distributions, shell out whatever they charge for bundling it up and use their kernel. When that kernel breaks, go whine to the distribution maintainers. (I've done this personally with RedHat, and found them to be very responsive to bug reports.)
Its either that, or fix it yourself, it's that simple. What, you want something for nothing? That's not how free software works.
Whining about the problem will not fix it. Going out and fixing it yourself, will.
1. See posts about Linus and maintaining stable kernels here and here.
If they're doing a lot of I/O device control directly with the app, they're going to have to code different versions for Unix and NT with C/C++, too. Your argument doesn't help here unless there's a cross-platform I/O device control library, in which case you can still use JNI to interface with that.
Why not use Java JNI to help give a clean interface between the code which needs to be platform dependant?
Lots of good comments here, and I'll throw in my 2c and experience with them:
The entire 2.4 series is called stable. Whether or not that is actually true for you is a different story.
For every stable kernel, there is someone out there where something doesn't work quite right in it and that person will call it unstable.
If you want a highly tested kernel, don't use Linus' or Alan's kernel, instead use a kernel from a distribution such as Redhat, Debian, Suse or Mandrake. Linus' kernel is stable for Linus, Alan's kernel is stable for Alan, and each distribution's kernel is stable for them.
Linus's and Alan's kernels receive less testing than a distributions kernel, so unless their kernel's have some feature or bugfix that you can't live without, stick with a distribution's kernel.
Of course, if you just want to be l33t and say that you're running the latest kernel 2.4.45-ac32, go ahead. Just don't cry if it doesn't work on your setup and workload.
Hmm, have you looked at the price of SCSI RAID cards lately? Certainly not out of the bugdet, you can pick up an Adaptec single channel RAID card for $333.95 at mwave.com. This card supports raid 0, 1, 0/1, and 5.
Having redundant disks is important enough to me to spend the ~$350 + extra disk that I would consider it on any machine where I consider uptime to be important.
4-5 months ago I put 3 15GB 75GXP drives into a Linux server. 1 month ago, 2 of them started failing reporting bad sectors and bad clicking noises.
Both of these drives were made in Thailand, so it's not just the Made in Hungary drives.
I also had a 40GB 40GV (a 5400 RPM drive!) completely die after 3-4 months at about the same time the 75GXP drives died. It would no longer get detected by the BIOS in any machine I tried. This drive was also Made in Thailand.
All three drives were RMAd and now I have 3 new IBM drives sitting here, but I'm scared to put them back into any mission critical machine.
Apache Projects have got to be some of the most collaborative and open projects out there. Go read
the Apache Jakarta's Getting Involved document to see how to get involved there. It's the same for all Apache projects.
Select "Disaster Relief Fund" to have your money go towards the people affected by yesterday's attack.
For a desktop machine, bumping up the CPU speed isn't that big a deal. Having a fast hard drive makes a bigger difference.
But for servers and other machines doing constant work, doubling CPU speed makes a big difference.
What makes you think that a 500MHz increase in CPU speed today is harder to achieve than a 50MHz increase 5 years ago? 5 years ago when the Pentium 200s were hot, another 50MHz would have been as big a deal as 500MHz today. It will take the same amount of time, too. Let me point you to Moore's Law clearly shows that CPU speeds increase at the same rate.
Let me tell you also, that if I'm running a maching on CPU bound tasks, even a 5% speed increase is worth buying. Especially if those tasks I'm running take large amounts of time to complete (weeks for scientific calculations!).
Have you been paying attention to 2.4 kernel development at all?
If you've watched linux-kernel at all, you will know that there are several potentially system-crippling bugs which were fixed in 2.4.7.
If you NEED your 2.4.x kerneled Linux machine running, I would recommend one of the following before upgrading any mission critical servers:
1. Stick with RedHat's official 2.4.3-12 kernel if you don't know what you're doing.
2. Else wait a couple days for the guinea pigs to find any serious bugs and any patches you run to be ported to 2.4.7.
3. If it all looks OK, then download, config, compile and install.
Besides, using the newest kernel DOES make you more 1337. Ask anyone. You don't see Linus running old kernels do you, and no-one gets more 1337 than him!
The quick list:
Lots of obscure deadlocks fixed.
A number of Reiserfs patches (including one to make exporting NFS shares work properly).
Lots of driver updates.
Lots of platform updates (s390, sparc, mips)
The super quick list:
Lots of bug fixes, just upgrade damnit!
I love their silencer cooling fans ($9 each), open up your power supply and swap this fan in place of it, works great. A lot cheaper than the ~$100 for a new PSU.
Throw this fan in the front of your case too, to get extra airflow lost when moving to this quiet fan.
Their CPU coolers also work well and are very quiet.
After switching my K6-2 450 to their 275W silencer power supply, a silencer fan in the front, their CPU fan, the loudest thing in my case was the hard-drive.
Modern 5400 RPM drives are a LOT quieter than 7200 RPM and older 5400/7200 RPM drives. Pick up one of the new inexpensive Seagate, Fujitsu or Quantum drives, they run just about silent.
After all these changes, I can finally sleep in peace (only a very slight whirring left) with my PC on all the time.
If you have a faster CPU, the CPU coolers that PC power and cooling sells aren't up to the job IMO. In that case, you'll want to look at water cooling your CPU. Cheap, and a lot quieter than most CPU fans, since this one uses a 120mm fan spinning slowly at ~2K RPM instead of the normal 60mm fan spinning at 5-8K RPM.
It's more than a web based template engine, it also works wonders for generating any type of text-based content from templates.
The Velocity engine can be loaded in stand alone apps as well as Java Servlets, so it's very flexible!
It also performs great, I found it significantly faster than JSP for some simple pages.
Well, if you want SSL support, I would stay away from the Apache 2.0.x series, I would consider mod_tls alpha quality since they only recently got it's SSL support working.
Upgrading to Apache 1.3.19 and mod_ssl is the way to go for now, unless you feel the need to pay for Stronghold.
There really isn't any easy way to merge the configuration file to 1.3.19. My best suggestion is to set up the new server running on an alternate port (like 8080/8443) and move the configuration over bit by bit, testing as you go.
Good luck!
Don't forget that your telephone company will charge you per-minute while connected via ISDN.
This adds up pretty quick when you want you leave it on 24/7.
Let's see, at 1 cent a minute, it'll run you
60*24*30 = 43200 minutes in a month or $432/mo in telco charges.
Uh, no wonder ISDN isn't very popular.
Now if the telco doesn't charge per minute anymore, I want to hear about it!
There's no reason not to at least try it out, (except that it'll take a couple hours to compile the kernel on your 486!), so go for it.
> whois microsoft.com
.com, .net, and .org domains can now be registered
- BY BIRTH.ARTISTICCHEESE.COM
. CO M
. OR G
S .N U
T IO N.COM
R OR ISTS.NET
T .J IMPHILLIPS.ORG
T IS TICCHEESE.COM
. CO M
V ES .NET
W OR K.COM
I S. FRANCS.DOUZE.ORG
N ET
.COM, .NET, .ORG, .EDU domains and
[whois.crsnic.net]
Whois Server Version 1.3
Domain names in the
with many different competing registrars. Go to http://www.internic.net
for detailed information.
MICROSOFT.COM.WILL.LIVE.FOREVER.BUT.LUNIX.SUCKS
MICROSOFT.COM.SHOULD.GIVE.UP.BECAUSE.LINUXISGOD
MICROSOFT.COM.SE.FAIT.HAX0RIZER.PAR.TOUT.LE.ZOY
MICROSOFT.COM.OWNED.BY.MAT.HACKSWARE.COM
MICROSOFT.COM.N-AIME.BILL.QUE.QUAND.IL.N-EST.PA
MICROSOFT.COM.MUST.STOP.TAKEDRUGS.ORG
MICROSOFT.COM.IS.SOON.GOING.TO.THE.DEATHCORPORA
MICROSOFT.COM.IS.SECRETLY.RUN.BY.ILLUMINATI.TER
MICROSOFT.COM.IS.NOTHING.BUT.A.MONSTER.ORG
MICROSOFT.COM.IS.NO.MATCH.FOR.THE.UEBER-GEEKS.A
MICROSOFT.COM.IS.GOD.BUT.LINUX.SUCKS-FOREVER.AR
MICROSOFT.COM.IS.BORING.COMPARED.TO.TEENEXTREME
MICROSOFT.COM.IS.AT.THE.MERCY.OF.DETRIMENT.ORG
MICROSOFT.COM.INSPIRES.COPYCAT.WANNABE.SUBVERSI
MICROSOFT.COM.HAS.NO.LINUXCLUE.COM
MICROSOFT.COM.HACKED.BY.PSYKOJOKO.ON.A.ROOT-NET
MICROSOFT.COM.HACKED.BY.HACKSWARE.COM
MICROSOFT.COM.GUTS.NL
MICROSOFT.COM.FAIT.VRAIMENT.DES.LOGICIELS.A.TRO
MICROSOFT.COM.ER.IKKE.NO.I.FORHOLD.TIL.LATHANS.
MICROSOFT.COM.AINT.WORTH.SHIT.KLUGE.ORG
MICROSOFT.COM
To single out one record, look it up with "xxx", where xxx is one of the
of the records displayed above. If the records are the same, look them up
with "=xxx" to receive a full display for each record.
>>> Last update of whois database: Tue, 23 Jan 2001 10:55:29 EST
The Registry database contains ONLY
Registrars.
It's fixed in the latest pre-patches, so you just might want to wait until 2.4.1 to try it out since it'll take forever for it to compile on a 386. By the time it is done compiling, you 2.4.1 might be out, anyway! ;-)
FWIW, I am using 2.4.0 on a P133/64MB and it runs great. This would be way overkill for just a firewall, we're using it as a development machine running Apache.
Your 486/100 32MB machine will be overkill for a firewall.