Slashdot Mirror
Linux 2.6.27 Out
diegocgteleline.es writes "Linux 2.6.27 has been released. It adds a new filesystem (UBIFS) for 'pure' flash-based storage, the page-cache is now lockless, much improved Direct I/O scalability and performance, delayed allocation support for ext4, multiqueue networking, data integrity support in the block layer, a function tracer, a mmio tracer, sysprof support, improved webcam support, support for the Intel wifi 5000 series and RTL8187B network cards, a new ath9k driver for the Atheros AR5008 and AR9001 chipsets, more new drivers, and many other improvements and fixes. Full list of changes can be found here."
Well, yes and no. The old LK dev model had unstable releases where bugs were expected. Now every release is stable, and bugs are truly anomalies.
How we know is more important than what we know.
It's a shame this won't be in the upcoming Lenny release of Debian. The in-kernel support for heaps of webcams via gspca is a very nice user-visible element of this release.
Debian never paid much attention to desktop features, may I suggest Ubuntu 8.10?
Live today, because you never know what tomorrow brings
In only 3 months, all of this code has been completed and reviewed by multiple developers. This happens *every* three months. ... It is clearly the case that the Linux kernel has hit a new kind of critical mass and is now a form of software development that has never been seen before.
Intel HDA audio still has static noise in the left channel since at least 2.6.20 kernel (probably before). This is a known problem and the solution is 'try random settings of some undocumented (outside the kernel source code) module parameters and hope it maybe works'.
This is on Dell hardware. model=dell3stack, position_fix=1(?). This hardware works perfectly under Windows, with no tweaking whatsoever. It worked under older linux kernels, which means they probably broke something.
The linux kernel is good, but just having a bunch of people look at the code means nothing unless they are actually finding and fixing problems people care about.
Some do, some don't. It depends on the revision and particular model you're using. I'm on a Santa Rosa Macbook with Broadcom, but earlier revisions used Atheros.
I believe you have my stapler?
No, this one isn't red.
Live today, because you never know what tomorrow brings
I know this is going to get modded as "off topic", but let's cover this...
SYSTEM and Local System are basically one and the same, and are almost perfectly synonymous with root. Network Service would be the equivalent of the "nobody" user - i.e. an account that you can use to run low-privilege services. Administrator would be the same as a user with administrative privileges in Linux (perhaps someone in the sudoers list). The trouble, of course, was that, until Vista/2008 came along, it was trivially easy for an Administrator to escalate to SYSTEM - you just had to run a scheduled job in interactive mode (think of a cron job with no password required) and you'd not only have root access, you'd also have access to the current user's console. For an administrator, this came in handy - of course, what was handy and convenient for an administrator was just as handy and convenient for someone else.
Naturally upcoming Maemo (Nokia Internet Tablet) releases will feature ubifs, since much of the work on it has been done by Maemo Software kernel team.
My exception safety is -fno-exceptions.
For those moderators who didn't get it and modded him Troll: it's the (only) line from the Pink Floyd song "One of these Days".
By the way, it's "cut", not "chop": http://en.wikipedia.org/wiki/One_of_These_Days
Try out one of the wireless driver packages from http://linuxwireless.org/ (for hardy http://wireless.kernel.org/download/compat-wireless-2.6/compat-wireless-old.tar.bz2 ).
You will need to install your kernel source headers and the build environment
Then it's simply,
This will install the latest wireless drivers for your system and will not conflict with your distribution's package manager, should you want to remove the install and restore your previous drivers:
Make sure you are in the directory where the wireless driver installer is.
(It would probably be a good idea to reboot after that).
Normally I would never, ever recommend people compile stuff on Linux, however, in your case, it seems this would be the only way to get good support and this is really a last resort (a resort that you couldn't do under Windows if you ran into this problem).
Change is certain; progress is not obligatory.
I see your point, but consider the fact that every option (if you use "make menuconfig" at least) has a context-based help message. For the most part, they are actually very useful. Just go through all the options and think whether you need something or not. If you're not sure, there's a recommended safe default right at the end of the help message.
.config file (the one that stored your choices) and that's typically 10-20 options tops for new major versions.
And you really need to do this once. After that for each new version, you just do "make oldconfig" against the old
Changed hardware? New PC? Just reconfigure the "Drivers" section in a few minutes and you're golden. That's assuming of course you stripped down everything you don't need - if you left it in, you don't evenhave to do as much, it will just work.
BTW, if you're into tinkering, go all the way and try Gentoo. That project is alive and kicking, regardless of what the media have been saying recently.
To pick a random example from my collection of incompatible hardware, Microtek isn't helping the SANE project make drivers for its ScanMaker 4850 flatbed scanner.
That's OK. It looks like they're doing you a favor. If it makes you feel any better, they don't support Vista either.
Dewey, what part of this looks like authorities should be involved?