On Thursday 27 September 2007, Dan Farrell wrote:
> On Wed, 26 Sep 2007 21:21:26 +0200
>
> Alan McKinnon <[EMAIL PROTECTED]> wrote:
> > Ouch. That's file system corruption. You need to fsck that disk
> > right now. I once saw similar stuff on a reiser filesystem and the
> > only thing that helped was --rebuild-tree. Good luck on your end.
>
> Wrong!  In this case the user probably has execute permissions on the
> directory so they can list the file names, but doesn't have read
> permissions on the files in the directory, so ls can't list the
> permissions, attributes, & so on.

Ah yes, you are right. I missed the 'd' in the 'd????????' part of the 
output, my bad.

If Herbert hasn't gotten this fixed yet, here are working permissions 
for the .ssh dirctory and contents;

[EMAIL PROTECTED] ~ $ ll -d /home/alan/.ssh/
drwx------ 2 alan alan 80 Feb 24  2007 /home/alan/.ssh//

[EMAIL PROTECTED] ~ $ ll /home/alan/.ssh/
total 13
drwx------  2 alan alan   80 Feb 24  2007 ./
drwxr-xr-x 96 alan alan 5088 Sep 27 09:01 ../
-rw-r--r--  1 alan alan 5229 Sep 10 22:44 known_hosts

alan


-- 
Optimists say the glass is half full,
Pessimists say the glass is half empty,
Developers say wtf is the glass twice as big as it needs to be?

Alan McKinnon
alan at linuxholdings dot co dot za
+27 82, double three seven, one nine three five
-- 
[EMAIL PROTECTED] mailing list

Reply via email to