Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 25 Mar 2008 18:59:41 +0300
From:      Vladimir Grebenschikov <vova@fbsd.ru>
To:        Joe Marcus Clarke <marcus@FreeBSD.org>
Cc:        freebsd-gnome <freebsd-gnome@FreeBSD.org>
Subject:   Re: GNOME 2.22 has been released!
Message-ID:  <1206460781.1675.29.camel@localhost>
In-Reply-To: <1206459565.93352.18.camel@shumai.marcuscom.com>
References:  <1206336222.49828.11.camel@shumai.marcuscom.com> <1206451201.1675.7.camel@localhost> <1206459565.93352.18.camel@shumai.marcuscom.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 2008-03-25 at 11:39 -0400, Joe Marcus Clarke wrote:

Thank you for answers.

> > But it still stalls while scanning folders,
> > like here:
> > http://212.24.36.217/vova/busy-evolution.png
> >=20
> > It goes trough long long loop (about minute or even more)
> > truss shows lots of:
> > poll({6/POLLIN 11/POLLIN|POLLPRI 12/POLLIN|POLLPRI 14/POLLIN|POLLPRI 15=
/POLLIN|POLLPRI 16/POLLIN|POLLPRI 18/POLLIN|POLLPRI 17/POLLIN|POLLPRI 23/PO=
L
...
> > poll({6/POLLIN 11/POLLIN|POLLPRI 12/POLLIN|POLLPRI 14/POLLIN|POLLPRI 15=
/POLLIN|POLLPRI 16/POLLIN|POLLPRI 18/POLLIN|POLLPRI 17/POLLIN|POLLPRI 23/PO=
L
> > LIN|POLLPRI},9,-1) =3D 1 (0x1)
> > etc ...
> >=20
> > Probably there is such fix for that problem also ?=20
> > (I have large tree of folders)
>=20
> This is a known bug with imap-uw.  There is a hack for e-d-s (attached)
> which prevents it at the cost of not being able to subscribe to new
> folders.

Hm... I have no imap folders et all, just usual mail folders, this patch
will still help me ?=20
=20
> > Another strange thing is non-desired auto-mount.
> > I have=20
> > $ egrep '/m/[CD]' /etc/fstab
> > /dev/ad0s1              /m/C                    ntfs    rw,noauto,-C=3D=
koi8-r     0       0
> > /dev/ad0s3              /m/D                    msdosfs rw,noauto,-u=3D=
operator,-g=3Doperator,-m=3D775,-l,-L=3Dru_RU.KOI8-R,-W=3Dkoi2dos  0 0
> > $
> >=20
> > Both have "noauto" keyword in fstab, but after upgrade they mounted
> > automatically.
> > And, what is totally strange, C drive appears on desktop, but D drive
> > does not.
>=20
> I don't have any fixed NTFS or FAT volumes so you'll need to analyze
> this.  The code that handles the auto-mounting can be found in
> devel/gvfs and devel/glib20 (libgio).  I would think that you shouldn't
> be able to mount these at all unless you own /m/C and /m/D and you have
> vfs.usermount set to 1.

real ownership answers why it shows only C on desktop
=EF=BB=BFdrwxrwxr-x  1 operator  operator  8192 Jan  1  1980 /m/D
drwxr-xr-x  2 vova      wheel      512 Aug  4  2007 /m/C

yes, I have vfs.usermount=3D1

> If HAL is claiming the volumes, and Nautilus is mounting them using
> gnome-mount, then you could merge the
> storage.automount_enabled_hint=3Dfalse property to turn this off.

some-thing like:=20
$ hal-device | less
0: udi =3D '/org/freedesktop/Hal/devices/volume_uuid_8CF07973F07963FC'
  info.parent =3D '/org/freedesktop/Hal/devices/volume_part1_size_322198405=
12'  (string)
  volume.is_partition =3D false  (bool)
  volume.mount_point =3D ''  (string)
  info.udi =3D '/org/freedesktop/Hal/devices/volume_uuid_8CF07973F07963FC' =
 (string)
  info.subsystem =3D 'block'  (string)
  volume.ignore =3D false  (bool)
  volume.fsversion =3D '3.1'  (string)
  info.capabilities =3D { 'block', 'volume' } (string list)
  volume.fsusage =3D 'filesystem'  (string)
  info.product =3D 'Windows'  (string)
  org.freedesktop.Hal.Device.Volume.method_names =3D { 'Mount', 'Unmount', =
'Eject' } (string list)
  info.category =3D 'volume'  (string)
  volume.fstype =3D 'ntfs'  (string)
  org.freedesktop.Hal.Device.Volume.method_signatures =3D { 'ssas', 'as', '=
as' } (string list)
  volume.label =3D 'Windows'  (string)
  info.interfaces =3D { 'org.freedesktop.Hal.Device.Volume' } (string list)
  org.freedesktop.Hal.Device.Volume.method_argnames =3D { 'mount_point fsty=
pe extra_options', 'extra_options', 'extra_options' } (string list)
  volume.uuid =3D '8CF07973F07963FC'  (string)
  org.freedesktop.Hal.Device.Volume.method_execpaths =3D { 'hal-storage-mou=
nt', 'hal-storage-unmount', 'hal-storage-eject' } (string list)
  block.device =3D '/dev/ntfs/Windows'  (string)
  volume.block_size =3D 512  (0x200)  (uint64)
  volume.mount.valid_options =3D { 'ro', 'noexec', 'noatime', '-u=3D', '-g=
=3D', '-m=3D', '-a', '-i', '-C=3D', '-W=3D' } (string list)
  block.major =3D 0  (0x0)  (int)
  volume.size =3D 32219840512  (0x78073c000)  (uint64)
  block.minor =3D 95  (0x5f)  (int)
  volume.num_blocks =3D 62929376  (0x3c039e0)  (uint64)
  volume.is_mounted =3D false  (bool)
  block.is_volume =3D true  (bool)
  volume.is_disc =3D false  (bool)
  volume.is_mounted_read_only =3D false  (bool)
  block.storage_device =3D '/org/freedesktop/Hal/devices/storage_serial_5LZ=
1Q84Z'  (string)

# hal-set-property --udi /org/freedesktop/Hal/devices/volume_uuid_8CF07973F=
07963FC --key storage.automount_enabled_hint --bool false

Executed without error, will check on next boot.


> Joe

--=20
Vladimir B. Grebenschikov
vova@fbsd.ru



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1206460781.1675.29.camel>