Curious behavior of HAL in 2.18
oberman at es.net
Tue Mar 20 22:10:40 UTC 2007
Following up my own message, It is not the mounting or umounting of a
system that triggers it. It is the creation or deletion of a device in
I can understand this triggering HAL, but I don't know why it wants to
alway remount all of the system partitions.
If it is relevant, the device created/destroyed is an md device.
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman at es.net Phone: +1 510 486-8634
Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751
> Date: Tue, 20 Mar 2007 13:52:25 -0700
> From: "Kevin Oberman" <oberman at es.net>
> Sender: owner-freebsd-gnome at freebsd.org
> Since my update to 2.18 (which went pretty smoothly on all three
> systems I have updated), I have seen an odd issue with HAL.
> Every time I make a change in devices, it tries to mount all of my
> system partitions again. I mean /, /var, /tmp, and /usr. It fails with
> "mount: /dev/ad0s3a : Operation not permitted", so it really does
> nothing, but it is annoying. Any idea what changed to cause this and how
> I can get it to stop?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 224 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-gnome/attachments/20070320/d094f43c/attachment.pgp
More information about the freebsd-gnome