Arthur Archnix
March 4th, 2008, 11:00 AM
I have a pretty flexible partition scheme, two primary 128 MB and a 900MB swap, the rest is an extended with at the moment two partitions for Nixs, a shared /tmp and shared /data partition.
I also have a no cd's, and only a few dvd's, and no money to buy more, so I tried to install Arch using a net install disc extracted to my free 128MB boot partition. I edited grub on my /dev/sda1 boot partition and rebooted into the net installer. Installed normaly then rebooted into Ubuntu.
First problem: Because it's a shared /tmp partition arch creates a new partition and then Ubuntu doesn't have the correct permissions. Simply chowning it doesn't work. Fortunately, there's a workaround on the ubunty forums explaining how to set the correct ownership on tmp.
At this point I should have left well enough alone, but I moved the /arch/boot to the second 128 /boot partition, updated arch's fstab and booted into arch.
Everything worked fine. I ran pacman -Syu which oddly enough found updates. Apparently the net-install disk doesn't take down the latest packages. Or maybe I was just using an out of date mirror. Anyway, it updated the system, BUT, and here is where my system got hosed, it complained about there being no boot partition when creating the image.
Since I knew I had a boot partition I ignored it, and now, I must start again from square one.
I thought I'd share this with you in case anyone is considering something similar. This time I'm just going to leave boot where it is on the /root partition, at least at until I find out where its getting it's information on partition layout if not from fstab.
I also have a no cd's, and only a few dvd's, and no money to buy more, so I tried to install Arch using a net install disc extracted to my free 128MB boot partition. I edited grub on my /dev/sda1 boot partition and rebooted into the net installer. Installed normaly then rebooted into Ubuntu.
First problem: Because it's a shared /tmp partition arch creates a new partition and then Ubuntu doesn't have the correct permissions. Simply chowning it doesn't work. Fortunately, there's a workaround on the ubunty forums explaining how to set the correct ownership on tmp.
At this point I should have left well enough alone, but I moved the /arch/boot to the second 128 /boot partition, updated arch's fstab and booted into arch.
Everything worked fine. I ran pacman -Syu which oddly enough found updates. Apparently the net-install disk doesn't take down the latest packages. Or maybe I was just using an out of date mirror. Anyway, it updated the system, BUT, and here is where my system got hosed, it complained about there being no boot partition when creating the image.
Since I knew I had a boot partition I ignored it, and now, I must start again from square one.
I thought I'd share this with you in case anyone is considering something similar. This time I'm just going to leave boot where it is on the /root partition, at least at until I find out where its getting it's information on partition layout if not from fstab.