1 |
I ran the commands without any problems and the disk seems to work fine, |
2 |
can i just remove those 2 lines from the bootmisc script until i find a |
3 |
better solution? or is it kind of a tactic a redneck that came from |
4 |
Texas Chainsaw Massacre would use? :P |
5 |
|
6 |
Thanks for the reply |
7 |
|
8 |
"Hmm, are you sure your disk drive isn't about to die?" <- disturbing, i |
9 |
hope not! :P |
10 |
|
11 |
Richard Fish wrote: |
12 |
> On 7/26/06, Rafael Barrera Oro <rafael@××××××××××××××××.ar> wrote: |
13 |
>> anyway, this also happens when cleaning /var/run and /var/lock |
14 |
> |
15 |
> Hmm, are you sure your disk drive isn't about to die? Any other disk |
16 |
> IO performance problems? |
17 |
> |
18 |
> What happens if you run the commands yourself manually after booting?: |
19 |
> |
20 |
> rm -f /tmp/.X*-lock /tmp/esrv* /tmp/kio* /tmp/jpsock.* /tmp/.fam* |
21 |
> rm -rf /tmp/.esd* /tmp/orbit-* /tmp/ssh-* /tmp/ksocket-* /tmp/.*-unix |
22 |
> |
23 |
> -Richard |
24 |
|
25 |
-- |
26 |
gentoo-amd64@g.o mailing list |