Slackware This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
|
07-05-2007, 05:21 PM
|
#1
|
|
Senior Member
Registered: Mar 2004
Location: Middx UK
Distribution: Slackware64 14.0 (multilib)
Posts: 1,165
Rep:
|
Slackware 12, HAL automount
I have just installed slackware 12 and cannot get the hang of Hal.
I plug in a usb drive and the box comes up asking what I want to do with it.
What I want to do is automount and nothing else, no new boxes, no konquerer.
How do I do this?
Where is a good Hal FAQ
TIA
|
|
|
|
07-05-2007, 06:38 PM
|
#2
|
|
Senior Member
Registered: Aug 2003
Location: UK
Distribution: Slackware
Posts: 3,081
|
You should be able to choose 'do nothing' and tick the box to always do this. It's a kde feature rather than Hal.
There are also options in control centre to put device icons on the desktop when mounted.
It's possible to use a combination of Hal and Autofs so it's possible to have the choice of using command line or konqueror.
|
|
|
|
07-05-2007, 06:46 PM
|
#3
|
|
Member
Registered: Feb 2004
Distribution: Slackware 10.2
Posts: 669
Rep:
|
I dont know if kde's automounter will mount the cd without opening konqueror. I think ivman will function the way you want but you have to disable kde's automounting. Maybe someone that has ivman installed in kde 3.5.7 can tell you better than I can.
|
|
|
|
07-06-2007, 02:05 AM
|
#4
|
|
Senior Member
Registered: Mar 2004
Location: Middx UK
Distribution: Slackware64 14.0 (multilib)
Posts: 1,165
Original Poster
Rep:
|
'Do nothing' leaves the device unmounted. I have the option set so that the device icon appears but it is still unmounted.
|
|
|
|
07-06-2007, 02:12 AM
|
#5
|
|
Slackware Contributor
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 1,894
Rep: 
|
HAL doesn't actually mount anything; for lack of a better way to put it, HAL simply provides (in a standardized format) information about the hardware and what actions are potentially allowed, and then something else can use dbus methods (pending proper permissions) to actually *do* something with/to the hardware.
For what you're trying to do, I believe you'll want to investigate ivman and/or pmount (though there may very well be other options). http://slackbuilds.org has ivman and pmount scripts for 11.0, but they have not been tested or approved for use on 12.0, so caveat emptor.
|
|
|
|
07-06-2007, 06:38 AM
|
#6
|
|
Member
Registered: Oct 2003
Location: Finland
Distribution: Slackware 12.0
Posts: 34
Rep:
|
I don't think there is a good FAQ for HAL yet, nor much in terms of troubleshooting or tutorials on how to use it. I'm also having trouble getting into terms with HAL.
For example, just inserting and getting my CDROM mounted, is a problem. I do get the box asking what to do with it. But when I click that I want browse it, konqueror launches and I get a weird error message:
A security policy in place prevents this sender from sending this message to this recipient: see message bus configuration file (rejected message had
interface "org.freedesktop.Hal.Device.Volume"
member "Mount" error name "(unset)"
destination "org.freedesktop.Hal")
Anyone have a clue what this means?
|
|
|
|
07-06-2007, 06:42 AM
|
#7
|
|
Senior Member
Registered: Mar 2004
Location: Middx UK
Distribution: Slackware64 14.0 (multilib)
Posts: 1,165
Original Poster
Rep:
|
I do not know if this will help your problem but it may be worth checking that the cdrom line is commented out in fstab and that you are joined to the cdrom group.
|
|
|
|
07-06-2007, 06:53 AM
|
#8
|
|
Member
Registered: Nov 2005
Location: Greece
Distribution: Slackware
Posts: 129
Rep:
|
Not tested, but I think you should be member of plugdev group..
info taken from CHANGES_AND_HINTS.TXT
|
|
|
|
07-06-2007, 08:15 AM
|
#9
|
|
Member
Registered: Mar 2005
Posts: 74
Rep:
|
Quote:
|
Originally Posted by Datamike
I don't think there is a good FAQ for HAL yet, nor much in terms of troubleshooting or tutorials on how to use it. I'm also having trouble getting into terms with HAL.
For example, just inserting and getting my CDROM mounted, is a problem. I do get the box asking what to do with it. But when I click that I want browse it, konqueror launches and I get a weird error message:
A security policy in place prevents this sender from sending this message to this recipient: see message bus configuration file (rejected message had
interface "org.freedesktop.Hal.Device.Volume"
member "Mount" error name "(unset)"
destination "org.freedesktop.Hal")
Anyone have a clue what this means?
|
It means you didnt add yourself to the 'plugdev' and 'cdrom' groups
" Users in the "plugdev" or "cdrom" group will be able to use such devices on the desktop without the need to mount/umount them manually."
|
|
|
|
07-07-2007, 12:39 AM
|
#10
|
|
Member
Registered: Oct 2003
Location: Finland
Distribution: Slackware 12.0
Posts: 34
Rep:
|
Quote:
|
Originally Posted by bmfan
It means you didnt add yourself to the 'plugdev' and 'cdrom' groups
" Users in the "plugdev" or "cdrom" group will be able to use such devices on the desktop without the need to mount/umount them manually."
|
I did actually, but I noticed that my HAL has the same problem as my Apache; reloading or restarting doesn't help. Whenever I changed some settings, I have to restart apache, using the stop-start sequence. With HAL, even that did not help. I have to reboot the whole computer. Very strange. Anyone else have this issue?
But yeah, now it works. Thanks for the help
Are there more groups for this purpose? E.g. if I want to automount an usb stick or an external usb drive, etc. Any groups I should add myself to accomplish this?
|
|
|
|
07-07-2007, 01:46 AM
|
#11
|
|
Slackware Contributor
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 1,894
Rep: 
|
Quote:
|
Originally Posted by Datamike
I did actually, but I noticed that my HAL has the same problem as my Apache; reloading or restarting doesn't help. Whenever I changed some settings, I have to restart apache, using the stop-start sequence. With HAL, even that did not help. I have to reboot the whole computer. Very strange. Anyone else have this issue?
|
Yes and no. Yes, in that restarting hald won't solve it. No, in that restarting dbus will. That's documented in CHANGES_AND_HINTS.TXT, by the way.
Quote:
|
Are there more groups for this purpose? E.g. if I want to automount an usb stick or an external usb drive, etc. Any groups I should add myself to accomplish this?
|
plugdev and cdrom should cover it.
|
|
|
|
07-07-2007, 02:34 AM
|
#12
|
|
Member
Registered: Oct 2003
Location: Finland
Distribution: Slackware 12.0
Posts: 34
Rep:
|
Quote:
|
Originally Posted by rworkman
Yes and no. Yes, in that restarting hald won't solve it. No, in that restarting dbus will. That's documented in CHANGES_AND_HINTS.TXT, by the way.
|
And not surprisingly, I have read the said document, at least the bits about HAL. When I said restarting HAL, I meant restarting DBUS. Sorry for the confusion. For me, the difference isn't so clear.
Reloading (as in /etc/rc.d/rc.messagebus reload) does not help. Neither does stopping and starting. Actually, automounting stops responding if I stop and start again. It's very peculiar.
|
|
|
|
07-07-2007, 03:43 PM
|
#13
|
|
Senior Member
Registered: May 2003
Distribution: Slackware, SLAX, OpenSuSE
Posts: 1,511
Rep: 
|
Not sure, but maybe you need to re-login after adding yourself to the relevant groups, as your login session reads the groups your user belongs to at login time... It shouldn't be necessary to reboot, but it may be necessary to restart D-BUS and/or HAL.
gargamel
|
|
|
|
07-07-2007, 05:18 PM
|
#14
|
|
Member
Registered: Nov 2006
Location: Slovenia
Distribution: Slackware 13.37
Posts: 511
Rep:
|
Quote:
|
Originally Posted by bmfan
It means you didnt add yourself to the 'plugdev' and 'cdrom' groups
" Users in the "plugdev" or "cdrom" group will be able to use such devices on the desktop without the need to mount/umount them manually."
|
This works, if you have in fstab the option users on that device.
But what about USB storage devices? Where do I need to add the users?
|
|
|
|
|
Tags
|
automount, cdrom, dbus, drive, flash, fstab, group, hal, plugdev, slackware, usb, utf8  |
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 11:28 AM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|