Slashdot Mirror
Ladies And Gentlemen, Linux 2.4
Lars Lehtonen writes: "The 2.0 kernel is no longer obsolete, it is now "vintage." 2.4.0 is out. " Here is a bit on
LinuxToday
but I'm sure there will be many more. I don't think the mirrors have updated as of this writing, but if I don't post this now, I'll have to spend the next 3 hours deleting hundreds of submissions. Download! Compile! Rejoice! Thanks to Linus and all the rest of the guys who made it happen.
There were a few major things that had to be done right at the end of the development process after other things had stablilized, such as adding proper flushing and syncing to the page cache. The page cache is, by the way, where a lot of the improved performance of 2.4 comes from. Before the page cache was only used to reading, now it's used for reading and writing, consuming only half the cache memory. The other big performance improvement came from a fairly major modification to the memory management system, to use an approach called page aging which you can see works a lot better. This radical surgery all happened in the last 3 months of the leadup to 2.4, and there were a lot of stupid little bugs and problems to track down and kill as a result of it. It came together pretty fast, actually.
--
Life's a bitch but somebody's gotta do it.
Currently (about 20:49 EST), the largest slashdot effect I've ever seen is taking place -
We're pounding kernel.org at almost 99 MBit/S.
Now only if they had another 1.5 terabit router...
Now everyone will have to go change their votes from Pr0n to Kernel Downloads Sorry, only eligible residents of Florida are allowed to change their votes.
I hate my ISP. So to help consume their bandwidth, here is my very own mirror.........
http://www.primenet.com/~rwd/linux-2.4.0.tar.gz
I'm currently running 2.4.0test12 on a system I just built, not just because I wanted to be cool and brag to all of co-workers (who would of course give me a blank stare and go on about the NY Jets, etc.), but because I had use for the features. What I'm actually using in 2.4.0:
It has been promised that reiserfs will show up in 2.4.1. Imagine a journalled filesystem! Currently, filesystem checks on my volumes requires about 45-60 minutes. That sucks. I'm
That said, I agree, don't use them if you don't need the features. I had a lot of problems with test11. I was one of many that saw panics when running RAID5, sometimes within 4 hours after boot. test12 hasn't failed yet, but it has only been 20days.
Go on IRC at irc.openprojects.net channel #nvidia and the bot named "ice-dcc" can hook you up with the appropriate patches. I'm running 2.4.0 final with full acceleration on my GeForce 2MX right now.
kernel.org got SLASHDOTTED!
/.!
I'll bet if they posted their logs, half of the referals would come from
Anyway, for those of you who can't get through (everyone), here's the list of US mirrors...
(HTTP)
www.ymb.net
kernel.stuph.org
ftp.compsci.lyon.edu
jhcloos.com (100 Mbit/s)
www.in-span.net (200 Mbit/s)
www.internap.com
www.gnaps.com (250 Mbit/s)
www.semaphore.com
www.linux.locus.halcyon.com
sourceforge.net
www.rowan.edu
www.sit.wisc.edu
www.netop.surfsouth.com
metalab.unc.edu
kernel.valinux.com
(FTP)
www.ymb.net
kernel.stuph.org
www.cais.com (100 Mbit/s)
ftp.compsci.lyon.edu
cac.psu.edu
mirror.chpc.utah.edu (100 Mbit/s)
www.clarkson.edu
www.club.cc.cmu.edu
kernel.csh.rit.edu
www.nas.nasa.gov (100 Mbits/s)
www.cybertrails.com
jhcloos.com (100 Mbit/s)
osu.orst.edu
www.in-span.net (200 Mbit/s)
www.internap.com
www.gnaps.com (250 Mbit/s)
www.stealth.net (200 Mbit/s)
www.semaphore.com
www.linux.locus.halcyon.com
sourceforge.net (90 Mbit/s)(probably swamped)
limestone.uoregon.net (300 Mbits/s)(good bet)
www.netnitco.com
www.ndlug.nd.com
www.rowan.edu
www.sit.wisc.edu
www.netop.surfsouth.com
www.twtelecom.net (155 Mbit/s)(Good for RoadRunner users)
kernel.valinux.com (45 Mbit/s)(50/50 chance)
No number = less than 50 Mbit/s. Happy compiling! Note: sites are not hyperlinked because my fingers already hurt!
CAP THAT KARMA!
Moderators: -1, nested, oldest first!
SIG: HUP
From linux/Documentation/Changes:
;)
Current Minimal Requirements
Upgrade to at *least* these software revisions before thinking you've
encountered a bug! If you're unsure what version you're currently
running, the suggested command should tell you.
Again, keep in mind that this list assumes you are already
functionally running a Linux 2.2 kernel. Also, not all tools are
necessary on all systems; obviously, if you don't have any PCMCIA (PC
Card) hardware, for example, you probably needn't concern yourself
with pcmcia-cs.
o Gnu C 2.91.66 # gcc --version
o Gnu make 3.77 # make --version
o binutils 2.9.1.0.25 # ld -v
o util-linux 2.10o # fdformat --version
o modutils 2.4.0 # insmod -V
o e2fsprogs 1.19 # tune2fs --version
o pcmcia-cs 3.1.21 # cardmgr -V
o PPP 2.4.0 # pppd --version
o isdn4k-utils 3.1beta7 # isdnctrl 2>&1|grep version
*snip*
The recommended compiler for the kernel is egcs 1.1.2 (gcc 2.91.66), and it
should be used when you need absolute stability. You may use gcc 2.95.2
instead if you wish, although it may cause problems. Later versions of gcc
have not received much testing for Linux kernel compilation, and there are
almost certainly bugs (mainly, but not exclusively, in the kernel) that
will need to be fixed in order to use these compilers. In any case, using
pgcc instead of egcs or plain gcc is just asking for trouble.
For even more details, read the file yourself
Oh...and if you choose to include devfs, do remember to install devfsd before you reboot with your new kernel (I forgot)
You got off easy.
I woke up just to see this article, a full half hour before I went to bed, then I beat the NT-loving CIO, cut him up in pieces and danced on his grave.
Now here I am in a Chinese prison serving as child labour sewing shoes for Nike.
It was worth it.
If I were given the opportunity to send a buck, securely, in celebration, to Linus. Such that he may, for a week or so, not worry about bug fixes, but spend time thinking, with his family, where to donate the accumulated pennies. To have a total, at the end, to show the press . o ( here is what the OSS model MEANS to the community ).
Wouldn't you?
Before I part with'em: two pennies weigh ~4.996+/-0.014g, have a zinc core, and the face of Lincoln. You can keep 'em.
It wasn't until 2.2.8 that 2.3 broke off from the main kernel branch. I'd give them at least 2 months to track down all the major bugs in the initial 2.4 release before anyone starts jumping the gun on new development.
Interested in open source engine management for your Subaru?
> 1. Photoshop
:-)
gimp
> 2. Quark
adobe's thing, framemaker. heard rumors it may be coming back to life on linux. This is probably your strongest point.
> 3. 3DSMax or Maya. Take yer pick.
Blender. Moonlight Atelier. Povray.
> 4. distributed network renderers for the above
ever watched Titanic?
> 5. Non-linear video editing systems (Avid, >Media100)
Broadcast2000
> 6. Digital audio editing packages (ProTools, etc.)
I'm not into digital music so I can't comment. Didn't a book about making music on linux just get published by No Starch Press?
> 7. Excel
Gnumeric. Star Office. Applixware.
>8. Powerpoint
Star Office. Mayber others I don't know about.
> 9. Outlook
yeah, like you need a gui to read email.
mail, mailx, mh, mutt, pine on the CLI off thetop of my head. www-email in any of several browser, and this includes calendar functionality. Oh and of course the 20+ gui email clients (kmail and balsa come to mind)
> 10. $GAME (Everything except Quake3 I guess).
www.loki.com for starters. More are out there.
> Academia? Government? Military?
hah. 70% of the scientific and engineering departments at my university run all-Unix-and-mostly-linux-at-that shops. I don't work for the government or the military, but they're hardly shining examples of wise procurement decisions in most cases.
>From where I sit, installing Linux on a workstation reduces its functionality.
The problem is that you are apparently sitting in
the short bus.
--
News for Geeks in Austin, TX
I would just like to say that when I read this, I ran around the office showing all the NT admins who for the longest time were saying what crap linux is, and how it 2.4 would never come out. I then ran around the office naked screaming "Viva la tux" and here I am, at Starbucks...jobless. =P Give me some food! Maz
As you may of noticed, there is not a release of it noticable. Its only available right now as a diff inr elease-diff
ftp://ftp.kernel.org/pub/linux/kernel/testing/pre
So as of right now, you need the pre-release source. Hope that helps youll get this new kernel, mine is already compiling - wanted to try and help the world get their's going too Enjoy
Linux: Because a PC is a terrible thing to waste.
James Brents
I've been salivating for months anticipating the anticipation for 2.6. Let the wait begin!
:)
http://www.cowsnet.com.au/linux/kernel/v2.4/linux- 2.4.0.tar.bz2 - 2.4.0.tar.bz2.sign - 2.4.0.tar.gz - 2.4.0.tar.gz.sign
http://www.cowsnet.com.au/linux/kernel/v2.4/linux
http://www.cowsnet.com.au/linux/kernel/v2.4/linux
http://www.cowsnet.com.au/linux/kernel/v2.4/linux
You can also find a list of US mirrors here, or search here for mirrors for your country. Last I checked the new kernel hadn't been mirrored yet, FYI.
ObJectBridge (GPL'd Java ODMG) needs volunteers.
Finding God in a Dog
Dude, I'm sure so many people have offered Linus free (money, hardware, software, beer, food, cars, lusty wenches, lusty men, lusty goats, rides in nuclear submarines or fighter planes) he could take everyone up on their offers and live 'till he was 180 before he got through with them all. :-) Of course, IMHO he deserves all that and a whipped cream sunday besides. Linus, in the unlikely even you read this comment: You rule!. 'Nuff said.
--
News for Geeks in Austin, TX
Noooo... Please don't, because each extra user that sticks to v2.0 becomes my trouble instead of the corporate bug-munching crowd on linux-kernel. Yes, I admit I was stupid when I accepted maintainership, but someone had to.
Regards: David Weinehall, maintainer of the v2.0 kernel-series.
The main reason I got broadband access:
[ ] 24 hour IRC Idling
[ ] MegaTokyo
[ ] Pr0n
[X] Kernel Downloads
[ ] apt-get -u upgrade
[ ] www.cowboyneal.org
[ ] MP3s
[ ] I Saw "The Net" and thought it would be 31337
Now everyone will have to go change their votes from Pr0n to Kernel Downloads. But even broadband won't help here in Europe until the mirrors get updated. Damn slashdot effect.
the AC
Hemos is like...sci-fi fans;he thinks technology is cool, but he hasn't bothered to understand the science it's based on
Looking back on some of the bugs that stayed in the 2.2 tree for so long (including some that caused massive filesystem corruption) i can't help but worry that 2.4 is just as far from BugFree(TM)
Unless I see a feature in 2.4 that I absolutely need, I'm sticking with 2.2 until 2.4 becomes stable enough that they open the 2.5 tree. Granted, there's a lot of neat stuff in 2.4, but there is a difference between neat and necessary. I'm sticking with kernels i know are stable.
#define F(x) int main(){printf(#x,10,#x);}
F(#define F(x) int main(){printf(#x,10,#x);}%cF(%s))
So just yesterday I wrote:
-
Why We Should All Test the New Linux Kernel
on Advogato.It's got some helpful, practical tips on downloading and building a kernel from sources as well as providing feedback to the kernel developers. All of the information in the article is available somewhere, but when I first began testing with 2.4.0-test1, I found some things difficult to figure out, so I felt that it would be nice to put what I learned all down in one place.
This is part of an overall effort to improve the quality of Free Software. Another part of the effort is the just-founded Linux Quality Database, so far just a proposal - contact me at crawford@goingware.com if you want to help.
And finally, some interesting trivia for you:
After a long beta testing period and many delays, Windows 2000 shipped with 64000 documented bugs of which 25000 were considered serious by Microsoft itself (the figures are quoted from memory, I might be a bit off). The Windows trade press reported that the opinion was widely held by IT managers that one should not install Windows 2000 on any machine until a few service packs had been released, with Windows 2000 server not being considered ready for use until much later than the desktop user version.
The BSD/Mach based Mac OS X, derived from the NeXT operating system and now in beta testing, is Apple's first operating system to support protected memory that is expected to be widely used. (Another was A/UX, Apple's Unix port, but it served only a niche market).
Apple has been trying for ten years, longer than Linux has been in existence, to write a modern operating system. The first was Pink, renamed Taligent when Apple collaborated with IBM on it. In the end all that came of it was a little-used object-oriented programming framework.
The next was Copland, and I don't know why it was never completed exactly, but I was offerred a job as a performance engineer on the Copland project when I worked at Apple, but I turned it down - I didn't tell them this but I had the sense that Copland was a project that would never ship.
And Linus wrote Linux when he was a college student, which combined with the GNU utilities forms the operating system we know and love today.
These huge, well-funded corporations can't get it together to program their way out of a wet paper bag but a bunch of freaks on the Net have written the fastest growing operating system in use today.
Michael D. Crawford
GoingWare Inc
-- Could you use my software consulting serv
If is very easy to figure out your nearest mirror:
Determine the two-letter country code for the nation you reside in. This will be the same as the top-level national domain, ca for Canada, uk for United Kingdom, ch for Switzerland and so on.
If you're using ftp, the server name starts with ftp. If you're using http (a web browser), then it starts with www.
Put the country code in the middle. Add .kernel.org at the end.
Michael D. Crawford
GoingWare Inc
-- Could you use my software consulting serv
That's quite untrue, actually. Sounds like someone with stock in a particular distro company may have told you that. ;-)
/proc to get just about every bit of information you need), and follow all the proper instructions.
/usr/src (remove the existing /usr/src/linux symlink first), rename new linux/ directory to something else, then recreate /usr/src/linux symlink to that directory. Then, cd into /usr/src/linux and do "make " plus either config, menuconfig or xconfig. For beginners, menuconfig or xconfig are best (you'll need to be running X for the latter to work). Configure the kernel as you need/want, then save & exit. Type "make dep", then "make bzImage", then (if you selected any options to be compiled as modules) "make modules" and "make modules_install".
/usr/src/linux/arch/"your platform"/boot/bzImage to /boot/vmlinuz-"something unique". Replace "your platform" with i386 for Intel, "alpha" for Alpha, and so on. Then edit /etc/lilo.conf. For details on lilo.conf, do "man lilo.conf". If you're using LILO and have edited lilo.conf, make sure to rerun "/sbin/lilo" before rebooting your system.
Under all but rare or weird circumstances upgrading to a newer kernel will only break a program if it relies on a special module or patched code in the kernel that the distro makeer has pre-applied to the kernel and that is not standard with stock kernel downloads. These kinds of programs are few and far between.
Recompiling a kernel is not a sacred initiation rite for the elite. It's actually very easy as long as you understand the hardware in your system (you'll need to know specific model numbers and such for just about everything in your system that you want to get working properly; you can consult the files under
You can either look below for very brief instructions, or download and untar the kernel and read the README file in the newly created linux/ directory where you untarred.
The very abbreviated instructions are: download kernel, ungzip and untar the kernel in
Copy
Most configuration options for the kernel have decent little bits of info attached to them saying what they're for (hit "?" with the option selected to see the help text).
Hope that helps. If not, read the README a couple times. If you're ever unsure about a kernel option, look for documentation on it under the linux/Documentation directory. There's detailed info in there for most options in the kernel.
But, definately, look here;
README
INSTALLING the kernel:
- If you install the full sources, put the kernel tarball in a directory where you have permissions (eg. your home directory) and unpack it:
Replace "XX" with the version number of the latest kernel.
Do NOT use the /usr/src/linux area! This area has a (usually incomplete) set of kernel headers that are used by the library header files. They should match the library, and not get messed up by whatever the kernel-du-jour happens to be.
(Yep, it stung me a couple times too! RTFM....)
A firewall can not protect you from yourself. Turn off what you do not need. Do not use the firewall to do your work.