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.
issue i'm having is sometimes when i power on my slackware box it gives me an error saying missing device /dev/hda1 . not really sure how to capture the error message since when i reboot it again it comes up fine and dmesg is overwritten. anyone having issues like this also??
i am using slackware 10.2 with the new packages from piter.
I started playing with PiterPunk's udev solution today, and I thought I had exactly the same problems. But what I missed, was that I booted the wrong 2.6 kernel. I had my old 2.6.13 kernel still as default in LILO, and forgot to boot the 126.96.36.199 kernel I had prepared. PiterPunk warns that his UDEV framework does not work for Linux kernels < 2.6.15. Is this what you did?
When I boot my 188.8.131.52 kernel, all is fine.
So far, I am disappointed with the bootup speed of my desktop. I had thought I would see an improvement in the time it takes to get to the command prompt, but the "cold-plugging" phase takes quite long. Also, since udev starts a lot of devices before the syslog is started, I see far too many logging messages scrolling across the screen.
Thanks for the link slackamp. I had been looking for a modern udev / hotplug-less solution for some time. I've installed PiterPunk's packages and booting is really much faster than before. I've rebooted 5 or 6 times, but haven't seen the error about the missing device that you're talking about.
I guess part of my slowness in booting is that I have 4 network cards, of which 2 wireless, and the latter take some time to get their WPA association. It is a pity that this is delaying the boot, but I'll have a look at what happens if I let the network initialization run in the background. Apart from the network delay, the boot is fast.
i do have kernel 184.108.40.206. if only i could capture the messages. maybe ill take a picture 1 day. i didn't want to upgrade to the 2.6.16 yet because they took off ULOG support that I use for my firewall logging. so im stuck with 220.127.116.11 for now.
Just to quickly post my experience, I share the trouble, even with a very recent (2.6.15.x) kernel, I cannot get the system to boot the harddisks anything but read-only, and that of course makes udev creation etc etc quite difficult. I believe I have a pretty stock system, but for some odd reason it just won't work.
Guess I'll wait for it to be officially part of Slackware, or valuable input from this list
i also had some problem with the 0.89 udev packages, so i stick with 0.88. It displays 2 process running all the time and it won't mount my filesystem, but when i downgrade to 0.88, it was fine again, so for now, i stick with 0.88.