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.
Most of the addresses, ftp.us.kernel.org in particular, point to several machines, and which one you get is random. If you find a mirror that hasn't updated yet, just disconnect and try again. Same deal if you hit a really loaded server. Eventually you'll find one you like. I had no trouble just now.
And, of course, always get the patch(es), if you can.
Actually, since Alan Cox is now the official maintainer of the stable tree we might see kernels coming out at this time more often, considering he lives in England! :)
chown -R us.
I just have to whine - just when I FINALLY got some ISA ISDN cards this morning, what happens? Almost simultunaeosly comes 2.2.11 with support for those teles pci -cards too..
--
It has to work - rfc1925
Well, Linux may have some neat features on the top, but it lack a lot internally. I mean, Linux VM sucks big time(no merged cache/buffer, no zero-copy read()/write() etc), Linux has nothing like SoftUpdates, LFS or XFS etc, instead it uses unordered delayed writes and has a limited filesize of about(?) 2GB. Neat? I think that the Linux folks should implement some old neat features before they do neat new features. IMHO, if Linux is the best free OS, then FreeBSD is the better free OS. -T
Really, people into radio have thought in terms of UTC (formerly GMT) for years - remember where the International date line is and that on any day, when someone in Hawaii is just stumbling out of bed to get the paper and make breakfast, someone in Japan has already come home from work!
It's always sometime somewhere.
Chuck
try { do() || do_not(); } catch (JediException err) { yoda(err); }
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); }
BTW, the reason I knew about the new kernel was because of the linux-kernel-patch email list. Just send a message to majordomo@vger.rutgers.edu with "subscribe linux-kernel-patch " in the body of the message. They email out changelogs and, if the patches are small enough, complete patches whenever there's a fresh kernel.
----------------------
"This moon-cheese will make me very rich! Very rich indeed!
There is no K5 cabal.
I am not the real rusty.
Make sure your local machine name is listed in your hosts file. This will solve that problem.
(I was only an egg, but then I cracked)
SOrry haven't been following kernel devel recently *ouch*
I am planning to get a laptop soon, so I need to know which DVD drives are supported (if at all!) to make a decision.
linuxlover
My provider offered 128Kbit for $30 bucks,
or 1.5Mbit for $60/month. (it's an apartment complex and they run few T1s in it, then go over
phone cables) I decided to save money.
Nevetherless, I ALWAYS get around 80 Kbyte
download/upload to my office machine and under 14ms ping.
I think there are actually no 2 speed options -
it all sits on the same pipe. It just a scam.
P.S. It is amusing how many people on the subnet run stock Win95 with file sharing (to the whole world to see and write)... I thought about mailing them with a warning, but decided not to bother. What do you think, should I warn them? They are good people in this neibourhood.
<^>_<(ô ô)>_<^>
Some updates are more important than others. It is unfortunate that RH 6.0 shipped with 2.2.5 as they greatly improved TCP/IP performance with 2.2.7. Samba speed is now almost double on several of our client machines (4.7 MB/sec vs 2.6 MB/sec) also ultra/DMA support was improved after 2.2.5 (an automatic doubling of hard disk performance on one of our servers when we put on 2.2.7). 2.2.5 - good but comparatively slow 2.2.7 - nice 2.2.8 - sucked - someone rushed too much for more speed after MindCrap. 2.2.9 - 2.2.10 whispers of hard disk corruption. 2.2.11 - Time to upgrade :)
It defaults to your old configuration, and prompts you about new options only.
Methinks our "FreeBSD friend" was not trolling. His was just asking, using sarcasm (FreeBSD...), why should each and every kernel release be trumpeted? That's all. I think.
Wow, I didn't know that. I always figured they were the same server. Thanks. Still, it irks me to find out that some servers (notably, ftp.uk.kernel.org) seem to lag behind for days (I think 4 days is the longest I remember). I think it makes more since to call these "photograph" sites.
Actually most of us do it for fun.
Bitcoin pyramid: Join here: http://www.bitcoinpyramid.com/r/1427 it's FREE!
What's the point. Everytime we make big hype about a public release, something allways goes wrong, and kernel.blah.blah+1 shal be released within a few days. What's the point of using slashdotters as dogfood. heh. save the linux-kernel list the spam
Jordy, If you wanted to just start a flame war, I am sure the gang at Slashdot can send you the URLs for the top-10 flame-war subjects for your perusal, and save us from reading your typical "new kernel" message. If not, let the board know, and someone will dig 'em up.
Just compiled the 2.2.10 kernel on a slow 486 last friday. I'm very tempted to pretent that the new kernel is not there at all.....
*sigh*
Well, time to read up the new features/bug-fixes before I decide whether to download it or not... might not need it this time.
Didn't countries such as Great Britain throw all the convicts and other scum into boats with "American" written on them?;)
Unfortunately Linux is buggy like an old rug, and those kernel upgrades are in fact *needed* to keep production servers alive (actually, no sober sysadmin would run Linux on a production server - but there's no such thing as a sober sysadmin anyway).
He lives in Wales - see his wife's diary at http://roadrunner.swansea.linux.org.uk/~hobbit/ind ex.html.
-- Ed Avis ed@membled.com
Nah. "Australia".
My Karma: ran over your Dogma
StrawberryFrog
I bet everyone who flamed the AC has no clue about the Linux kernel. Just like the "Windoze" users they flame, they apply this patch, that patch without even looking to see what it does. One of these days it will catch up with them. Maybe not today, but someday. Richard E. Gooch (and yes, a real live kernel coder)
i hope
Its spelt "L-I-N-U-X", but pronunced as "Free Beer"
Try here: http://www.linux.org.uk/VERSION/relnotes.2211.html
...that news got posted at this time of night (or is it morning?). Props to Justin, for serving slashdotteres at 3:26 AM. Or maybe I'm just being silly and not thinking about the other coast of America.
I'll just quietly go and get 2.2.11 before the servers get busy.
It seems you haven't gotten *their* point.
Their point is: Sure, frequent releases mean that the code can get debugged in massive parallel.
*But* it seems that there isn't much appreciation in Linux development for *feature-frozen releases*. These would be releases put out solely for the purpose of fixing bugs, and *not* for adding new "features". These releases could be expected to be truly "stable" (and not cutting edge). Basically, Linux doesn't put out stable releases in the sense of *feature-frozen releases*. Although Linux claims to have "development" and "stable" releases, the truth is that the "stable" releases are treated as "development" releases also. The idea that "many eyeballs" can (as in "being able to" or even "being willing to") catch all bugs in something as complicated as the present Linux kernel is naive. The kernel development must adopt additional QA (Quality Assurance) techniques, or else we'll forever put up with frequent dribbleware. This is not to stomp on the great work the kernel guys are doing, but merely a suggestion about the direction they will be forced to take eventually if they want Linux's claims of superior quality to be other than exaggerated cheerleading.
Good job guys!.. World Domination is drawing nearer.
5 hours ? Try to run crash and come back then. I'd be curious but have not second spare machine at home anymore 8]
Sendmail looks up your hostname before starting up, and it takes a long time for it to find if it does not succeed (for example, you blew up your eth0, erased your /etc/hosts.conf or your /etc/resolv.conf).
Try looking up any other thing, you should have the same problem - nslookup will seem to hang forever until it dies. The same if you try to ping any machine without specifying its IP.
A word of warning - There have been ENORMOUS changes between RedHat 5.2 and the current Linux versions. Kernel 2.2.x will NOT work correctly with 5.x RHs if you don't install a bunch of RPMs, including the new glibc (which may force you to rebuild many programs).
My advice? Either downgrade, or (if possible) get an updated CD.
Those guys don't rest do they?
*Yawn*
Guess I'll go get me some source then =)
- dc.
It's just Crap.
>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.
you just got to love evolution :)
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.
Does this kernel have the dozen or so patches
that Alan Cox has made to 2.2.10?
Do the "ac" kernels have a web page?
I have always just kept the latest mainstream
kernel on my system but I've been told that the
latest "ac" kernel is really the one to have...
Is this true?
So are you saying that if someone finds an exploit/hole/bug in 2.0.37 that it shouldn't be fixed? It may not affect you, but I'm sure it might affect someone else?
The problem you are complaining about is actually the reason why linux is so stable; things get fixed in Internet time and there are thousands of people out there just looking for things to fix. If you believe that it is possible to put an official stamp of completion on a software project with the size and complexity of the linux kernel, you might as well go back to MS, because it ain't ever going to happen. The only difference is that linux problems get fixed right away, while you'll wait quite a while for the next NT service pack release.
If you aren't having any problems, then don't upgrade. But I recommend that you take a look at the kernel changelogs every once in a while, since you never know when I bug will be fixed that could affect you.
Posted by Justin:
:) and yes, i do live on the east coast, btw.
bedtime = 3am-noon
waketime = noon-7pm
i heard about this an hour ago and gave the mirrors time to sync. thanks for the kind words, though
And so is the 4.0-19990809-CURRENT iso image.
Is it really necessary to announce every kernel patch? It's not like Alan Cox isn't going to release 8 more next week. Like we really need to know that 2.2.11-ac12 is out...
Actually, 2.2.11 is the first kernel patch in recent memory to fix a pertinent, widespread problem, namely the massive FS corruption that seemed endemic in 2.2.10. How bad was it? It scared me into buying a tape drive. I'm quite glad to see 2.2.11.
I think there is a world market for maybe five personal web logs.
Patching your system beyond recognition is not the path to job security. There is no such thing as true job security, no-one is indespensable. Anyone who kids themeselves that they are is sadly deluded.
Then run windows :)
This is a definition of "fun" of which I was not previously aware...
Slashdot Must Post More Patches. I Want To See Every AC Patch For Linux, Announced On Slashdot. Every Apache Patch, Heck, Every Patch For Every Piece Of Software. That Would Kick A**.
Yo, niggaz, whassup?
Check the linux-kernel mailing list for details. Basically, several people have already reported filesystem corruption bugs in 2.2.11.
Well, at the time of writing, my local mirror
:-)
(ftp.uk.kernel.org, at HENSA) had it, in its full
glory.
Plenty fast enough for us UKers cowardly enough
to want the stable series..
Remember, some mirrors are faster than others-
balance speed of update with mirror load in making
your choice. There are a LOT of mirrors.
Enjoy..
I believe RAID patches are in all of the 2.2 series. I have 3 boxes using the software RAID tools to concatenate large IDE disks and so far everything has been hunky dory. Can't wait to try this with the new IBM 37GB IDE monsters! With a Promise card I'll be able to put together a .25 TB file server for about $5,500. Course there is the lack of fault tolerance, but most of the data we are serving is Read Only and the originals are on CDROM. Since most of our ancient network is 10-Base-T performance of the "slow" IDE drives has not been an issue..... Loosing interest in tape libraries and HSMs (we've been dabling in this fied a little). At $22,000 for a terrabyte of online storage it's hard to see a reason for "nearline" storage.
DOOM clone is in Excel 95. You might be amused by the flight simulator in Excel 97, although it is admittedly somewhat less interesting.
Here's how to get to it:
(courtesy of eeggs.com:)
1. On a new Worksheet, Press F5
2. Type X97:L97 and hit enter
3. Press the tab key
4. Hold Ctrl-Shift
5. Click on the Chart Wizard toolbar button
6. Use mouse to fly around - Right button forward/ Left button reverse
Drop by eeggs.com to find some of the other, less "official"-looking (read: likely non-sanctioned) eggs.
---
DNA just wants to be free...
>
GEEK!!!!
lol
yeah i do. but the server is inside a large intranet - who's going to bother? Anyway, the bug causes a reboot, upgrading the kernel is a reboot: so why reboot to prevent a bug from rebooting the machine when the machine hasn't rebooted because of that bug?
and i have 2.2.7-ac compiled on it and ready to go should the machine ever need a reboot. I'll wait a week or three, and if 2.2.11 turns out to be stable i'll compile it and replace the unused 2.2.7-acX.
I use Friend/Foe + mod-point modifiers as a karma/reputation system.
Ahhh.. sounds like a MS approach. Phrases like embrace and extend, proprietry lock-in spring to mind. You should use NT, you could even put your own BO2K on it - that'll fuck em!
From binfmt_elf.c :: /tmp/cc6ch0Du.s:109: Warning: using `%eax' instead of `%ax' due to `l' suffix and so on ... I shall not tell whether it works, leaving the fun to the must haves'. Some more, have to find out how to post to the kernel list.
A question: What money?!?! Did you pay any money at all to Linus?
Phobos - Greek word for fear or flight
Anyone isolated cases/hardware where the fs bug seems to happen? I run several linux machines for personal testing/general productivity, and I've never had a fs problem.... typing this on a 2.2.10 system that's doing fine in it's file system. Is it on some scsi drives/controllers, odd ide timings (mb has via82c586 chipset, option enabled, no problems) raid controllers? Basically, any common elements to the fs corruption?
BTW, rest of the boxes just have generic ide... no special chipset support... no scsi cause ide has never been too slow yet.. always too many other things going in the the background I call life...
This sig left intentionally blank.
Obviousle it's stable in the sense of "We still haven't figured out how to fix this file system corruption bug, but it's been 3 weeks already and a new kernel is due anyway".
We sent the convicts to Australia
America got the religious nutters
Oh, well maybe it's just me that's got it wrong then ;)
Aye, and that's why I be patchin' tonight! I too fear for the corruption, as I got a minor hit from it in recent weeks. It seems I had some null/unprintable characters in my Modelines in my XF86Config files. very odd indeed.
Lowmag.net
take a look at the article in linuxtoday.
there's a surprising amount of fixes. (smp races, ext2fs problems, driver problems)
this one's worth the time to upgrade
look at the article in linuxtoday
I was trying to get raid working recently i thought by using the development kernel it would automatically have the newest raid stuff in it. But infact 2.2 and 2.3 only have 0.35/0.36 version of raid. You cant even get the v0.9 patch for the development series as far as i can see But it is pretty sweet to have 0.9, booting from a raid simply and easily
Watch it, or I'll mount your share, if you know what I mean..
I looked all over last night for this, but didn't find it until tonight.
Apparently there are some significant SECURITY UPDATES in this one.
Take a look at http://www.linux.org.uk/VERSION/ relnotes.2211.html for details.
I am normally not one to advocate "up"(?)grading just to have the largest available version number, but this isn't a case of something that is "not broken."
Anyone considering not upgrading to this kernel should go read http://www.linux.org.uk/VERSION/ relnotes.2211.html and reconsider.
Smart users will use the pgp signature to verify the package! I do it all the time.
You can also maintain oldversions of your kernel to immediately go back if you have problems.
---------------------------
^_^ smile death approaches.
Stable means that the kernel works well enough on enough machines and the amount of bugs are negligable to the user.
There is wisdom in upgrading for these reasons:
Kernel Exploits found.
More efficient code.
More traps for GPFs.
Workarounds for Hardware errors like F00F.
Better filesystem support.
More EYES the less bugs.
The list goes on. I advise to backup your old kernel, give new kernels a try and if your computer crashes go back to the old one
(Don't do this for mission critical servers). A petty crash won't fry your machine (I hope).
Also complain about any anomolys you may find. The more eyes the better linux gets. That is the heart of linux's stability.
---------------------------
^_^ smile death approaches.
Stupid troll... Go back to AOHell.
.
== WolfriderV6 == I'm willing to admit that *I just might* be wrong... Are you??
maybe, maybe not. but at least a hundred slashdot readers will know the truth shortly. this is a major problem with the linux community... a kernel comes out one day and everyone runs it. does anyone bother to even read the changelogs or the patch itself? bet not. this will be the downfall of linux.
>nfortunately Linux is buggy like an old rug, and those kernel >upgrades are in fact *needed* to keep production servers alive >(actually, no sober sysadmin would run Linux on a production server - >but there's no such thing as a sober sysadmin anyway).
Hmmm. Don't you reallly mean Windows 2000 rather than Linux? In case you didn't know as of 8/10/1999 at 7:48 am the Windows2000test.com site has gone down yet again....Doesn't say much for you and your microsoft buddies, does it?
Either do a make oldconfig or make sure that you have selected the maximum physical memory size you want in the config. It's a new option that's in this release.
Using make xconfig it's on the same page as the choice for SMP MTRR etc.
Iggy
Eat a beaver:)
I see even classic Slashdot is now pretty much unusable on dial up anymore.
Always do "make oldconfig" when compiling a patched kernel. In linux 2.2.11 you are required to select one of three possible memory configurations (1GB, 2GB, 3GB).
bobo@bspc.sk
> no sober sysadmin would run Linux on a production server
Hey Rob, I think it's time to change AC from Anonymous Coward to Astroturfing Chump.
ps - I'll send you the money for a sixpack if you do, even temporarily.
Sheesh, evil *and* a jerk. -- Jade
Always remember: irreplaceable implies unpromotable...
indeed, upgrading kernels for the sake of it is plain stupidity. (anyone upgrade from 2.2.5 or so to 2.2.8 just for the sake of it? see what i mean?)
i have a machine with uptime of ~80days running 2.2.2-ac7. Previous uptime was ~90 days on 2.0.36.
The reboot was to upgrade the kernel. And i only did that cause 2.2 had a couple of things i wanted. I tested the new kernel on non esential machines first for a while before upgrading the server.
you don't have to upgrade to every new kernel. In fact doing so is silly on anything else apart from your desktop linux 'play' box.
I use Friend/Foe + mod-point modifiers as a karma/reputation system.
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
Hey, it's bad enough that I'm not using the latest and c00lest XFree86 release. It's bad enough that I don't have the features that come with the latest CVS checkout of Gnome. At least let me play with the latest _stable_ kernel!
Nth post.
Too long to compile on an 8MB 386DX33? Then use your kick-a$$ machine to cross-compile the kernel for your 386 machine. :) Ah the wonders of free software. :)
Why the need for the latest glibc ? I've got kernel 2.2.10 and 2.2.11 working just fine on RedHat 5.2 (two machines - both production servers), and I also have kernel 2.2.11 running without a hitch on Slackware 4.0 (libc5 based). In fact, the Slackware distro is the most stable one that I have running Kernel 2.2.x. RedHat 6.0 has troubles, could be to glibc 2.1 not being quite ready (still researching that one).
Not stable at all indeed. 2.2.11 breaks lots of things. rebooting every hour to avoid out of memory errors. sigh! i'm seriously thinking of switching back to 2.0.37. at least that one is stable.
kernel 2.2.11 is running on both linuxgod.net and ws2.linuxgod.net. After 1 hour of screwing around i finally got the damn thing to compile my custom work for ATAPI/SCSI emulation. If you download it, download from ftp://ftp.us.kernel.org. I got a pretty fast download off a 56k taking 33 minutes of my wasted free time. http://www.linuxgod.net ( if im online )
Where can I get it? I searched for it but couldn't find it anywhere.
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.
You guys just don't get the concept of tongue in cheek humour, do you?
some servers (notably, ftp.uk.kernel.org) seem to lag behind for days
:-)
I believe ftp.uk.kernel.org is actually four servers - Demon and three on JANET. Luckily JANET has better LINX connectivity than it used to
Hmm. Applying the patch and then compiling seems to cause a blowup.. In file included from /usr/src/kernel-source-2.2.11/include/linux/locks. h:8, from /usr/src/kernel-source-2.2.11/include/linux/blk.h: 5, from init/main.c:23: /usr/src/kernel-source-2.2.11/include/linux/pagema p.h: In function `page_address': /usr/src/kernel-source-2.2.11/include/linux/pagema p.h:17: `PAGE_OFFSET_RAW' undeclared (first use in this function) /usr/src/kernel-source-2.2.11/include/linux/pagema p.h:17: (Each undeclared identifier is reported only once /usr/src/kernel-source-2.2.11/include/linux/pagema p.h:17: for each function it appears in.) /usr/src/kernel-source-2.2.11/include/linux/pagema p.h:18: warning: control reaches end of non-void function In file included from /usr/src/kernel-source-2.2.11/include/linux/vmallo c.h:7, from /usr/src/kernel-source-2.2.11/include/asm/io.h:101 , from init/main.c:26: /usr/src/kernel-source-2.2.11/include/asm/pgtable. h: In function `get_pgd_slow': /usr/src/kernel-source-2.2.11/include/asm/pgtable. h:408: `PAGE_OFFSET_RAW' undeclared (first use in this function) /usr/src/kernel-source-2.2.11/include/asm/pgtable. h: In function `pte_alloc_kernel': /usr/src/kernel-source-2.2.11/include/asm/pgtable. h:497: `PAGE_OFFSET_RAW' undeclared (first use in this function) /usr/src/kernel-source-2.2.11/include/asm/pgtable. h:505: warning: control reaches end of non-void function /usr/src/kernel-source-2.2.11/include/asm/pgtable. h: In function `pte_alloc': /usr/src/kernel-source-2.2.11/include/asm/pgtable. h:515: `PAGE_OFFSET_RAW' undeclared (first use in this function) In file included from init/main.c:26: /usr/src/kernel-source-2.2.11/include/asm/io.h: In function `virt_to_phys': /usr/src/kernel-source-2.2.11/include/asm/io.h:112 : `PAGE_OFFSET_RAW' undeclared (first use in this function) /usr/src/kernel-source-2.2.11/include/asm/io.h:113 : warning: control reaches end of non-void function /usr/src/kernel-source-2.2.11/include/asm/io.h: In function `phys_to_virt': /usr/src/kernel-source-2.2.11/include/asm/io.h:117 : `PAGE_OFFSET_RAW' undeclared (first use in this function) /usr/src/kernel-source-2.2.11/include/asm/io.h:118 : warning: control reaches end of non-void function /usr/src/kernel-source-2.2.11/include/asm/io.h: In function `check_signature': /usr/src/kernel-source-2.2.11/include/asm/io.h:175 : `PAGE_OFFSET_RAW' undeclared (first use in this function) You'd think they'd test these things before releasing them.. Daniel
Some people Just Don't Get It.
The more people who use a kernal, the more bugs they find, the more bugs get fixed, the better the OS gets. Upgrading is the _whole point_.
Now, if you've got a production server you don't want to risk (a reasonable concern) then you slam the upgrade on your test server (you _do_ have a test server, don't you?) and run it there for a while.
Upgrade! It's not just fun, it's part of the evolution process!
Is there a changelog available for 2.2.11? http://edge.kernelnotes.org/changelist.cgi?show=2. 2. doesn't seem to have one. I want things in web time! The kernel was released several hours ago! Give me my info rush!
Like we needed to see that code spew. ;>
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.
A deep unwavering belief is a sure sign you're missing something...
I bet it's more likely that one of the thousands of anonymous Microsoft employees puts a Trojan in Windows 2000 than that Linus and/or Alan put one in a kernel.
That's a sobering thought...
In an environment where people can be fired for inserting easter eggs et al in the product, you still see pinball games, flight simulators and even entire DOOM CLONES in Microsoft software. And these people are just screwing around for fun... what happens when you get someone with an agenda working on these projects? Say, a psychopath or a terrorist?
How well do companies like Microsoft screen their employees?
---
DNA just wants to be free...
actually Win2K was created in a stadium sized room packed with thousands of monkeys punching away at computers...
Its spelt "L-I-N-U-X", but pronunced as "Free Beer"
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.
Does this kernel have the dozen or so patches
that Alan Cox has made to 2.2.10?
Do the "ac" kernels have a web page?
I have always just kept the latest mainstream
kernel on my system but I've been told that the
latest "ac" kernel is really the one to have...
Is this true?
The ac kernel patches should usually be available from ftp.*.kernel.org/pub/linux/kernel/alan (Replace the * with a country code, ie lu for Luxembourg or no for Norway) Unfortunately I didn't find any homepage for them.
;)
As for them being better than the 'normal' ones, I have absolutely no idea because until now I only used the standard kernels. I was told that ac contains newer drivers but is a little more unstable. (Sounds like something between 2.2 and 2.3
Anyway, keep compiling!
Is that stable in the sense of " constantly being updated because we tweak stuff" or "constantly changing because we fix broken stuff" or "completely stable but we release even more completely stable versions every three weeks" or "It's stable because it doesn't crash, but you need to reboot every three weeks to upgrade the kernel anyway" or, rather is it stable in the sense of:
"Not stable, but in fact, constantly changing."
Only 50% tongue in cheek....
-----
It has been shown that support costs increase dramatically with every deviation from a standard operating system release. You may know that your system was patched, why and how it was done. Your successor on the job will not. Beware.
Tell your friends about xenu.net
And what if I don't want to have a successor? It seems to me that using as many patches as possible is the path to true job security.
Hmm still wondering why /dev/changer can't be put into the kernel tree, even the 2.3.x tree seems to stable for it...
/dev/changer
/dev/changer is working since 19 May 1999...
See
Maybe when it's in the experimental 2.3.x tree, maybe that more people would try it which would speed development up as more hardware can be tested... There is a multiple-cdrom-status in 2.3.x which is stated as "beginning of multimount-support" while
Greets,
Jeroen Massar
(/dev/changer maintainer/coder)
--
http://unfix.org
My production fileserver is 2.0.34 (behind a firewall, keep your panties on)...
:-)
:-)
the web/mail/news/radius/ldap/db server is 2.2.1 I believe (too far away to keep rebooting)... I need to get around to getting a new kernel on this because there's a DoS which takes down servers 2.2.3 I think. It's got 2.2.5 ready to come in on next reboot so if it does get shut down it comes back fine.
My masq server at home: 2.0.33 (it takes too damn long to compile on an 8M 386DX33!) But then my toy boxes are running 2.2.9 and 2.3.something.
Stable? damn right. that 2.2.1 box has almost a half year of uptime and there ain't nothing protecting its ass but itself on a 10mb backbone 60km away from where I'm typing. The 2.0.34 fileserver had some decent uptime but something weird is happenning either with the EATA RAID controller or the SCSI Zip drive... sometimes accessing the zip drive causes a bus hang (EATA reports mbox # is full, resetting controller). If anyone has any insight, please let me know!
anyway enough ranting. The point was that not everyone is hell-bent on the latest and greatest.
I have redhat 6.0 (upgraded from 5.2), and when I went to 2.2.11, sendmail takes a long time (2 mins) to start up. Time to downgrade I guess.
Wow, an SMC Ultra driver update! Here's to hoping it'll fix my Tx timeout problems.
I'm sure most of the replies regarding job security and such were tongue-in-cheek, but the real point of keeping a standard kernel is to help manage your own workload. Doing massive modifications means keeping track of it somewhere - that means either in your head (good luck) or doing extensive documentation (good luck). What really happens is that you end up spending lotsa time backtracking over your old code and mods to try to figure out what the hell you were doing!
Caveats: don't get anal about this - mods and patches are needed. But the more you can mods and patches, the easier your job becomes (use the time to manage more systems, do kernel research, or play Solitaire FAIC).
f
klag qit fweep pwes te beyoop!
Rather than doing an enormous diff and browsing through thousands of changes to see if the problems we *do* have on our server might be fixed, is there a place where a ChangeLog can be found? The Documentation/Changes file is just changes for 2.2 in general.
-Lars
Oops...
s/more you can mods/more you can avoid mods/
f
klag qit fweep pwes te beyoop!
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!).
now i'm running on 2.2.11 for about 5 hours and nothing like FS corruption yet.
hany
One thing that has been bothering me is the software RAID support patches from ftp.kernel.org. Does anyone know whether the stock kernels are going to be supporting the 0.90 raid tools in future versions? (For all I know, they already are...) What I am talking about are the patches from ftp://ftp.us.kernel.org/pub/linux/daemons/raid/alp ha/ . Sometimes I wonder whether or not I should be installing some of the RAID patches on a kernel since it almost seems as if the change might have been merged in already, but not quite...
A flurry of 2.0.x kernels came out. Finally, 2.0.18, the "last" stable kernel was released. No, wait, there was 2.0.19. Then 2.0.29. And so on, up to 2.0.37. Which we think is stable.
Consider, for a moment, the system used by Gnus, the singing, dancing mail and news reader for Emacs. Gnus has alpha releases with names ("September", "Red", "Quassia", "Pterodactyl"). These aren't announced to the general public, though they are discussed on a mailing list. These are essentially analagous to the a.n.x Linux kernel releases, for odd n. Then there are beta releases, which have version numbers like a.n.x for even n. These are probably stable enough to use, but if you care a lot about your mail you'll wait. Finally, there is a single final release with a version number of the form a.n for odd n (5.3, 5.5, 5.7).
The problem with the Linux kernel development model is that it has lots of "alpha" and "beta" releases, but no "final" release. So there's really no way to tell if a particular even-numbered kernel release is "stable" or not, aside from by reputation. At some point there needs to be a "final" we've-done-all-the-testing-we-can-possibly-think-o f-and-fixed-every-single-bug-which-is-wh y-we're-working-on-the-next-version release.
I was so proud of my 200-some day uptime on my one 2.0.36 box that I didn't reboot it after installing 2.2.9 or .10 (I forget which). Then the power went out at my colo and it came back up as a 2.2 box. Oh well c'est la vie. Next time, I'll put it on a UPS. :)
-Chris
If you are fired, the chance is high that your successor would simply take a weekend to blow away what you did and replace it with something done "their way".
Everyone knows that Ireland belongs to America.
If you can't get replaced you can't get promoted.
If the code and the comments disagree, then both are probably wrong. - Schryer
Alan Cox is supposed to be the official maintainer of the stable series of the kernel.
You can take a look at his web page at http://www.linux.org.uk/diary/ . These pages should contain alot of useful information if you want to use the ac's (tecnically beta releases).
Wow, well thanks for your advice, but I've held on to my cushy job (I do nothing except occasionally tweak one measly server) for seven years. They try to get rid of me, but the consultants they bring in take one look at the server and shake their heads. I play quake, daytrade, and read slashdot all day. Soon I'll be able to retire off my daytrading profits. Bwahahahaha.
Everyone knows that America belongs to Indians (or should i say Native Americans?)
remind me to never operate on a network that you admin.
you realize that there is a nasty DoS in 2.2.5.
who don't care if their neighbor is sniffing their passwords and mounting their shares..
Too long to compile on an 8MB 386DX33? Then use your kick-a$$ machine to cross-compile the kernel for your 386 machine. :) Ah the wonders of free software. :)
:-)
:-)
I'm getting there.
I recently put together a diskless box (P2-450, 128M RAM) to do nothing but compile. I mean the main server's a P90, the gateway is a DX4/120... compile times are too long on those boxes so I'll just mount the filesystems and do it that way.
Mind you, I'm not sure if doing a compile on an NFS-mounted filesystem will be much faster.
Andrew
Unfortunately, that sounded more like a troll than like humor. At least to my ear. If I imagine a smiley on it though...
Pity that the tonal subtilties I hear in my mind never show up when another reads the written text.
I think we've pushed this "anyone can grow up to be president" thing too far.
Is it somewhere in NT4, Office97, or IE4? I'm sitting here at my Windows box procrastinating, and I could procrastinate far more effectively with something like DOOM on my machine.
I have been reading slashdot for a few months now, and this is my first post. I was hoping that this isn't how I'd get my start, but...
I think it's great that kernel.org is mirrored. Especially when you know a few mirror servers that are hardly loaded that give you good speed (ftp.us.kernel.org is not one, of course). However, sometimes it literally takes days for the new updates to reach the mirror sites. What's the point of saying "We're busy. Please use a mirror" when you can't get what you're looking for anyway? I am aware that there are lots of other things on kernel.org besides the Linux kernel, but I bet it's quite commonly downloaded from there. I guess I'm just a little annoyed that they don't take the time to distribute this first to all the servers before making the official release.
The bz2 patch is 1.13Mb, that seems awful large... Yup, the next largest, 2.2.4, is only half the size, and most are smaller still. Looks like we've got quite a few changes this go around. I hope that nasty FS corruption bug is finally squashed. Well, I'll know soon enough...
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.