Slashdot Mirror
Linux 2.2.8
KrON writes "Linux 2.2.8 Is being upp'ed to mirrors as we speak...
" A few people have noted that a 2.3 directory
has appeared on some of the mirrors, although it is
empty.
← Back to Stories (view on slashdot.org)
← Back to Stories (view on slashdot.org)
I wasnt whining, i like having the latest kernel but its a pain in the ass when they come out every 2 weeks. There has been 8 kernels now since the end of january (aprox. 14 weeks) when 2.2.0 was released.
Actually, kernel headers come with the kernel.
ssh doesn't give you a login screen like that, non-foul-mouthed-gnulix-guy (is that an emacs mode?).
"this is not politcally parody, my.."
*hah*
There's no reason to upgrade minor releases just to get the higher version number. Unless there's some specific feature you need in 2.2.8, don't bother upgrading. I'm still running 2.0.36, and I probably will until something in the 2.2.x series seems worth upgrading for.
Speaking of ISDN not being included...
Would anyone out there be interested in getting
a working 2.2.8 + ISDN system going ? I've got
a 2.2.7 build that mostly works but I couldn't
pull up a second channel, which may only be a
config issue, pretty close and a little help from
others migh kick in something usable.
http://opensrc.org/isdn4oz/
mailto:markc@renta.net
hello can you say 'conflict of interest'?
the only way to have benchmarks that are trustwortyh
(hell benchmarks by themselves are hardly trustworthy)
is to have a group of total independents do it.
i fail to understand how supposedly mature
adults can think that a redhat sponsored benchmark
lab would not be seen as biased, let alone not actually be biased.
So what? I'm pretty sure more people reading /. are interested in new kernel releases than not.
So it doesn't harm to tell us about them in here. I probably wouldn't have noticed the release at all if it wasn't here
(I don't have time to read freshmeat and all those kernel related sites every day..)
Well, they have removed unnecessary code that made it slower, and tuned it for the common case. Also they added wak_up_on_one, which affects accept (waking up only a process that is waiting, not all. *think to 250 apache process :)*
ethertap seems to be broken in 2.2.8...?
it seems i cant get the kernel to see my modules installed... everything is in /lib/modules/2.2.8/
but even after a depmod -a it fails too see the new modules, am i doing something wrong?
insmod slhc
insmod ppp
everytime i reboot is damn i annoying, surely there must be a more automatic way? not loading it in bash.profile
(running rh6)
A changelog someone pointed to mentioned that you should not start update in your init scripts due to modifications in the buffer-flushing code. I tried starting with and without it--with it, update complained about not being able to do bdflushing and fell back to sync. Without it--well, no complaints and everything worked..and stuff is being buffered..but are there other ill effects that I have to take action to prevent (memory overuse..poor disk I/O..etc..) or am I home free?
Daniel
I had to reboot my NT Workstation at the office because the keyboard spontaneously stopped working.
Messing with the cables and drivers did nothing, but rebooting it fixed everything.
That's what "make menuconfig" is for.
You get all of the source by rpm or whatever, and then you select what you will actually compile in.
I meant for it to be used by the kernel developers, for plain and simple development and technical advance, not for use by marketroids.
Jelle.
Ok, name-calling anonymous coward, you had it coming. How many Apache developers do you think develop on Linux?
Maybe it's wiseguy-attitudes like yours that made apache in such need of accelerators like squid for static content.
I noticed that this time they actually made it to prepatch 7 which is a long way past most of the 2.2 kernels have been. Maybe I can actually get an uptime of more then 2 weeks now.
ftp.funet.fi and ftp.ca.kernel.org have 2.2.8 for you must-have-it-right-now-cant-wait-30-mins people
[root@localhost linux]# make
make: *** No rule to make target `include/linux/autoconf.h', needed by `include/config/MARKER'. Stop.
[root@localhost linux]#
at one stage it was compiling then it told me I didnt have 'as86' command (near the end of a make bzImage)...
fuck
as86 is part of the bin86 package (RedHat) ...
... for kernels you need kernel headers and some of the development packages. It isn't so hard to figure out if you try to understand the errors
you need a few basic things installed iwhen you try to compile stuff
There's an option to tie down the DMA buffer for an ISA bus soundcard so it doesn't swap. Gives me a major reduction in drive thrashing under gnome + Enlightenment.
Pop over to www.linuxhq.com. If they don't have a change summary up yet, there should be a link to the cutting edge linux site that usually has them.
...to discover that Linus has taken a patch you
sent out twelve hours before marked "please test"
and stuck it into the official kernel, without
saying a word.
Is USB supported? No.
But that doesn't mean it won't be. The code is out there, ready for nice people to test. Uncomment it from config.in and have a go at it, and be sure to check out the project info at the new Linux-usb web site.
Of course, after ESR's paper, marking a piece of open source code "please test" is equivalent to asking the author to have lots of people try it out. :)
You will see such updates and fixes in EVERY kernel release. What goads me is people who complain about just having downloaded 2.2.X and now 2.2.X+1 is out so now they have to download THAT. It all comes down to this: if there is a legitimate reason to upgrade the kernel, do so. If not and you have some fetish with running the latest kernel all the time, then don't complain about them being released so often. No one is making anyone upgrade and its nice that there is active development on the kernel. Like someone mentioned, we could have the Microsoft format - a monolithic service pack every few quarters or few years, with a bunch of hot fixes in between.
I believe the scheduler updates did make it.
There is a lot of new scheduler code in, certainly, and I remember all of the discussion about scheduler issues, but could someone please summarize exactly what they do? Is it just to handle high-load situations with a lot of processes (i.e. Apache), or does it fix a scheduler bug of some kind?
The funny thing is this probably won't affect the benchmarks at all. In the benchmarks, the web clients are all on fast LAN links, so they will quickly download the files and get on with the next request. In the real world your clients are on the other side of modems, ISDN connections and other bottlenecks like the Altantic and it takes them an appreciable time to get the data. So for a given bandwidth you have a lot more open connections ie a lot more Apache threads/processes. to get the data.
I wonder when there will be an Apache release that actually takes advantage of this.
Of course, you also need realistic benchmarks.
I haven't found a Changelog either, but I went through the diff and noted a lot of changes in the USB tree. You still can't pick it from the menu though (as far as I can tell).
Why waste your time getting the tarball and then doing a 'make config'. The mirrors are fast, but they aren't that fast (and I'm sure your typing isn't either). Get the patch and 'make oldconfig'.
You can do that if you're truly stupid. Sensible people will get bzip2'd patches rather than gzip'd tarballs.
First off, simply install the bin86 package to get round your second error. For a quick and painless kernel build:
/boot/vmlinuz-new /boot/System.map-new /etc/lilo.conf
make mrproper
make menuconfig
(fiddle with those options)
make dep
make clean
make bzImage
cp arch/architecture/boot/bzImage
cp System.map
vi
(add stanza for new kernel)
/sbin/lilo
reboot
Once everything is running Ok, then you can remove the RedHat kernel RPM's (kernel, kernel-pcmcia-cs, kernel-headers, etc) using --nodeps if necessary. Edit Do make clean in your Linux source directory to recover some space, and wait in anticipation for the next kernel patch ...
Chris Wareham
That is probably the best combination of having the latest kernel, and keeping uptime. I'm running 2.2.2 (with the bug/exploit/whatever that people are talking about), and having 70 days uptime now (the last time it went down was when somebody unplugged the power). But I will probably compile 2.2.8 (aka 2.3.0) any time soon, just in case...
/* Steinar */
(This comment is of course GPLed.)
Ya know that goofy little chimes sound Windows makes when it starts up? Well, you'll never guess the sound file I installed to replace it with... ;-)
Your Servant, B. Baggins
The include for drivers/usb/Config.in is commented out in arch/i386/config.in. Uncomment it, and USB will show up in menuconfig. It isn't even in the config.in for other platforms.
I still haven't gotten it running, tho, so YMMV. At boot time, it doesn't detect the USB keyboard. If you send SIGUSR1 to the uhci-control thread to dump some debugging info, it does detect the keyboard... but alas it still doesn't work.
-- Rob
--Rob
Could someone kindly point me to a changelog? I've looked and I can't seem to find one. :(
This sig is false.
ld -T arch/ppc/vmlinux.lds -Ttext 0xc0000000 -Bstatic arch/ppc/kernel/head.o init/main.o init/version.o \
/usr/src/linux-2.3.0/lib/lib.a \
--start-group \ arch/ppc/kernel/kernel.o arch/ppc/mm/mm.o arch/ppc/lib/lib.o kernel/kernel.o mm/mm.o fs/fs.o ipc/ipc.o \
fs/filesystems.a \
net/network.a \
drivers/block/block.a drivers/char/char.a drivers/misc/misc.a drivers/net/net.a drivers/scsi/scsi.a drivers/cdrom/cdrom.a drivers/sound/sound.a drivers/pci/pci.a drivers/macintosh/macintosh.a drivers/video/video.a \
--end-group \
-o vmlinux
arch/ppc/kernel/kernel.o: In function `sys_mmap':
arch/ppc/kernel/kernel.o(.text+0x4a38): undefined reference to `fget'
Now, man has references to fgetc, fgets, getc, getchar, gets, and ungetc, but there is no mention of 'fget'. Where does this come from? The code reference is apparently in syscalls.c as follows:
file = fget(fd);
where fd is an unsigned long in the function sys_mmap. Is there a simple answer here that I am missing? Where is the right place to ask such questions?
- Vincit qui patitur.
Here is the URL to the changelog
.
/proc virtual filesystem driver updates.
http://edge.linuxhq.com/changelist.cgi?show=2.2
And for those who are really lazy:
Notes: Due to the changes in this kernel's buffer code, you may want to disable the update (bdflush) daemon
in your init scripts.
Documentation updates.
3c527 net card driver added.
MTRR support added for Cyrix 6x86, Cyrix 6x86MX, Cyrix mII, AMD K6-2 (stepping 8 or higher)
and K6-3.
Netwinder Rockwell WaveArtist sound system driver added.
#PCMCIA NE2000 net card driver added.
Major Netwinder (ARM) architecture.
Alpha architecture updates.
ARM architecture updates.
x86 IRQ code updates.
x86 MCA support updates.
Cyrix 6x86 coma bug workaround added.
x86 SMP code updates.
Large m68k architecture updates.
MIPS architecture updates.
Major PowerPC architecture updates.
Macintosh architecture updates.
SPARC architecture updates.
SPARC64 architecture updates.
Minor IDE driver update.
Ramdisk driver updates.
Generic Non-IDE CD-ROM driver updates.
Lineprinter driver updates.
PlanB frame grabber driver added.
Cadet radio card driver updates.
Zoltrix radio card driver updates: Radio strength and stereo scans now use somewhat less CPU.
minor SpecialX multiport serial board driver updates: It appears that IO base and IRQ are now
configurable with module parameters.
act2000 ISDN driver updates.
Parport driver updates.
de4x5 net card driver updates: Workaround for buggy SROM in Motorola embedded boards, PCI/EISA
probing order changed.
Locking changes in various drivers: SCSI drivers, net card drivers.
Minor EQL net device driver update.
ethertap net card driver updates.
PPP driver updates.
WaveLAN net card driver updates.
IBM MCA SCSI driver updates.
MegaRAID SCSI driver updates.
Generic SCSI driver updates.
ad1816 sound driver updates.
ESS sound driver updates.
USB driver updates: OHCI-HCD and OHCI-HCD virtual root hub support added.
USB mouse driver updates.
Minor Matrox framebuffer console driver updates: CHRP and PReP fixes.
Framebuffer console drivers updated.
Minor ADFS filesystem driver update.
Minor AutoFS update.
Minor a.out binary loader updates.
Minor ELF binary loader updates.
Filesystem buffer code updates.
Disk quota code updates.
ext2 filesystem driver updates.
VFS updates.
Minix filesystem driver updates.
NFS filesystem driver updates.
Minor QNX4 filesystem driver update.
Minor SMB filesystem driver update.
Memory management code updates.
Scheduler updates.
Net code updates.
ipv4 updates.
Minor ipv6 updates.
IRDA drivers updated.
SunRPC updates.
Unix domain sockets code updated.
Minor MenuConfig update.
XConfig updates.
********************************************
Superstition is a word the ignorant use to describe their ignorance. -Sifu
You want people to stop whining because they don't NEED to upgrade? I'm ignorant.. I'll admit it. But when you look at the changelog and see things like:
ipv4 updates
Filesystem buffer code updates
Minor IDE driver update
Locking changes in various drivers: SCSI drivers..
... they seem pretty important when you look at them, don't they? Or is there a difference between an update and a fix?
Arg! I just finished going from 2.0.36 to 2.2.7 on my main server last night. (what a rush).
:)
Its real depressing when the frequency of reboots to an OS is dictated by the frequency of new features to it.
Though, I'd rather reboot my linux box every few weeks for an upgrade than reboot it for the same reason we reboot the NT server at work.
"Its recommended that NT be rebooted each week to flush out any crap that gets built up in it"... Hmmm, if I flushed NT any more, it would sound like a toliet.
I use to have a funny sig, but slash cut it off, and I forgot what the punchline was.
What's the point of dpkg'ing (or RPM'ing) a kernel? Aren't they MEANT to be customised for your computer? (Yes... i'm not talking about .src.rpm's :P
Isn't customised kernels one of linux's main advantages over the Win32 platform?
Rumors say that this is the first version in the 2.2.x series where some problems with the scheduler (that existed since the late 2.1.1xx kernels) are finally ironed out.
I'd like to see what difference this one makes on the 'dreaded' Quad PIII/Quad 100mbit/Hardware RAID/>1GB RAM configuration that is soo popular lately in MS-sponsored 'benchmarks'...
Btw: Who thinks like me that it may be time for one or more larger Linux organisation (like Linux International, RedHat labs, and/or Suse) to setup a high-performance benchmark lab that can be used for in-house benchmarking, and kernel development and optimization of Linux by our cutting-edge Linux developers (linus, alan, david, andrea, donald, stephen, andre, richard, rick, and the o-so many others, including the samba, apache, and squid guys).
--- Hindsight is 20/20, but walking backwards is not the answer.
So what's new in this one? I just upgraded to the last one.
Guess it's time to start 'ye olde compiler back up.
----
"War doesn't determine who's right, just who's left"
"War doesn't determine who's right, just who's left"
Steven Wright
On the Cutting Edge Linux page, it says to disable bdflush when installing the new kernel. Could someone explain exactly what this does, and why I have to disable it now?
For those of us who don't have the disk space needed to recompile the kernel, debs are nice.
I just compiled 2.2.8 not too long ago, and I don't recall seeing anything in "make menuconfig" related to USB. Kernel 2.2.7-ac4 had it, though.
I put some debs of the new kernel up at my ftp server. They don't have SCSI, SMP, or ISDN, but they've got most everything else.
Consider it as confirmation that someone else agrees that you had a good idea. If your patch was included unaltered, then they agree that you also phrased it correctly.
I saw a couple threads not long ago that there was a couple different USB efforts going on and that 2.2.7 had some code disabled.
I've looked (not very hard I'll admit) for a changelog or something to see whats in 2.2.8
from
cutting edge change listing
Simple USB driver added: You can't enable this option from the configuration yet. Maybe in 2.2.8.
but there is no changelog up yet for 2.2.8?
Im running 2.2.5 on my SuSE 6.1 system, which also has 2 iP2-350 processors. The SMP performance is actually quite nice and lacks nothing in comparison to NTs SMP support.
I cant wait, I still havn't gotten 2.2.7 to go.
On for 2.2.8
How is SMP support in these newer kernels?
I am about to put together a dual proc pent II
and I want to make sure I get a rock solid
SMP kernel on it. Would 2.2.8 be the
way to go? or would another rev be more appropriate? How is smp support in 2.2.5..the
one that comes with redhat 6.0?
Thanks.. Mike
You are correct, my delightfully anonymous friend! Once again the technological empowerment of others serves as my undoing! Foiled by an cowardly anonymizer!
...signed, the ever-lovable gnulix guy!
It's parody, not politics, my anonymously cowardly little friend! Don't hate me, I'm the ever-lovable gnulix guy!
...signed, the ever-lovable gnulix guy!
Is there anything IN these new kernels or am I just using them to keep my GCC from getting dust on it?
PDG--"I don't like the Prozac, the Prozac likes me"
"Where is my mind?"