From: Dumas Patrice (dumas@centre-cired.fr)
Date: Thu Aug 31 2000 - 14:53:21 CEST
Hi,
> 2- the second way lets me think that you still want to use the hdd, but then
> only for saving files and configuration (since michele didnt leave space on the
> floppies to save cd-images of other distro's), but remember that you still will
> get corrupted filesystem with a power-fail.
> try to mount the harddisk, something like:
> mount -t ext2 /dev/hda1 /home
> i never tried it but i see no reason why it shouldnt work.
I don't understand the problem like that. In my opinion, the goal is to use a
cloned system, but in ram. It offers several advantages against floppy based
systems mounted in ram : it boots really much faster, even with a ton off adds-on,
and an hard drive is much more reliable than a disk.
The way to do that would be to copy the filesystems in ramdisks at each boot. That
pose a problem, as /usr, for example, cannot be mounted in /dev/ram1 and copied
then. I think, the trick is to mount /dev/ram on a /tmp dir and remount them.
Something like (but take only the ideas, my cp is quite strange) :
mount /dev/ram1/tmp/mnt;
ls /usr | grep -v ..........eliminate the add-ons (see in the scripts, it is well
done)........... | cp -a -- /tmp/mnt;
mount -o remount /dev/ram1 /usr
(you have to do that for add-ons first).
It doesn't solve everything, as /startup resides on the disk, and so everytimes
you want to store something you will have to mount it. The whole stuff is not a
trivial thing, I warn you... It interests me, I think it would be good and even
more if you can load some things in memory and others not. That trick should even
help little configs.
Pat
---------------------------------------------------------------------
To unsubscribe, e-mail: mulinux-unsubscribe@sunsite.auc.dk
For additional commands, e-mail: mulinux-help@sunsite.auc.dk
This archive was generated by hypermail 2.1.6 : Sat Feb 08 2003 - 15:27:15 CET