Keystone should evolve in a few directions: manual, automated (manual), TUI (ncurses), and GUI (GTK).

Manual

Expose all of the modular functionality via loading various functions into the shell.

Something like that.

Automated

Ask for all configuration up front and then run through a bunch of keystone-load commands. This is similar to what we have now.

Tried keystone on my custom rig (EFI), Everything went smoothly. Grub installed A-OK, the only thing was installing nvidia drivers, and then i was good to go.

Maybe my laptop just likes being difficult.

installed with Gnome+Mutter

Exact recreation of installing:

[root@archiso]# mkfs.ext4 /dev/sda5

[root@archiso]# mount /dev/sda5 /mnt

[root@archiso]# wifi-menu

[root@archiso]# ./install.sh

[root@archiso]# arch-chroot /mnt /usr/bin/bash

[root@hyrule]# pacman -S nvidia-320xx

[root@hyrule]# exit

[root@archiso]# reboot

Everything worked like a charm, though i did have to re-install grub with a new configuration in order to have windows 7 pop up.

Ran through with a normal install (partitioned using fdisk, formatted to ext4) with Gnome & Mutter. All the internals worked perfectly, (Arch by itself was installed) However i came across a couple of problems with grub as well as vesa

The problem:

Grub failed to install to the device

Steps to fix:

After mounting the partition and attempting to execute "grub-install /dev/sda" i received some lvm warnings, as well as an error that went something along the lines of:

warning: Attempting to install GRUB to a disk with multiple partition labels. This is not supported yet..

after mounting the partition, and running "grub-mkconfig -o" then "grub-install --force /dev/sda" I received the warnings, however grub then installed.

Another problem:

After this, i attempted to boot, however only to be met with a black screen (The computer was hanging, i couldn't even change tty's)

Steps to fix:

Removing "xf86-video-vesa" and installing the appropriate intel driver for my machine removed the hang, and i could then switch tty's and startx

A few other things to note:

• GDM gave me a hard time about getting up and running. it seemed starting the daemon manually fixed the issue (a bit unsure what fixed the issue, i was doing multiple things at once.)
• "wifi-menu" needed an additional package 'display' (i think) to run. I think we should think about implementing that for users who decided not to install any kind of environment (Maybe have a preset packages file to load?) , otherwise they would need to chroot into the partition and install it manually. (I have rebooted at least 20 times in the process of figuring things out, NOT fun)