-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Package: mount
Version: 2.19.1-5
Followup-For: Bug #618912

I want to ask what happens with the user, group and users mount/umount
as it is documented in the man page and worked for ages now.

The fstab options user, users and group do not work for many months now.
(In the original report I only tested "user".) This is a big constraint
of the functionality of mount.

- -- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (800, 'unstable'), (700, 'stable'), (60, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.0.8 (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) (ignored: LC_ALL set to 
de_DE)
Shell: /bin/sh linked to /bin/dash

Versions of packages mount depends on:
ii  libblkid1    2.19.1-5 
ii  libc6        2.13-21  
ii  libmount1    2.19.1-5 
ii  libselinux1  2.1.0-4  
ii  libsepol1    2.1.0-1.1

mount recommends no packages.

Versions of packages mount suggests:
ii  nfs-common  1:1.2.5-2

- -- no debconf information
Gruß
   Klaus
- -- 
Klaus Ethgen                              http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16   Klaus Ethgen <[email protected]>
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQGcBAEBCgAGBQJOtq2VAAoJEKZ8CrGAGfasj7YL/3CnZNUncpmFEaOwqh2mpdxj
KmnMis6dOk+3DmAHntDWEQ6EUNwa+MexfgokM/SnJYmnwZ/6Hy+BSgzaNhA8nPuL
oPdd5Md31zO6Zw4N6ztInEsSw/1ga/B9GPocrc6fPMbueS7/11rx6zv3wmIVmsoL
by/PxtKYZmYNcX8oLM29PszPL7jfluhW6YhzbUAxgqTYyJcEi0Vx6b12o1/YnHjk
mEe3O9sD5Nim/staVc/Ag5RR5/nBIgNjur5ATDMcQdzWW+Xj/PVOwrL2e1rJ2lJI
+NTENpPXfhSy1j9umuw/1EM//CfTeUvrhS0Y1++H03Z8C9AlBJvBDPp6EuO0353I
hym3Db/x6YElDL9Ag6rwcjgg6WHD9sQIId9IUXLc9V+TNJdgzAnhAWCIrs9OJEJ3
W/OIftTUjICQkfbk7he7mX/RWUL0FAu/DY1kN1/vwzbJmHn+IQBeAPbjA+3PMrif
2hEpgWjljJ2SujOqlBJWzR+Ouz0HTEmdfmO3YoC9nA==
=3621
-----END PGP SIGNATURE-----



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to