A few weeks ago, I had to install on Sandy Bridge hardware that is not
supported in the kernel in the 2.5.0 media.

While I've done some installer work recently, it will be at least weeks
before there's a new installer you can use.

In the meantime, here's an alternative, manual workaround process for
getting Foresight installed on hardware not supported by 2.5.0 media.
This is from memory, so reply with supplementary information or fixes.

Download two things:
* Latest sysrescuecd (has recent kernels)
* Recent tarball of Foresight

Put the tarball somewhere you can get at it from the system you are
installing; USB key, NFS server, HTTP server.

Boot sysrescuecd, and be sure to choose a 64-bit kernel option if you
are installing 64-bit Foresight.  It won't work otherwise!

Partition and make filesystems in sysrescuecd.  If you choose ext4
instead of ext3, remember that you did so.  (It will work, even for
/boot -- new foresight has new enough extlinux.)  Set up swap..
Make sure that the partition containing /boot is flagged as the
bootable partition.

Mount the filesystems somewhere.

Mount the filesystem containing the tarball if it's on a filesystem.
Or make sure you have network available for getting at your tarball.

Unpack your tarball in the right directory.  tar xzSpf

rm /path/to/var/swap -- you aren't using it anyway.

Edit /path/to/etc/fstab -- make sure everything is right, including
ext4 if you made ext4 filesystems, and setting up swap.

chroot /path/to /bin/bash
mount /proc
mount /sys
MAKEDEV null full zero sda    <-- add devices as necessary
mkinitrd -f INITRD VERSION <-- figure this out
useradd -all-the-args-you-want YOURUSER
usermod -a -G wheel  YOURUSER
passwd YOURUSER
passwd (you're going to want a root password when this thing doesn't boot!)

cat /boot/extlinux/mbr.bin > /dev/sda
extlinux -i /boot/exlinux

umount /sys
umount /proc
exit

Now unmount all your newly-installed filesystems, and reboot.

With luck you'll have a working Foresight system.  If you don't,
ask for help.  Probably I forgot an important step.  Sorry.
_______________________________________________
Foresight-devel mailing list
Foresight-devel@lists.rpath.org
http://lists.rpath.org/mailman/listinfo/foresight-devel

Reply via email to