Richard Adams wrote:
> Try reading 'man rm'.
> Quite possably what you need is;
> 'rm -- -filename'
> Files or directorys beginning with special chars, cannot be deleted even by
> root with just 'rm - '
It's very strage. I mean take a look. This is part of the fist
page of the output:
total 833165668
srwx----w- 1 13869 8736 892155456 Jan 9 1987 #61186=
cr----Sr-- 1 11651 9510 59, 145 Sep 4 1971 #61187
b-wx--S--t 1 5441 39578 154, 149 Apr 22 2024 #61189
c---r-SrwT 1 7963 9766 55, 116 Jun 18 2036 #61196
c---r--r-x 1 8707 9517 32, 74 Oct 21 1989 #61204
cr--r-srw- 1 1054 9765 32, 38 Feb 22 1988 #61208
p--S-wsrwT 1 9504 55251 0 Feb 2 2004 #61211|
b---rwS--- 1 29789 63600 140, 133 Nov 6 1904 #61213
cr-Sr-sr-x 1 10022 35205 156, 153 Feb 15 2031 #61217
c---r---w- 1 29206 19232 172, 132 Jan 4 2010 #61223
c---r--r-x 1 9502 25472 216, 197 Oct 2 1918 #61224
p-wS--S-wT 1 799 36126 0 Nov 20 1969 #61225|
b-w---s-w- 1 29734 41097 75, 84 Jul 17 1927 #61227
cr--r-Sr-x 1 5407 33823 30, 30 Jan 6 1986 #61229
p--Sr-S--T 1 789 13878 0 Jan 13 2004 #61231|
srws-w-rwt 1 55044 50886 3419391652 Jun 13 1905 #61232=
cr-s------ 1 53186 16438 34, 54 Jul 2 1946 #61241
c----wsrwt 1 7718 8222 4, 77 Jan 3 1986 #61246
brw------t 1 50629 16448 175, 161 Mar 25 1988 #61249
For me it doesn't make any sense. And it's getting worse in the
listing. There are some files that are reported as soft links and inside
isn't stored the path to the real file but parts of files from my
filesystem. Ok. So like showing parts of /var/logs/messages isn't such a
big problem because I'm the only one using this machine. But how come
there are parts of messages I received? My $HOME is located on another
partition.
Else, does anybody has any solution? I have a very busy period.
And time is one thing I really lack. And it's getting more and more
disturbing. So all works well. Than I shutdown the system. Eventually I
go to windoze to finnish some work. Next time I boot the root filesystem
is corrupted, sometimes beyond repair. These last days I reinstalled
linux like it was windoze. I repeat: isn't from the hardware, unless the
2.0.30 kernel is too stupid to work with a udma hard drive, but I don't
think so.
I love Linux, and I will miss a lot of features. But if I don't
find a solution I'll erase Linux - probably for good. It's somehow
insulting. I mean I have OSR2 as well, and it didn't crash in about 3
months. I'm desperate! And this is taking me too much time.
My partition table looks like that:
/dev/hda1 vfat 300M
/dev/hda2 ext2 / 300M
/dev/hda3 dos extended which contains 2 disks 2g each
/dev/hda4 extended
/dev/hda5 ext2 /usr 1g
/dev/hda6 swap 24m
/dev/hda7 ext2 /home 1g
/dev/hda8 ext2 /extra the rest till 8.4g
_No_other_partition_had_any_problems_so_far_. And had2 doesn't
have any problems while I'm running it. The nightmare starts after
shutdown (or at boot time).
Raider
--
``Liberate tu-temet ex inferis''
