Slashdot Mirror
Linux 2.2.11 Released
kuro5hin writes "Yet another in the stable 2.2 series, linux 2.2.11 is out and on the mirrors. Download, patch, compile, repeat as necessary. " Seems Alan has blessed us with a present for LinuxWorld. Please use a mirror to download it.
Maybe what we need is a view of economics where value is expressed as a complex number w/ both real and imaginary components; then products and services can have a phase angle as well as magnitude, and could go a long way toward pleasing both the cluel^H^H^H^H^Hlayperson user and the technical specialist at the same time, instead of one at the expense of the other. Where's my application form for a research grant...
But I may be hallucinating again.
Chuck
try { do() || do_not(); } catch (JediException err) { yoda(err); }
>Mind you, I'm not sure if doing a compile on an NFS-mounted filesystem will be much faster.
;-)
It has been my experience that it is much faster. I'm running a 486/100 w/16 mb as my masq/gateway box, I only have a 200mb HD on it now and no monitor, kbd - so I only compile from my PII on a nfs-mounted FS on the 486. This works just fine, compiles much faster than the 486 ever did (used to run this as a stand-alone box before I got cable) and it seems to complie just about as fast as a native filesystem on the PII does. (although I'm running a 10/100 mbps network, so your mileage could vary if you are using 10mbps)
I used to run an older kernel on this box because I hadn't gotten around to figuring out how to cross-compile from another macine, and the old kernel was fine. When I wanted to start port-forwarding, I moved up to 2.0.36 and patched it with port forwarding and recompiled from the PII. No sweat.
Anybody else notice that there is a serious shortage of moderator points being allotted lately?
:-)
Used to be that offtopic crap used to get hammered down to -1 where I didn't have to see it. Now I guess I'll have to start browsing at a score of 1 to filter out the AC's.
As of 11:30 GMT I don't see anything on the list to indicate file system corruption. Do you have a reference for this?
It is tempting, if the only tool you have is a hammer, to treat everything as if it were a nail. - Abraham Maslow
I thought that's how they came out with the Windows 2000 Betas..
Yeah, in comparison, Microsoft's expediency with fixes to bugs is phenomenal. You have to wait 6 months for a service pack that fixes a bug that exists but supposedly hasn't affected anyone.
be-fan wrote:
:-).
Actually, any version of Linux is infinate in value. If value is coolness/cost and cost=0, then now matter what the coolness is, value is infinity. That also means that if windows were free (it is, how many people actuall BOUGHT a copy of Windows 98?) it would also be infinite in value. Must be something wrong with my equation. Oh Well.
There's nothing wrong with your equation. People get Windows three ways: Retail sales (which are paid for), OEM computer purchases (which are paid for, the cost is just hidden in the cost of the system), and illegal copying (which are free, so infinite in value). In addition, the coolness of Windows is imaginary, so the value of any costly copy of Windows is also imaginary. The only Windows with real value are pirated copies
Likewise, the free developer's release of Be is infinite in value, but the users' versions are not (but they do have real value, not imaginary). Downloading Linux is far more valuable than getting a CD, but only if you have a flat rate internet connection. I think I should stop now.
----
----
Open mind, insert foot.
Its been said over and over, but should keep being said:
Avoid to "must upgrade" urge, especially on production servers. If it works, it doesn't need fixing.
The idea that these are "stable" kernels is a misnomer, they're just tweaks and updates on the stable tree, and there's no guarantee they're actually stable. Example in point, one of my servers was experiencing pretty serious corruption using MySQL in the databases, whenever the load on the database got too high. System was running 2.2.5 SMP. Upgraded to 2.2.9/SMP and the problem went away. Pretty indicative of a problem in 2.2.5.
If you've got a production server, you run the same risk that 2.2.11 might cause a problem that you weren't having before. So think first before upgrading, and only do it if you're having specific problems. We don't want people to start claiming Linux is as instable as NT because of the occasional bad kernel release (like some of the pre-2.0.36 kernels!).
If you can't get replaced you can't get promoted.
If the code and the comments disagree, then both are probably wrong. - Schryer
I find it amazing that, even though a kernel release has no features of bugfixes which directly impact a user, that user feels compelled into upgrading.
:)
People actually argue that Linux releases too many kernel upgrades too often. As if someone stands behinds them, points a gun at their head and forces to them compile and install the kernel.
I think this is probably one of those reasons FreeBSD is perceived to be more stable than Linux. It's because Linux people reboot their damn boxes for kernel upgrades every week (or 4) for no reason other than to have a spiffy new version number.
If you have a production server, don't fix what's not broken. Kernel upgardes for the sake of kernel upgrades is not a good reason
--
The world is neither black nor white nor good nor evil, only many shades of CowboyNeal.