LinuxQuestions.org
Go Job Hunting at the LQ Job Marketplace
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 05-17-2007, 05:56 PM   #16
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 1,922

Rep: Reputation: Disabled

Correct.

Make sure you have a look at the line about -EEXIST errors in CHANGES_AND_HINTS.TXT though - you'll get that with the huge* kernels.
There may very well be other issues along those lines with huge* kernels, but none of which I'm aware at this time.

The huge* kernels are really intended for installation, with the generic* ones for actually running the system. The "safe" option (the way it falls back after an installation) though is to link /boot/vmlinuz with the huge kernel, as that way (as long as /sbin/lilo is run and the correct boot and root devices are specified), the system will definitely boot after the upgrade (in case you forget to make an initrd).
 
Old 05-17-2007, 05:59 PM   #17
Michielvw
Member
 
Registered: May 2005
Location: Leicester,UK
Distribution: Slackware
Posts: 108

Rep: Reputation: 19
Quote:
Originally Posted by Drone4four
lol

I can't wait until 12.0 because I need to use slackbuilds to install things.
That is nonsense. I run slackware 11.0 and SlackBuild scripts just plain work. In fact all Slackbuild scripts currently hosted at SlackBuilds.org work on standard 11.0 installs. Thats the way they are written *and* tested.

More Likely you have missed out something of the d/ selection. Unless you post better errros, it's hard to say what "does not work" constitute off. Just upgrading to -current because you think something is not right, is probably not the best way to go about troubleshooting.
 
Old 05-17-2007, 06:02 PM   #18
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 1,922

Rep: Reputation: Disabled
Quote:
Originally Posted by Drone4four
lol

I can't wait until 12.0 because I need to use slackbuilds to install things. Slackbuilds at the momment stop half way to complain about GCC and C++. -current is my only option. I am willing to learn.
As BlackPanther advised, this is not a good approach. I don't know for sure if you're referring to using things from SlackBuilds.org, but nothing there is guaranteed to work on -current at all. Everything is tested and supported on 11.0.

It sounds like you missed some things in the D/ package series.
 
Old 05-18-2007, 06:55 AM   #19
Alien_Hominid
Senior Member
 
Registered: Oct 2005
Location: Lithuania
Distribution: Hybrid
Posts: 2,247

Rep: Reputation: 53
What my post was about, you should have 2.6 kernel headers installed if you plan to compile glibc with 2.6 kernel (not 2.4). The headers which are in use, should be those against which you will compile your glibc.
 
Old 05-21-2007, 11:00 PM   #20
Drone4four
Member
 
Registered: Feb 2006
Distribution: Ubuntu, Slackware. Gentoo
Posts: 188

Original Poster
Rep: Reputation: 30
I still have some questions before I go through with upgrading glibc. Is this the only command I need to enter for Step #1 in Pat V's Hints and Changes text file?

Code:
# installpkg kernel-huge-2.6.18.8_smp-x86_64_slamd64-1.tgz

Last edited by Drone4four; 05-22-2007 at 12:00 AM.
 
Old 05-21-2007, 11:59 PM   #21
Drone4four
Member
 
Registered: Feb 2006
Distribution: Ubuntu, Slackware. Gentoo
Posts: 188

Original Poster
Rep: Reputation: 30
And what does Pat V mean when he says:
Quote:
After successfully booting the new 2.6 kernel, you may now remove the kernel-ide and kernel-modules-2.4.* packages.
In what directory can I find kernel-modules-2.4.* packages?
 
Old 05-22-2007, 12:44 AM   #22
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 1,922

Rep: Reputation: Disabled
You're attempting to use instructions written for Slackware but on Slamd64. If memory serves correctly, Slamd64 11.0 didn't have a 2.4 kernel. If it did, though, the records would be in /var/log/packages.

Should a disclaimer be added to UPGRADE.TXT / CHANGES_AND_HINTS.TXT ?? Something along the lines of:
"If the instructions in this file do not make sense, do not attempt the upgrade - continue running your present version."
 
