On Sat, 2015-05-09 at 13:05 -0400, Eric Griffith wrote:
The one that comes to mind is... if you're an "Administrator" then
you
have the ability to use grub2-mkconfig but... you have to blindly
specify an output file on an EFI system. On my system only root can
look inside /boot/EFI/ (not modify mind you, just LOOK) which means
if
i'm under my user account and decide to change a grub parameter I
have
to either blindly remember what the path is, or take the time to swap
to root and then swap back just for the sake of updating the boot
config.
I think 'sudo -i' does what you want.
*If user account creation gets removed then gnome-initial-setup
needs
to trigger under KDE, XFCE, and LXDE spins as well, or they need to
get appropriate first-time-setup utilities as well.
I don't suggest any of these changes for other products or spins: that
would probably be a nonstarter. Just for Workstation.
*I already said I thought hub-and-spoke was a bad idea. Installer
starts --> Keyboard and Language selection ---> Disk partitioning -->
User Creation ---> Done. Keep an expert button for software selection
and non-default network config if we really want to keep those in.
Note that we don't have software selection on the live image and never
have.
Disk layout needs some work, seriously. It might have been a bug but
when I installed it on my laptop i couldn't get it to automatically
create btrfs partitions + encrypted volumes. I spent an easy
30minutes+ fighting with Anaconda and at the end of it I threw in the
towel and just opted for ext4 + encryption because thats what I could
get it to show me... in the end what I was told I was gonna get (ext4
+ encrypted, possibly LVM in there too) and what I GOT (btrfs +
encrypted... which is what I wanted anyway, but the installer told me
I wasn't gonna get it) were very different.
Ouch, that really needs to never happen. :(