Quote:
you do have /home on a separate partition?
|
no.
Code:
simon@indigo-prime:~$ sudo fdisk -l
Password:
Disk /dev/hda: 4321 MB, 4321787904 bytes
255 heads, 63 sectors/track, 525 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 1 122 979933+ 83 Linux
/dev/hda2 400 525 1012095 82 Linux swap / Solaris
/dev/hda3 123 399 2225002+ 83 Linux
Partition table entries are not in disk order
Disk /dev/hdb: 80.0 GB, 80026361856 bytes
16 heads, 63 sectors/track, 155061 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes
Device Boot Start End Blocks Id System
/dev/hdb1 * 1 155061 78150712+ 83 Linux
hda1 = boot /boot
hda2 = swap
hda3 = spare space formatted ext3 for the heck of it.
hdb1 = root /
Thanks... I actually have a great deal of information about backup methods. It's just implimenting it.
Next I upgrade my HW, I'll probably convert the current HDD's to external - USB. Until then, I backup mission critical files to CD regularily and the entire set when I upgrade to a new release. The disk that disintegrated contained critical files - however, it meant that I had a recent backup of them to fall-back on, so nothing that cost me money got lost. Murphey strikes - 5 disks of photos and music, any of which could have gone awol without fuss, was safe. (Interestingly - my old DOS4 floppies are still holding their data... they were written c. 1985. I have a 70's cassette tape of "starfighter" for trs80, which I am told still plays. There is just no telling.)
For the sake of more info - here are the top ten off the top utility:
Code:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
[block1: gdesklets running]
5536 simon 16 0 34156 21m 9.9m R 41.3 2.8 0:48.49 python
4516 root 16 0 35636 23m 7996 R 37.2 3.1 0:24.24 Xorg
5526 simon 15 0 20176 9.9m 7464 S 4.7 1.3 0:03.12 wnck-applet
5483 simon 15 0 55196 16m 11m S 3.2 2.2 0:04.60 nautilus
5479 simon 15 0 13512 7760 6120 S 2.2 1.0 0:02.15 metacity
5601 simon 15 0 31916 12m 8528 S 2.2 1.7 0:02.95 gnome-terminal
5469 simon 15 0 34308 12m 9348 S 0.6 1.7 0:01.52 gnome-settings-
5564 simon 15 0 14608 2772 1848 S 0.6 0.4 0:00.35 gnome-screensav
1 root 16 0 1564 528 460 S 0.0 0.1 0:01.19 init
2 root RT 0 0 0 0 S 0.0 0.0 0:00.00 migration/0
[BLOCK2: only the terminal window open anywhere]
4516 root 21 0 34900 22m 7292 R 77.8 3.0 0:38.42 Xorg
5526 simon 16 0 20176 9.9m 7464 S 6.6 1.3 0:04.34 wnck-applet
5601 simon 15 0 33044 13m 8936 S 4.7 1.7 0:05.89 gnome-terminal
5479 simon 15 0 13512 7820 6164 S 4.0 1.0 0:03.64 metacity
5483 simon 15 0 55196 16m 11m S 4.0 2.2 0:05.35 nautilus
5564 simon 15 0 14608 2776 1848 S 1.0 0.4 0:00.56 gnome-screensav
5469 simon 15 0 34308 12m 9348 S 0.7 1.7 0:01.76 gnome-settings-
4244 haldaemo 17 0 2008 864 760 S 0.3 0.1 0:00.05 hald-addon-stor
5737 simon 16 0 2200 1104 856 R 0.3 0.1 0:00.05 top
1 root 16 0 1564 528 460 S 0.0 0.1 0:01.19 init
The first block is when I was monitoring performance with gdesklets - hence the python entry. The second block is after stopping gdesklets. Nothing else was active on any workspace (there are 6).
Those figures came from dragging the terminal window around the screen - the load was particularily high when the terminal window overlapped another one or an icon or a desklet - which seems reasonable, that's when the most work needs to be done. (And the terminal background is "transparent".)
It looks like cpu load is still shared between apps. i.e. xorg gets a bigger share when python ain't running. But the share is HUGE.
It may be that this is not a X issue at all ...
Now: I first noticed this after loading gdesklets - for the CPU monitor. In the same session I had discovered I needed to install gdm too (for some reason the last upgrade removed this but not gnome... so I would logout to rl3...)