DSL will reconstruct your /etc/fstab and rebuild it automatically on every reboot.
If you wish to create a permanent fstab, you will need to either remove the part inside the startup scripts where it rebuilds the fstab, OR you can add manual mount commands to your /opt/bootlocal.sh and mount your filesystems.
Just make sure to specify the correct mountpoints in your commands, IE: /dev/hda5 = /usr for example.Really? It seems like fstab is the same even after I reboot. Is the system rebuilding it and then replacing it with the one on disk? And like I said, executing mount -a mounts all the partitions I wanted mounted before. So far, right now I've got /home and /var on separate partitions, and now card manager freaks out a little bit because /var isn't mounted yet. There's no serious problems, as I can just mount after I login and everything works fine. And bootlocal.sh seems to be the last thing that the system does before bringing me to the login screen. The problem is, I was hoping to move /usr to a separate partition as well, and I don't want to do this if the system expects it to be there at boot. It seems like some of the stuff in there is important =)The /opt/bootlocal.sh method worked for me when moving /home to a different partition. Changing /etc/fstab directly didn't work, which really puzzled me until I read cbagger01's reaction.Yeah, bootlocal.sh works for me too -- at least for /home. I was hoping there was a way to mount before that point. Or maybe that isn't neccesary? I don't know what is neccesary to start up. If I could get away without, say, /var or /usr until just before login, that would work... Problem is, I don't think that's the case. As I said, those files look too important to only be neccesary to start X.
Would it work to just put a line into one of the startup scripts, like "mount -a"?
Maybe I'll just take the plunge, see what happens. That's what emergency disks are for, right? And there's always my Windows partition =P
Quote (Chaos750 @ Nov. 16 2004,18:46)
Really? It seems like fstab is the same even after I reboot. Is the system rebuilding it and then replacing it with the one on disk?
Hi all. I'm in the middle of this at the moment. I have the following:
swap / /usr /home (cos then I can keep/move my user data easily or trash it and mount home from another machine /var (cos I've had problems with logs filling up before, so they can fill up their own partition and leave some space for root to play in
My version of knoppix-autoconf (don't know what version of DSL I'm running. thought it was 5 - maybe it's 0.5) does detect partitions but it adds them into fstab, so manual changes to fstab survive. An exception is the usb drive detection, which adds itself to fstab whether or not it already exists... a stupid bug which should never have made it into the script...
I did something like the following (note: not checked any syntax, just illustrating the approach I used)
# fdisk /dev/hda [ set up partitions, leaving alone the current / partition ] # mkfs /dev/hda2 ... # mkfs /dev/hda4 # reboot # cp -r /home /mnt/hda2 ... # cp -r /var /mnt/hda4 # vi /etc/fstab [ set up new mountpoints ] # mv /home /home.orig ... # mv /var /var.orig # reboot
One problem I had was that knoppix-autoconf uses stuff in /usr before mounting the fsystems so I had to copy a few files from /usr/bin to /bin.
I'm in the middle of hacking knoppix-autoconf to pieces, as I believe a lot of it should only be run once, on the first boot after installing to HD.