Date: Thu, 08 Oct 2009 16:55:09 -0500 From: "Jeremy Messenger" <mezz7@cox.net> To: "Ted Faber" <faber@isi.edu> Cc: freebsd-gnome@freebsd.org Subject: Re: automounting and glabel Message-ID: <op.u1h4ivij9aq2h7@localhost> In-Reply-To: <20091008163923.GB79434@zod.isi.edu> References: <20091005180808.GE38781@zod.isi.edu> <1254976110.99325.107.camel@shumai.marcuscom.com> <20091008163923.GB79434@zod.isi.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 08 Oct 2009 11:39:23 -0500, Ted Faber <faber@isi.edu> wrote: > On Thu, Oct 08, 2009 at 12:28:30AM -0400, Joe Marcus Clarke wrote: >> On Mon, 2009-10-05 at 11:08 -0700, Ted Faber wrote: >> > hald & nautilus seem to not automount USB memory disks with glabels on >> > them, even if that label is a single character (no spaces). Is there >> > some configuration file I need to change to get the mount to happen? >> > >> > I didn't include all the debug information, because I see this >> behavior >> > over several systems and over FreeBSD7-STABLE and FreeBSD-8RC1. >> > >> > If it's a bug, here's how I can reproduce it: >> > >> > Insert an unlableled USB memory stick without a glabel. >> > Nautilus will mount it. >> > Unmount it from the menu and make sure it no longer shows up in df >> > put a glabel on: >> > >> > $ sudo glabel label A /dev/da0s1a >> > >> > Pull the drive out, and put it back in. /dev/label/A and /dev/da0s1 >> > will appear in the FS, but the drive will not be mounted by Nautilus. >> > >> > $ sudo glabel clear /dev/da0s1 >> > >> > Remove and replace and the drive will mount again. >> >> You may want to try with hal-0.5.13 in MarcusCom CVS at >> http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi/ports . > > Is there a place to get a tar of the port or an easy way to pull it down > from cvsweb all at once? A target for cvsup or portsnap? Yes, the document is at http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi/ .. Cheers, Mezz >> http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi/ports . If that >> doesn't work, you will need to follow the instructions at >> http://www.freebsd.org/gnome/docs/halfaq.html to properly report a >> problem with hal. > > This is attached. > > Specifically there is a uname -a, pkg_info listing and an environment > dump. As you can see this is from a freshly portsnap updated tree. > > Two traces and lshal outputs are attached. The first is > from inserting and mounting the un-glabeled drive and the second is from > the glabeled drive. Between the two runs I unmounted the drive, killed > the debug instance of hal, added the glabel as described above (the > single character 'A'), and removed the drive. I restarted hal (with the > debug options using the script command) and plugged the drive in. The > first lshal is with the un-glabelled drive inserted (and mounted) and > the second is with the glabeled drive. It is the same physical drive. > > Finally the dmesg from a verbose booted kernel is included. It is the > dmesg from the session described above. > > To be clear, the attachments are (in order): > uname > pkg_info > /usr/sbin/env > /etc/fstab > trace of hal output when mounting un-glabelled drive > lshal output with un-glabelled drive mounted. > mount command output with un-glabelled drive mounted. > trace of hal output when mounting glabelled drive > lshal output with glabelled drive inserted but not mounted. > mount command output with glabelled drive inserted but not mounted. > dmesg > > Please let me know if I can provide more info. -- mezz7@cox.net - mezz@FreeBSD.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?op.u1h4ivij9aq2h7>