SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
You might have just left it off in the copy/paste or I may just be barking up the wrong tree, but shouldn't there be a -m before the modules list?
Yeah, that's just a typo in my post.
There is definitely a kernel bug during the install, it occurs at about where fontconfig runs, after the packages are installed. I could only salvage part of it, but it looks redundant, look at the Oops line near the bottom. The earlier ones are lower numbered and occur on alternating cores.
1 Which means that I most likely will get the very samy result.
2 Therefore I will have to redo lilo.
3 GOTO 1.
Seems to be a "dynamic halt"... (synonym for "infinite loop")
Well, I think I prefer the "Hello world" kind of program. Seriously, if you can't get lilo to cooperate, you might give grub in /extras a whirl. Nice thing about it is that you don't have to keep reinstalling it everytime you fiddle with the kernel and initrd, which I find makes debugging the situation easier. Not that I have anything against LILO, used it for years!
I don't see an indication that the /dev/root thing is my way, but I really don't know.
My recent "experiments" didn't solve the problem, however, here are my observations:
(1) New install including formatting / and /boot, following the README_CRYPT.TXT word by
from the point where the LVM setup is complete, including creation of initrd and switching
to generic SMP kernel, liloconfig and lilo. Reboot.
==> In fact I was asked to enter a LUKS passphrase. However, my USB keyboard wouldn't work...
(2) So once again boot with the install DVD, add USB support modules to initrd (uhci-hcd,
ehci-hcd,...), lilo. Reboot.
==> Kernel panic, RAID not working.
However, I noticed something strange. After a complete install like in (1) including
formatting the first run of mkinitrd reports more than 9000 blocks written, while running it
again and again it only reports 6500 blocks. Even when I remove the initrd-tree completely,
mkinitrd would only write about 6500 blocks. But after a full install it writes 9000 plus
blocks, it reports, exactly one time.
Then I downloaded the latest version 1.40 of mkinitrd-command-generator.sh. With some of my
attempts this created just about what I already had, but in my recent attempts it doesn't
"see" the RAID anymore. Weird!
Thanks. Yes, 12.1 worked flawlessly here, once I had it up and running thanks to the great support
of the folks here. The most valuable part coming from Alien Bob --- thanks, Eric, once again!
Although he doesn't stop emphasizing that he is not here for holding hands, he and his mates in the
Slackware team (Robby Workman and some other people) are very helpful, just like Pat V. himself, too.
Indeed they didn't ever refuse to hold my hand, and I am very grateful for that!
As to 12.2, there's a lot of updates, I like to have, such as Mozilla Firefox 3.x (note that 2.0.20 is
supposed to be the last 2.0.x version of this browser, the 2.x branch will no longer be maintained).
But there some truth in the saying: "Never change a running system!"
Well, I did, and immediately had a reason to return to LQ.org...
Yeah, that looks really good. I have a few minor suggestions though.
1. From experience, the modules needed for USB keyboards are *NOT* added automatically.
2. This is more of a suggestion, but perhaps you would like to include a note about multiple initrds? This is especially relevant if the user is going to be compiling their own kernels. mkinitrd will overwrite the initrd each time it is run, so there should be a unique one for each kernel entry, ie, the initrd for the default slackware 12.2 kernel should be copied to initrd.gz-18.104.22.168-smp. This can also be set with the -o switch to mkinitrd.
1. Ok, I'll correct this. Although it once looked to me as if my USB keyboard was working although initrd did not provide modules to the kernel for it.
2. I understand your point, but the topic is already complex, and adding information on multiple initrd setups would make it even more complex and further reduce the number of potetntial readers...
Also I don't have time to try it out myself, at the moment. That's why I am a bit reluctant, here. What do others think?