Date: Fri, 03 Nov 2006 14:31:36 -0500 From: Joe Marcus Clarke <marcus@marcuscom.com> To: Kevin Oberman <oberman@es.net> Cc: gnome@freebsd.org Subject: Re: HAL taking over Message-ID: <1162582296.4927.63.camel@shumai.marcuscom.com> In-Reply-To: <20061103192849.1B34A45053@ptavv.es.net> References: <20061103192849.1B34A45053@ptavv.es.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-TGG1F1LLKvcx78gR3vzP
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
On Fri, 2006-11-03 at 11:28 -0800, Kevin Oberman wrote:
> > From: Joe Marcus Clarke <marcus@marcuscom.com>
> > Date: Fri, 03 Nov 2006 14:04:12 -0500
> >=20
> > On Fri, 2006-11-03 at 10:54 -0800, Kevin Oberman wrote:
> > > > From: Joe Marcus Clarke <marcus@marcuscom.com>
> > > > Date: Thu, 02 Nov 2006 23:29:29 -0500
> > > >=20
> > > > On Thu, 2006-11-02 at 19:53 -0800, Kevin Oberman wrote:
> > > > >=20
> > > > > The partition that did not show a label looks fine when I do a du=
mpfs> on
> > > > > it, so the tunefs did the trick.
> > > >=20
> > > > You need to restart hald, and re-login to GNOME for this to take ef=
fect> .
> > > > lshal should show a volume.label property with your label. If it d=
oes
> > > > not, then gnome-vfs will not show a name.
> > >=20
> > > But I did and it does! I logged out of Gnome and restarted all three
> > > daemons in order dbus, polkitd, and hald. Then I restarted Gnome.
> >=20
> > You might want to make sure gnome-vfs-daemon actually died, and was
> > respawned. If not, it will hold on to the old volume name.
>=20
> I also tried rebooting the system. (It's my laptop, so it got rebooted
> this morning when I got to work.) No improvement.
> >=20
> > >=20
> > > udi =3D '/org/freedesktop/Hal/devices/volume_label_aux'
> > > volume.mount.valid_options =3D {'ro', 'noexec'} (string list)
> > > org.freedesktop.Hal.Device.Volume.method_execpaths =3D {'hal-storag=
e-mo> unt', 'hal-system-storage-unmount', 'hal-system-storage-eject'} (stri=
ng lis> t)
> > > org.freedesktop.Hal.Device.Volume.method_signatures =3D {'ssas', 'a=
s', > 'as'} (string list)
> > > org.freedesktop.Hal.Device.Volume.method_names =3D {'Mount', 'Unmou=
nt',> 'Eject'} (string list)
> > > info.interfaces =3D {'org.freedesktop.Hal.Device.Volume'} (string l=
ist)
> > > block.storage_device =3D '/org/freedesktop/Hal/devices/storage_seri=
al_N> T02T53258CW' (string)
> > > info.product =3D 'aux' (string)
> > > info.udi =3D '/org/freedesktop/Hal/devices/volume_label_aux' (stri=
ng)
> > > block.is_volume =3D true (bool)
> > > volume.mount_point =3D '' (string)
> > > volume.is_mounted_read_only =3D false (bool)
> > > volume.is_mounted =3D false (bool)
> > > volume.num_blocks =3D 1048576 (0x100000) (uint64)
> > > volume.size =3D 536870912 (0x20000000) (uint64)
> > > volume.block_size =3D 512 (0x200) (uint64)
> > > volume.uuid =3D '' (string)
> > > volume.label =3D 'aux' (string)
> > > volume.fsversion =3D '2' (string)
> > > volume.fstype =3D 'ufs' (string)
> > > volume.fsusage =3D 'filesystem' (string)
> > > volume.ignore =3D false (bool)
> > > volume.is_partition =3D false (bool)
> > > volume.is_disc =3D false (bool)
> > > block.minor =3D 97 (0x61) (int)
> > > block.major =3D 0 (0x0) (int)
> > > block.device =3D '/dev/ad2s1a' (string)
> > > info.category =3D 'volume' (string)
> > > info.bus =3D 'block' (string)
> > > info.capabilities =3D {'block', 'volume'} (string list)
> > > info.parent =3D
> > > '/org/freedesktop/Hal/devices/volume_part1_size_39999504384' (string=
)
> >=20
> > On what mount point will this volume be mounted? At this point, it's
> > not mounted at all.
>=20
> Oh, yes, it is. It is mounted and I am able to edit files on it. But I
> did another lshal and hald does not seem to know it. It still shows an
> empty mount_point and both is_mounted_read_only and is_mounted are
> false.
>=20
> Something is clearly broken at this point.
Collect everything mentioned at
http://www.freebsd.org/gnome/docs/faq2.html#q19 .
>=20
> Another thing I just noticed: I have a vnode backed md device mounted on
> the system and it is not showing up at all. While I can believe that
> gnome-vfs and hald don't understand md devices, but could the fact that
> the backing file for the md volume is on the problem disk be related to
> the problem?
No.
Joe
--=20
PGP Key : http://www.marcuscom.com/pgp.asc
--=-TGG1F1LLKvcx78gR3vzP
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (FreeBSD)
iD8DBQBFS5kYb2iPiv4Uz4cRAjJVAJwImuTgwDmhYUW9+2d4sBJ7Ez3wPwCglJLz
a16tvMF1HNbVlQyKOmhQQ6I=
=hTOu
-----END PGP SIGNATURE-----
--=-TGG1F1LLKvcx78gR3vzP--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1162582296.4927.63.camel>