--===============1410480986==
Content-type: multipart/signed; boundary=nextPart1867266.oHyPSEjFj9;
 protocol="application/pgp-signature"; micalg=pgp-sha1
Content-transfer-encoding: 7bit

--nextPart1867266.oHyPSEjFj9
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Em Ter=E7a-feira 20. Outubro 2009, =E0s 20.49.44, David Hubner escreveu:
> I am not sure if
>=20
> if (fstype =3D=3D "nfs" || fstype =3D=3D "nfs4" || fstype =3D=3D "smbfs" =
|| fstype =3D=3D
>  "cifs")
>=20
> is a good idea. Would have to updated for new network filesystems and cou=
ld
>  cause problems if naming changes. Maybe call mnt_fsname and check if a
>  '//' is at the beginning of the char*. I believe all network related nam=
es
>  start with a '//' in fsname.

Except for nfs, which uses servername:/export/path. But if you put both=20
approaches together, you may come up with a good heuristic algorithm for=20
detecting future network mounts.

=2D-=20
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
  Senior Product Manager - Nokia, Qt Development Frameworks
      PGP/GPG: 0x6EF45358; fingerprint:
      E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358

--nextPart1867266.oHyPSEjFj9
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iD8DBQBK3iemM/XwBW70U1gRAqrpAJ4s0VR4EA0HZRtptBJf1bJICUdNRgCfSv1h
psSovufDrWUP6lxG6McWkCU=
=0tMk
-----END PGP SIGNATURE-----

--nextPart1867266.oHyPSEjFj9--

--===============1410480986==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

--===============1410480986==--