SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I decided I wanted to try slackware-currents testing kernel 2.6.12.4 (i think) SO I downloaded everything and and ran upgradepkg * in that directory. Needless to say everything pretty much quit working after that
What a pita... I booted to a slackware 9.1 rescue cd (I couldn't find the 10.1 cd's) chroot'ed the system and and I couldn;t run mkinitrd to create a startup image file. I dont remember the error but I dont think you can run mkinitrd or lilo when you boot from a livecd. I tried a few other live cd's and couldnt get it to work.
anyways.. the fix was simple.. I used the 9.1 cd and reinstalled the default kernel and lilo. booted right up and installed the kernel correctly. I had done this many times before but I hadnt done it in a while and thought I remembered exactly how to do it.
so.. the moral is.. stop and think before you start to do it. My mistake cost me 10 minutes of downtime
"If you want something done right, do it yourself".
Try getting a vanilla kernel, and make your own config from scratch. Might take some time the first time, but you'll get to know it well enough to start from scratch at any time without such serious crashes.
the moral of the story is this..........the proper way to upgrade all the package in a directory is.......
upgradepkg *.tgz
OH, I'll also mention that slackware v10.1 does NOT have a live rescue disk........since Pat V. did not take out gnome (like he said he would) there was not enough room on the disk to make it a live boot CD.......D'oh.........we should all complain so he'll get it right in v10.2
First of all, at freakyg, either slack CD can be used as a rescue CD. Boot from CD1, log in as root, but instead of using setup, go straight to chroot. And if you've bothered to check the changelog, you'll see that gnome WAS removed from current, at the exact time he decided it should be.
Second, trey85stang, did you read the README from that kernel DIR ? Do you know that you have to load FS modules using an initrd if you're on certain file systems, as that is a generic kernel?
The lesson of the story is: know what you're doing. A simple upgradepkg *.tgz without looking into stuff can be dangerous.
Also, that kernel from /testing DOES work very well.
Alternatively, one could boot CD1 with the line:
boot: root=/dev/hdwhatever noinitrd ro
to boot their root partition as the root partition, as per the instructions on CD1.
I have NEVER been able to boot from CD2, don't know of anyone who has.
I believe Pat has already dropped Gnome for 10.2.
Charred, Slackware 10.0 (and 9.1 too if my memory doesn't fail)'s CD 2 was booteable, it was more a rescue CD than CD 1, but that changed on 10.1, CD 2 is not a rescue cd anymore.
Since gnome is no longer part of the distro, are there any suggestions on how best to remove it?
It is somewhat ironic, I think, that gdm is still the default login manager even though it's not in 10.2. I found that out while I was going through the '.new' rc files. I'll stick with kdm thank you.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.