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.
What was your original boot loader?
Do you still have the config for it?
If so see if there are any command line options for the kernel that you didn't include in the lilo config.
Also post a copy of your current lilo.conf.
Ahh..... I had to abort Slackware and re-install AntiX for the time being, as I have to have access to my Crunchbang for work.
I'll be giving Slack another try though, soon. This time, I'll do it the other way around. I'll skip installing LILO, and leave GRUB in place on the MBR. Hopefully that configuration will work.
Also, yes, skipping LILO and letting another GRUB to it's job it's not a bad ideea.. Slackware also has GRUB in the extra packages.. You can use install it from Slackware too, if you feel more comfortable..
Also, yes, skipping LILO and letting another GRUB to it's job it's not a bad ideea.. Slackware also has GRUB in the extra packages.. You can use install it from Slackware too, if you feel more comfortable..
I will give that a try when I get a chance to re-install Slack.
In retrospect, I don't think LILO was the problem. I tried mounting Crunchbang's filesystem in Antix, and got an error message. I ran fsck on the Crunchbang partition, and now it mounts. I'll bet if I had done that from Slack, Crunchbang would not have been frozen when booted.
Well, I have to say....I certainly am learning a lot this week!
I'm back to square one: With Crunchbang and AntiX. I'll be ready in a day or two to try Slackware again. I must say, I have learned more in the last two days than I had in the last 4 years of Linux use!
I'll be ready in a day or two to try Slackware again. I must say, I have learned more in the last two days than I had in the last 4 years of Linux use!
Good to hear. Slackware grows on you. You will be back. Praise bob.
You're so right, Hitest! I'm just itching to install Slack again- and I would right now....but for the fact that I want to get to bed at a reasonable time for a change. I got as taste of Slack; It's not the monster some portray it as. In fact...it's pretty cool! Even though it might take a little effort, it seems as though Slack is orderly and logical- so even though some things may be new to me, they are not really difficult.
I believe it, Bert. Installation was one of the easiest I've ever done- with the possible exception of AntiX (But the AntiX installer is only easy because it gives you no real choices in most things). Initial configuration of Slack was easy too- as long as you follow the instructions.
It seems, with most things we use, you can either choose something that does everything automatically [which usually means little or no choice; and a lot of trouble trying to "get around" the system to make it do what you really want] -or something that lets you make the choices- which is usually the easier way to implement those choices, as long as you haven't become so used to them being made for you, that you don't know/don't care what to do. And ALWAYS, the one that lets you make the choices, is inherently simpler, and therefore breaks less often; and is easier to fix when it does break. Whether it's an automotive transmission or an operating system....same general cocepts apply!
You're so right, Hitest! I'm just itching to install Slack again- and I would right now....but for the fact that I want to get to bed at a reasonable time for a change. I got as taste of Slack; It's not the monster some portray it as. In fact...it's pretty cool! Even though it might take a little effort, it seems as though Slack is orderly and logical- so even though some things may be new to me, they are not really difficult.
Well, it was maintained by pretty much one person for a long time. So you'd think that a single person (like you, for instance) could figure out how it's put together.
Well, it was maintained by pretty much one person for a long time. So you'd think that a single person (like you, for instance) could figure out how it's put together.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.