Slashdot Mirror
Ask Slashdot: Upgrading Red Hat 5.2 to Linux 2.2.0
Daniel Roberts
wants to know about the following::
"I am running Red Hat 5.2, and I have been
trying to upgrade to 2.2 since pre1.
My problem is, I have read through the
"Changes" file very carefully, and
tried to upgrade all the needed packages...
But it still won't work. I am looking for
binary RPMs whenever I can, but even Raw
Hide does not seem to have all the needed
updates to make it work. In particular, I
cannot get libc5.4.46 to work, for some
reason, even though I've tried to install
the binary tar version. My question is:
what do I need to do to get Linux 2.2.0
working properly with a stock Red Hat 5.2
system??" Update: 02/12 03:02 by
C :
I've just discoveded information about
"Project Tango" which may be the answer
to this question. Thanks to
Palin for the heads up.
C :I was going to run this as another
story on this, but after rereading I figure it's
better if we add in this libc-5 issue from
davie,
who is in the process of a similar upgrade:
"I've built and installed libc-6 and it seems to be working fine. Now I need (at least according to the Changes text in the kernel source) to upgrade my libc-5. The problem is, I can't find any references on how to install a new build of libc-5 for compatability support only--I'm concerned that if I just 'configure, make, make install', I will break libc-6. I've looked at every FAQ and HOWTO I can find and there's nothing helpful. I looked at a libc-5 update RPM for RH 5.1, but I'm reluctant to guess where files go and which files need to be replaced. The libc-5 binary tarball includes fewer files than the update RPM, so I'm not sure what to do. Is there a doc online that explains how to build libc-5 and install it for compatability on a libc-6 box?"
Palin wrote in with this information...and a reliability question on the Tango Project, which looks to be the cure for this problem:
"Do you or anyone else in the Linux comunity know if the Tango Project's RPMs work? If you don't know what the Tango project is... It is a set of rpms for Redhat Linux 5.2 that provide all the necessary software (in RPM format) that one needs to install a 2.2.X kernel. I'd like to apply them...but was wondering what success others have had... The software can be found.... here and here. If it works I might be able to mirror it in the US...but I'm not going to try unless I know people have had success with it... "
"I've built and installed libc-6 and it seems to be working fine. Now I need (at least according to the Changes text in the kernel source) to upgrade my libc-5. The problem is, I can't find any references on how to install a new build of libc-5 for compatability support only--I'm concerned that if I just 'configure, make, make install', I will break libc-6. I've looked at every FAQ and HOWTO I can find and there's nothing helpful. I looked at a libc-5 update RPM for RH 5.1, but I'm reluctant to guess where files go and which files need to be replaced. The libc-5 binary tarball includes fewer files than the update RPM, so I'm not sure what to do. Is there a doc online that explains how to build libc-5 and install it for compatability on a libc-6 box?"
Palin wrote in with this information...and a reliability question on the Tango Project, which looks to be the cure for this problem:
"Do you or anyone else in the Linux comunity know if the Tango Project's RPMs work? If you don't know what the Tango project is... It is a set of rpms for Redhat Linux 5.2 that provide all the necessary software (in RPM format) that one needs to install a 2.2.X kernel. I'd like to apply them...but was wondering what success others have had... The software can be found.... here and here. If it works I might be able to mirror it in the US...but I'm not going to try unless I know people have had success with it... "
I'm running stock redhat 5.2 with the known updates and it works fine.
According to the Linux Distribution discussion that's been going on for the last couple days,
you need SuSE 6.0
Thppt
first,
i had no problems upgrading to 2.2 on my own homebrewed system.
i suggest recompiling all you binaries that rely on libc5 and link them to glibc2.x.
I have a 5.1 box and a 5.2 box, don't remember upgrading the libraries for anything major on them, I have 2.2.0 running on one and 2.2.1 on the other, all pre releases also worked fine.. Giev it a go and see what happens I say! (You have done that haven't you?...)
I successfully upgraded to the 2.2.1 kernel without upgrading libc5 from the version that came with Redhat 5.2.
Upgrading libc5 really doesn't matter if you compile all of you own apps, and not too many of the rpms in RedHat 5.2 are libc5.
Netscape is the only program that I use everyday that uses libc5. It crashes more often than before I upgraded to 2.2.1, but that's hardly enough to warrant not upgrading the kernel if you need new kernel features (like Soundblaster PCI support. Yay!)
Hi, you don't need to upgrade your libc at all. The one you have will work fine -- the kernel doesn't care.
RH 5.2 will pretty much work with 2.2 out of the box.. it did for me.. although I had to upgrade my DHCP utilities. Red Hat claimed they were 2.2 ready but this was not the case when I tried to use them. I had to get the tarball from the URL listed in the Changes file, and install that, worked fine afterwards.
If you have no use for DHCP then install the kernel, reboot, and enjoy
Kernel 2.2.1 is on rawhide.redhat.com in RPM format.
Other stuff that you have to upgrade:
util-linux
modutils
ipchains (if you used ipfwadm)
among others I can't seem to remember.
You need to format and install the latest version of Slackware. Slackware 3.5 all the way up through the current version includes all the necessary utilities to use the latest kernels. All I did was download the source, compile, and reboot.
And all you redhat users claim you're hardcore UNIX people. Bite me!
I have made some RPMs of the Linux kernel version 2.2.1
Email me if you want them.
ecarter@cs.arizona.edu
I'd think RH5.2 is 2.2 ready. I just did a fresh Slack 3.5 install, and dled and compled 2.2.1 and it worked just fine. (The 5 in 3.5 is bold because the latest Slack is 3.6)
I just grabbed 2.2.1, unpacked it, built it, copied bzImage over /boot, make and installed the modules, edited lilo.conf, ran lilo, and rebooted, and it was mostly happy.
The only thing that broke was the lm78 module I used to get the fan speed and temperature. I couldn't find the web site for the module I was using to see if there was a new one, so I found a different one, and that works.
Only after doing all this did I read the documentation and notice that I was supposed to update a couple of other things before updating the kernel.
In retrospect, I suppose this was rather reckless and foolish. Whenever Red Hat comes out with a kernel update, they usually come out with updates to at least SysVInit and initscripts, and warn of dire consequences if you don't update those, so I suppose I had no right to expect just throwing in a 2.2 kernel would work, but it did.
--Tim Smith
this might not help much, but i've got redhat 5.1 and made it to 2.2.1 with only a clean format and these upgrades:
-ld.so
-procinfo
-net-tools
-binutils
-dhcpcd
-modutils
i didn't upgrade libc5 or 6 and it worked just dandy. oh, and the second last one is only needed if you use dhcp.
I've been running the 2.2.1 kernel on a redhat 5.2 based system for days now... no problems. I just downloaded the source and compiled, that's it. Hmm what exactly have you done so far, other than just making sure your system was uh "upgraded [to] all necessary packages"?
BTW, don't bother with RPMs--they're really a waste. I find configuring and compiling is much easier (eg, just try to do a rpm install of enlightenment and gnome--almost impossible from a redhat 5.2 system despite what www.gnome.org tells you).
In any case, good luck... smile...
Lots of us have never "claimed" anything. Go bite yourself pal.
I'm running stock RH 5.2 with 2.2.0, no problems except XEmacs doesn't like running from the text console anymore (display is screwy.) Running it under X works fine, though. All other programs seem to work fine, too.
Debian has a superior package manager that will insist on upgrading all packages that DEPEND upon the selected package you are changing. I've been running the distro 'potato' all along and they change the packages per the requirements for me. What a concept!
I installed RH 5.2 w/ 2.0.36 kernel from CDROM , downloaded the latest kernel source from ftp.kernel.org, compiled a kernel, installed it, rebooted. That's all. I didn't need to upgrade anything to move to my current 2.2.1 kernel.
..I took a day or two looking at my RH 5.0 system. Most of the upgrades I should have had anyways. Biggest oops is ldd, make sure you check the version number on the library; ldd --version reported an incorrect version number. Read the "Moving up to 2.2" at linuxhq; especially Alan's stuff. DHCP/bootp will break for certain; sound broke for me because I wasn't used to using conf.modules. Plugging in the new version of dhcpcd will work under RH's "netcfg" util, and even works faster than the original RH5.0's version.
Scott Francis[Mechaman]
I get this error when I tried to compile the 2.2 kernel under redhat 5.2. Any sugestions. I tried to upgrade gcc and binutils and all the appropriate libraries, but I got the same error when I did a "make". I am getting very pissed at this! I had more crashes on my linux system than any other NT system I have used. Netscape also crashes xwindows and it sometimes says "buss error". What gives? Any one had these problems before? I need HELP!!
Criminy - if Netscape starts crashing more frequently, I may as well give up web browsing completely.
I guess do what all of the other people do when they post somewhere with questions like this.
Man, am I sick and tired of seeing these questions. Why is so special about redhat that requires all of these posts to say something like:
I am running redhat x.x and xyz does not work. Why can't it be something like:
I am currently running kernel 2.0.30 and want to upgrade to kernel 2.2.1 because everyone else is. I refuse to look at the documentation or other peoples posts and I will not read what you reply but I am going to ask anyway.
Install FreeBSD /usr/src
cvsup stable-supfile
cd
make world
recompile kernel
reboot
I read something about this, over on LWN for last Thursday. http://lwn.net/1999/0204/bigpage.phtml#kernel. It says that "the kernel now automatically adds a network route to an interface when it is configured. Thus a separate 'route' command is not necessary. Most systems have startup scripts which, not being 2.2-ready, do the 'route' command anyway, thus adding a redundant route to the tables. It is harmless, but aesthetically displeasing."
Hope that helps.
Would you people just STFU with your distro crap?
I just once would like to read something without seeing "redhat sucks" or "format and install slackware" or "redhat owns you! down with slack"
Its extremely childish and immature. You people are one step removed from the people that spam _usefull_ newsgroups with porn. You people need to be shot so those of us who dont give a fuck what everyone else is running can live out our lives in peace.
I have 3 differents ATAPI CDROM and no one runs at 2.2.1. I've tried UDMA patch, nothing!
When kernel boots display 5,6 times ATAPI RESET.
I can't even mount.
Alexandre tsialex@geocities.com#
There's nothing quite like one of these posts. Obviously, the person posting has no idea of what it's like to upgrade a RedHat 5.2 kernel with RPMs, having never done it, only read an in-depth and specific document that covers installation without using RPMs (which are available). If you actually LOOK at the documentation, there is no RedHat specific information, only a how-to-install-kernel doc. Consider those instructions --verbose. Obviously Vip put a lot of time in putting together an in depth description of "How To Install a Kernel" properly, and I thank him.
Are you a Troll or just a Distribution Snob (TM)? Frankly, people, it's Linux. If I choose to use RedHat, that doesn't make me a newbie, unaware of other dists, nor does Debian make me the all pure, snow white guru with the flowing beard. Frankly, if you prefer one distribution over another, do it for a VALID reason, such as you philosophically support Open Source only dists, or you find one technicially superior. Deriding one because of ignorance or a false sense of superiority is a sign of a small mind.
Disliking RedHat (or any other dist) because of ignorance or because its 'cool' to is like hating Microsoft because they are Microsoft, and it's cool to hate Microsoft. Hate Microsoft because they perform unfair business activities, because their OSes are unstable and undependable, that they try to kludge an metaphor (Start Menu) that was a kludge in the first place upon all their products whether it makes sense or not (Why do you need a Start Menu on a Handheld or a Sever?), that they spend more money on marketing than development and would rather market than innovate (and don't get me wrong, innovation is good, but NOT WHEN YOU COPY THE IDEAS FROM SOMEONE ELSE-- quick test, when was the last time Microsoft came out with an innovation that was copied, rather than the other way around?).
Remember:
1) Think Before You Type.
2) Just because someone disagrees with you, it doesn't mean that they are a moron.
3) You are free to run whatever Operating System, Distribution, Kernel, Window Manager, or audio player you want. So am I, and because you use it doesn't mean I have to or am wrong for running something else.
4) If someone's asking for help, that usually means that they are looking for help. Making snide comments about needing help or deriding other people's attempts to help is like spitting in an open wound or spitting in the eye of a doctor while operating. If you really can't find anything constructive to make yourself feel better about yourself and are forced to making uninformed comments on Slashdot (and as an Anon. Coward, no less) about people trying to help other people, then you seriously need help. Write code, or literature. Design graphics. Run a web page. Do something constructive. You're not helping anyone, least of all yourself, and Slashdot is not the forum.
5) Shift Key. It works. Try it sometime. You'll be amazed how much more intelligent your posts look.
-Ether
(too lazy to login)
http://www.linuxhq.com/lnxlists/linux-kernel/lk_99 01_04/msg00969.html
u /Tango/
But better use the mirrors...
As you connect to omni.rk.tusur.ru, it says:
"Our link to the world is 512kbit only, so transfer rate may be very slow
for you !
Project Tango now mirrored on in Russia :
ftp://ftp.balabanovo.ru/users/vlad/Tango/
ftp://hrgforce.org/pub/tango/
and in Australia :
ftp://ftp.gist.net.au/pub/mirrors/omni.rk.tusur.r
Try mirror first !"
hi.
could someone point me to new RH rpms to update the DHCP libraries or let me in on how to fix my DHCP with the 2.2.0 kernel? i can't seem to get it working.
thanks.
rediscovered@hotmail.com
Jeez...
If this is what is needed, RedHat products start to resemble those coming out of the black hole in Redmond, VA.
Am I ever so glad I use BSD...
Which DHCP distro did you get to work? There are at least two that are listed in the upgrade pages. I keep getting a signal (SIGXXIFORGETXXX) error and then it bombs on me. I have tried this under RH5.2 and Slackware upgraded to the 2.2.1 kernel to no avail.
I'm running boxed RH 5.2 but still cannot compile new kernels (2.2.0pre1 -->). I have read *carefully* "Changes"-file for about half-a-million times and updated all the software it recommends, but... No result, still facing trouble. Should try clean/everything install and compile everything in order? (but what's the order)
RedHat has /lib/modules/preferred set as a symlink
/etc/rc.d/rc.sysinit about half way down and you will see where it is used in the modules section. By removing this you will find using new releases of the kernel a lot easier.
/usr/src/linux/System.map to /boot may be a good idea ... (it gets rebuilt with each recompile of the kernel and hold the symbols in it).
Delete this begger and problems with modules just *go away*. As far as I can tell RH are trying to be a bit too clever by half with this.
Have a look in
Also, I don't know if anyone has mentioned it yet but copying
You aren't by chance using an AMD K6 are ya? Those chips (early ones) have a small flaw that causes GCC to screw up under heavy loads (like long intensive compiles -- i.e. the kernel) You can either compile on another box...or just keep typing make bzImage (thats what I did) and it keeps chugging along from where it last crashed (took about 4 tries).
--Bryan
bbatchel@stetson.edu
Compile your scsi card driver and scsi
support into the kernel .
(NOT as modules)
Works every time.
If your card needs args, add them to lilo.conf.
Also, I think there is an easier way to make
an initial ramdisk...
(Type "man mkinitrd" at $ prompt...)
Thanks for the info, though... Made me think.
Hi, I'm using rh5.0 with 2.2.1 without much problems (xfstt freaked out, dont know if it was because of the kernel upgrade). If you're having trouble finding the rpm's you need you should go to Rufus: http://rufus.w3.org/linux/RPM/
Can one (or better -both) of you shitheads tell me how to run Sybase on FreeBSD?
Btw. Did you guys use Amigas before changing to Unix?
-Me
- cd
/usr/src - ftp ftp.us.kernel.org
- get pub/linux/kernel/v2.2/linux-2.2.1.tar.gz
- tar xvfz linux-2.2.1.tar.gz
- cd
/usr/src/linux; make menuconfig - make dep; make zlilo; make modules; make modules_install
- Reboot.
Done!Worked the first time.
Red Hat is for illiterate dumb fucks.
Hm. I don't know about everyone else, but I installed RedHat right out of the box, I didn't even do a custom install, I let it do the workstation install. I didn't add much to it, except things that don't matter, like KDE, ssh, ircii, ssh, x11amp, real player, and word perfect 8. NOTHING else, and I went and got 2.2 final, and accidentally overwrote the source for 2.0.36 on my machine, (OOPS) but I ran menuconfig and compiled it no problem (Except for that sound thing, I had to apply the patch for that) But other than that it compiled fine and I put an entry in lilo, and am using it right now....
It is worth noting that the /sbin/mkinitrd command will make your initrd image for you, removing a shitload of the work, above.
/boot/initrd-2.2.1 2.2.1
/sbin/mkinitrd
Make sure you've already done a
make modules && make modules_install
See the man page for mkinitrd if you have any questions.
You guys are a hoot. You really made my morning.
Yeah, "Linux is ready to take over the desktop." "It isn't too hard." "My grandmother runs it." Well, granny may have a CS degree and is retired so she has nothing better to do but recompile kernels all day, and a lot of you are skipping your literature and art classes to get your systems running, but some of us have to do real work. If Linux is to have half a chance to enter the workplace, then things like RPM will have to work. All this nonsense about the great free technical support for Linux may be true as far as it goes, and works for those setting up servers, etc, who want to get their hands dirty. But telling a business user "well, first switch to Slackware or SUSE..." isn't going to cut it. These aren't stupid people, despite the many comments about "lusers". Their focus is different--they want to get work done. Upgrading Linux will have to be made easier if it wants to conquer the world.
---
But on the other hand, the early worm gets eaten.
'nuff said
It's people like you who are running FreeBSD because they can't handle a little infighting among distributions!
I had no problems installing gnome .99.3 and enlightenment DR.14 from RPMs on a RH5.2 over the past couple of days.
This generally shows some sort of hardware problem, generally memory (main or cache) problems, but there is a FAQ specifically on this topic. One location I found for it was http://www.bitwizard.nl/sig11/
I had this problem, and ended up having a bad SIMM.
Waiting for the next release from RedHat might benefit the none linux crowd who can't get a kernel upgrade to work. But for the rest of us who can figure it out, waiting is toooooooooo long, and upgrading is easier. Period!
That's really awfully complex. Maybe just take another distro that can handle libc6 and kernel 2.2 (currently SuSE 6.0).
I went to rpmfind.net and upgraded everything like
the changes file said... The only thing is now
the GNOME panel doesn't work, and a few apps
crash with seg faults. I think it is because of
glibc 2.0.110, but I'm not sure.
And does anyone know which package contains syslogd?
Version 4.5 (glibc) and Version 3.0 (from Word Perfect Package) Haven't given me any more trouble than I used before upgrading kernel.
Do you have any real reasons to use Linux other than "it's cool?"
I read some where that you DON'T want to upgrade the libc5 libraries. Anyway, the few of the libc5 programs that I use I haven't noticed any problems
ldd on one of them though shows it can't find libc5!
libc-5.3.12-28.i386.rpm
You and Linus, the TWO SOLE CREATORS OF LINUX,
the only 2 not RETARDED enough to be using a distro...
Eh well, I guess when you WROTE THE FUCKING THING
you have no need to get some LAME DISTRO LIKE REDHAT... I mean, you WROTE IT ALL YOURSELF...
you had it all looooooooooong before anyone was
LAME enough to start distributing it!!
While the rest of us have to start with the first
distro we can get our hands on, in the days before we have 24-hour internet access, and THEN use that distro as a STARTING-POINT to alter it to our own personal preference (like the vast entirety of OSS!), you and Linus just said, "Hell, I don't need to get a distro... I wrote the damn thing MYSELF!!!"
... which is, of course, why I respect you so...
you, as an original creator of our beloved OS, have a far more valid, informed and above all intelligent input into the DISCUSSION and COMPARISON of the various distributions than anyone else.
Thankyou for your time, Great One.
You don't need to upgrade libc5, it is included
in Redhat 5.x for compatibility reasons. Most/all
apps should be built for libc6 now, unless you
get binaries (which would really suck), then
you'd get messy issues. In that case, get a
statically linked libc5 binary.
Got it? RTFM, you only upgrade libc5 if your
system is based on it, i.e. Redhat 4.x
To all those Windows gloaters out there,
Just let us know when the last kernel update came out for Windows in any form!
Let's See, Windows 95, OSR1, Windows 98, NT 4.0...
Each has a slightly different kernel, but no major improvements. The new Linux 2.2 kernel is loaded with stuff and you could have tested it all along the way, while the 2.0.x kernels were awesome in their own way.
The Windows gloaters ought to be sick that they have been left for so long with poor kernel performance and no updates - rather than trying to blast Linux for it's perceived flaw - difficult updates...
Now, for the Linux impaired, can you run TWO kernels on your Windows box? No way - you can't even really control the one kernel you've got.
Later
Both of you suck. Slashdot is a giant flame war. You will never ever have an intelligent discussion here. I gave up on that a long time ago. Simply too many opinions to have that. So, it's a flame war. Post flame, and enjoy. I do. :)
And wow, I'm a Windows user? Fuck you. I have three systems on my desk: a Sun SPARCstation running a homebrew Linux distribution, a dual Pentium Pro running Slackware, and a Pentium 133 running Slackware. Tell me in that pile where Windows is you stupid fuck?
What? I don't think so. Redhat doesn't say "Oh, your trying to install xterm, so you need the xlibforms packages". No, Redhat says, "Oh, you need Xlib.so.1". Well, which Redhat package is that in? Well the majority of users aren't going to know. That's my point.
Debian does it as you need the xlibforms package to install your xterm package (not necessarily correct, but I am using this as an example). So, I go out and look for the xlibforms package, not having to figure out where the damn file Xlib.so.1 is. What a concept.
RedHat upgraded their 5.2 halfway through production, it seems, and did not say anything about it on the package. They also stopped including installation floppies in the middle of that run. It seems RedHat doesn't want it's users to know when they upgraded, and to what level. :/
Rion WulfeDid I get it?
(Sorry, slap me...)
I installed 2.2.1 on a Redhat 5.2 box without upgrading hardly anything. I, of course, have applied every rpm -Uvh in the 5.2 updates at redhat, and had to upgrade my pppd to 2.3.5. Other than that, I have had no problems and 2.2.1 works great and much better than the 2.0.36 pre kernel that 5.2 ships with.
Lemme see...
ALL the pc's at work run slackware and KDE
I formatted and eradicated the last NT4.0 server yesterday.
We now have control back of the computers, all the pirated software from the users is gone forever.
People cant screw up their destops anymore (except for the contents of the directories the config files re-write themselves upon log out.
I control what they see, do, access, run, eat, sleep.
I can at will remove net access for services like http,irc etc without killing email and intra-net stuff at my admin station.
and productivity has increased 90%
Yup you're right.. Linux isnt ready for business or the desktop, it takes an IT department that has 1/10th of a brain to run it. Unlike the MSCE idiots we had to let go... heheheheh Bye bye MSCE morons!
WAHHHHHHHHHHHHHHHHHHHHHH! :-) :-)
It's another works for me message!!!
WAHHHHHHHHHHHHHHHHHHHHHH!
BTW, it did work for me
and pretty damn cool too, now I run 8 percent slower!
I love how speedy my 1.2x kernel machine is screaming along
MORAL? dont upgrade unless you need it! there is no coolness in running the latest and greatest if you dont use it!
If you have a Red Hat 5.2, then you are ready for 2.2.x, even if you don't know that ;)
I run an Intel Red Hat 5.2 all the day at work, and i upgraded it to 2.2.0 about 10 days ago. It works perfectly. No problem encountered at all!
I had a problem compiling 2.2.1 in which gcc did a call to the assembler withthe files checksum.o and checksum.h. I had just upgraded to the latest binutils and I wonder if this had something to do with it. Here is the error: :200 "redefinition of 'csum-partial.copy allready defined
checksum.c
checksum.c:105: 'csum-partial_copy'previously defined here.
{Standard input}: Assembler messages:
{Standard input}:108:Fatal Error:Symbol csum allready defined
I current have the latest version of the binutils and I have kernel 2.0.34 and caldera 1.2
Red Hat has their special way of identifying kernel with modules. After make [b]zImage and /proc/version", but this means that you have to boot the new kernel up and have it complain about wrong module version. My trick of getting the version of the newly built kernel is to look for it in the _uncompressed_ kernel image. This is not fool-proof, but my command is, assuming that my hostname is "myhostname", and I have just rebuilt the latest 2.0.36 kernel modules:
/lib/modules/2.0.36
.rhkmvtag file a hidden file, thus creating all this wrong module version problem. .rhkmvtag hidden, "rhkmvtag" would have served the same purpose and not trip everyone up because a
make modules_install, you have to create a
/lib/modules/whatever/.rhkmvtag file that
contains the version of the newly built kernel.
You can get the version of the _running_ kernel
with "cat
strings -a vmunix | grep myhostname > \
/lib/modules/2.0.36/.rhkmvtag
After that you can rename
to whatever you want, and the Red Hat init
script will find the correct module directory
and make the "preferred ->" symlink.
The advantage is that you will always have a
matching kernel module directory with the
booted kernel, no matter how many kernels
you have.
The disadvantage is why the hell did Red Hat
make the
I see no reason at all to make the
decent sys admin would have noticed that non-standard file and said "eh?", and would have discovered the Red Hat Way after a little investigation. Ah well...
Cheers!
Red Hat has their special way of identifying kernel with modules. After make [b]zImage and /proc/version", but this means that you have to boot the new kernel up and have it complain about wrong module version. My trick of getting the version of the newly built kernel is to look for it in the _uncompressed_ kernel image. This is not fool-proof, but my command is, assuming that my hostname is "myhostname", and I have just rebuilt the latest 2.0.36 kernel modules:
/lib/modules/2.0.36
.rhkmvtag file a hidden file, thus creating all this wrong module version problem. .rhkmvtag hidden, "rhkmvtag" would have served the same purpose and not trip everyone up because a
make modules_install, you have to create a
/lib/modules/whatever/.rhkmvtag file that
contains the version of the newly built kernel.
You can get the version of the _running_ kernel
with "cat
strings -a vmunix | grep myhostname > \
/lib/modules/2.0.36/.rhkmvtag
After that you can rename
to whatever you want, and the Red Hat init
script will find the correct module directory
and make the "preferred ->" symlink.
The advantage is that you will always have a
matching kernel module directory with the
booted kernel, no matter how many kernels
you have.
The disadvantage is why the hell did Red Hat
make the
I see no reason at all to make the
decent sys admin would have noticed that non-standard file and said "eh?", and would have discovered the Red Hat Way after a little investigation. Ah well...
Cheers!
Red Hat associates kernel and modules with a /lib/modules/xxxxxxx/.rhkmvtag file. This file contains the kernel version info. Kernel version can be obtained by "cat /proc/version" of a running kernel, or looked for in the _uncompressed_ kernel image, usually /usr/src/linux/vmunix if you built it there.
.rhkmvtag file.
Use "strings -a vmunix" and grep for your hostname or something like that, and stick that info in the
I think this is a nice idea, but I wished that Red Hat had not used a hidden file. A non hidden file would have served the same purpose without tripping users up unduly.
Cheers!
I had virtually no problems at all with the upgraded kernel. My ppp dialer is flakey now, just hangs after about a week. Probably need to recompile latest version. Other than that, no probs.
Grab ftp://ftp.phystech.com/pub/dhcpcd-1.3.17-pl2.tar.g z
compile and install (keeping a backup of the old dhcpcd, of course)
Worked for me, though I had to scroung around for a net/ethernet.h for my RH 4.2
-Philip
I have Red Hat 4.2. I read Documentation/Changes slowly, carefully 2 times. It took me the best part of a day, but I now have 2.2.1 working on this computer.
Does this make me a "hardcore UNIX" person, or do I have to develope the attitude of an ass-hole first?
-Philip
Gosh, if you can compile a kernel, you must be a Real Man(tm). That's sooo hard to do. Especially for us lowly Red Hat users, like Linus Torvalds. Now *there's* a guy who's definitely not a "hardcore UNIX" person. Unlike yourself, of course.
I used 4.5, and had a few problems after upgrading. But then I discovered the 'unsupported' glibc version, and it seems to be a great improvement.
He or she is probably implying the use of RPMs to do the upgrade.
If one only uses RPMs, it makes it much easier to maintain/upgrade the system.
Sure, its fun to get source and compile packages or the kernel from time to time, but not everyone has the time to mess with that stuff.
If thats all you did, you're not finished!
You can find all you need at.
ftp://ftp.sslug.dk/pub/rpm/kernel-2.2-updates/
I was using a stock Red Hat 5.2 system, and I didn't think about upgrading any software. The only things I have encountered so far are the use of ipchains for IP masquerading, and the open.so library needed for RealPlayer.
You have to make sure that you have cleaned out your /usr/src/linux link...it is a link to your kernel source tree. I just delete it, untar the new kernel, rename the directory to the appropriate kernel name and re-create the link. I am pretty sure those sig 11 problems people are having are due to them simply overwriting their existing 2.0.x kernel.
ttyl
Farrell
CAN-CON 2019 - Ottawa's only book oriented Science Fiction Convention! October 18-20, Sheraton Hotel, Ottawa, Canada h
I origionally had a RH5.1 system and upgraded to 5.2. I keep my kernels up-to-date... was running Linux2.0.36 on 5.1.
:) Needless to say, I ain't even THOUGHT about going back to 2.0.36, I've considered getting myself a multiprocessor box.
After the 2.2 kernel was declared stable, I downloaded the source, read the readme's, downloaded the packages it said I had to upgrade, and began planning.
On a lark, I decided to configure and try to compile the 2.2.0 kernel without adding all the other stuff. IT WORKED FINE!
I now use the framebuffer and it works fine. My virtual terminals in KDE, under 1280x1024x16 hi-res backgrounds, switch twice as fast as they did under 2.0.36. Everything is snappier and the video looks alot more smooth. Sound works like a champ. x11amp is broke so I use freeamp.
What can I say? Linus and the Kernel Crew did a fine job! That's what.
Codifex Maximus ~ In search of... a shorter sig.
Posted by Aur0ran:
I have had problems too. Upgrading everything except libc6 was pretty easy, and I was able to compile and install the kernel fine. However, the new dhcp client from ISC (www.isc.org) requires libc6 (glibc2) to compile. I'm able to get it compiled and then installed, and even edited the specs file ala advice from the Glibc2-HOWTO, but ldd still reports that my binaries are compiled with libc5.4.46. So, I gave up and reverted back to 2.0.36 where my netaccess worked. Any ideas?
I'm using 5.1, and the only changes I made were the upgrade of net-tools and modutils. 2.2.1 is running smoothly so far.
"Pray arm me further by your reply" Winston Churchill
I got the necessary SRPMs (based on the update info at www.linuxhq.com) from rawhide and
rebuilt them with rpm --rebuild. I think there may have been one or two things that I got from contrib, too.
Check http://www-stu.calvin.edu/~clug/users/jnieho38/got o22.html for the list of packages; I upgraded a 5.1 system based on this and it worked fine.
You'll need to change your networking scripts a bit, though.
--
I've had TONS of problems with SuSE 6.0... First off, it was a 2 gig download... Networking was broken and still isn't totally right. I can't compile anything. Lots of window managers, enlightenment works, gnome seems to work. Lots of other good stuff too, but kinda buggy.
Uh-huh. Linux is not about memorizing a twenty step installation procedure. Here's mine:
make xconfig
make dep; make clean;
make; make modules;
make zdisk; make modules-install
reboot
I have used 2.1 kernels with near stock 5.1. (I needed to update ppp and a few other util files) and 2.2 kernels with stock 5.2.
Use the resources you have available to you.
g oto22.html
_ 9901_04/msg00969.html
Specifically these two links from there:
A complete upgrade guide, with a list of required versions/packages and where you can get them.
http://www-stu.calvin.edu/~clug/users/jnieho38/
A mail message from Vladimir V. Ivanov on the linux-kernel list. This one has a link to a page/ftp site with everything you need to upgrade rh5.2 to 2.2.0
http://www.linuxhq.com/lnxlists/linux-kernel/lk
"No nation could preserve its freedom in the midst of continual warfare."
--James Madison
As long as you have the latest glibc-2.0.x, you should be fine. glibc-2.1 will give you ptmx support, etc., but it may also break other things.
Use a stock dist. and all of the updates from "ftp://updates.redhat.com/5.2/" for your architecture.
With 2.1.??? and 2.2.x kernels, bringing up an interface automatically adds its routes. Comment out the following lines from '/etc/sysconfig/network-scripts/ifup':
'bootpc' doesn't seem to work on my Multia's on a "down" interface. My workaround has been to build a kernel w/bootp support and not bring the interface down before using 'bootpc'.
There's a bunch. Can't think of it right now (construction workers just started up the jackhammer right outside my window). Please feel free to add.
/* MAGIC THEATRE
ENTRANCE NOT FOR EVERYBODY
MADMEN ONLY */
Always expect stuff NOT to work when you use binaries.. especially if you are getting them from rawhide, they are linked with new and different libraries old redhat's dont have! what to do? compile it yourself. its not hard! say it with me! ./configure ; make ; make install
phew. that was hard.
I've found that after I updated all the RPM's from their website that I had everything already in place for 2.2. The only thing that needed to be updated was modutils and the kernel (I believe the modutils package should be 2.1.121 but check with LinuxHQ to be sure) I then grabbed the full source for kernel 2.2.1 and the modutils full source extracted them and then compiled them. It worked for me.
Nullhero
Save Pangaea!! Stop Continental Drift!!
In your situation, you're going to have to get your hands dirty and compile some sourcecode. Binaries do not always work as they were compiled to a given system situation- which includes a given kernel version.
As an example, the binaries for pppd that shipped with Red Hat 5.0 and 5.1 will not work in any way, shape or form, with the 2.2.X kernel- there's been quite a few changes that render the daemon inoperable, unless you use the sourcecode from the latest version or use the binary version installed with Red Hat 5.2.
If Red Hat didn't ship the latest binary version of libc with 5.2 (which, since libc's depreciated, I'm pretty sure they haven't) then you need to obtain the source and attempt to compile it as it's your only recourse- at least as long as nobody else works on the problem.
I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas
Has anyone tried this on a Sparc machine... I really want to upgrade my Kernel on my Sparc to 2.2.1 however I keep seeing things about DHCP not working ... I have both DHCPd and DHCPcd running on the machine and do not want to lose this functionality (router for my home net to cablemodem) Thanks for any info....
Of all the things I miss
that Documentation/Changes note about libc5 i understand as: if you have libc5, upgrade libc5, if you have glibc2, upgrade glibc2
i think that's all; i'm running 2.2.0 since pre6 (now 2.2.1) and i have glibc-2.0.109-0.990112 (previously glibc-2.0.7-29) and i encounter no problem (relating to kernel and glibc)
hany
You can also read the Changes file that comes with 2.2.1 ... in it are instructions to fix Realplayer without downloading anything.
-- Rick
I can't compile 2.2.1 on my RH 5.2 system. I have had various "can't redefine" error messages ( I can change which ones I get by changing the config) such as
make[2]: Entering directory `/usr/src/linux/arch/i386/lib'
gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -pipe -fno-strength-reduce -m486 -malign-loops=2 -malign-jumps=2 -malign-functions=2 -DCPU=686 -c -o checksum.o checksum.c
checksum.c:200: redefinition of `csum_partial_copy'
checksum.c:105: `csum_partial_copy' previously defined here
{standard input}: Assembler messages:
{standard input}:188: Fatal error: Symbol csum_partial_copy already defined.
make[2]: *** [checksum.o] Error 1
make[2]: Leaving directory `/usr/src/linux/arch/i386/lib'
make[1]: *** [first_rule] Error 2
make[1]: Leaving directory `/usr/src/linux/arch/i386/lib'
make: *** [_dir_arch/i386/lib] Error 2
Does anyone know what I am doing wrong?
Steve
LOL. Uh, no. Some of us are using RH just because it's the last disto we installed. I'm thinking very seriously about debian (again) or slackware (again,) even though this will cause a bit of trouble for my wife and kids, while I transition. You really should not lump people together. :)
Redhat has gotten better (first tried 4.x, IIRC,) but it's inconsitencies with the rest of the world can still be mind-numbing at times.
Does it even support libc6 without fscking around compiling crap yet?
It didn't. One reason I installed RH. It has glibc now, though. And compiling stuff is all part of the environment. If you don't want to do any compiling, what are you doing using Linux. m-a-k-e is not that damn hard.
Slackware also lacked sysv init support which makes the startup scripts absolutely horrible.
Agreed. I prefer sysv. Wondering if Slack changed that, myself.
But then, how do you add an item to your Afterstep menu in RH (Don't give me the answer... I know how.) Add it globaly, and you have to restart X (not normal.) Add it to the user, and it goes away next time they start X. After figuring it out, I didn't find anything anywhere on how to do it for a good 3 months. That's a big fat inconsitency. And RedHat is full of 'em.
When it all comes down to it, they are all Linux, though. That was the point of my post. A distro is a stupid thing to fight over. They all have good and bad points.
I did the upgrade, and everything works fine, however i have a network card that uses the ne2000 pci drivers, and when i display the routing information, the card always seem to show up twice. I have tried it as both a module and built in, no difference. It works fine, but its just something that bugs me. I am not sure if it is a bug, or if some package need to be updated, but i haven't heard anyone complain about it as yet, so i guess it may be a problem on my side and not with the actuall code...
Its spelt "L-I-N-U-X", but pronunced as "Free Beer"
Get shlibs5.rpm from SuSE 6.0 and install. It works great with RH! Upgrades ld.so to 1.9.9 and libc5 to 5.4.46. Many other extras too. Bulletproof. Intalls in same directory as RH. /usr/i486-linux-libc5/lib first though. As previously posted RH does not need this for the 2.2 kernels but it does strenghten the libc5 support.
Would be wise to remove the files in
-- Ted tsikora@powerusersbbs.com
Take a look at Project Tango:
_ 9901_04/msg00969.html
http://www.linuxhq.com/lnxlists/linux-kernel/lk
Peace and love, y'all
one of my machines is running minimal 5.2, had no problem downloading the kernel sources and installing.
- MbM
- MbM
I compiled my 2.2.1 kernel on the home system,
which is sort of a hybrid, but started with Slack
many years ago. It has since undergone upgrades
to RH 4.1, 4.2, 5.0, 5.1, and 5.2. I have used
this kernel on a fresh 5.2 install and a 4.2
install, both production systems. On all systems,
all I really had to upgrade was modutils and
net-tools, as per kernel documentation.
If you are having trouble compiling and/or using
2.2.1, I would guess you have some hardware
issues.
Miles Lott
I've been using 2.2.1ac1 for a while now with now major problems... the only thing I remember having to upgrade was mu DHCP, otherwise it is mostly 5.2 apps and utilities. I wish I could be of more help. I had to use the patch initially because I was building sound into the kernel, but otherwise, I can't think of anything that would prevent you from installing and using the newer kernel.
Just used the following to compile...
make clean && make deps && make zImage && make modules && make modules_install && make install
Hope you have success.
Baggio
Time flies like an arrow;
Time flies like an arrow;
Fruit flies like a bananna
I upgraded to 2.2.0 (and 2.2.1 since) on 2 seperate RH 5.1 machines with 0 problems. It was just like tracking kernel releases always was with either 2.x tree; download kerenl, remove linux symlink, untar in /usr/src, rename to linux-2.x.x, symlink linux over to it, then the standard makes (menuconfig,depend,zImage,modules,install,modules_ install) and away I went.
I don't see where RH5.2 is any different, it's based on the same glibc and (incremental releases aside) same compilers. It seems very strange that 5.2 would give problems where 5.1 didn't...
Upgrading the kernel is not going to make your life immediately better. Constantly upgrading software, getting the latest sources, recompiling, recompiling, recompiling...all of this is quite interesting if you don't have anything to do with your time. You aren't going to notice any real differences. Just wait and RH will release all this crap on their next CD and you can take five minutes to upgrade painlessly instead of two hours. All of this obsessive upgrading is imply going to make you frustrated in the long run with no clear benefit.
I rather like RPM's "--nodeps" argument to allow me to upgrade (by way of local build) libraries and such while keeping other RPM-installed software that depends on said libraries.
I don't know about Debian's system, so I won't comment on it, but I don't think that a system "that will insist on upgrading all packages that DEPEND upon the selected package you are changing" is really superior--eek.
-rozzin.
Well, there were something peculiar about
the 2.2.1.
Although the intranet can be reached, but
the internet cannot be reached. So, what I
know is that at least my network card works.
Another problem is that X term from the
XFree 3.3.3 ( binary distribution ) doesn't
work. Even my WindowMaker can't invoke any program
using the menu.
I think the 2.2.1 should work correctly but I can't figure out why it can't.
Overall it wasn't that difficult, just some annoyances and tips
/usr/src" and do a "ls -l". You should see something like:
:-) If it is an actual
:-)
/dev/sda5.
:-) /boot/initrd-2.0.36-0.7.img" in there?
/boot" and "ls *.img". :-)
/dev/ram 1500" Why 1500? If you look
/dev/ram /mnt"
/mnt" You should see /lib/aic7xxx.o" means it needs aic7xxx.o)
/dev/ram" (or /mnt) and run dd again with:
/boot with /boot/initrd-2.2.0.img" Note the missing
:-)
/etc and cat your lilo.conf. Write down all
/usr/src/linux link to /usr/src" "rm linux"
to get by that aren't documented anywhere.
This is VERY long, and probably missing a few steps, but this
is what I remember doing. It took about 4 or 5 hours to solve.
If you don't care about, don't like, don't want, this, then
stop reading and delete this message.
When I looked about, and asked about, I've been trying to figure
out how to add new kernels for a couple of months now without any
success, people generally said, "I've never seen that!" "It's
not supposed to be like that!" "Please stop abusing my warez
site!" and so on. The errors were stuff like "kernel-module
mismatch" and "Cannot open root device."
First, download the new kernel from ftp.ca.kernel.org or wherever
else you want.
"cd
lrwxrwxrwx 1 root root 11 Jan 26 23:57 linux -> linux-2.2.0
drwxr-xr-x 14 root root 1024 Jan 10 16:04 linux-2.0.34
drwxr-xr-x 17 root root 1024 Jan 26 23:55 linux-2.0.36
drwxr-xr-x 15 1046 1046 1024 Jan 26 16:10 linux-2.2.0
drwxr-xr-x 7 root root 1024 Oct 14 16:05 redhat
Of course, the first line, linux will point to 2.0.34 or 36. This
link may or may not be there, it does seem to vary, I don't know
why. If it's there, "rm linux".
directory, "mv linux linux-".
Now uncompress and untar the kernel sources, this creates a tree
with the name "linux". Now "mv linux linux-2.2.0". And finally
re-create the ORIGINAL link using "ln -s linux-2.0.36 linux".
That's just in case things go horribly wrong, you still have your
old source trees, otherwise they would be overwritten.
Now "cd linux-2.2.0" and do the general configuration. One easy
way to get started is to go into the old version of kernel
source you have, and type "make menuconfig", then select
"Save Configuration to an Alternate File". Save it to "blah"
and copy the file to the new source tree (linux-2.2.0). In
the new source tree, do another "make menuconfig" and
"Load an Alternate Configuration File" and select "blah".
This should keep most of your settings from the old sources.
If it doesn't...heh, life's tough, eh? Start from scratch.
Now go through the rest of it, and ensure everything seems ok,
and you might want stuff like joystick support, and the
"Magic SysRq key". This one allows you to press Alt+PrtScrn
to get to debug if something goes horribly wrong with
Linux. You can sync your filesystems and stuff with it.
It's under "Kernel hacking".
One other thing to check is the "Processor Type and features".
Make sure it is set to your processor, which will most likely
be "586/K5/5x86/6x86 Processor family". If it's not, change
it.
Anyways, finish your config, and then do the normal
"make dep ; make clean ; make bzImage ; make modules ; make
modules_install" Note the bzImage, mainly because images do
seem to be larger than 1MB. It won't matter at boot time.
Once you are done, you will have a fresh kernel, assuming
nothing went wrong during the compile. I haven't seen it
fail for a long time, has anyone else?
Your kernel will be "/usr/src/linux-2.2.0/arch/i386/boot/bzImage"
Now you want to install your new kernel. In RedHat it's
reasonably simple, via the "linuxconf" utility. It brings
up a GUI screen, and a ways down the page, you find stuff
about LILO. You can start with "LILO defaults" and work
your way down, it has some stuff you might want to see...or not.
Go to the one that says "a kernel you have compiled", and fill
in the info. Kernel image file is the one above. Label it
"linux-2.2.0". If you want to take a chance, you can select
it as "new default", but if you don't want to "selectable"
is just as good. And please don't select "replace". That's bad.
Where to copy is "/boot/vmlinuz-2.2.0". The root partition
is just that, what device is your root? Mine was
You can find that under "Lilo linux configurations" and
the "Partition" column, with your current kernel listed.
At the bottom is "Initial ramdisk". How many have this setup?
I don't know. Some I talked to did, others didn't. None of
them knew how to set one up. So I fudged one out.
How do you tell? In "/etc/lilo.conf", do you see a line
similar to "initrd =
If so, you have an initial ramdisk!
The reason I had to do this was because when I booted, it
would complain that I was using kernel version 2.0.36 and
the modules to be used during boot were from 2.0.34. (change
the versions as you want, I fought this one for a long time,
same error, different numbers) The boot would just stop at that point.
If you do have one, read on. Otherwise you are all set. Accept
the changes, run "lilo" from the command line, and go check your
lilo.conf. Write down the "label" lines, and what version they
boot. You will need this if the boot fails. More on that later.
You can skip down a bit if you don't need to create a RAMdisk...
To setup the ramdisk, the easiest way is to "cd
Remember above when you pulled out the initrd line? That file
should be in there. Copy this file somewhere, preferably not somewhere
where it will be deleted during boot.
Now goto where it was copied, and do the following, carefully.
The file you copied is compressed. "mv initrd-foo.img initrd-foo.img.gz"
then "gunzip initrd-foo.img.gz". You now have an uncompressed image
file.
Make a RAMdisk. "mke2fs -m0
at the image file size, it should be 1.5MB in size. You can
adjust accordingly.
Now copy the contents of the file into the RAMdisk.
"dd if=initrd-foo.img bs=1k count=1500 of=/dev/ram"
Now mount the RAMdisk.
"mount
Now make the required changes. "cd
a file called "linuxrc". cat it out, and it will list the
modules required to load initially in order to find disks.
(eg. "insmod
Go into "/mnt/lib" and "ls -l" and I find the file "aic7xxx.o"
I want the current one, for my new kernel, so I can find it at
"/lib/modules/2.2.0/scsi/aic7xxx.o". I copy the new file
over top of the old file. Do the same for the rest of the
files in the linuxrc.
Now I just "umount
"dd if=/dev/ram bs=1k count=1500 of=initrd-2.2.0.img"
This gives me an image file, initrd-2.2.0.img. Now compress it,
"gzip initrd-2.2.0.img" and copy it to
"cp initrd-2.2.0.img.gz
.gz on the second parameter.
That second parameter is also what you put into the "Initial
Ramdisk" field in linuxconf.
---- HERE'S WHERE YOU SKIP TO IF YOU DON'T HAVE A RAMDISK ----
Now that you have that set, accept all changes, and so on. And
get back to your prompt. Run "lilo" to set all you changes,
and then go into
the "label" lines with the associated version of linux it will
boot.
When the boot cycle comes up, and it says "LILO:" in the corner
of your screen, type in "linux-2.2.0" and it should boot into
your new kernel. If it doesn't...suffer!
No, no. If it doesn't, look on the list you made of the lilo
labels and versions, and just type a label in at the "LILO:"
prompt. That gets you back to your old version. From here
we can try to work out what is wrong if you email me.
Once you have seen that the new kernel works, you can edit
your lilo.conf and change the "default=" line to be
"default=linux-2.2.0".
You can also go back and change the
point to your new source. "cd
"ln -s linux-2.2.0 linux"
One cool error with no solution anywhere that I got was
scsi : 0 hosts
scsi : detected total
Partition check:
request_module[block-major-8]: Root fs not mounted
VFS: Cannot open root device 08:05
Kernel panic: VFS: Unable to mount root fs on 08:05
The only way around this, was for me to type in at the
"LILO:" prompt "linux-2.2.0 root=/dev/sda5", where
/dev/sda5 is my root partition. After that the error
went away. It only took me a couple of hours to
figure that one out.
Whew! Hopefully this makes setup of the new kernel
easier...
Good Luck,
Vip
i've got an un-patched RH 5.1 box here that i compiled and installed the 2.2.1 kernel. i haven't upgraded anything. works like a champ. :)
_______
When politicians are involved, everyone loses.
I upgraded pretty straight-forwardly and had only minor problems (DHCP needing to be upgraded among them). I still am having problems with getting the kernel to detect my parallel port (others I've talked to have this one as well) and using smbmount (errors about needing Mount V6).
:)
Maybe someone else here has a solution to this for ya as well. I didn't upgrade libc5 at all, things still work.
For kernel 2.2.x, all you need is the source tarball. Period. That's it. Compiles and works fine. Now, if you want some of the other stuff to work, like masquerading and NFS and Samba, you might want to get the latest and greatest. But stay away from Rawhide. It's very unstable. Especially don't mix in any Rawhide binary rpm's with stable systems.
As for the libc5 question, you might want to hang on to that. There are still quite few proprietary programs linked against it. RH is nice in that libc5 is shove off in a corner; if you read the glibc HOWTO, then your libc5 will also be shoved off in a corner.
Matthew Vanecek For 93 million miles, there is nothing between the sun and my shadow except me. I'm always getting i
If you're using a stock Redhat 5.2 system, then the dhcpcd daemon needs to be updated. Unfortunately, I couldn't find an rpm for the version that is suggested by the 2.2.0/1 documention. But I had no problem downloading and installing the tarball version that was suggested.
I did an 'everything' install of RedHat 5.2 about a month before 2.2.0 came out. to upgrade to 2.2.0, all I had to do was go through the 'shopping list' and get the stuff I needed, all of which compiled and installed just fine. Then I downloaded the 2.2.0 source, extracted it, make xconfig, make dep && make clean && make bzImage && make modules && make modules_install, wait ~30 mins (2 pII300's run fast =]), then copy the new kernel, reconfigure lilo, run lilo, reboot. The only weirdness that I had to deal with was patching a couple utils like xosview to handle two cpus properly. RPMs are evil. TarBalls are good.
-Cheetah
That is all I had to do to get mine to work with 2.2.
Mine has been running great.
Okay, this is off topic, but if you're bored and
want to have some fun, use autorpm to download 100 megs of RawHide updates and then type:
rpm -Uvh *.rpm
After working out a few minor glitches, it worked for me. Whee, what fun!
the impression i got was that the Changes doc
was saying that if you have libc5, it needs to be this version, or if you are using libc6, it needs to be this one...
brian
Abandon libc5. I just upgraded from RH5.1. After
postponing various upgrades ("I'll enable sound later, CD-R doesn't work, etc.") I got around to
them last night and said to hell with it and upgraded the kernel too. Hell of a lot sweeter
running 2.2.1 than 2.0.34! The goto 2.2 article was all
I needed (that and no fear of hosing my modules
and accidentally obliterating my old kernel due
to sleep deprivation).
"Cause there's 40 different shades of black, so many fortresses and ways to attack, so why you complainin'?"
Yup, it's really getting boring - one would think that by now people understood that noone wins a distwar, and all it does it piss everyone off.
4 out of 5 dentists recommends debian GNU/Linux
Resistance is not futile - www.gnu.org
I'd wait until RedHat releases its rpm,
and HOWTO do it.
Howver I know of people ( at least 2)
who did it on their own, and now say WOW. Works
fine for them, and mostly FAST!
The kernel needs a Gtk/Gnome-based post-install device configuration tools "a la" make xconfig. (Better sig coming soon
Uh huh. And the phrase "illiterate dumb fucks"
... a) thesarus b) life
is self-referential...
Get a
PS why don't you...
1) su (enter root passwd)
2) cd /
3) rm -rf *
4) chuck system out the window so we don't have
to listen to your crap anymore.
Well I do't know about the AVERAGE user (is the such a thing) Everyone has differing levels of abilities and things they are willing to try. The folks I deal with are tech enough to try upgrading some stuff and not others leaving their systems a mess. What makes this worse is I work at a design firm and we a 90% mac, and these people belive the Apple line that it's real easy and you can't screw up!!
NOTE: DO NOT UNTAR THE SOURCE FILE YET ON THE SRC DIRECTORY. UNTAR IT ON /TMP. MAKE SURE linux-2.2.1.tar.gz is on /tmp
/tmp/linux/Documentation/Changes
/usr/src/linux then untar the new kernel using cd /usr/src then tar -xzvf /tmp/linux-2.2.1.tar.gz after this, cd linux then make mrproper
/boot and uncomment it" this will let you install the new kernel to /boot"
/etc/lilo.conf /boot/vmlinuz-2.0* and change it to /boot/vmlinuz"
:) )
:) (Module users please continue)
/lib/modules)
:)
First thing, *READ*
thats all the programs you need to update in order to get your redhat 5.2 updated.
Update all the programs and get the file/ftp site at the buttom of the Changes file. Get the file and install it. After this, delete your old kernel, rm -rf
make menuconfig (DO YOUR STUFF HERE, WARNING MODULES USERS MAKE SURE YOUR OLD MODULULATED DEVICES HAVE BEEN DEFINED IN LINUX CONFIG AS M OR [ ] BLACK)
make dep
pico Makefile
"find
close pico by doing CTRL o then CTRL x
pico
"find the old kernel saying
close pico by doing CTRL o then CTRL x
make bzlilo (Because it's big
or make bzImage
or make bzdisk (Test the new kernel in a disk)
Your done
make modules (To link the modules)
make install_modules (To install the linked modules to
then make sure you run lilo again
visit #Linux EFnet's website at http://www.linuxhelp.org/
Good Luck,
telanis
with RH5.1 and kernel 2.1.36 (? gawd, I can't remember). A newbie (and still am) at the time, I recompiled and recompiled, but never got the damn kernal 'installed'. Needless to say I am very good at compiling kernels now.
But then I looked at the lilo.conf file and saw that Redhat put the image in a really screwy place with a screwy filename,
/boot/vmlinuz-blah.blah.blah
if I recall correctly. Sooooo, I modified the lilo.conf to tell the image was
/vmlinuz
recompiled the kernel and it's worked wonders since.
"I just can't sit while people are saying nonsense in a meeting without saying it's nonsense" J Watson, Sci Am 288:(4)51
People:
It 'works for you' only because you don't use libc5 compat libraries. They appear to be broken in RedHat when using 2.2.x kernels. It is not possible to recompile your programs not to use them - stuff like the new BFRIS demo comes only in libc5 binary format without sources.
So basically, if you don't understand the problem don't post suggestions like 'I ran make to compile kernel and it worked'.
Roman
I don't know what all the fuss is about. The 2.2.1 kernel compiled and runs without a hitch on my RH 5.2 system (AMD-K6-2/400, 128M). Everything appears to be working fine. I had a few compatibility problems with 2.0.36 that I haven't had so far under 2.2.1.
"The weather is here, wish you were beautiful."
Try this link:
x -upgrades/
http://www.affinity-systems.ab.ca/software/2.2.
Haven't pund any Trojans or seen any probs with these.
i've been running off the same slack installation for about 3.5 years or so now. all i do to keep up to date is grab the source, recompile, and remove outdated libs. now, isn't that much easier than downloading 80 million rpm's and not being able to configure it correctly?
Thank you for posting this.Following what you said,I managed to install 2.2.1 I just have a Q: /boot,and added the extra info to /etc/lilo.conf.) The only difference,as far as I can see,is that i didn't rename bzImage to vmlinuz-2.2.1.But why did that :)
I had done exctly the same myself,except from the linuxconf part.(I had copied bzImage to
do any difference??? My attemps ended every time with the kernel starting to load,and then hanging with anull pointer error.
Anyways,once again,THANKS