Here are some areas i intend to work on, any info / comments on the
implementation of these would be appreciated.
A. ZFS Modules should not be loaded by the installer unless explicitly
chosen by the user.
ZFS works on most sparc64 boxes, but not all of them. Especially the
older sbus machines and a few of the large enterprise boxes that do
funky things with memory allocation. If we always load ZFS modules the
installer will panic on these machines even if the end user has no
intention of using ZFS. I propose two options.
1. Only load zfs modules if the user is creating a ZFS pool at install
time.
2. Create a prompt asking the user if they wish to enable ZFS support
before partitioning.
B. Select / Install software fails every time on multiple machines.
(tested on T5120, T1000, V210, M4000)
Not sure what happening here, but ill look into it and try to patch
out the issue. Not critical as you can skip this section and move on
to installing silo.
C. The partitioner should always create an ext2 boot partition.
Installing with "Guided - use whole disk" will create a single ext4
partition which silo cannot boot from. The partitioner does warn
against this, but having the partitioner take care of this by itself
makes more sense. The question is, what size do we make /boot by
default? 128M / 512M?
D. The kernel is missing drivers for a lot of older sparc gear. Sparc
ESP, PTI Qlogic, etc... Ill make a list of the ones i can verify and
make a patch.