New Testing Version Of Linux 2.6 327
Posted
by
michael
from the crashy-crashy dept.
from the crashy-crashy dept.
James A. A. Joyce writes "It's all up now at the kernel archives. Get the full 2.6.0-test2 or a patch, whichever suits you. We need to test those new kernels! Hop to it!"
New in 2.6 (Score:5, Informative)
In-kernel Module Loader and Unified parameter support: http://www.kernel.org/pub/linux/kernel/people/rus
Nanosecond Time Patch: http://www.ussg.iu.edu/hypermail/linux/kernel/021
Fbdev Rewrite: http://www.uwsg.iu.edu/hypermail/linux/kernel/011
Linux Trace Trollkit (LTT): http://www.uwsg.iu.edu/hypermail/linux/kernel/020
statfs64: http://marc.theaimsgroup.com/?l=linux-kernel&m=10
POSIX Timer API: http://marc.theaimsgroup.com/?l=linux-kernel&m=10
Shared Pagetable support: http://marc.theaimsgroup.com/?l=linux-kernel&m=10
Hotplug CPU Removal Support and Kernel Probes
Re:New in 2.6 (Score:5, Informative)
HERE YOU GO (Score:3, Informative)
And you're fired.
Re:I just installed FreeBSD (Score:3, Informative)
Re:Woo Hoo (Score:4, Informative)
Re:The AMD and Nvidia Issue (mem=nopentium) (Score:3, Informative)
Re:PowerPC? (Score:5, Informative)
Re:2.6.0-test1 was really boring (Score:5, Informative)
I have no information regarding running it on "stable".
Bruce
SPARC64 seems to work (Score:2, Informative)
One interesting note is that the sun/type5 keymap/keyboard settings for the console/XF86Config don't work anymore. Had to revert to the kernel keymap for the console, and xfree86/pc101 for X11. Also had to change
A minimum level of stability needed (Score:5, Informative)
For setups like me, I couldnt test Linux beta versions. The server is really not mission-critical but I believe 2.6 will keep crashing for me till version say 2.6.15 or something. I'll be trying to add my contributions to the community but not at such an alpha stage.
Re:I just installed FreeBSD (Score:5, Informative)
The Very Verbose Debian 3.0 Installation Walkthrough [osnews.com]
This will give you a minimal but extremely stable install. If you want newer stuff you can shift to "testing" or "unstable". Unless your are doing cutting edge stuff, this install is bulletproof!
Re:Question (Score:3, Informative)
Works under Debian Woody 3.0 (Score:2, Informative)
Actually you don't need this much... (Score:3, Informative)
You could use modutils and, say, gphoto2 [sourceforge.net] along with a script to do it for you.
Since there's likely a specific USB driver, just insert a post-install line (post-install drivername command ) and when you plug it in, the module handler will start things going for you.
Since you're the one writing the script (which doesn't really have to be more than a gphoto command telling it where to put the pictures), you can make it as robust as you like... for instance, set up a file with camera ID to username mappings, and drop stuff in ~user/.photos-incoming or something.
If it's a camera that Linux sees as USB storage, the same thing pretty much holds, but you'll have to just run cp and put them where you'd like... no need to compile gphoto.
To bring this back on topic, I can't wait to check out 2.6, but I'm still in the middle of configuring test1. ;-(
Re:do you see that! (Score:2, Informative)
A new kind of karma whoring... (Score:5, Informative)
Grab kernel 2.6.0-test2 via Bittorrent here [bandedartists.com]
Scheduler patch (Score:5, Informative)
Re:New in 2.6 (Score:3, Informative)
Being a LKML lurker, here are a few of the new features.
You need a test server. (Score:4, Informative)
Have a test server configured exactly (or as close as you can get) like your production server.
Always test new software on the test machine before putting it on the production machine.
This is important whether you're running Linux or Windows or whatever. Even when you're testing new versions or updates of apache or PHP or perl or postgresql or whatever.
Running untested (by you) code on production servers is guaranteed to bite you eventually.
Just save yourself the lost time and headaches and get a test box.
Your time and data are worth far more than the cost on a test box.
Thank you goes to... (Score:3, Informative)
FWIW, I read the kernel ML daily and I can say that the kernel team strongly desires end user feedback in the form of commentary and bug reports (not flames!)
They're looking for all the possible "oddball" cases (AKA "corner cases") and also for extreme loads such as huge files/filesystems, throughput, mem and net bandwidth, fs integrity, etc.
Regular users should participate; Linus has said that his focus is still on desktop usability and responsiveness. Anyone else who is interested should make sure to enable the -preempt option as well -- amazing performance!
Damn... now I need to try -test2.
Re:I have yet to get this working... (Score:5, Informative)
Re:Compiling It? (Score:2, Informative)
cd
make menuconfig
make bzImage modules modules_install
cp arc/[your arch]/boot/bzImage [appropriate place]
modify lilo/grub config, run lilo if required
get the new module-init-tools and install them (debian can apt-get them I believe, gentoo just emerge them)
reboot, enjoy.
Re:I have yet to get this working... (Score:5, Informative)
xosview problems? (Score:3, Informative)
bdonlan@bd-home-comp bdonlan $ gdb `which xosview`
GNU gdb 5.3
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu"...(no debugging symbols found)...
(gdb) run
Starting program:
(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...
[time passes...]
^C
Program received signal SIGINT, Interrupt.
0x4017af39 in std::basic_istream >& std::operator>> >(std::basic_istream >&, char*) () from
(gdb) bt
#0 0x4017af39 in std::basic_istream >& std::operator>> >(std::basic_istream >&, char*) () from
#1 0x0805d6fb in strcpy ()
#2 0x0805d195 in strcpy ()
#3 0x080561d4 in strcpy ()
#4 0x08054949 in strcpy ()
#5 0x08055a9a in strcpy ()
#6 0x402217a7 in __libc_start_main () from
top shows it comsuming a lot of cpu time while it's hung.
Re:2.6.0-test1 was really boring (Score:2, Informative)
Video is a little twitchy if you're running an ATI board and a KVM switch. (It wigs out on first switch.) Other than that, it's fast and rock solid. USB-2.0 works with an external drive.
I wrote 9 DVD's with it and copied 30 G's over to a usb drive without a problem. 4 of the 9 DVD's were backups from over a network.
Can't wait to throw test2 on the box.
Oh, one wierd clock error, but it didn't crash anything out.
Re:The AMD and Nvidia Issue (mem=nopentium) (Score:3, Informative)
Re:Changelog? (Score:2, Informative)
Re:Issues not disscussed in kernel documentation (Score:2, Informative)
Turns out that in the "Input Device Support" section, you must have "Input devices" compiled in. I had it set to module, and unfortunately that doesn't cut it.
Once you've set that, enter the "Character devices" section. At the top there will now be a "Virtual terminal" item which you can select. Once you've done that, you'll get the familiar scrolling of kernel messages.
I didn't get any compile errors, but then I went into the top level makefile (2.6.0-test1/Makefile) and changed all "gcc" and "g++" entries (3 total) to gcc-2.95/g++-2.95 which could account for something. You can also run "make V=1" to get the old, verbose output so you might get a better idea of what's causing the problem.
The dependencies thing I'm still working out myself. I suspect it's why the sound's not working yet.
In all, I'm quite pleased with 2.6.0-test1's performance on my system.
Cooper
Re:PowerPC? (Score:3, Informative)