From owner-freebsd-gnome@FreeBSD.ORG Wed Mar 21 06:27:41 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 72E8C16A408 for ; Wed, 21 Mar 2007 06:27:41 +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 29AAC13C43E for ; Wed, 21 Mar 2007 06:27:39 +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 l2L6RM37055344; Wed, 21 Mar 2007 02:27:22 -0400 (EDT) (envelope-from marcus@marcuscom.com) From: Joe Marcus Clarke To: Kevin Oberman In-Reply-To: <20070321040849.1271545047@ptavv.es.net> References: <20070321040849.1271545047@ptavv.es.net> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-OXpYbk/p7gFCiF1GWj94" Organization: MarcusCom, Inc. Date: Wed, 21 Mar 2007 02:26:41 -0400 Message-Id: <1174458401.79605.54.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 06:27:41 -0000 --=-OXpYbk/p7gFCiF1GWj94 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Tue, 2007-03-20 at 21:08 -0700, Kevin Oberman wrote: > > From: Joe Marcus Clarke > > Date: Tue, 20 Mar 2007 23:54:21 -0400 > >=20 > > On Tue, 2007-03-20 at 15:10 -0700, Kevin Oberman wrote: > > > 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 i= n > > > /dev. > > >=20 > > > I can understand this triggering HAL, but I don't know why it wants t= o > > > alway remount all of the system partitions. > >=20 > > Please provide a step-by-step procedure of what you're doing to create > > this behavior as well as the version of FreeBSD. >=20 > Only one step: > mdconfig -f file > or > mdconfig -d -u 1 > In stable, the first would have been "mdconfig -a -t vnode -f file". >=20 > FreeBSD slan.es.net 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Mon Mar 19 09:07:= 43 PDT >=20 > A couple of seconds after I issue the command (which creates or deletes > /dev/md1), I get the messages. >=20 > All ports are current except p5-Cairo which won't build the new version. 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 --=20 PGP Key : http://www.marcuscom.com/pgp.asc --=-OXpYbk/p7gFCiF1GWj94 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) iD8DBQBGANAhb2iPiv4Uz4cRAk6QAJ48SIW5zQjv5uftK4Ico1eQNV9W1wCgpL7R cc06i7h2BCnXdknmLa4CQz8= =JGiq -----END PGP SIGNATURE----- --=-OXpYbk/p7gFCiF1GWj94--