Slashdot Mirror
Kernel 2.6.1 Released
jnf writes "And so he said it is released, and then jumped on a plane to Australia. Linus announced the release of 2.6.1 a few minutes ago, fixes include AGPGART, a fork() bugfix, and misc changes to XFS, and those are just the patches applied since v2.6.1-rc3. Full changelog is avialable, kernel at the usual places, i held off posting this until kernel.org was updated." 2.6.0 is now in Debian unstable...
still doesn't build on cygwin..
... it gets released the minute I've installed 2.6.0.
:)
Perhaps I'll wait until at least 2.6.2 before doing it again
Hell, it took me until 2.4.5 to switch from 2.2. Let's hope this one is faster :)
Linus Flees! The time of judgement is upon us. Oh, repent!
Besides Debian, What distros have 2.6.x ?
Does this release fix the do_mremap() exploit? I coulden't find it in the changelog. I got the impression from security sites that 2.6.0 had this bug.
We didn't have all these kernel updates...and we's liked it that way!
</bitter young man>
clifgriffin > blog
We will know that it is time to use 2.6.x in anger when Patrick ships his distro with it as the default kernel. This is usually a sure sign that stability and maturity is upon us.
Stick Men
I download it, double click on the .exe, click next a few times and restart?
Thanks,
Clif
clifgriffin > blog
*Watches as linus releases an embedded back-door to make a supercomputer to bring rise to the new world power, Australia*
Well, you see, my BLT drive just went AWOL and I got this real big presentation due tomorrow for Mr. Kawsaki and if I don't get it in he'll ask me to commit Harry Carry. Could you read me the numbers on your version? It's the thing that you get when you type 'uname -a'
Oh wait, we are all about reality here. My mistake.
NetBSD...wtf?
I guess you'll just have to upgrade your bootloader. Recompilation of init and other software might also be necessary - 2.6.x is known to break the binary compatibility with current versions of NetBSDs. Filesystem should work, though.
Save your wrists today - switch to Dvorak
I'm going to be in Australia (and on airplanes) for the week, but we're
:-)
all in the capable hands of Andrew, so why worry? The fact that I'm
fleeing the country should in no way be construed as anything sinister at
all, no siree. Nope. I'm innocent, and nobody saw me do it.
Linus is not only a great project manager, system architect and coder, he's funny as hell too.
(If that isn't an underhanded slap in the back of the head of Dalek McBride, I don't know what is. "I'll be in Oz all week, try the veal!!")
I hope SCO sticks around for a while just for the comedy factor.
Soko
"Depression is merely anger without enthusiasm." - Anonymous
Native support for SATA hard drives!
I've been wanting to dual-boot for several months now, but the Linux installer (any distribution) does not recognize my SATA hard drive.
For an OS that's supposed to be innovative and cutting edge, Linux is really dropping the ball on this one!
Socialism: A feeling of discontent and resentment caused by a desire for the possessions or qualities of another.
Damn, my patch didn't make it in. It was the first kernel patch I ever wrote. It was just a two-liner, but I was told to submit it to Linus. I later simplified it to a one-liner. I guess it was too close to the deadline.
Here's hoping for 2.6.2!
Is it safe to assume that 2.6.1 is stable and secure to use, or would it be more reasonable to wait until it enters more main stream usage and possible problems are exposed?
Have there been any articles or reviews comparing the performance of various kernel versions? I'd find it interesting how much progress has been made in areas such as network throughput, disk access, etc. I guess its possible there isn't any more room for progress in some areas, I would find that interesting too.
Grrrrr... don't bother me, I'm thinking.
To Sum it up:
/proc/net/tcp fixed
o lots of USB-Updates, eg. for storage-devices and BUGS
o seeking in
o some more use-after-free()-fixes
o [libata promise] fix another ugly bug (for those who use it)
o lots of misc small fixes
o lots of ARM stuff
o dvb: Update DVB core (and more stuff, for those video-people)
o Fix via686a/KX133 TSC failure (for ppl with an Abit KA7/KA7-100 etc)
o Fix memleak on execve failure (memleaks are always bad)
o cpuqfreq stuff/additions
o "at least" one important X86-64 fix
o mremap() security fix
- UML
- ipsec
- ebtables & bridge-netfilter
- robert love's preemptable patch
- LSM-hooks (which make not everybody happy:grsecurity, RSBAC
- LS-module SE-linux
- filesystem-encryption
- apci 2.5 backports
- Kernel
.config
- DVB-support
I got really tired of applying combinations of those patches to newest kernel source (due to security issues). They 're now all included to 2.6! Only MPPE-support seems still to lack.They must have beaten up Linus to get all those accepted ...
Wow, he must be really insecure about this one if he had to run away...
Is this just a turgid troll, or Linus is really enlightening us? Linus, don't you spell your last name with Torvals?
Cygwin is great but a full linux would be even better. In theory at least, User Mode Linux should be able to run under Windows. Possibly with a MinGW compile under Cygwin so after building, it doesn't need the Cygwin layer.
Let's hope they've fixed ALSA in this release then. I was surprised when I tried using it with 2.6.0 and it seems full of broken drivers. Of course, downloading ALSA and building it the same way I would with 2.4.x works fine! I'm thinking they should either try to include the latest ALSA driver code in the kernel, or just leave it out so that it can be built separately...
Code, Hardware, stuff like that.
So he releases the kernel and runs away. what does he know that we don't?
Is there a place where someone can find a list of the hardware that is supported by the 2.6.x kernel? I have been able to find hardware compatability lists for the 2.4.x kernel on redhat and mandrake's websites, but I have not found anything for the 2.6 kernel.
http://github.com/gbook/nidb
... 'with TAA' ...
;) ... as an aussie who grew up in the 70's, linus' quip at the end just rings a bell.
its those little 'cultural synchronicities' that make linus such a fun person to know
canny finns.
; -- the corruption of government starts with its secrets. a truly free people keep no secrets. --
Slackware kernel 2.6.x compile/upgrade guide available here.
Anyone running 2.6 in a heavy load environment? Specfically, a database such as oracle/informix/db2 in a large data warehousing or OLTP environment. I've had above average performance and reliability with 2.4 and although I don't see myself upgrading to 2.6 soon, I am pretty curious as to how things have developed.
That's a heck of a lot of changes for a "stable" kernel.
Me: How many fingers do you have on your right hand? ...All right, I can see you're upset. How much would it take to clear this up? Patches? A syctl named after you? The head of Alan Cox?
Linus: What?
Me: Oh, how I have prepared for this moment. The coding, the studying, the kernel crashes, never seeing the sun...
Linus: What the hell are you talking about?
Me: My name is Saint Aardvark the Carpeted. You killed my kernel. Prepare to die.
Linus: How the hell did you find me? Did Darl send you?
Me: My name is Saint Aardvark the Carpeted. You killed my kernel. Prepare to die.
Linus:
Me: My name is Saint Aar--
Linus: Stop saying that! Guards!
Me: --killed my kernel.
Linus: What do you want?
Me: I want my -rc3 kernel back, you son of a bitch.
Carousel is a lie!
This is a bit off-topic, but:
I was an early user of Linux (1.2.8 and earlier w/ Slackware). ("Back in my day, we had to compile our own kernels!").
Anyway, I've been screwing around again lately. I've got two machines running Mandrake 8.2 and one w/ Mandrake 9.2 (VMWare actually). Also planning on messing w/ Redhat 9 and Suse. Knoppix rules, etc.
What I want to know is: What are the complications/problems with upgrading your kernel? I remember there being all sorts of problems with shared libraries versions since they don't have any internalized versioning system to run things side by side.
Is it still true that I might break half the apps running on my system if I try to update my kernel?
Please help to re-educate a guy who has lost his way.
Thanks.
Tom
---- It puts the lotion on its skin or else it gets the hose again. It does this whenever it's told.
Here.
"Res publica non dominetur"
Okay, if 2.6.0 is stable, and 2.6.1 is unstable. What version number would you give to the next stable kernel when bugs are fixed (not new features, just bugs). 2.7.0? that would lead to version bloat. 2.6.0.1 ? That gets even more confusing. The current even/odd allows you to add new features to the unstable branch, while still putting in bug fixes into the stable branch, all the while keeping "major" version numbers the same.
Uhm, it's the second number that determines stable or development version. 2.6.0 and 2.6.1 are both stable releases.
The rewhide version of fedora has it. If I am not mistaken.
So you can install FC1, and then upgrade to 'unstable'. You obvioussly dont want to do this unless you want UNSTABLE!
I got to hand it of to you guys. News gets here pretty blazing fast. A few minutes ago? Pfft, that is "fresh news" in my book.
Good job.
Oh, and good kernel to and stuff...
In looking at the changelog, I see lots of 2.4 fixes are being added into 2.6.1. I understand the kernel versions are completely parallel development paths. So does this mean there are lots of 2.4 bug fixes that are still not in 2.6? If so, I would think that might be something worth waiting for before upgrading.
Fix silly mremap test.
Get off the drugs, Linus.
Does someone have a super easy procedure to upgrade kernels. This is something I haven't done since kernel 2.0.x. I have moved to redhat9 and I am wondering if there's an easy way about it.
A slashdot a day keeps the doctors away - linux penguin
I fail to see how 2.6.1-rc3 (rc == release candidate) is confusing. rc numbering is pretty standard, even Bill's boys do it (Windows 2003 rc-1 for example).
There's also the question of why exactly people new to Linux are compiling their own kernel rather than using that provided by their distro of course.
For even more clarity the ftp site now has the rc-whatever releases in a 'pre-releases' subdirectory, so I really don't see an issue here.
Blaming GW Bush for the Iraq war is like blaming Ronald McDonald for the poor quality of food.
This is a way to make the Windows 85% desktop share vanish overnight.
Just compile the most expansive possible kernel. Package it and "sell" it to cnet as the p2p app to have. Include boot loader.
No one reads warnings/lisenses anyway...
And voila! 85% linux on the world's desktops overnight! And what a night it will be!
I pity Dell support and the Indians....
/. Where the truth
stop trolling
Oh, the irony!
Linux 2.6.1 kernel? Great, compiling it now.
Linus coming to Linux.conf.au Australia's annual Linux conference? It's soon to start next week in Adelaide! Now that would be something considering Linus isn't listed as one of the speakers. Rest assured we'll buy you a drink.
There's all sorts of initialisation ramdisks containing kernel modules, etc, which get loaded by the boot loader - it's impressively scary for someone who's a few years behind the times.
I prefer to leave it to the distribution people - my SuSE 9.0's had a few minor kernel upgrades done for me, and nothing's broken ye4^&g$%&
NO CARRIER
...can be found here.
Lots of stuff to work on there... that's just the architecture directory...
The Army reading list
uh, because they can?
Recently Linus has shown his dislike for the scsi emulator for ide devices. He went on to say that there werent any common devices that needed the scsi layer. One such device are zip drives. I use a Zip 750 in my server to backup a small but important set of data. The only way this drive will work is with the scsi emulated layer. Has this been fixed in the 2.6 kernel series (it wasnt fixed in 2.6 pre4), or does someone have another way to use this device without scsi?
Tis better to be silent and thought a fool, than to open your mouth and remove all doubt --Abraham Lincoln
Shouldn't have any problem. I didn't have any problem when I upgraded my friend's machine from 2.4 to 2.6 (no, I still haven't done it myself... too lazy.)
http://mediagoblin.org/
meh... old and lame... please grow up and piss off... and dont claim credit for other peoples work. this was funny about two years in its original form.
When I went from 2.4.xx t 2.6.0-testxx (on a Gentoo 1.4 system) I downloaded the 2.6.x kernel and checked in Documentation\Changes. That file will list several packages and the minimum version needed. It also has the command to check the version and the site to download updated packages. Once you have verified that you have the correct versions of extra software compile the new 2.6.x kernel. Boot it and see what breaks. Of course you want to keep a backup of your current working 2.4.x kernel to boot.
As for breaking half your apps: no. I built my Gentoo system under a 2.4.x kernel and now run a 2.6.x kernel with no problems.
the_crowbar
Have you read the Moderator Guidelines
I've been toying with the idea of putting Linux on my Inspiron 8200 for awhile now (n00bs gotta start somewhere :)...). How well does 2.6.x support the TrueMobile 1300? I think (don't hold me to it) that it's a Broadcom chipset.
Also, what's the most user-friendly distro for someone really unfamiliar with Linux to start with?
Been playing with 2.6 since test9 and been upgrading the kernel since.
They keep on top of things with Gentoo.
"Music is everybody's possession. It's only publishers who think that people own it." - John Lennon.
The Win2k kernel won't compile on GCC.
A kernel is very different from an application. It requires some very tricky compiler support in order to function as designed. If you don't want to sit down and write it entirely in assember, you end up picking 1 compiler and using many compiler-specific features to get your results.
--
Internet Explorer (n): Another bug -- that is, a feature that can't be turned off -- in Windows.
It wont break your system, but a few subsystems change:
* Module loading: There are new tools for this (usually called module init tools). These are MANDATORY.
* Logical Volume Management: lvm2 is available but possibly not required (not sure on this)
* Alsa: Can now be compiled in the kernel. Might need minuscule tweaking
* A few modules have been renamed. (e.g. printer.o -> usblp.ko)
Divide et impera!
http://saveie6.com/
The 686 flavor at least makes the ramdisk too big and will kernel panic before loading the initrd image... append ramdisk_size=8192 in lilo or add the bootparam to the grub boot arguments.
I have been using test9, and have been having a hell of a time with my PS2 mouse. On my system, with 2.6 kernels, whenever there is any load, the mouse becomes very erratic bouncing about the screen and clicking on things at random. I've tried as many of the "fixes" as I can find, but none have done the trick. I assume it is limited to sometihng unique about my system (KT600 mobo), otherwise people would raising a big stink. Have I missed the fix somewhere>
Yeah, I know bud.
It's a hard nights work at the WOK STATION when you work in a Chinese restaurant !!!
I just downloaded the tarball, modified my 2.6.0 configuration a little bit (what the heck do I need UFS support for?), compiled and rebooted. Without any tweaking, ALSA, LVM2, ide-scsi (in your face, Torvalds!), the Promise IDE-Controller and all the usual tidbits work. Nice one.
BTW, does anybody know how to make K3B understand the new ATAPI cdburning stuff?
Divide et impera!
I'm a loyal and happy Linux user
Hippy is spelled with an i not an a.
Hey, *TROLL* what about checking your facts?
I have been using SATA disks on Linux for over a year.
Support for some *buggy* chipsets has been less than perfect, but it sure as hell works with all common chipsets. And workarounds for most of those bugs have been in 2.4 and 2.6 for quite some time.
Now we can go back to our standard slash-FUD program...
\\k
P.S.: Maybe the RedHat installer doesn't support SATA(haven't tried), but that has nothing to do with kernel support, that has been there for a *long* time.
Wel.. I have a question.
:( And I can't compile the kernel with bootsplash..)
On a nforce chipset vit nvidia geforce 4 MX card, must I use agpgart + nvidia-agp modules or the agp support provided by the nvidia proprietary driver ?
(This 2.6.1 doesn't bring me the framebuffer on my geforce4 mx.. I don't understand
Ploum.net.
Yep. Go to this site and download the diff for your version of the driver.
You'll need to run the NVIDIA installer with the --extract-only argument to untar it, then cd usr/src/nv and patch -p1 the diff file and then cp Makefile.nvidia Makefile. Then just run make install in the top-level directory of the nvidia installer and it'll build and install a 2.6.1-compatible module.
"People new to Linux" probably won't download a kernel anyway.
Sig (appended to the end of comments I post, 54 chars)
What's /sys for, anyways? Is it just that /proc was getting crowded?
All's true that is mistrusted
Look in CVS HEAD. It'll be in the nightly compile, too.
Next time read the damn patch log!
That was supposed to read "2.4.21 to 2.4.22".
XJS*C4JDBQADN1.NSBN3*2IDNEN*GTUBE-STANDARD-ANTI-U
Ah good point. Supports my case, though - I've compiled a few kernels and still forget how it works. In that case, how about 2.6-stable-1 ?
I know many people will not read the documentation so I'm posting it here.
You need module-init-tools with the 2.6.x series.
<torvalds@home.osdl.org>
Fix silly mremap test.
Get off the drugs, Linus.
I fail to see how 2.6.1-rc3 (rc == release candidate) is confusing. rc numbering is pretty standard, even Bill's boys do it (Windows 2003 rc-1 for example).
What I don't like is the information implicit in the odd/even number version number when it could be text. It's just another piece of trivia to remember. It could be 2.6-unstable-1-rc3 (or actually 2.3-unstable-1-rc3 as you'd go through numbers half as fast).
There's also the question of why exactly people new to Linux are compiling their own kernel rather than using that provided by their distro of course.
Why shouldn't they?
Anyway, the information is not just useful for installing kernels. What about just checking a system to see what kernel is currently installed? Currently you have to know about odd-even versions to know if you have a development kernel or not using uname -r , whereas if it was textual it would be obvious.
OK, then...how about:n d-comple tely-up-to-date.tgz"
"Linux2.6-use-this-version-it-is-stable-a
I'd like to start playing w/ compiling custom kernels. Can you get the .config files that are used to make the RH RPM kernels or do they just use default options?
Evolution: love it or leave it
Or they can build a monolithic kernel.
;-)
We don't need no stinking modules!
They that can give up essential liberty to obtain a little temporary safety deserve neither safety nor liberty.
Ben
www.sh.nu Which is linked from the site you mentioned.
Maybe for idiots (and trolls). Directly from kernel.org, no emphasis necessary:
Hasn't this been beaten to death, like decades ago? Seriously.
I 'fixed' eroaster just by adding a bash alias for
alias cdrecord="cdrecord -dev=ATAPI"
And SCO claims ownership of all 998 files.
[posting AC to avoid karma whore charges]
the 6 is an even number, hence it implies stable.
the 2.5 series was/is unstable until it matured into the current 2.6.x stable series, the next unstable kernel will be 2.7.x, etc etc.
adding an unstable anywhere in the name would be redundant
...when do you actually do stuff on your machine?
apart from upgrading and watching tentacle-porn I mean.
Um yes... let me second this. Just tried installing 2.6.1 (upgrading from 2.4.22) and ran into this problem. lsmod / insmod / modprobe etc were all giving some weird error. Had to apt-get install module-init-tools... suddenly it all worked.
It would be redundant only if you kept the odd/even versioning system. I am suggesting (starting from kernel 3 for simplicity):
3.0-unstable-0, 3.0-unstable-1 etc.
3.0-stable-0, 3.0-unstable-1 etc.
3.1-unstable-0 etc.
etc.
Using alternate numbers to indicate unstable kernels is a poor way of representing development versions IMO.
>>>>2.6.0 is now in Debian unstable...
.0 kernel releases all the time...
i just installed this on my debian box - and the kernel didnt boot on my computer. probably better idea to wait a while since this happens with
my blog
I find it very interesting that that we use three decimal points now for version numbers. I mean fractions of fractions come on. Yes I know im a troll because theres a reason for all this. But seriously what are we gonna have 10 years from now. Linus JR. just released the 5.8.9.3.4.7.0.0.2 version of Linux.
If I wanted easy I wouldnt be an engineer or a patriot.
Being on teh spoke. What's it like, is it good, or is it whack?
I would like to make clear I am drink right now.
Under 2.6.x, you simply type:
make (menu|g)config
make
make install
make modules_install
"make install" tries to figure out whether you're using LILO or GRUB and tell you what to do next, though it didn't quite work in my case since I never bothered setting up a boot menu (I just use the GRUB boot prompt). Another thing you should watch is that, by default, you can't remove modules from a running kernel. Be sure to check out the options for this.
Anyone else notice that you don't see the actual gcc commands anymore? Compiling Linux now looks eerily similar to compiling DJB's software.
Hopefully my HPT370 chipset will work under 2.6.1; it locks up 2.6.0 at boot unless I disable it in the BIOS (or don't compile in support for it). But it does "feel faster" than 2.4.x on the desktop, and ALSA and my nVidia card worked like a charm (thanks minion.de).
WMBC freeform/independent online radio.
In 2.4.x, I was able to mount my Sony DSC-S85 camera via USB under /dev/sda1, using USB mass storage and scsi.
This seems entirely broken in 2.6.0. Can someone clue me in on how to go about doing this now?
Thanks.
"Would it kill you to put down the toilet seat?" -- Maya Angelou
I JUST finished upgrading to 2.6.0 yesterday. I'm not kidding.
AFAIK, the SATA command set uses SCSI commands, not ATA, SATA is much more SCSI-over-serial than ATA-over-serial. The drives are ATA-like in quality, performance, and features, but the commands they respond to are SCSI-based in nature.
FireWire, USB, and ATAPI also implement SCSI commands, ATAPI implements SCSI commands -OVER- ATA wires.
What I'd like to see is an abstraction of the SCSI-over-[anything] idea, so new drivers are basically just cutting up an input stream for their respective mediums. ATA as a whole could be implemented as part of this, the drivers would just say that your ATA drive is a SCSI drive, on an ATA bus, with a command set capable of features X,Y, and Z. It would make it a lot easier to implement TCQ and other stuff on ATA drives, and pre-ordered queing on dirty write buffers for slower serial devices.
All storage should be based on the most capable and broad command set, with lower-level drivers disabling features (fom said command set) to their needs.
"Sometimes, I think Trent just needs a cup of hot chocolate and a blankie." -Tori Amos on Nine Inch Nails
I don't code, but I DO read code and spend a lot of time compiling stuff. The Linux Kernel is some of the cleanest and best-written looking code I've ever seen. Everything is concise and simple, the names of most things make sense, and the build process, even in 2.4, is pretty clean looking.
"Sometimes, I think Trent just needs a cup of hot chocolate and a blankie." -Tori Amos on Nine Inch Nails
You seem to be confused about the meaning of "stable". "Stable" means that the set of features is more or less fixed. It does not mean "bug-free" or even "well-tested". Likewise, "unstable" simply means that the features available are subject to change. "Unstable" says nothing about the presence of bugs. You can have a "stable" release that is completely untested, or an "unstable" release that's been tested for months before release.
Releases of stable kernels have nothing to do with releases of unstable kernels. If it helps you understand this better, consider the stable kernel a completely separate project, run by different people, than the unstable kernel.
Sure, Linux has all sorts of handy command-line autoget stuff. Butt! BUTT!! Windows has clicking!
And what do users want? We want clicking! More clicking! Give us a button to click after we type in 'emerge programname' and windows will totally be in trouble. Ph33r thy buttons!
- shazow
I mean, my cdrom drive is mounted from /devices/pci@1e,600000/ide@d/sd@0,0:c,raw.
Sigh.
THIS THING CAN TURN ON A DIME, MACROSSZERO STYLE ALSO FUCK BETA, ~NYORON
What does the bttv/v4l patch do?
-- Repeat with me: "There is no right to profits".
1) They include all hardware under the sun.
2) They assume you've applied about 50 patches to the stock kernel (some of them RedHat specific), so a lot of the stuff is going to be ignored, or could cause the make to fail.
THIS THING CAN TURN ON A DIME, MACROSSZERO STYLE ALSO FUCK BETA, ~NYORON
I've used to think of the kernel as some beast, full of black magic. Some of the parts dealing with broken hardware, are a little arcane. But the more I look at it, the more I see that most of it is just C.
;). To the most of us it might as well have been written in the tounge of Mordor. Though I hope the kernel is full of white magic instead, because the "one kernel to rule them all" doesn't really give me good associations. Once you wield the magic, it's not "magic" in that sense anymore, now is it?
In other words, it's black magic in C
Kjella
Live today, because you never know what tomorrow brings
That's not exactly fair. Although installing a kernel independently of a distro isn't easy, program installation in general is far, far easier than it is in MS Windows. In debian, you just type "apt-get programname". In Mandrake, you type "urpmi programname".
You mean to tell me that you honestly believe that for the majority of users, it is easier to live in a command prompt and type things like "urpmi programname" instead of getting a nice, professional Autostart program that lets you browse CD contents, run the program, install (with the ability to CHOOSE program locations and options!), stick itself on the Start menu for access, and uninstall itself correctly?
"Sufferin' succotash."
From the README:
Make sure you have gcc 2.95.3 available.
gcc 2.91.66 (egcs-1.1.2), and gcc 2.7.2.3 are known to miscompile some parts of the kernel, and are *no longer supported*.
Will gcc 3.2.2 suffice, or do I really have to go hunting for an ancient version of this compiler?
"Nine times out of ten, starting a fire is not the best way to solve the problem." - my wife
It depends on which distro you choose. Heavily modified kernels like RedHat's are a pain and probably will break at least a couple of your apps if you try to replace them with the latest stock from kernel.org.
I've been using Debian and upgrading all the way through 2.4 without any problems. I'd imagine Slackware or Gentoo to be the same. Can't say about Mandrake or SuSe.
I would advise that you skip RH9, though, and go straight to Fedora. It doesn't (yet) have a lot of changes vs. RH9; and, what changes there are, are mostly good ones (prelink, acpi, gnome 2.4). Welcome back!
"I assumed blithely that there were no elves out there in the darkness"
Have you tried Solitaire?
the mod facists are on they're usual
psycho rampage
I've checked for first time the 2.6.x series, and the first impression was a complete disappointment. Intensive I/O completely freezes the machine, and performance is awful. For example, a simple "dd if=/dev/zero of=verybig bs=1M count=300" took a minute and a half in 2.6.1 versus the 11 seconds in a 2.4.22...
I suppose that's not a normal behaviour, and it's caused by the CONFIG_PREEMPT option(I'm compiling again without it), but can anybody who follows the kernel development explain why is this option recommended for the desktop user if its results are so poor? (or why am I wrong and that's not the cause of the problems....)
The Games aren't loaded :-)!!!!
Anyone got any screenshots for this thing?
That man tried to kill mah Daddy
In Mandrake, you type "urpmi programname".
And now we see why Linux has so little marketshare. Who would want the slightest thing to do with a system that has commands like urpmi?
Who said anything about living "in a command prompt?" Yes, believe it or not sometimes it's easier to open a terminal window (horrors!) and type a single command to fetch, compile and install a software package than it is to futz around with a GUI "installer." And you're insane if you think that every piece of software written for Windows has a "nice, professional Autostart program..." or that it can correctly uninstall itself!
You really are a tool. You're so used to an inferior way of dealing with software that you can see no alternative.
Why aren't network devices given nodes under /dev? Nodes are alocated for PPP and ISDN devices but there is no /dev/ethX. What gives here?
The single biggest software maker in existence is IBM, not Microsoft. Don't bother quoting NASDAQ at me, it doesn't tell the whole story.
IBM don't issue Minesweeper Consultant and Solitaire Expert (MCSE) certs (except possibly when their janitors replace the empty rolls).
Got time? Spend some of it coding or testing
I'll be seeing him tomorrow morning. At an airport in Australia. Any guesses which one?
I can pass along any explict repentances, if you post them below this. (-:
I don't actually use LVM anywhere, so I haven't tested it, but on paper Mandrake 9.2 supports that.
Got time? Spend some of it coding or testing
Still no drivers for the WinBond memory stick reader, and I have yet to port the driver for my Minitar PCMCIA WLAN card, but otherwise neat and sweet. Burns DVDs over USB2 as fast as the Pioneer drive will spin them. Firewire fires. Video is reliable including in 3D but not up to gamer speeds. Worked as well on a rebuilt kernel as on a mint binary.
My wife's nForce2 (Athlon 2400) also goes well on the same kernel, but because the NVidia drivers are execrable in terms of reliability I jammed a Radeon into it, and it's now up to about three times as reliable as a Windows box. )-: About to try some major hardware swapping to find out where the remaining hardware bugs are. One of them was a Minitar PCI WLAN card, which is now working flawlessly in an K6-2/450 box.
Got time? Spend some of it coding or testing
Just use bochs or another VM.