search

concordusapps / keystone

Arch Linux automated install procedure.
MIT License
4 stars 1 forks source link

Vision #3

Open mehcode opened 10 years ago

mehcode commented 10 years ago

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.

mehcode commented 10 years ago 
# Ask for configuration up front.
$ keystone-configure
[?] hostname (keystone):
[?] shell (bash):
[?] console font (Lat2-Terminus16):
[?] console font map (8859-1_to_uni):
[?] language (en_US.UTF-8):
[?] timezone (US/Pacific):
[?] root password (none):
[?] re-enter root password:
[?] username (administrator):
[?] <username> password (none):
[?] re-enter <username> password:
[?] AUR helper (aura):
[?] bootloader (grub):
[?] boot device:
[?] desktop environment (none):
[?] window manager (none):
[?] login manager (none):
[?] network manager (none):

# Install an arch linux system
# No need to shove everything at the user that is happening
$ keystone-install
==> Installing base system...
==> .....
off-by-some commented 10 years ago

Shouldn't be too hard to implement. Maybe here we can pipe all the output to a log... What to DO with the log is a good question. But it would be a good thing to have.. maybe submit an error report (That option IS available in the GUI)