Martin Randall wrote:Eigerstein.
>
> Does anyone else have problems with :-
>
> A) Occasional problems saving/exiting the setups. Sometimes ctrl-c and
> alt-q don't work and I have to use ctrl-k/alt-k.
>
> B) Quite often, doing a simple change (removing a singles #) will prevent
> me from backing up without logs. It will complain that /root is full or
> whatever. Further, when this happens, it destroys the disk making it
> unbootable.
Have no experience with A.
B sounds like problems with not enough memory to do the backup. The backup
takes all the files from the file system (ram) compresses and writes the lrp
file to the ramdisk (/dev/ram0) and then asks you if you want to write it to the
media. The symptoms you have indicate not enough ram. Are you on a cable
system? Logs can fill up memory and may have to be deleted before backup.
NEVER reboot until after you have checked the size of the backups on the floppy.
# mount -t msdos /dev/fd0u1680 /mnt
# ls -l /mnt
# umount /mnt
If root has changed size, delete some logs and try again until you get it right
- it may be tricky if you are running on a marginal amount of memory.
You can check your memory status
# df
Filesystem 1024-blocks Used Available Capacity Mounted on
/dev/ram0 6076 3358 2718 55% /
Free tells you about the memory used by the OS for files, buffers, etc.
# free
total: used: free: shared: buffers: cached:
Mem: 23375872 12251136 11124736 6168576 4046848 2539520
Swap: 0 0 0
MemTotal: 22828 kB
MemFree: 10864 kB
MemShared: 6024 kB
Buffers: 3952 kB
Cached: 2480 kB
SwapTotal: 0 kB
SwapFree: 0 kB
There is usually no reason to backup everything - especially root - since you
rarely change anything there. (Exception - configuring a dialup modem or
replacing a particular file such as grep in the file system) All your network
configs go in etc, and individual packages back up individually.
_______________________________________________
Leaf-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-user
