dslrgm
Group: Members
Posts: 84
Joined: July 2007 |
 |
Posted: July 22 2007,12:29 |
 |
| Quote (roberts @ July 21 2007,23:54) | I am not sure what kind of install you are thinking about...
But doing a regular traditional install onto a CF will cause failure due to excessives writes and ext3 would be even worse!
Still, if you insist, using such installation type, you would need to add the nofstab to stop the generation of /etc/fstab upon each boot. That way you can edit your fstab to suit your drive/partiton mount mappings.
You could also "move" other directories using the technique of the bind option to the mount command. |
I knew for the time I started with CF cards, that they would not function as 'typical' drives. And that I would have to limit writes. Challenge is to find those files that get written to alot...
So for files like /etc/fstab, I was thinking about what I see with how /etc/named.conf is handled with chrooted named...
I have a directory, say /stuff/slop/etc (/stuff is on the partition on the microdrive) and there I create /stuff/slop/etc/fstab
I cp the current /etc/fstab there, delete it, and make a symbolic link of /etc/fstab to /stuff/slop/etc/fstab. Then reboot.
I guess the bigest question is how to move all those mappings. I might THINK that booting bootfloppy.img, mounting the CF card and CF microdrive, make the changes then boot regular from the CF card (/dev/hda0), and hope for the best!
|
.
DSL Market ,
Great VPS hosting provided by Tektonic
