I had a similar problem with a previous install, it ocuured oddly enough after
I had repositioned the swap space to a different area of the drive from
before and was gone after I moved the swap back to the end of the drive. I
have a 4.3gig hard drive broken up into partitions like this (give or take):
/boot 15M
/root 350M
/home 660M
/usr 1555M
/usr/local 1050M
swap 128M
I tried previously to move swap in between home and usr I think it was, and
that's when I developed problems. I moved the swap back to the end of the disk
and haven't had a hang or lock since. I think the Partitioning how-to might be
able to explain it. I'm not sure if the swap space was split in between
platters causing the head to have to read all the way to the end of first
platter and then move back to the beginning of the second inorder to complete
the swapping. Whatever it was, what's your partitioning scheme as well as the
size and geometry of the disk. Also take a look at the partitioning how-to
which my be able to give you some idea on the whole concept of partition
physics.
Second, what time is it doing this? I think at 3 or 4 the slocate crontab runs
which makes a database of all the files on the drive, I don't think that would
be large enough to really hang the system but take a look at what's going on at
the time. When slocate had to database my entire windows drive though, it did
take a while and did slow up slightly.
Just some possible suggestions.
Tom
On Wed, 05 Apr 2000, you wrote:
> On Wed, 05 Apr 2000, you wrote:
> > I have 64Megs of RAM and 128Megs of swap.
> >
> Ok. As long as you've got at least a PII that should be
> sufficient...
> John
