1 |
Apparently, though unproven, at 14:51 on Monday 01 November 2010, Harry Putnam |
2 |
did opine thusly: |
3 |
|
4 |
> Alan McKinnon <alan.mckinnon@×××××.com> writes: |
5 |
> |
6 |
> |
7 |
> [...] |
8 |
> |
9 |
> >> > What shell are you using? |
10 |
> >> > What is the output of "echo $HOME"? |
11 |
> >> |
12 |
> >> My shell is xterm... and was just updated to: |
13 |
> >> Wed Oct 27 10:15:06 2010 >>> x11-terms/xterm-262 |
14 |
> > |
15 |
> > That's the terminal. |
16 |
> > |
17 |
> > What shell do you use/ |
18 |
> |
19 |
> Sorry... still asleep... bash-4.1_p9 |
20 |
> |
21 |
> |
22 |
> Willie Wong <wwong@××××××××××××××.EDU> writes: |
23 |
> |
24 |
> [...] |
25 |
> |
26 |
> > Before we go further, when you said `ls' will not complete against |
27 |
> > $HOME, which of the following scenario did you mean? |
28 |
> > |
29 |
> > a) you typed `ls $HOME' as a user (the one I think Alan thinks you |
30 |
> > |
31 |
> > mean) |
32 |
> > |
33 |
> > b) you type `ls' while in your home directory (/home/reader) |
34 |
> > c) you typed `ls /home/reader' ? |
35 |
> |
36 |
> All three of those produce the same effect. Also if run from root |
37 |
> shell against my users home `# ls /home/reader' |
38 |
> |
39 |
> The command just hangs there as described. |
40 |
> |
41 |
> However, as indicated earlier... my user or root can run `ls' against |
42 |
> any other directory like normal. |
43 |
> |
44 |
> ls /etc |
45 |
> |
46 |
> Shows the content of /etc |
47 |
> |
48 |
> ls /home/reader |
49 |
> |
50 |
> Hangs eternally. |
51 |
> |
52 |
> Also, as mentioned, I can view /home/reader with emacs in dired |
53 |
> (directory) mode, Which oddly enough uses ls and ls switches for that |
54 |
> display far as I know. |
55 |
> |
56 |
> However, vim will not display /home/reader... and |
57 |
> hangs eternally... requiring the shell to be killed. |
58 |
> |
59 |
> Viewing $HOME with emacs shows nothing untoward that I see. I thought |
60 |
> maybe I'd somehow acquired thousands of files and `ls' was just taking |
61 |
> forever to display the list... but no... nothing unusual in $HOME. |
62 |
|
63 |
|
64 |
I suspect directory corruption in /home - is it a separate partition? |
65 |
|
66 |
I don't recall if you mentioned this or not, do you get the same result if you |
67 |
run "ls $HOME" as root? root's home dir is not on /home so that will vbe a |
68 |
valuable clue. If that command works, do an fsck on /home |
69 |
|
70 |
|
71 |
-- |
72 |
alan dot mckinnon at gmail dot com |