Ramon Gandia wrote:
> This is precisely the problem with partitioning without knowing
> which way your partitons are going to be heading. I always
> advise newcomers to Linux to simply create one giant partition
> for everything, and another small one for swap. Once they have
> experience with the system, they can redo it.
A wise idea in retrospect. I kind of hate the way you always have to
reformat and start over whenever there is an update so I like keeping
the things that are replaced by that process separate from my own
configurations and datafiles. I thought I was being generous when
RedHat suggested 50-80mb for / to always give myself 100mb. Obviously
the world keeps changing and small partitions are part of the past.
> Most likely your trouble is with /var. It has probably
> accumulated a lot of log files. Use the du command to
> spot which is giving trouble. Here is a listing of my du
> command on my personal workstation:
That was one of my problems. It did free up enough that my print
queue started to work again. But I see that I only have about six mb
left and I suspect that is in imminent peril of being overwhelmed.
> **root@amber[/root]# cd /
> **root@amber[/]# du -s *
> 5025 bin
> 3083 boot
> 42 dev
> 2201 etc
> 563281 home
> 12302 lib
> 12 lost+found
> 1 misc
> 4 mnt
> 4699 opt
> 0 proc
> 1554 root
> 2756 sbin
> 1 scsi
> 145 tmp
> 883906 usr
> 26845 var
> **root@amber[/]#
Other than the old log files, what would be a good candidate for
deletion or movement to somewhere else? What can I move without
screwing things up completely?
Any help would be appreciated and I want to thank you for the help
you have already given.
--
Traci Collins, MA
Professor of Computer Education
Colorado Mountain College
http://www.rof.net/wp/tcollins/traci.html
