Please make salix gpt partitions ready.
Thanks for a great OS
stepomaticc
gpt partitions
Re: gpt partitions
IIRC you can exit the installer, run parted, and set up a GPT table and partitions, then restart the installer and set things up as needed. It should work fine; the only related bug in Slack 13.37 (which probably applies to Salix) is that the installer won't recognize swap partitions on a GPT disk, so they have to be added to fstab manually. Not the ideal solution, especially for novices, but there you have it.
(One warning though: BE CAREFUL WITH PARTED. Unlike fdisk and cfdisk, parted makes changes to the partition table instantly, and will gladly destroy all your data if you're not careful.)
(One warning though: BE CAREFUL WITH PARTED. Unlike fdisk and cfdisk, parted makes changes to the partition table instantly, and will gladly destroy all your data if you're not careful.)
Re: gpt partitions
Umm wait a minute though, one other thing. If you set up a GPT table like I indicated, IIRC LILO needs to be installed to the boot partition, because GPT does not use an MBR. So make sure your boot partition is formatted with a filesystem compatible with LILO, e.g. ext3.
Re: gpt partitions
This howto should help: http://www.salixos.org/wiki/index.php/H ... hard_drive
We'll probably do something to make it more straightforward in future versions.
We'll probably do something to make it more straightforward in future versions.
Re: gpt partitions
Do novices have GPT partition tables?GJones wrote:Not the ideal solution, especially for novices, but there you have it.

Re: gpt partitions
You should just need to run mkswap on your designated swap partition before you start setup again.GJones wrote:the only related bug in Slack 13.37 (which probably applies to Salix) is that the installer won't recognize swap partitions on a GPT disk, so they have to be added to fstab manually.
Does lilo actually work? I'm interested in using gpt for some large drives I'm saving for but I thought you needed to use syslinux or grub2 to boot.gapan wrote:This howto should help: http://www.salixos.org/wiki/index.php/H ... hard_drive
We'll probably do something to make it more straightforward in future versions.
I tried it out using extlinux on an ext3 partition (set to bios bootable) a few weeks ago but it didn't work. That said, I was using gdisk instead of parted so may be that was the problem.
Re: gpt partitions
Yes it does. Just follow the howto. Worked for me anyway. It works like that in the installer, but if you run liloconfig in an installed system, I remember there is a trick. For some reason liloconfig sets "boot=/dev/root" in /etc/lilo.conf instead of "boot=/dev/sda" or similar and you have to edit it manually before running lilo.pwatk wrote:Does lilo actually work? I'm interested in using gpt for some large drives I'm saving for but I thought you needed to use syslinux or grub2 to boot.
Re: gpt partitions
I should try this with my next drivegapan wrote:Yes it does. Just follow the howto.

-
- Posts: 1
- Joined: 28. Dec 2011, 09:38
Re: gpt partitions
Pardon me, I am new here.
I've been struggling to install Salix64 in my box equipped with Intel Atom D510. I want it to be UEFI and GPT-aware. The guide about installing Salix on GPT hardrive (which is mentioned above) wasn't much of help to me. Lilo gave me warnings when I tried to write the boot loader to root partition, but it's finished eventually. At last it won't give me a bootable system.
Still, I wonder how usb-stick installation media via unetbootin works just fine.
___
Edit: it turns out to be faulty firmware in the motherboard
I've been struggling to install Salix64 in my box equipped with Intel Atom D510. I want it to be UEFI and GPT-aware. The guide about installing Salix on GPT hardrive (which is mentioned above) wasn't much of help to me. Lilo gave me warnings when I tried to write the boot loader to root partition, but it's finished eventually. At last it won't give me a bootable system.
Still, I wonder how usb-stick installation media via unetbootin works just fine.
___
Edit: it turns out to be faulty firmware in the motherboard
