Linux 2.6.0 Kernel Released
thenextpresident writes "It's here! Just updated on kernel.org, the Linux 2.6.0 kernel has finally arrived! We've been waiting a long time for this, and it had been rumored it was going to be released tonight. Well, it's here indeed. Happy downloading." There's also a changelog online for this long-awaited update.
For the Longhorn release, coming soon!
Why is 2.4 gone from kernel.org?
[23:21] http://slashdot.org/article.pl?sid=03/12/18/041820 5&mode=nested&tid=106&tid=185&tid= 190 the sound you just heard was half a million geeks all orgasming at once!
I've been using 2.6.0-test11 for some time now, and find it quite stable and satisfactory.
Seems this fixes a few bugs, and beefs up Wireless support. Sweet. Can't wait till we start seeing this in "production systems".
This is not the sig you're looking for.
Wow, Lord of the Rings and 2.6 Kernel released on the same day? This just shows the dedication the Linux developers have. To not go see the movie and to work to release the kernel. My hats are off to these guys. They have gone above and beyond the call of duty.
Jason Lotito
Got a torrent of it for ya'll:
Linux 2.6.0 final (tar.bz2)My god. Now SCO will have to update all of their lawsuits!
Kiss ide-scsi goodbye!
--AROS is an Open Source AmigaOS clone, and source compatible with AmigaOS! Try the x86 build at http://www.aros.org
I must admit I have been looking forward to this, I have been running all the tests from about 3 onwards and am quite happy already with the level of test11. On the other hand now that its stable maybe we will see some distros that come with it as standard. Now that will be a good thing.
Can somebody please save me from reading the entire changelog? I just want to know the major differences between 2.4.x and 2.6.x.
:)
Please save me! I'm lazy
At least offer a bitorrent version for those suffering the wrath of the slashdot effect.
If only the latest vanilla sources of gentoo linux were stable. I would not need to download 2.6 in order to get the nvidia opengl drivers to work.
http://saveie6.com/
copyright violations
Fix ide-scsi.c uninitialized variable
... sad
You have been waiting a long time for this? Wow, that is
I run linux as my desktop at home, and I also run it at work in a scientific computing cluster.
I'd like to know what benefits I could expect from the new kernel in each area in which I use linux.
Since it's impossible to track global downloads of the Linux 2.6.0 kernel, The SCO Group has set up a PayPal tip jar. Please abide by the honor system and send them your $699 after downloading the new kernel.
Tired of FB/Google censorship? Visit UNCENSORED!
Since the official UTC timestamp is at 03:04 on the 18th its my birthday!!
OK, slightly more on-topic I am already running test11 on a couple boxes with no overriding need to upgrade. However I am curious as to how 2.6 will be managed as opposed to 2.4. Since Linus has already handed off the kernel to Andrew Morton, are we going to see the 2.7 development branch open a whole lot faster than happened with 2.5???
AntiFA: An abbreviation for Anti First Amendment.
I'm glad the new kernel is out in time for the holiday season... wait... that's sad isn't it?
Esoteric reference.
Distros like Slackware 9.1 are already 2.6 ready - meaning just plug 2.6 in and it should work! The only reason why kernel 2.6 wasn't included is, well, that it wasn't released until now :)
Peter is going to kill you, our poor server.....
X(7): A program for managing terminal windows. See also screen(1).
But I just upgraded to 2.4.21!
Redhat is on version 9 wtf?
So uh, what is new in this version?
$foo_obscure_driver doesn't work I'll never use Linux again!
Now I can finally switch from windows!
$bar_obscure_feature which I can't live without never made it in, I hate Linux.
but I *liked* make menuconfig; make clean && make modules modules_install bzimage!!
I just spent the last 3 days trying to get the SELinux extensions, courtesy of the NSA installed on a Fedora Core 1 system.
I eventually gave up. However, the SELinux extensions were merged into the 2.6 kernel and it's apparently the plan of Fedora/Red Hat to put it into Fedora Core 2 sometime later this spring.
I, for one, can't wait.
I have no problem with your religion until you decide it's reason to deprive others of the truth.
This is great news! I'm excited even though I'm now an OS X dude. Once I find the time to back up my system and repartition I'll be trying LinuxPPC. Speaking of which, if anybody knows of (or wants to write) a non-destructive repartitioning tool for OS X please let me know!
-DA
For a summary of changes from 2.4 to 2.6, read Dave Jones' "post-Halloween" document. (The Changelog only lists changes from -test11 to 2.6.0 and so is not very useful. However, a full Changelog from 2.5.0 to 2.6.0 would be massive information overload, as well as just not terribly useful for a broad picture of what's different.)
nvidia users might want to download the proper patches before trying out 2.6. the patches can be foundhere
the start of something?
Here
It's really here... and it just seems unreal.
2.6.0 is a kernel. Unreal is a game. Get it straight.
I'd rather be a conservative nutjob than a liberal with no nuts and no job.
For those of us upgrading from 2.4 to 2.6 and don't know where to begin, you may want to check out an upgrade guide.
It's small but very helpful for someone that doesn't completely know what they're doing.
Gus
I mean I went there but there's no trusted computing logo. How can I trust software if it doesn't say I should. Linux will never be ready for the desktop until it's part of a trusted computing initiative.
You don't mirror kernel.org! They have more bandwith than God and NASA combined!
Fellowship 9/11
Start the build, go see LotR, come back to a nice compiled result - unless of course you enjoy watching the compiler do its thing, line by line. If so, you could always redirect stdout to a file and watch the instant replay when you return.
I'm sitting on top of a decently fast link and I'm leaving tomorrow, so I suppose this mirror couldn't hurt: linux-2.6.0.tar.bz2.
I'll try one:
the beaver is free
now let the party begin
burn up the mirrors
-- Given enough time and money, Microsoft will eventualy invent UNIX.
The answers is obvious:
Download & configure kernel.
Start compilation and go see Lotr with a smug "i'm more clever than thou" geek look knowing that you are actually multitasking.
Come back from the film with the kernel and modules crisply compiled for you, install boot loader and enjoy.
If not, why not? It's been 10 minutes since the kernel was posted and I'm not getting any younger.
So preempt must still be broken, as it has been since test10. Don't use it.
--
Internet Explorer (n): Another bug -- that is, a feature that can't be turned off -- in Windows.
i just updated all mission critical servers with this new kernel!
Well, huzzah to the kernel team, I've enjoyed their work for enough years. Not much champagne available here, but a heartfelt and lukewarm Milwaukee piss (offered).
I've been using 2.5.x and -test kernels off and on here, and its definitely a step in the right direction even for my humble desktop, IMHO. If I was to be bold I'd even say that 2.6 is a positive change (for users) in the same way that 2.0 was. Just based on the scheduling and device support, SMP (I use it), bigmem, etc.
And no, I'm not really worried about the SCO/IBM thing - the outcome won't change my opinions or Linux usage patterns an iota.
C|N>K
Its great to see this go out in 2003, capping off a stellar year for open source. Mozilla 1.4/5, Gnome 2.4, KDE 3.2 (almost), Apache 2.x...and countless other pieces of the puzzle coming together in an awesome ecosystem.
Corporations haven't just 'taken notice', they are actively pushing this stuff. They are amping up great services behind the new commodity - software.
RedHat and IBM and Novell are leading the charge from the .com side while a huge developer community has taken root in the volunteer ranks.
2.6 was the icing on the cake - the version that really challenges the most established kernels across the entire spectrum. BRAVO!!
Why is an insignificant little dot-release suddenly front page "news" around here? C'mon, guys, this isn't Freshmeat.
Cheers,
IT
Power corrupts. PowerPoint corrupts absolutely.
unlike 2.4 i must say 2.6 doesn't really have anything i'm very excited about...
What are you smoking? Better USB support, much better firewire support, Apple G5 and AMD Opteron support, pre-emptive kernel, ALSA by default, blah, blah blah the list goes on.
Unless you have a 386-25 with 4 megs of ram, an EGA monitor, and 40 MB MFM hard drive, you should be pretty damn excited (at least if you are a normal geek like the rest of us).
I'd rather be a conservative nutjob than a liberal with no nuts and no job.
In related news, Redhat/Fedora has announced that the next Fedora release will ship with 2.6. They've called it a "stop-ship" feature :) Fedora Core 2 is tentatively scheduled to be released in April 04.
I'm working on a free version of a
Linux-lookalike for AT-386 computers. It has finally reached the stage where it's even usable (though may not be depending on what you want), and I am willing to put out the sources for wider distribution. It is just version 0.02 (+1 (very small) patch already), but I've successfully run bash/gcc/gnu-make/gnu-sed/compress etc under it.
I have been pwned because my
My preciousssssssssss...My precioussssssss 2.6...
SCOses can't haveses our precioussssssssssss kernel....
do I have to send $699 to SCO if I already paid. I think this is a legitimate question that must be answered asap. I'm sure SCO will let us all know after the DDos has stopped against their network.
Look at the evidence from the Changelog:
s hing.orgh otmail.com
mdharm-usb@one-eyed-alien.net
trini@kernel.cra
jes@trained-monkey.org
James_McMechan@
Now ask yourself, do you want a patch submitted by someone at "one-eyed-alien.net" running on *your* production server? Can we really trust patches submitted by people using Hotmail accounts?
Go back to Windows, and rest assured that every developer will be using a trusted microsoft.com e-mail address. Don't you feel safer already?
You want the truthiness? You can't handle the truthiness!
From the following Cnet article:n efd_top
http://news.com.com/2100-7344_3-5127627.html?tag=
All these quotes apparently came from Mr. Morton himself.
"...the part of 2.6 that communicates with memory is less efficient, imposing a practical limit of 24GB of memory to the 32GB that 2.4 could handle. However, he believes that programmers will address the problem."
Is this reduced limit useful? Why should it be up to programmers to code around? Did I miss something?
"The new kernel also monitors for new events more frequently--1,000 times per second instead of 100--a fact that slows down the system about 1 percent..."
I assume it's to try and respond to events faster but increasing it tenfold, isn't that overkill? I mean, it slows the system down by 1% which isn't horrible and if a real-time app has a problem with it, you can always modify the kernel yourself but couldn't they have upped the polling to 250 which is a decent increase but not a 10x one.
"In addition, 2.6 requires somewhat more memory to run and shows worse performance when it has to use hard drives as extra memory under heavy loads... "
That seems reasonable that it needs a bit more memory but why should it see adverse effects under heavy loads as compared to the 2.4 kernel? Shouldn't they degrade at around the same level or are there some new file system issues that cause this?
Enlighten me.
You have to laugh at the anonymous jerks who have nothing better to do than hang out on slashdot and make fools of themselves -
In the first place, he is confused about the difference between a desktop environment and a kernel, but attempts to talk a good game anyway.
LOL, what sort of sad life do these trolls have?
"Burning CD's...something that has been common and easy on Windows platforms for, what, 4 or 5 years now?"
This functionality has only been built into the OS since WinXP. Third-party apps handled it before XP.
TW
But I just finished
compiling the 2 (point) 4
(point) 23 kernel!
Slackware 9.1 and -current still come with LVM version 1. Kernel 2.6 requires LVM2. So Slack is still not 2.6-ready, at least for people with LVM'ed filesystems. Okay, for everybody else, it is. :)
It's still a beta
But let's pretend it's finished
Linus needs testers
Irritable, left-wing and possibly humorous bumper stickers and t-shirts
Reuters - December 18 - Shares of Logitech surged on unexpectedly high sales figures released by the keyboard maker. Customers at CompUSA refused to comment.
I mean I went there but there's no trusted computing logo. How can I trust software if it doesn't say I should. Linux will never be ready for the desktop until it's part of a trusted computing initiative.
...that's how most people will understand it. They don't realize that the logo means that others can trust the computer not to do what you want, should that be something they don't want.
I'm still praying that people will learn from experience. Don't seem they'll learn much any other way at least...
Kjella
Live today, because you never know what tomorrow brings
I just finished downloading 2.6.0-test11 1.5 hours ago and then I see this. Anyhow, I downloaded the path test11->final, recompiled, and rebooted:
Linux boxor 2.6.0 #3 Wed Dec 17 23:53:09 EST 2003 i686 unknown unknown GNU/Linux
My Radeon binary drivers wouldn't work at first with it on my nforce2 motherboard but I've just found patches in Gentoo's portage tree. I'm currentely running Linux 2.6.0 final on an nforce2 computer with hw 3d acceleration enabled on my Radeon 9600 pro!
There are 2 kinds of people in this world: Those who write in decimal and those who don't
Upgrade to unstable, 'apt-get install module-init-tools', and you are ready to run 2.6. You can either compile it from source (use the instructions linked in the other reply and this will take very little thought), or if you don't want to compile anything, wait around for a binary image to show up on apt (there is a -test9 image right now, so 2.6.0 should be added eventually), and install that.
"(Man) tries to live his own life as if he were telling a story. But you have to choose: live or tell." --Sartre
Should kernel.org be slow for you, use a mirror, such as this one.
Now I know what to get my girlfriend for Christmas!
"The new kernel also monitors for new events more frequently--1,000 times per second instead of 100--a fact that slows down the system about 1 percent..."
I assume it's to try and respond to events faster but increasing it tenfold, isn't that overkill? I mean, it slows the system down by 1% which isn't horrible and if a real-time app has a problem with it, you can always modify the kernel yourself but couldn't they have upped the polling to 250 which is a decent increase but not a 10x one.
Polling 100 times a second has been the standard figure in the Linux kernel for a long long time. Meanwhile, the top CPU speed has increased by much more than one order of magnitude (say 300MHz -> 3GHz). Most desktop distributions have already been shipping with this set to 1000 already, since it makes the machine overall more responsive, something that's particularly important for a GUI.
I'm guessing that on a top-of-the line server pushing bits to this disk here, that NIC there at very high speeds, it'd be just as good as the old setting, keeping buffers flowing. That 1% quote is completely without context, and might be true on a really low-end machine where 1000 context switches takes up a lot of CPU time, but overall I don't think that's accurate.
Edit: I found this quote on a google search:
"I don't know what the costs of a higher HZ value might be, except for the obvious one: more cpu cycles will be spent servicing the timer interrupt. On my PPro, servicing the timer interrupt takes around 1500 cycles, so with HZ = 100 this accounts for fraction of a percent of the processor's time. With HZ = 1024, this still wouldn't be much more than one percent (I expect the figures to be similar for a K6)." So that figure might be accurate for a 150MHz Pentium Pro...
If you're running an embedded system or something else on limited hardware, you'd probably want to tweak that now, but then again you probably should have tweaked a lot of kernel settings in the past as well. So nothing new here, just staying with the times. Hell, on a GUI machine I'd consider experimenting with setting it even higher.
Kjella
Live today, because you never know what tomorrow brings
Linus Torvalds himself said to not use it for a couple of builds.
S W
0 .
http://linuxtoday.com/developer/2003112400826NWKN
"There is still something strange going on that seems to be triggered by preemption, so for now we suggest not enabling CONFIG_PREEMPT if you want the highest stability. On the other hand, I'd love to have more testing, so that we can try to figure out what the pattern is - but please mention explicitly that you ran with preemption if you have problems."
Someone else reported that it was just a mistake on the part of one of the testers, which was revealed http://article.gmane.org/gmane.linux.kernel/16319
Who is a troll -- a person who follows what Linus says in official annoucements, or some random person who says, "works for me" in a rude way?
--
Internet Explorer (n): Another bug -- that is, a feature that can't be turned off -- in Windows.
-make xconfig looks really professional now /etc/modules.conf contains only OSS aliases, no alsa config files at all. so no sound at the moment...
-make / make modules / make modules_install has all been tidied up by the looks of it -- no more endless printout of GCC syntax. had me worried for a second that nothing was compiling but overall looks pretty slick
-alsa comes installed as default, but the configuration seems a little screwy (on debian at least) --
-usb mouse doesn't seem to work here when compiled in the kernel, but works fine as a module -- same problem i've had with 2.4.18-23
-the nvidia 2.6.0 patch available at minion.de works great, so i have a functional X11 server with nvidia modules
The only thing I can find to fault is that somehow the X11 server on the backup 2.4.23 kernel crashes on bootup due to some problem parsing the XF86Config-4 file. I'm not sure if this is a side-effect of the 2.6.0 install or something else (maybe some apt-get update X11 changes i missed?), and i've had the occasional problem before with older kernels becoming only partly functional after newer kernels are installed.
All around though, nice job! Compiling the kernel is getting easier and nicer to look at. And it seems the problems with mouse lagging during 100% CPU usage are gone, at least as far as I've tried it this evening.
Thanks to Linus and all that contributed..
experimental audiovideo minimalism: Rebuild All Your Ruins
this text is pasted from a mail i sent to the smbfs maintainer. i have not received an answer, didn't really expect one at this time, but maybe somebody else has encountered and solved this problem. could you point out what i missed?
--
sorry to bother you this late in the 2.6 test series, but i wondered whether this change in smbfs behaviour was intended (or how it could be affected by mount options, etc):
during my using the 2.4.x kernels, i mainly used smbfs as a convenient way to access various data which was not located in subdirectories of the mount source, but symlinked from other server directories. i think this is also the behaviour the user experiences when mounting from other operating systems.
with 2.6.x (can't remember 2.5.x...) clients i have been unable to mount the same sources in a similar way, symlinks would still appear as symlinks, making the linked data much more difficult to access.
could you tell me whether i missed a mount option or this diverging behaviour is intentional?
Short answer, just do it.
Shorter answer: Yes
Little Brother, watching the watchers
Well, since they all RUN the kernel... try them all ;-)
42 + 1 = 42
For the fact that the entire linux community just started downloading the same 100 meg file...the server runs amazing. When 2.4 came out I think we toasted it right quick.
snowulf.com
BitTorrent downloads are checked with SHA1 hashes. md5summing it is only worth doing if you don't trust the .torrent
Linux is a process, not a product.
Slashdot: Where people pretend to be twice as smart as they really are by behaving like children.
Windows uses SCSI-emulation just like Linux 2.2 and 2.4. Using ATAPI directly is one place where Linux is way AHEAD of windows.
If you are complaining that CD-burning was not setup for you automatically (which has nothing to do with kernel 2.6), throw out your geek-friendly Gentoo, and use a user-friendly distro instead, which will setup things just like windows.
This really bores me.
Work and home, XP for me
You all need a life
Oh wait, you said colorful. Ok...
Pasty white skin tone,
Yellow teeth, bloodshot red eyes.
Come out of the basement!
Tomorrow, Bill and Linus announced it earlier today. Linux wrote some VB code for the new version of the Windows Explorer Clippy add-on. Once it has been tested and verified to be full of security holes, Gates will make it worse and make it available via windows update.
I'm not drunk, I'm just in touch with pi.
You might want to keep an eye on your 2.6.0 machine if it's on a network that's readily accessible to the outside world. Apparently not all of the security fixes that occurred in the 2.4 line have made it into 2.6.0.
Dave Jones' post halloween document, which is mentioned in an earlier post as a good summary of changes, mentions the following (near the bottom):
Security concerns.
~~~~~~~~~~~~~~~~~~
Several security issues solved in 2.4 may not yet be forward ported
to 2.6. For this reason 2.6.x kernels should not be tested on
untrusted systems. Testing known 2.4 exploits and reporting results
is useful.
Hi, I'm using an acm-ppp device and the Badness/kernel panic bug still exists, this has been there since 2.5.something and has not been patched. It's very annoying, fills syslog with Badness output and eventually disables pppd with k-panic.
As shown below.
Dec 18 01:30:12 ubik kernel: cdc_acm 3-3:1.0: ttyACM0: USB ACM deviceBadness in local_bh_enable at kernel/softirq.c:121Dec 18 01:30:12 ubik kernel: Call Trace:
Dec 18 01:30:12 ubik kernel: [local_bh_enable+133/144] local_bh_enable+0x85/0x90
Dec 18 01:30:12 ubik kernel: [__crc_blk_start_queue+1169403/2870650] ppp_async_input+0x2d7/0x5a0 [ppp_async]
Dec 18 01:30:12 ubik kernel: [__crc_blk_start_queue+1166374/2870650] ppp_asynctty_receive+0x52/0xb0 [ppp_async]
Dec 18 01:30:12 ubik kernel: [flush_to_ldisc+160/272] flush_to_ldisc+0xa0/0x110
Dec 18 01:30:12 ubik kernel: [__crc_sleep_on+1947600/2407885] acm_read_bulk+0xbf/0x140 [cdc_acm]
Dec 18 01:30:12 ubik kernel: [__crc_blk_start_queue+162921/2870650] usb_hcd_giveback_urb+0x25/0x40 [usbcore]
Dec 18 01:30:12 ubik kernel: [__crc_blk_start_queue+1216947/2870650] dl_done_list+0x11f/0x130 [ohci_hcd]
Dec 18 01:30:12 ubik kernel: [__crc_blk_start_queue+1219352/2870650] ohci_irq+0x84/0x170 [ohci_hcd]
Dec 18 01:30:12 ubik kernel: [__crc_blk_start_queue+163002/2870650] usb_hcd_irq+0x36/0x60 [usbcore]
Dec 18 01:30:12 ubik kernel: [handle_IRQ_event+58/112] handle_IRQ_event+0x3a/0x70
Dec 18 01:30:12 ubik kernel: [do_IRQ+145/304] do_IRQ+0x91/0x130
Dec 18 01:30:12 ubik kernel: [rest_init+0/96] _stext+0x0/0x60
Dec 18 01:30:12 ubik kernel: [common_interrupt+24/32] common_interrupt+0x18/0x20
Dec 18 01:30:12 ubik kernel: [rest_init+0/96] _stext+0x0/0x60
Dec 18 01:30:12 ubik kernel: [default_idle+35/48] default_idle+0x23/0x30
Dec 18 01:30:12 ubik kernel: [cpu_idle+44/64] cpu_idle+0x2c/0x40
Dec 18 01:30:12 ubik kernel: [start_kernel+332/352] start_kernel+0x14c/0x160
Dec 18 01:30:12 ubik kernel: [unknown_bootoption+0/256] unknown_bootoption+0x0/0x100
Dec 18 01:30:12 ubik kernel:
Dec 18 01:30:12 ubik kernel: Badness in local_bh_enable at kernel/softirq.c:121
Dec 18 01:30:12 ubik kernel: Call Trace:
Dec 18 01:30:12 ubik kernel: [local_bh_enable+133/144] local_bh_enable+0x85/0x90
Dec 18 01:30:12 ubik kernel: [__crc_blk_start_queue+1166389/2870650] ppp_asynctty_receive+0x61/0xb0 [ppp_async]
Dec 18 01:30:12 ubik kernel: [flush_to_ldisc+160/272] flush_to_ldisc+0xa0/0x110
Dec 18 01:30:12 ubik kernel: [__crc_sleep_on+1947600/2407885] acm_read_bulk+0xbf/0x140 [cdc_acm]
Dec 18 01:30:12 ubik kernel: [__crc_blk_start_queue+162921/2870650] usb_hcd_giveback_urb+0x25/0x40 [usbcore]
Dec 18 01:30:12 ubik kernel: [__crc_blk_start_queue+1216947/2870650] dl_done_list+0x11f/0x130 [ohci_hcd]
Dec 18 01:30:12 ubik kernel: [__crc_blk_start_queue+1219352/2870650] ohci_irq+0x84/0x170 [ohci_hcd]
Dec 18 01:30:12 ubik kernel: [__crc_blk_start_queue+163002/2870650] usb_hcd_irq+0x36/0x60 [usbcore]
Dec 18 01:30:12 ubik kernel: [handle_IRQ_event+58/112] handle_IRQ_event+0x3a/0x70
Dec 18 01:30:12 ubik kernel: [do_IRQ+145/304] do_IRQ+0x91/0x130
Dec 18 01:30:12 ubik kernel: [rest_init+0/96] _stext+0x0/0x60
Dec 18 01:30:12 ubik kernel: [common_interrupt+24/32] common_interrupt+0x18/0x20
Dec 18 01:30:12 ubik kernel: [rest_init+0/96] _stext+0x0/0x60
Dec 18 01:30:12 ubik kernel: [default_idle+35/48] default_idle+0x23/0x30
Dec 18 01:30:12 ubik kernel: [cpu_idle+44/64] cpu_idle+0x2c/0x40
Dec 18 01:30:12 ubik kernel: [start_kernel+332/352] start_kernel+0x14c/0x160
Dec 18 01:30:12 ubik kernel: [unknown_bootoption+0/256] unknown_bootoption+0x0/0x100
Dec 18 01:30:12 ubik kernel:
Maybe this version will make me popular with women.
Anyone know if 2.6 has better power management for laptops? -- the speedstep chip I've got goes for hours in Windows, and for an hour in Linux.
Vaya con huevos, my darling.
It will be ready
To run Debian stable
Some time next decade
"Proudly Posting Without Reading The Article"
Do you care about the security of your wireless mouse?
http://www.kniggit.net/wwol26.html
seems to be a pretty comprehensive description.
Does anybody have a howto on how I can migrate my LVM version 1.0.7 volumes from 2.4.23 to 2.6.0? I know LVM has been replaced by device-mapper. Do I have to run some kind of conversion tool, or will device mapper just magically find and activate my LVMs? I can't find any information on this.
Date: Thu Dec 18 2003 - 00:15:50 EST
---cut---
Desktops and laptops may have more trouble at this time because of the much wider range of hardware and because of as-yet unimplemented fixes for the hardware and BIOS bugs from which these machines tend to suffer.
During the 2.6.0 stabilization period a significant number of less serious fixes have accumulated in various auxiliary kernel trees and these shall be merged into the 2.6 stream after the 2.6.0 release. Many of these fixes appear in Andrew Morton's "-mm" tree (...)
---cut---
Should invading one's peaceful neighbours be opposed, or rewarded with trade deals?
I have an Asus A7M266-D with an AMD 760 MPX chipset. I just upgraded to 2.6.0 - everything seemed fine, kernel booted with no issues, but AGP support is apparently broken. Upon loading my ATI FireGL drivers (rebuilt against the latest kernel, and configured to use the kernel's AGP GART rather than ATI's), I get a kernel OOPS (null pointer dereference) in the AGP GART driver (specifically when it enables AGP 4x transfer mode on device 01:05.0 - my video card. Enabling AGP4X on the northbridge reported success, but when it gets to the card itself, crash time!)
:)
Has anyone had similar experiences with the new kernel? I'd like to see if it's just my configuration, my video drivers (though the ATI drivers had no AGP problems and were rock solid under 2.4, and claim to support 2.6, you never know...), or something else. I know that the AGP subsystem has had a major overhaul in 2.6 and the bugs are still being ironed out, but it'd be nice to know what to blame.
And if something in my post doesn't make sense, it's 1:45 AM over here (GMT -08:00), so I have an excuse
Every cloud has a silver lining (except for the mushroom shaped ones, which have a lining of Iridium & Strontium 90)
I took my life in my hands, and tried writing to an XP NTFS volume about 3 months ago. The write operation completed successfully, yet ntfsfix said the volume was irrepairable. I booted into XP anyway, which didn't even blink an eye at this new data, and it all worked fine. No idea what ntfsfix was trying to do then, and a manually run scandisk found no errors. ntfs support == all good, imho
but my point is that the quality of bugs has been pretty high lately - Linus
;)
We have bugs... but at least they are *high quality* bugs! Take that Microsoft
(Congrats to all the developers for 2.6! Looking forward to getting rid of OSS and ide-scsi!)
If both ide-cd and ide-scsi are used as a module, I don't see why you can't just load and unload the correct modules when you want to change modes.
But OTOH, why would you want to do that anyway? With ide-scsi, you can do everything you need to do with the drive, I don't see why you can't just use that mode all the time.
The biggest bonus I got from 2.6 was DMA with ATAPI commands finally works. Earlier kernels would not use DMA for ATAPI commands (read: CD/DVD burning commands) even if DMA was enabled for the IDE device. This effectively limited CD burning to the speed that PIO would work at, which was about 12x on my 900Mhz K7. It also ate up your entire CPU.
:)
With 2.6, DMA works properly with ATAPI commands, at least when using the new ATAPI virtual SCSI bus (NOT the ide-scsi module!). To use the new virtual bus, use 'dev=ATAPI:0,0,0' in a cdrecord command. You may also need to use the latest alpha of cdrecord.
I can now burn 2 CDs at once (multiple burners), at 52x without my CPU load going over 0.2!
Of course, if you had the luxury of using REAL SCSI CD burners before, this won't make a lick of difference to you.
Comment removed based on user account deletion
the biggest problem is when it hits 3.1. Everyone will think, "hey, I had windows 3.1 years ago"
2.A, you decimal supremisist
How ready is it? Is there a site that breaks down which hardware drivers support/do not support the sleep states? I remember during the test releases it was documented that many drivers had not yet been updated to support the sleep states.
APM support has gotten me so far, but some things on this laptop would be more doable if I had acpi support, and I have another laptop which doesn't support apm at all.
XML is like violence. If it doesn't solve the problem, use more.
...anecdotal evidence. So do we have any real scientific stress tests of Linux's NTFS write capability? With all due respect, the parent post sounds like "I tried it once, and it worked! => Linux NTFS support is perfect"
So does it work:
a) Sometimes
b) All the time (we hope... maybe)
c) Good enough for common users
d) Production quality
On a wild guess, I don't think it'd d) just yet...
Kjella
Live today, because you never know what tomorrow brings
"But Windows can seemlessly change between SCSI-emulation and IDE, without requiring boottime option (allthough a reboot is required for installation)."
This sounds very unlikely to me. I admit, I don't really know, having not owned a windows computer in a few years...but I can't see any conceivable way this could be true. Does windows have some right-click option on the drive letter that has a check-box for "use scsi-emulation" or something?
I think it is much much more likely that either a)windows leaves the drive in scsi-emu mode all the time, or b)windows loads normal ide stuff, and nero/roxio/whatever loads up the scsi-emu.
The big question is "can you really tell windows to turn scsi-emu on/off?" I doubt it.
Given a choice between free speech and free beer, most people will take the beer.
Use -k to keep the settings for your drive - the drive should remember the settings and they should remain active while using scsi-emulation (which is only limited to whatever IDE settings you're using)
Effing yesterday I was twiddling some config options in my kernel to see if I could get a cleaner boot-up on my laptop, so I popped over to ftp.us.kernel.org to see if there was something later than 2.6 test 11 out there. There wasn't, so I tweaked and compiled my test11 image with quite satisfactory results. Now I'm going to have to do it all again *sigh*...
I'm trying to teach myself to set people on fire with my mind... Is it hot in here?
My old HP CD-RW drive would crash (along with my system) if I tried using scsi-emulation for reading anything larger than a megabyte from the drive. It was fine for burning though. I had to move to the ide-cd driver whenever I wished to use it for reading.
Once I bought a firewire enclosure and realized it still happened, infact worse than before, I decided to ditch it and bought a sub-$100 dvd+rw drive.
http://www.linux.org.uk/~davej/docs/post-halloween -2.6.txt
Direct booting from floppy is no longer supported.
You should now use a boot loader program such as syslinux instead.
"make bzdisk" continues to work (now using syslinux).
Does this mean what I think it does? No more floppy boot disks? Or am I misreading?
reech bee-yond ur clip-0n
Because it's broken in 2.6.
GCHQ Quantum Insert installed. If only our tongues were made of glass, how much more careful we would be when we speak
Enhanced coredumps are not new in 2.6.
/proc/sys/kernel/core_pattern~ $ sleep 60 &
sigma:~$ uname -a
Linux sigma 2.4.22 #2 Sat Oct 23 22:35:00 EDT 2004 i686 unknown
sigma:~$ cat
core.%e.%p
sigma:
[1] 450
sigma:~$ kill -BUS 450
sigma:~$ ls -l core*
-rw------- 1 rfc users 69632 Dec 18 10:44 core.sleep.450
You can still make boot disks, but it requires on of the boot loaders: grub,lilo, syslinux or another in order to boot. the code in question in the ernel to support direct booting from a floopy was apparently removed.
Linux 2.6.0 kernel, Now with more SCO IP!
I thought direct booting was disabled long long ago, as it hasn't been used much in recent years. AFAIK, in the olden days you could just copy the kernel image to a floppy (using dd etc.) to make it bootable.
Escher was the first MC and Giger invented the HR department.
Hint: 2.6.0 has two dots, but decimal numbers only have one. The version number is an ordered triplet of integers, which is why there are things like Linux 2.4.23. However, some pieces of software use decimal version numbers, like TeX 3.14159.
Escher was the first MC and Giger invented the HR department.
Interestingly, FreeBSD 4.x didn't use SCSI emulation to talk to a CD-ROM burner; you had to use it's burncd program, part of the 4.x base system, for IDE CD-ROMs. FreeBSD 5.x, on the other hand, uses SCSI emulation and they consider this an upgrade. (You have to use cdrecord from ports.) Could anyone explain to me the advantages of using SCSI emulation, if any, and the disadvantages besides problems sharing DVD and CD burning on one drive? (I have a seperate DVD-ROM and CD Burner. :-) )
Unless you have a 386-25 with 4 megs of ram, an EGA monitor, and 40 MB MFM hard drive, you should be pretty damn excited (at least if you are a normal geek like the rest of us).
I have several of those WITHOUT the hard drive just 16 meg of CF card on an IDE bus as storage and I'm super excited.
2.6 is an EXCELLENT kernel for embedded work on really slow/old computers.
Do not look at laser with remaining good eye.
Since SCSI is acctually a hardware independant protocol, SCSI-commands can be send just over any channel (there is even iSCSI whitch uses TCP/IP, if recall correctly). In FreeBSD 4.x cdburn could send SCSI-commands over the IDE-interface to the cd-burner. One coulnd't use cdrecord on ide-burners with it, because cdrecord needed pure SCSI-devices. With Linux 2.6 one can now also use the IDE-devices to send SCSI commands. New cdrecord releases support that, so there is no need to add "scsi-emulation" to the kernel any longer.
So both FreeBSD and Linux have the same features now, but they were added in reverse order *g*
What do you do when you see an endangered animal eating an endangered plant?
Also, I hate how people say "oh, well, it was only a local exploit..." It shows they dont understand the methodology used by malicious hackers. You use one flaw to give you remote access, then leverage that remote access into exploiting the local access flaw.
How else do you think Debian was hacked with a mere local access exploit?
Manipulate the moderator system! Mod someone as "overrated" today.