Slashdot Mirror
Linux 2.2.7 Released
MazMart was the first to report that a new stable kernel.
Linus decided to name it 2.2.7- a surprise move that
enraged and shocked, but since it was the next available digit
we shouldn't be all that surprised. Now if I only I had a T1-
hemos would kill me if I seized control of the ISDN
for something so selfish as as kernel.
d00d, you overflowed your jiffies. Jiffies is the count the kernel uses to keep track of time since boot. On intel, with the default of 100Hz, it overflows in about 1.3 years ~ 500 days. You can change the default value, but its probably a bad idea because your changeing how often you processor is scheduled; your system will be considerably less responsive, etc. IIRC, Alan Cox wanted to fix this problem before 2.2 shipped, but Linus decided it wasn't that big of a deal.
Well, this url will work fine once it is updated, and it will show the updates in 2.2.7
http://edge.linuxhq.com/changelis t.cgi?show=2.2.6
Hmm, the USB support in 2.2.7 appears to be an alternate development by Linus & friends rather than from the Linux USB project.
Anyone have any ideas why they wrote their own instead of working with Linux USB project's version?
The Linux USB projects sources seem farther along than what is included in the kernel.
--
The world is neither black nor white nor good nor evil, only many shades of CowboyNeal.
man syslogd
-m interval
The syslogd logs a mark timestamp regularly. The
default interval between two -- MARK -- lines is 20
minutes. This can be changed with this option.
Setting the interval to zero turns it off entirely.
Microsoft Windows NT 4.0 has had 26 "HotFixes" for critical bugs since October 21, 1996. Combine this with the 4 service packs and multiple versions of vendor released drivers targeted at different subtle revision levels of NT for a confusing mess. In the same time span, Linux has been through 20 stable kernel releases. (2.0.24->36, 2.2.0->2.2.7) with almost every important device drives included in the standard kernel distribution.
Rob and others, why don't you just patch the source? The last full kernel source I downloaded was like 2.2.1 I think. Since then, I have been downloading the patches, and after a while, I tarball and gzip the full source all up and I have an exact copy as the 13+ meg file. Try it. :)
--
Scott Miga
So, 1.0.x, 1.2.x, 2.0.x, and 2.2.x are all stable.
1.1.x, 1.3.x, 2.1.x, and 2.3.x [the last doesn't exist, yet] are all development.
It's too bad stupidity isn't painful"
Send your friends messages of love at fuck-you.org
(Presuming source is /usr/src/linux) /usr/src c )
cd
download patches (I like wget ftp://ftp.us.kernel.org/pub/linux/v2.2/patch-2.et
linux/scripts/patch-kernel
Ta da! All patched.
/*He who controls Purple controls the Universe. *
www.gotontheinter.net
Updated vaguely once a whenever, maybe once a whenever-and-a-half.
where you should replace zcat with bzcat if you downloaded the
--
Kyle R. Rose, MIT LCS
[ home ]
What a great phrase! Let's use it as a slang term.
"All right already, don't overflow your jiffies!"
"When I saw httpd was using 300 megs of memory, I nearly overflowed my jiffies."
Not too long ago, there was an ac patch almost daily. Now THAT is bleeding edge!
For major linux industry news such as new kernel releases and new distro releases, I'd personally like to suggest that no outside contributor's name be attached to it. I'm referring to such things as "Bonzo was the first to mention that 2.2.2-ac4 has been released", not the "Posted by CmdrTaco" lines. Maybe 150 people post such a news item, or maybe only 15 - I really don't know, but awarding people as the first to report a story that will shortly be all over the major Linux sites anyway is just like people posting "first!" comments - it isn't *that* much of a contribution. News about kernel releases is available through so many mediums - usenet, mailing lists, other websites such as freshmeat.net, etc.
The types of contributions which should be encouraged are the obscure story of someone in Australia getting a Windows refund, or a Usenet post about writing drivers for some new hardware. Post-worthy articles that receive less than 5 unique submissions by external Slashdot readers are the ones that really deserve honorable mention.
-b
Slashdot is a public forum, not a money-making machine. It does make a small profit, keeping our favourite administrators in leisure time, but at the moment it is not an in-your-face commercial venture.
If Rob needed more cash, he'd charge more for banner ads, put more of them in, or even go to the bank. Going to a VC is asking for millions, promising big returns. If slashdot was trying to make money off us (in a big way) it would turn off the traditional readership.
Don't you think so?
Jonathan
See http://electricrain.com/linux/uusbd-www/ for the project.
/
/.
The list archive is at
http://electricrain.com/lists/archive/linux-usb
Yes, this is not Inaky's driver. There are two drivers under development. The smaller one was sparked off by Linus because we needed something simple & functional in the kernel today for many reasons you can figure out yourself...
The projects are working together and will likely merge bunches of code.
BTW, working OHCI support is coming. The stuff in the 2.2.7 kernel is -not- even complete yet (Linus put it in despite a couple hopeful plees from me and others to wait until that worked).
No big deal though. It's not even enabled in config.in as "EXPERIMENTAL" because we all agreed that it hasn't reached that status yet.
If you want web pages for code history and latest snapshots on the small driver you'll have to find them yourself from the list archive; its on my DSL line which would quickly
The Linux kernel is developed by multiple people, however Linus is the only one to add to the "official" kernel. While I'm not sure why he doesn't use RCS (maybe he does), CVS would be pointless, since there is no "concurrent" development done on the official kernel. However, there was talk of him using a much better system for the type of development the kernel does (bitwize or something like that, which is designed much closer to the development model of the kernel). However, I haven't watched the kernel group lately, so don't know where that discussion went.
This is not a desktop calculator, it is best that all patches get reviewed, not just added and debugged later.
-- Keith Moore
This sig is the express property of someone.
If you send mail to Majordomo@vger.rutgers.edu with "subscribe linux-kernel-patch" in the body, you will automagically receive the latest patch, as soon as it is posted by the Linus.
/usr/src/linux/scripts/patch-kernel on the resulting file ....
If the patch is too big (> ~400k) you will receive a notification and the diffstat output.
The truly wicked could setup a procmail rule to feed mail from linux-kernel-patch directly to uudecode and then invoke
If you send mail to Majordomo@vger.rutgers.edu with "subscribe linux-kernel-patch" in the body, you will automagically receive the latest patch, as soon as it is posted by the Linus.
/usr/src/linux" ...
If the patch is too big (> ~400k) you will receive a notification and the diffstat output.
The truly wicked could setup a procmail rule to feed mail from linux-kernel-patch directly to "patch -p1 -d
I have just posted it to linux-kernel:
--- drivers/usb/usb.h.bak Wed Apr 28 21:59:45 1999
+++ drivers/usb/usb.h Wed Apr 28 22:08:08 1999
@@ -363,8 +363,8 @@
void usb_audio_interface(struct usb_interface_descriptor *, u8 *);
void usb_audio_endpoint(struct usb_endpoint_descriptor *, u8 *);
#else
-extern inline void usb_audio_interface(struct usb_interface_descriptor *, u8 *) {}
-extern inline void usb_audio_endpoint(struct usb_endpoint_descriptor *, u8 *) {}
+extern inline void usb_audio_interface(struct usb_interface_descriptor *interface, u8 *data) {}
+extern inline void usb_audio_endpoint(struct usb_endpoint_descriptor *interface, u8 *data) {}
#endif
#endif
not that thats a bad thing: i think this is a good counterpoint to FUD
-- your knees hurt, don't they?
Well, a bit on the silly side, I just went through a horrible horrible bug in Linux 2.0.30. After somewhere around 500 days uptime... IT WRAPPED!
According to last, it went up at:
reboot system boot Tue Dec 16 22:51
(That would be 1997).
Now:
11:40pm up 22:21, 1 user, load average: 0.01, 0.04, 0.00
Suddenly I was back at 0 uptime, and my logfiles went through a spasm with kernel error messages ending with this:
Apr 28 01:56:07 dream kernel: Call Trace: [do_gettimeofday+34/68] [sys_gettimeof
day+44/112] [system_call+85/124]
Apr 28 01:56:07 dream kernel: Code: f7 f1 ba 10 27 00 00 89 c1 31 c0 f7 f1 a3 dc
fa 1a 00 89 c3
Oh, well, still it didnt panic, altho a load of apps including X went haywire.
It sorta puts life into a perspective too. Last time I rebooted this machine I was 25. Now I'm 27. Agh.
Linux has far more releases than any closed source OS, because the philosophy behind closed source code is to never let your customer see a bug. Obviously this hasn't worked with NT. Open source on the other hand, releases every even marginally working piece of software. This software is then viewed and 'fixed' by a large number of people, then resubmitted to whoever is maintaining that code.
With closed source software, about 10% of the time is spent writing the code, then the rest is spend debugging. Debugging takes many many worker hours in order to do correctly. This is why there are alpha and beta versions available for some things, but they are still being tested.
With open source, such things are not worried about. The user has access to the source code, and those thousands or hundreds of thousands of 'eyeball hours' looking at the code for problems, can be accomplished in a matter of days or even hours.
There have been times during the development of linux that Linus released a new kernel version more than once a day. I would imagine that this happens more with the unstable releases. For discussion on how to tell, see earlier posts.
There is a civil war coming in the United States. Remember which side has most of the guns
As soon as I load up Netscape 4.51 and hit the bookmarks button it locks thats running with KDE 1.1, YMMV :(
I'm back to 2.2.6