Re: Cannot use /media/ properly



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Alexey Salmin <alexey.salmin@xxxxxxxxx> writes:

Please post here output from the "mount" command after plugging the
storage media to make things more clear.

Alexey

On Mon, Oct 19, 2009 at 2:48 AM, Merciadri Luca
<Luca.Merciadri@xxxxxxxxxxxxxxxxx> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I am encountering a major problem which seems to be related to my
(actually su's) /media/ folder.

# ls -al | grep media
lrwxrwxrwx   1 root root    11 2009-07-17 17:01 cdrom -> media/cdrom
drwxrwxrwx   9 root root  4096 2009-10-18 21:00 media

seems pretty nice, but, when a device is mounted correctly, linked,
etc., and that I am able to access it with /media/, it always appear
as empty. For example, let's say that I plug a `disk1' key in one of
my USB ports. It is recognized, I can

# cd /media/disk1/

BUT, after this,

# ls -al
total 12
drwxr-xr-x  3 merciadriluca root 8192 2009-10-18 19:16 .
drwxrwxrwx 10 root          root 4096 2009-10-18 21:42 ..


and the folder is apparently empty. However, when I ls -al on another
(Debian-powered) PC, the ls -al's output is correct, and there are
several files. It is the same for any external DD, or any other mass
storage device (that is, my non el cheapo usb key is not faulty).

My first suspicion was /media's permissions, but

# ls -al | grep media
lrwxrwxrwx   1 root root    11 2009-07-17 17:01 cdrom -> media/cdrom
drwxrwxrwx   9 root root  4096 2009-10-18 21:00 media

is what I encounter on my `faulty' computer, and

# ls -al | grep media
drwxr-xr-x   4 root root  4096 2009-10-18 21:04 media

is what I can read on one of my `not faulty' computers (which has
actually no CDROM). The only difference seems to be in the `9' which
is a `4' on the `not faulty' computer, but, although I do not know
what this number aims at, it shouldn't be the cause of the problem,
should it?

Any help would be much appreciated.

- --
Merciadri Luca
See http://www.student.montefiore.ulg.ac.be/~merciadri/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>

iEYEARECAAYFAkrbcSgACgkQM0LLzLt8Mhz7fACgp8cAbMGYJmSjUtQVDiXntjuY
w4EAoJb1XiQFDq0sMDB1s8tIYChplpFf
=aJPj
-----END PGP SIGNATURE-----


--
To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx
with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx



--
To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx
with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx
Bump (as I gave the outpout of mount on Monday, 19).
- --
Merciadri Luca
See http://www.student.montefiore.ulg.ac.be/~merciadri/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>

iEYEARECAAYFAkrgrbYACgkQM0LLzLt8Mhx8eQCfaDyisXyG84FcNeYFf541rK2g
1usAn0r9U/aCx+Ja2rZJnQt+BOTL4nL1
=NRq3
-----END PGP SIGNATURE-----


--
To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx
with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx