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.
if I dont set HAL at start up, and then go on to slot a memory card into the reader after boot, the system wont pick it up (DBUS?)
but when I put a usb pen drive directly into a usb slot after boot. the system (DBUS) does pick it up.
going back to the card reader, is this because DBUS is only seeing the cardreader itself and not the memory slots?
so HAL is needed to monitor the card reader slots for input of a memory card and pass that info onto DBUS?
DBUS isn't "picking up" anything - it's udev. The kernel generates uevents that udev receives, which then passes them to hal, which then does something (or not) with them by communicating over a message bus (DBUS).
In other words, it's the kernel you should be concerned with, not dbus (which is out of the picture entirely since you don't have hal running).
It sounds like you're on 12.0 since this isn't handled automatically - try running the /etc/rc.d/rc.scanluns script after inserting a card in the cardreader, and it should work. On 12.1, this isn't needed (and in fact, the rc.scanluns file is not present), as the kernel is configured to handle this automatically.
HI. I have a problem with hal. I has slack 12.1 with hal working perfectly, but now, I've upgraded to 12.2 with slackpkg and hal just doesn't work any more. I'm usin KDE 3.5.10 now (3.5.9 before). Is this common? I suppose that is some new configuration file the problem but i have no idea which one can be. GoodBye!
6. Fix your config files. Some of the config files in /etc are going to
need your attention. You'll find the new incoming config files on
your system with the ".new" extension. You may need to fill these in
with information from your old config files and then move them over.
Feel brave? You can use this little script to install most of the
.new config files in /etc. If you've made any local changes you'll
need to add them to the newly installed files. Your old config files
will be copied to *.bak. Anyway, it might be an easier starting
point. Here it is:
find . -name "*.new" | while read configfile ; do
if [ ! "$configfile" = "./rc.d/rc.inet1.conf.new" \
-a ! "$configfile" = "./rc.d/rc.local.new" \
-a ! "$configfile" = "./group.new" \
-a ! "$configfile" = "./passwd.new" \
-a ! "$configfile" = "./shadow.new" ]; then
cp -a $(echo $configfile | rev | cut -f 2- -d . | rev) \
$(echo $configfile | rev | cut -f 2- -d . | rev).bak 2> /dev/null
mv $configfile $(echo $configfile | rev | cut -f 2- -d . | rev)
Last edited by gegechris99; 12-17-2008 at 10:26 AM.
HI. I have a problem with hal. I has slack 12.1 with hal working perfectly, but now, I've upgraded to 12.2 with slackpkg and hal just doesn't work any more. I'm usin KDE 3.5.10 now (3.5.9 before). Is this common? I suppose that is some new configuration file the problem but i have no idea which one can be.
I suspect that you didn't *fully* upgrade to 12.2. Did you follow slackpkg's instructions? In other words, did you do "slackpkg install-new" first? If not, then you don't have parted installed, and that's at least part of the problem.
In here I "recommend" the fmask and dmask options, and "force" the codepage and shortname options.
Drawback: The "user" and "users" options in fstab will no longer work. If you need them, create a suid binary program instead of a script, and switch your identity to root before calling /sbin/mount.
I have unstuck this thread - huge numbers of people are now on 12.1/2 or current or even the 64bit version. For those who aren't yet, either this thread was helpful and you no longer have the issue or you don't care any more