New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Install an OS automatically in a predefined manner. #2229
Comments
See #1655 #1362 (both open) and #466 (closed) for some previous thoughts on the topic. There might have been an issue filed for kickstart-like support, but I can't find it. Basically, if you can load a job's configuration -- the whole configuration, e.g. also what it would do from user interaction -- then you can run the jobs in the |
Thank you for your advice. I got a inspiration from #1655. As a test, I created a job module "predefined-users" from a view module "users". If I raise the issue, should I PR commits? or can someone solve this problem? |
I don't think we should create new modules. Ideally, we should automate the existing modules so we only have to maintain a single code base. |
That is a good point that I didn't think about. |
Guys, did I understand correctly that now there is no way to install the OS fully unattended using Calamares? |
Is your feature request related to a problem? Please describe.
To install an OS interacting with a GUI is good enough for a user who manages only one or two desktops.
However, it is a time consuming job interacting with a GUI for a manager who installs the same OS with the same options.
Describe the solution you'd like
I suggest that calamares as an one-click installer that installs without any user interactions using predefined configurations.
Predefined options may be described by existing conf files like /etc/calamares/settings.conf and /etc/calamares/modules/.conf in calamares-settings-debian.
My rough design is as follows.
Describe alternatives you've considered
Creating new job modules would be a kind of time consuming job, hence this could be an option:
If the next button in the step is enabled, call ViewManager::next() to progress the next step automatically.
This can be done by adding a line
connect( step, &ViewStep::nextStatusChanged, this, &ViewManager::next()
of ViewManager::insertViewStep and changing a ViewManager to cope with a status of a next button.But with this design, ViewManager which is core part of calamares should be changed.
Additional context
No additional comments.
The text was updated successfully, but these errors were encountered: