From owner-freebsd-gnome@FreeBSD.ORG Wed Mar 21 16:22:50 2007 Return-Path: X-Original-To: gnome@freebsd.org Delivered-To: freebsd-gnome@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 53DB516A4E0 for ; Wed, 21 Mar 2007 16:22:50 +0000 (UTC) (envelope-from marcus@marcuscom.com) Received: from creme-brulee.marcuscom.com (creme-brulee.marcuscom.com [24.172.16.118]) by mx1.freebsd.org (Postfix) with ESMTP id E877C13C4AD for ; Wed, 21 Mar 2007 16:22:49 +0000 (UTC) (envelope-from marcus@marcuscom.com) Received: from [192.168.1.4] (shumai.marcuscom.com [192.168.1.4]) by creme-brulee.marcuscom.com (8.13.8/8.13.8) with ESMTP id l2LGMN09060321; Wed, 21 Mar 2007 12:22:23 -0400 (EDT) (envelope-from marcus@marcuscom.com) From: Joe Marcus Clarke To: Kevin Oberman In-Reply-To: <20070321154809.2B80445047@ptavv.es.net> References: <20070321154809.2B80445047@ptavv.es.net> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-kU3g6ymJIgZSXCyQB45C" Organization: MarcusCom, Inc. Date: Wed, 21 Mar 2007 12:21:40 -0400 Message-Id: <1174494100.92524.8.camel@shumai.marcuscom.com> Mime-Version: 1.0 X-Mailer: Evolution 2.8.3 FreeBSD GNOME Team Port Cc: gnome@freebsd.org Subject: Re: Curious behavior of HAL in 2.18 X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Mar 2007 16:22:50 -0000 --=-kU3g6ymJIgZSXCyQB45C Content-Type: text/plain Content-Transfer-Encoding: quoted-printable 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. > >=20 > > Joe >=20 > 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.=20 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. >=20 > 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=3Duid:oberman". >=20 > Of course, my system is running i386, not amd64. >=20 > 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 --=20 PGP Key : http://www.marcuscom.com/pgp.asc --=-kU3g6ymJIgZSXCyQB45C Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQBGAVuRb2iPiv4Uz4cRAj7PAJ9GnEjIzuSvvY3pO/hKEbezQ3TcIACdF6XT uFTuxDmEBqXZiOi4Zc64f80= =ws4E -----END PGP SIGNATURE----- --=-kU3g6ymJIgZSXCyQB45C--