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.
I'm having some udev problems on slackware-current (udev-062, kernel 220.127.116.11).
The udev daemon udevd seems to be not running... I don't know if this is normal or not. When i plug in usb devices hotplug recognises them correctly but udev doesn't do anything (such as creating the devices). I assume because it is not running.
Strangely enough /etc/rc.d/rc.udev does not seem to start udevd, it only runs udevstart.
When i manually run udevstart after plugging something in, it works fine. (so the udev rules are fine)
When i manually start udevd (simply udevd&) a lot of stuff breaks including my virtual consoles i think (all terminal emulators including Konsole won't work anymore).
Any help greatly appreciated (trying to get my Palm sync to work, it already works with the manual udevstart execution after hitting the hotsync button).
PS: Anyone know of a way to get KPilot or some equivalent app to store the downloaded data encrypted? I keep my passwords on my Palm and there's little point in having an encrypted KWallet when they're in clear-text on the disk too.
While it is true that I don't have any explanation for the change of usb storage device names (from sd* to ub*), some time ago, it still works fine and so it's not a problem. The problem is the devices not being created automatically on plug-in.
It may already be useful if someone using a correctly working Slackware with udev could tell me if udevd is running, and what file starts it at boot-up (rc.udev?) and any config changes they had to make. (or working udev.rules file)
i guess if the latest udev gives prob.'s with alsa, it's no suprise that other prob.'s might come out.
and if you wonder what's the prob exactly, don't give it to much time.
they'll probably change udev again before you find a workaround.
( in fact the newest is udev-063 )
Originally posted by don_pingu While it is true that I don't have any explanation for the change of usb storage device names (from sd* to ub*), some time ago, it still works fine and so it's not a problem. The problem is the devices not being created automatically on plug-in.
Look in your kernel config file and see if you see this:
# Block devices
There'll be several other CONFIG_whatever's under #Block devices but according to what you've said so far I'd be willing to bet that CONFIG_BLK_DEV_UB is set to y or m. I'm not sure about the 2.6.12 kernel series but in the 2.6.11 series the help file for UB says that if you enable it you will cripple usb-storage. Having UB set to y or m is why your USB storage devices are being assigned ub* instead of sd*. You may want to look at the help file for UB and see if this problem still exists.
Here is the help file from my 18.104.22.168 kernel config:
Low Performance USB Block driver (BLK_DEV_UB)
This driver supports certain USB attached storage devices
such as flash keys.
Warning: Enabling this cripples the usb-storage driver.