Date: Tue, 20 Mar 2007 15:10:39 -0700 From: "Kevin Oberman" <oberman@es.net> To: gnome@freebsd.org Subject: Re: Curious behavior of HAL in 2.18 Message-ID: <20070320221039.EEC6245047@ptavv.es.net> In-Reply-To: Your message of "Tue, 20 Mar 2007 13:52:25 PDT." <20070320205225.C8C5545048@ptavv.es.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--==_Exmh_1174428639_33085P Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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 /dev. 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@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@es.net> > Sender: owner-freebsd-gnome@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? --==_Exmh_1174428639_33085P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) Comment: Exmh version 2.5 06/03/2002 iD8DBQFGAFvfkn3rs5h7N1ERAi4OAKCcIlR6NPsqKOijgwweYWYqcb/tZACfddXZ SPlRF/9yPKmX6+oOecBx2/s= =oDeP -----END PGP SIGNATURE----- --==_Exmh_1174428639_33085P--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070320221039.EEC6245047>