Date: Mon, 26 Mar 2007 08:43:11 -0700 From: "Kevin Oberman" <oberman@es.net> To: Joe Marcus Clarke <marcus@marcuscom.com> Cc: gnome@freebsd.org Subject: Re: Curious behavior of HAL in 2.18 Message-ID: <20070326154311.7F62F45042@ptavv.es.net> In-Reply-To: Your message of "Wed, 21 Mar 2007 12:21:40 EDT." <1174494100.92524.8.camel@shumai.marcuscom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--==_Exmh_1174923791_70662P Content-Type: text/plain; charset=us-ascii Content-Disposition: inline > From: Joe Marcus Clarke <marcus@marcuscom.com> > Date: Wed, 21 Mar 2007 12:21:40 -0400 > > On Wed, 2007-03-21 at 08:48 -0700, Kevin Oberman wrote: > > > > I just tried this on 7-CURRENT amd64 with up-to-date ports. I do not > > > see this behavior. What other HAL configuration have you done (e.g. > > > extra fdi files)? Can you try to isolate which process is trying to > > > mount these file systems (e.g. using ktrace or truss)? It is probably > > > happening via hald, but something is telling hald to do this. My guess > > > is gnome-volume-manager. > > > > > > Joe > > > > I don't think that this is relevant, but the file I was using as the > > backing store for the md device is about 2GB in size and is a valid ufs > > device. > > I tried with the 6.2-RELEASE boot.flp image since I don't have large > file system images lying around. I don't see how the size of the file > is relevant since only one md device node will be created. > > > > > I have no idea what an fdi file is. The only hal configuration I have > > done is to hal-storage-fixed-mount-change-uid.privilege and > > hal-storage-fixed-mount.privilege where I have added myself the the > > Allow i.e."Allow=uid:oberman". > > > > Of course, my system is running i386, not amd64. > > > > Any place to read up on the gnome-volume-manager? I didn't see much in > > the FAQ. > > Not specific to FreeBSD. It's basically the process that watches for > HAL changes, and executes configurable actions on those changes. If it > is the one responsible for kicking off the mount, it will narrow down > where to troubleshoot. > > Joe > > -- > PGP Key : http://www.marcuscom.com/pgp.asc Just to let you know, the latest hal update seems to have fixed this one. It no longer is trying to mount my system partitions when I create md ramdisks. Thanks! -- 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 --==_Exmh_1174923791_70662P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) Comment: Exmh version 2.5 06/03/2002 iD8DBQFGB+oPkn3rs5h7N1ERAi9VAJ9V2kTzb0lwa+tMfFFqr20ywYquWQCbBQVV OyuvoDXVB5iMrH77kPShuME= =pW/x -----END PGP SIGNATURE----- --==_Exmh_1174923791_70662P--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070326154311.7F62F45042>