1 |
On Thursday 11 February 2010 19:58:25 ubiquitous1980 wrote: |
2 |
> With this command or similar, I made my directory and one file in / |
3 |
> unreadable: |
4 |
> |
5 |
> for entry in $(find $HOME); do $entry >> found; done |
6 |
> |
7 |
> the same of output for ls is similar: |
8 |
> |
9 |
> ????????-k?x?B?{????U?I?3s?? |
10 |
> ???N???Q |
11 |
> ?ܝw?Ϭw??9c̃}}Wz????Ǹ??t |
12 |
> Ƿ~??? |
13 |
> ?^8?O? |
14 |
> ?^????cB?f???????v????????V?!?@ |
15 |
> ???8%??????{??8?y??R??g?? |
16 |
> ??=c |
17 |
> ?$??????̝????????????~Ќ?t?)i}ˌW?6? |
18 |
> ??:????G?x??g*D???S(?I%?=?m?ۼVݶT??ն)u??K[(????[??4?u???g?_??1M???QL?8*9?P |
19 |
> 㓋?8M??4=?έ?w3?m?'?Dv??u? ?s?Ƭ????A?q??a]??~:??????.Kd??뗕oi?y????6:˿??? |
20 |
> N}Y?C????ậ?WŠ?W???K0???vY? Z?1?? |
21 |
> ?U0?T*?A??̻?ɸ?ȶ?IJ??????????????????? |
22 |
> |
23 |
> Any ideas on how to fix this? |
24 |
|
25 |
|
26 |
Is the output given from the same shell session in which you ran the command? |
27 |
|
28 |
Switch to a text console (Ctrl-Alt-Fx) and ls things there, perhaps the |
29 |
garbage dumped to the screen in your for simply upset the terminal emulation. |
30 |
|
31 |
|
32 |
-- |
33 |
alan dot mckinnon at gmail dot com |