Autofs or hal/dbus ?

When I was setting up my Arch box I used autofs so it would automount dvds I wanted to watch with smplayer. Then I wanted to try "thunar", which needed hal/dbus. When I enable hal in my rc.conf and rebooted, it said the DVD was locked - by autofs I assume. So I removed autofs from my rc.conf, and rebooted. Now thunar works. I had avoided hal/dbus because I thought I read they were part of gnome and I was afraid it would clutter my system, but then I found it was already installed and I just had to enable it. Is using autofs deprecated in favor of using hal/dbus?

HAL and dbus are needed by alot of things, and using it in conjunction with a volume manager (such as thunar-volman) seems to be the prefered way to do it.
not sure if autofs is "deprecated" (i can think of a few uses where it'd work better than hal/dbus+volume manager) but since you already got hal/dbus + a volume manager installed, use them

Similar Messages

KDE / HAL / dbus

I am trying to setup HAL/dbus with KDE, but have hit a bit of a snag. When popping in a CD/DVD or USB device, then selecting "Open in New Window" from the prompt, I get this message ("/mnt/usbdisk" differs when using a dvd):
/mnt/usbdisk is a folder, but a file was expected.
After that error message, I can click the link on my desktop to the device, and it opens up.
Here is some relevant information:
/etc/fstab:
/dev/sr0 /mnt/dvd auto ro,user,noauto,nodev,nosuid0 0
/dev/sdc1 /mnt/usbdisk auto user,noauto,nodev,nosuid 0 0

xyon wrote:
Here is some relevant information:
/etc/fstab:
/dev/sr0 /mnt/dvd auto ro,user,noauto,nodev,nosuid0 0
/dev/sdc1 /mnt/usbdisk auto user,noauto,nodev,nosuid 0 0
Removable media shall be controllable by HAL of operating system, which does automount. /etc/fstab creates hard mounts. Even if the documents or fstab examples state what you pasted, remove these lines or comment them out. Let Linux do it for you.

Hal/Dbus/gnome-volume-manager mount permission problem

Hello,
I have hal/dbus/gnome-volume-manager installed (of course I use gnome as DE).
I need help in configuring the permissions for automatically mounted disk/partitions.
When I connect an external USB HDD having 1 NTFS and 1 partition, these partitions are auto-mounted and the desktop icons appear for the both.
As a normal user I am able to read/write FAT partition (I think, not because I have configured anything properly, but because FAT does not support permissions on filesystem), but I am not even able to read (browse) NTFS filesystem (ERORR: You do not have permission...).
Yes, I have NTFS filesystm support enabled, because I am able to access that same NTFS partition as root.

Well, Thanks for the reply but I had not put any static entry in fstab for this external USB HDD.
Anyway, I figured out something (havn't tested it yet)
When an external USB HDD is attached ... depending storage.policy and volume.policy rules in /usr/share/hal .. the hal daemon (hald) calls fstab-sync with appropriate parameters.
fstab-sync, then, generates /etc/fstab enteries automatically (with comment=managed keyword).
I have added a user policy so that umask and gid value is set correctly. I'll test is as soon as I'll get time.
In the meanwhile if anybody have any other suggestions, please post it here.

HAL/DBUS No longer works in nautilus.

Hey,
After a recent upgrade I noticed that nautilus no longer recognises any devices such as USB or DVD/CD there's is no longer even an icon with which to mount from. This worked perfectly before but stopped after the upgrade. I checked hal and dbus and they both start and are definitely running, outside of that, I can't even see any errors.
Any help?
I also just noticed that my wastebasket no longer works. Has anything major happened to nautilus? I think that's where the problem may be/ I checked the logs and they mostly show udev picking it up but it never shows in nautilus, not even an icon. Also the only associated error is
kernel: sd 6:0:0:0: [sdf] Assuming drive cache: write through
Last edited by MrGone (2009-09-30 21:59:38)

No i'm just using the one in extra i believe.
Last edited by MrGone (2009-09-30 19:21:47)

Annoying inconsistent udev/HAL/dbus external USB HDD detection...

Hello! I am a newbie to ARCH. When I first installed it, my USB drive almost always was detected AND auto-mounted upon booting into GNOME. It was beautiful. This shows that I have DBUS/HAL and all that nice stuff installed.
After a while, I decided to update my daemons as below. (i added portmap and fam --- that is all!)
DAEMONS=(syslog-ng network portmap fam dbus hal netfs crond alsa openntpd gdm)
Anyway... now the USB external drive is never automatically detected or mounted, period. I have to boot into GNOME, THEN unplug the USB cable... wait a bit... plug it back in. Then it is detected. Then I have to manually do:
mount /dev/sda5 /media/usb
mount /dev/sda6 /media/usb
to mount them. This is very annoying.
Is there anyway to get consistent detection and auto-mounting behavior??? It was working fine the first few times. No idea where I went wrong, friends.
btw... i am in the proper groups for my user too, though that is irrelevant because if i wasn't, it would still show up, just give me a security msg preventing mounting - GROUPS = disk wheel ftp dbus hal network video audio optical storage camera power users pacman
Last edited by darweth (2007-04-07 13:42:39)

Well, I eventually discovered the necessity of gnome-volume-manager and all is fine now. No more help needed. Weird that the behavior was bipolar w/o it though.

Ivman hal dbus problem

I tried automount and this with the packages from current and extra
when starting ivman I get this:
libhal.c 644 : Error connecting to system bus: Failed to connect to socket /var/lib/dbus/system_bus_socket: Connection refused
** (process:3869): WARNING **: manager.c/656: Failed to initialize HAL!
if I start hal it seems to start but later does not have a process so I think it stops again:
12:08:17.822 [I] hald.c:394: hal 0.4.7
12:08:17.823 [I] hald.c:396: Will daemonize
12:08:17.823 [I] hald.c:406: Becoming a daemon
ps ax|grep hal shows me nothing
finally dbus:
dbus gets started at boottime and has this lines when I ps for it:
3746 tty1 S 0:00 /usr/bin/dbus-launch --sh-syntax --exit-with-session
3747 ? Ss 0:00 dbus-daemon-1 --fork --print-pid 8 --print-address 6
so somehow some kind of dbus is running but hal can't connect to it so ivman wont start.
I could not find any information about this problem.
any help appreciated
thanks
wabi

Hi
I got some other problem hal related
It was running since weeks without problems..automounting usb, cd etc.
since the latest update, where hal and dbus was updated some very very strange things happen.
After fresh start I had normally 77 processes running, mounting was ok etc.
Now...after a restart I got 150 processes running increasing every few seconds.
After a minute or so I got 280. 200 are hal and hotlug.hal related.
and the Hard Drive and CPU is always showing actibities. never happened before.
...and automounting isn´t working anymore too.
What is this?
tia
mic

Autofs not working

Hi,
I tried auto mounting my USB key drive and USB camera to automount but not sure where I am missing.
Here is my approac.
I followed this wiki!
http://wiki.archlinux.org/index.php/AutoFS_HowTo
my rc.conf reads
DAEMONS=(syslog-ng network netfs crond kdm alsa hal autofs dbus)
and my fstab
/dev/sdb1 /mnt/usb vfat noauto,users,rw 1 0
However, everytime I have to do a manual mount of /mnt/usb.
I would like my usb drive and camera to be auto mounted and the suggestions for appropriate application to open. Eg with the camera, digicam should open.
I am using kdemod.
EDIT::
When i do lshal and then connect the USB drive I get this output
bash-3.2# lshal -m
Start monitoring devicelist:
08:13:37.895: usb_device_66f_82e0_23DE9147973C4E9A added
08:13:37.928: usb_device_66f_82e0_23DE9147973C4E9A_if0 added
08:13:37.972: usb_device_66f_82e0_23DE9147973C4E9A_usbraw added
08:13:42.933: usb_device_66f_82e0_23DE9147973C4E9A_if0_scsi_generic added
08:13:42.941: usb_device_66f_82e0_23DE9147973C4E9A_if0_scsi_host added
08:13:42.941: usb_device_66f_82e0_23DE9147973C4E9A_if0_scsi_host_scsi_device_lun0 added
08:13:43.134: storage_serial_T_sonic_610_23DE9147973C4E9A_0_0 added
08:13:43.345: volume_uuid_B84A_0717 added
So hal is detecting a USB drive, but does not automount.
Regards,
Abhay
Last edited by abhaysahai (2007-06-12 02:45:26)

My suggestion is to try the hal/dbus aprotch instead of autofs. Atleast for me it has been alot more just works(tm)
http://wiki.archlinux.org/index.php/HAL
When it comes to the camera, Is it set up for mass storage or ptp?
Edit2: Oh, and you shoudn't need to set up a line in fstab. That can actualy breake automounting.
Last edited by Mr.Elendig (2007-06-12 07:39:31)

[SOLVED] Xorg and mouse with HAL doesn't work

Hi
I recently reinstalled Arch Linux and I have some problems... My mouse isn't working - at all! I'm using an HP Compaq 6510b.
I've installed the following packages:
* xf86-input-evdev
* hal
* dbus
I don't have an xorg.conf file at all, as I heard that hal should solve everything automagically for me. This seems to not be the case?
Any ideas? Thanks
Last edited by skorpan (2009-06-05 18:41:51)

Yeah, I'm doing that!
BTW, Xorg.0.log is here: http://dpaste.com/51933
Last edited by skorpan (2009-06-05 17:58:31)

Can't get HAL to work properly

Hello everybody! This is the first distro I've ever tried which gives you substantial control over the installation process, and I like that a lot, but there are some things I probably didn't manage to do well. One of those is getting HAL to work as I tell it to via policies. I need for it to recognize my italian keyboard layout and automount ntfs partitions. I followed the instructions on the wiki, but I probably messed up, so can somebody briefly sum up the steps I need to make HAL do what I need?
Last edited by eFFeeMMe (2009-04-10 12:12:35)

Just correcting this so that any beginners who stumble on this wont get confused/misguided
Neo_The_User wrote:
i love being in-depth explaining everything so i'm sorry if i couldn't make it as breif as you wanted it to be
as root or sudo:
pacman -Syy
pacman -Syu
pacman -Sy hal dbus fam
nano /etc/rc.conf
In DAEMONS it should look like this (sort of:)
DAEMONS=(!syslog-ng !netfs !crond network fam hal dbus alsa gdm)
DAEMONS=(syslog-ng crond network fam dbus hal alsa )
but basically it depends on what services you want to run.
starting gdm in inittab is better.
Now you can turn hal on 2 different ways. Reboot or just turn on. To turn on without reboot:
/etc/hal restart
/etc/rc.d/hal start
(You should probably turn on dbus too)
/etc/dbus restart
(And fam)
/etc/fam restart
everything is /etc/rc.d/daemonname start
Now after you do all that do this as root (log in AS root because it will be easier for me to tell you what exactly you need to do)
Xorg -configure
Now I forget off the top of my head what the exact location is so if it says No such file or directory in the first command, do the second one:
cp -L -vi /root/xorg.conf.new /etc/X11/xorg.conf
No luck? Try this:
cp -L -vi /home/root/xorg.conf.new /etc/X11/xorg.conf
There is no /home/root
Now you can install gdm and X and all that:
pacman -Sy gdm
Replace gnome with lxde or xfce4 or whatever
pacman -Sy gnome
Now fonts:
pacman -Sy ttf-bitstream-vera ttf-dejavu ttf-ms-fonts ttf-liberation
Turn on ntfs in DAEMONS though as I have mine off. Take the exclamation point out.
Hope that works!
I hope you meant netfs or nfsd here. ntfs-3g doesn't need a daemon AFAIK

Problem with hal[hal 0.5.2-3]

i test ubuntu5.04[gnome] and when put a pendrive add automatic entry in mtab but in arch not[kde], so, try an lshal in ubuntu and not problem, but in arch are problems:
lshal version 0.5.2
*** [DIE] lshal.c:dump_devices():72 : Couldn't obtain list of devices
and /etc/rc.d/hal start dont work(dont start hal), dbus[dbus 0.33-1] work ok, what can do or what is wrong???
other thing, before arch use mandrake, and mandrake[kde] use supermount, so connect a external device[cdrom, dvd, pendrive] and got a icon on the desktop, can "kde"[not mandrake] do the same, like gnome, connect a external device and got and icon on the desktop???.or is necesary go to the fuc*i** icon of "system"[is like my pc in win...] ???. And use hwd, not hotplug.

Dbus version is now 0.50-4 , upgrade.
Do you have dbus and hal in your daemons line in rc.conf ?
make sure dbus is listed BEFORE hal.

Gnome HAL and GVM

Hi,
Im still struggeling to get Gnome-Volume-Manager working.
Since the last upgrade of HAL and GVM every hardware i have tried has been recognized. :-)
I still however cant get the automont to work.
The device gets recognized and HAL creates the devices.
fstab-sync kicks in and creates nice entries in fstab and creates directories under /media
But the actual mount does not work. Automount does not work. When trying to mount the device as myself i get:
mount: only root can mount /dev/sda1 on /media/usbdisk
and when trying as root:
mount: wrong fs type, bad option, bad superblock on /dev/sda1,
or too many mounted file systems
When looking into /var/log/kernel
FAT: Unrecognized mount option "pamconsole" or missing value
What is this "pamconsole" stuff? Its in the corresponding line in my fstab.
Seems like either im missing some package or a badly configured one?

alexthelion wrote:in /usr/share/hal/fdi/90defaultpolicy/storage-policy.fdi you can disable that pamconsole thing. And you can change /media to /mnt, if you want.
I have noticed that one. But if i understand things correctly. You should not change anything in that file but instead add files in the hal/fdi/95userpolicy instead.
To be honest, I'm a little bit confused about all those new hardware things. udev, hal, dbus, g-v-m. it's not easy to understand which component does what.
For example: if I plug in a USB Mass storage, then hald emits some message via dbus, right? But it seems that hald is also directly calling fstab-sync. So what is g-v-m doing in this scenario? Obviously not the mounting part, or what?
My understanding is this. (Please correct me if im wrong)
UDEV is a userspace replacement for devfs and is responsible for creating the device files in /dev
HAL is a hardware abstraction layer that listens to hotplug and keeps an inventory of the hardware on your machine. HAL also uses dbus the new message bus to notify anyone about changes etc.
Then there are two important listeners for these events.
fstab-sync which listens to added and removed devices. And creates/alters the files in /media and the /etc/fstab file.
Finaly we have GVM, which also listens to these events, and does the actual mounting.
I think that there is something wrong with the util-linux package. util-linux contains among other things the mount command. And it seems like it is mount who does not understand the pamconsole stuff.

How do you get hal working?

What is the proper way to get hal working ?
Do I need to start gnome-volume-manger ?
How do you get hal started seems that adding it to rc.conf [DAEMONS] does not work
Its odd never had many problems mounting until recently
Or is it just again lol
MrG

Mr Green wrote:But I would rather get it working in DEAMONS do you use @ in front of hal & dbus?
No. I remember when I installed GNOME I added
portmap fam dbus hal
to the DAEMONS line in rc.conf, without @
Then I installed gnome-volume-manager and set it up. That picked up my ipod just fine, without any udev rule written by me.

Hal 0.5.14-1 does not mount some usb drives correctly

Hi folks
When I try to mount a USB hard disk (with KDE 4.3.4), it tries to mount it at some wrong path used by another USB hard disk. Or I have to mount it as root, or even as root it still doesn't work right... pfff I'm really disappointed by this showstopper...
For example, I own a LaCie hard disk (/media/disk), a Iomega one (/media/IOMEGA) and a LaCie mobile disk (no power cable, /media/MobileDisk):
- When I try to mount the Iomega one, it works fine, as normal user;
- When I try to mount the LaCie one, it fails, independently of the fact that the Iomega drive is mounted or not, with the following message:
Unable to run the command specified. The file or folder file:///media/IOMEGA does not exist.
Looks like it wants to mount the LaCie one where the Iomega one is/should be mounted...
- When I connect the LaCie hard disk, the directory /media/MobileDisk
is created, instead of /media/disk
, and when as root I try to manually mount the hard disk, it says:
ntfs-3g: Failed to access volume '/dev/sdb1': No such file or directory
Maybe there's some erroneous entry in some cache or data used by hal/dbus? I don't know how they work and how to activate their logging systems and then where to find the logs...
Maybe there's a way to simply completely wipe out hal/dbus/consolekit/policykit/... configuration data without having to reinstall the complete system?
I have:
hal 0.5.14-1
dbus-core 1.2.16-1
dbus 1.2.16-1
dbus-glib 0.82-2
dbus-python 0.83.0-2
I start KDM using /etc/inittab, as described in the wiki. I've put "/usr/sbin/console-kit-daemon" in /etc/rc.local and have modified /etc/inittab so that it starts kdm with: "x:5:respawn:/usr/bin/ck-launch-session /usr/bin/kdm -nodaemon"!
Is this the right setup, equivalent to the one with xinitrc?
The same setup works fine on my laptop.
I've got the impression that hal/dbus/... confounds my drives and does not know where to mount them...
Downgrading to hal 0.5.13-idontrememberwhatcifer does not solve the issue, the system is kept up to date with "pacman -Syu" about once a day and it still doesn't work...
Some clue?
Thanks and happy new year

OK something happened that I can't explain...
I just controlled about all files related to hal/dbus/mounting etc and, I don't know why, all devices I've mounted had a corresponding line in fstab... really weird.
I juste deleted those lines, and, well, mounting seems to work again
So this issue is solved
And finally Arch Linux is again my favorite distro
Last edited by yannick555 (2010-01-03 14:37:55)

Serious hal problem

Hi guys
Every time i click on CD or HDD icon i get following error:
Error org.freedesktop.DBus.Error.AccessDenied.
Details:
A security policy in place prevents this sender from sending this message to this recipient, see message bus configuration file (rejected message had interfave "org.freedesktop.Hal.Device.Volume" member "Mount" error name "(unset)" destination "org.freedesktop.Hal")
Another question: is it possible that this problem, in any way, caused my HDD crash (the one that i tried to mount)?

Well, I have the exact same problem and I've done all of the above, except that I also tried adding users hal, dbus and my own user to the suggested groups (storage, optical). however, the problem persists as described in the first post in this thread.
Correction:Uhm this is embarrising, but actually the only thing I had left to do after my other fiddling was a restart :rolleyes:g
It's now working as I wanted it too, and I also got around to take out the fstab entries for redundant cdrom and dvdrom entries (that the Arch Installer put there...) Sometimes you mustn't forget what running Gentoo has thought you
To possibly be of any help, here's my steps to resolve this issue that worked for me (possibly some unrelevant and redundant)
Do in terminal:
# pacman -Rd hal hal-device-manager hal-info
# pacman -S hal hal-device-manager hal-info
# gpasswd -a user optical
# gpasswd -a hal optical
# gpasswd -a dbus optical
# gpasswd -a user storage
# gpasswd -a hal storage
# gpasswd -a dbus storage
Then restart your system, carefully monitoring that dbus and hal are starting properly at boot up (or try to start the init scripts with "/etc/rc.d/dbus start" and then "/etc/rc.d/hal start" once your inside your DE)
Well it worked for me, so maybe it works for you
Last edited by killerrabbit (2007-04-29 17:47:34)

solved error: cannot resolve dependencies for "hal"

Hello all,
I tried doing a pacman -Syu today and recieved the following: error: cannot resolve dependencies for "hal"
Then I did a pacman -S dbus-glib and got : dbus-glib: not found in sync db
then I did pacman -S dbus and recieved the same message.
Then I did pacman -S hal and got:
error: cannot resolve dependencies for "hal":
"dbus-glib" is not in the package set
Am I missing something? Any help would be greatly appreciated.
Oh man, in my fleeting moment of panic I didn't think things through and posted right away.
I commented the following lines in pacman.conf and now it works
#XferCommand = /usr/bin/aria2c -s 2 -m 2 -o %o %u
#XferCommand = /usr/bin/pacget %u %o
Not too sure why, but I am happy all is working.
Last edited by Cancel (2007-02-17 08:15:54)

I followed this wiki and it did make a difference. It is still very fast downloading packages.
http://wiki.archlinux.org/index.php/Imp … erformance
I haven't had a chance to uncomment those lines again to see if it still gives me errors, but you might have luck trying what the wiki suggests.
After following the wiki, pacman tries a bunch of servers to give you the best speed possible (if I remember correctly). I hope this helps you.

Autofs or hal/dbus ?

Similar Messages

Maybe you are looking for