Old 05-22-2007, 01:28 AM   #23
Alien_Hominid
Senior Member
 
Registered: Oct 2005
Location: Lithuania
Distribution: Hybrid
Posts: 2,247

Rep: Reputation: 53
Run pkgtool and search for package. In /lib/modules directory.
 
Old 05-22-2007, 07:29 PM   #24
Eternal_Newbie
Member
 
Registered: Jun 2005
Location: The Pudding Isles
Distribution: Slackware 13.37
Posts: 573

Rep: Reputation: 59
Slamd64 is the origional 64 bit clone of Slackware, which is a 32 bit distribution. You do not want to install a Slamd64 kernel with Slackware -current, only grief and heartache lie along that path. If you are trying to install Slamd64 -current, then please say so.
 
Old 05-23-2007, 10:42 AM   #25
Drone4four
Member
 
Registered: Feb 2006
Distribution: Ubuntu, Slackware. Gentoo
Posts: 188

Original Poster
Rep: Reputation: 30
Quote:
Originally Posted by Eternal_Newbie
Slamd64 is the origional 64 bit clone of Slackware, which is a 32 bit distribution. You do not want to install a Slamd64 kernel with Slackware -current, only grief and heartache lie along that path. If you are trying to install Slamd64 -current, then please say so.
I am installing Slamd64-current. DUH.
 
Old 05-23-2007, 12:32 PM   #26
GregLee
Member
 
Registered: Feb 2004
Location: Waimanalo, HI
Distribution: Slackware 10, Fedora 6
Posts: 308

Rep: Reputation: 30
I installed several of the generic kernels before I noticed that warning about needing an initrd. Worked anyway.
 
Old 05-23-2007, 12:38 PM   #27
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 1,922

Rep: Reputation: Disabled
Quote:
Originally Posted by GregLee
I installed several of the generic kernels before I noticed that warning about needing an initrd. Worked anyway.
If you're talking about 11.0, then then the generic kernels had support for ext2 built in; as such, an ext3 root filesystem could be mounted just fine with the generic kernel and no initrd.

On -current right now (20070523), the generic kernels do not include any filesystem support, so you *will* need an initrd. If you do a full installation, then the the huge kernels will take precedence (as they are installed after the generic kernels during installation) over the generic kernels (with respect to symlinks created in /boot), even though the generic kernel is installed.
 
Old 05-23-2007, 02:02 PM   #28
GregLee
Member
 
Registered: Feb 2004
Location: Waimanalo, HI
Distribution: Slackware 10, Fedora 6
Posts: 308

Rep: Reputation: 30
Quote:
Originally Posted by rworkman
If you're talking about 11.0, then then the generic kernels had support for ext2 built in; ...
Yes, two of them were from 11.0, and I noticed a booting message that ext3 was being mounted as ext2. Apparently, I was just lucky.

I did upgrade to glibc 2.3.6, after "telinit 1", with no apparent problem.
 
Old 06-10-2007, 02:34 AM   #29
Drone4four
Member
 
Registered: Feb 2006
Distribution: Ubuntu, Slackware. Gentoo
Posts: 188

Original Poster
Rep: Reputation: 30
hmmm,I just installed the 2.6.21.3 smp kernel and it isn't showing up in lilo. What should I put for the image variable in my lilo.conf?
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Upgrading glibc to 2.4 shevegen Linux From Scratch 2 08-19-2006 09:22 PM
Swaret upgrade from 10.0 to current broke glibc - unable to login vharishankar Slackware 6 04-03-2006 01:30 AM
Problems with glibc on Slackware current? MS3FGX Slackware 2 03-30-2006 10:57 PM
upgrading glibc 2.3.2 to glibc 2.3.3 =cop=Jesse Linux - Newbie 3 12-09-2004 12:00 AM
Upgrading glibc-2.2.4 to glibc-2.3.2 on redhat 7.2 Shuja Linux From Scratch 2 07-30-2004 01:34 AM


All times are GMT -5. The time now is 08:51 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration