Why hd install is to an ext2 partition?Forum: HD Install Topic: Why hd install is to an ext2 partition? started by: dslrgm Posted by dslrgm on July 20 2007,22:09
per< http://www.damnsmalllinux.org/wiki....rd_Disk > Why ext2 and not ext3? And it seems that /boot is being put on the same partition as all the rest? Can it be put into its own partition. Posted by curaga on July 21 2007,06:34
ext2 uses less system resources and DSL is targeted to lower class machines.Feel free to make yours ext3 and separate /boot if you want.. Posted by lucky13 on July 21 2007,12:30
The HD installation script offers the choice of ext2 or ext3.
Posted by dslrgm on July 22 2007,03:22
I thought about this overnight.... My goal is 3 partitions, 2 on a CF card, /boot and / and 1 on a CF micro drive for at least /home and /var/log So I was realizing that /boot and / (when all active directories like /var/log are moved to the micro drive) could cope well with ext2. The microdrive, I was thinking would be a LVM and have at least one ext3? Or just the ext3? The challenge is getting all the active directories over to the micro drive without going crazy. I was thinking I should make a directory called /stuff that is mapped to the ext3 partition on the micro drive. Then make subdirectories, like /stuff/home and setup a symbolic link of /home to /stuff/home. Will that work? Posted by roberts on July 22 2007,03: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. On the other hand, doing a frugal install is way easier on CF type devices. Using the boot options of home=sda2 and/or opt=sdb1 for example. Allow for persistent store for these two directories. This is automatically done by the system when using those boot options. You could also "move" other directories using the technique of the bind option to the mount command. Of course this would be something you would have to setup. I don't think you would find your particulars documented anywhere as it appears to be a custom appliance type setup. Posted by dslrgm on July 22 2007,12:29
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! |