| Summary: | [Request] Anaconda doesn't provide OEM install option | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Denis Donici <denis_donici> |
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 26 | CC: | anaconda-maint-list, denis_donici, g.kaviyarasu, jonathan, mkolman, vanmeeuwen+fedora |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-05-29 12:11:22 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Denis Donici
2016-03-25 20:00:13 UTC
What exactly are you looking for you that is not provided by kickstart, image and dir installs, or tools such as livemedia-creator? It may also be worth noting that anaconda will save the settings from a given install to /root/anaconda-ks.cfg, which can be used a template for future installs. Feel free to provide details about features you feel are missing or areas where usability could be improved. I am looking for a simple and straightforward GUI way to install Fedora in OEM mode. Steps taken> *Plug in a USB with a ISO. *Boot in Anaconda. *Choose OEM install. *Fedora is installed automatically. Without any intervention from my side. *After install the device is powered off. *First boot after install, the user is required to set up an account, wifi connection, online accounts and other post installation settings. He also should be shown the GPL license and User Agreement. (In reply to Denis Donici from comment #3) > I am looking for a simple and straightforward GUI way to install Fedora in > OEM mode. > > Steps taken> > *Plug in a USB with a ISO. > *Boot in Anaconda. > *Choose OEM install. > *Fedora is installed automatically. Without any intervention from my side. This can be achieved with the "cmdline" kickstart command: https://github.com/rhinstaller/pykickstart/blob/master/docs/kickstart-docs.rst#cmdline Note that the kickstart file needs to contain all the required information for the installation. > > *After install the device is powered off. > *First boot after install, the user is required to set up an account, Initial Setup can be enabled with "firstboot --enable" so that the user can setup the user account once the machine boots up after the installation. > wifi connection, online accounts and other post installation settings. I think the Gnome Initial Setup tool has a screen for online accounts or I guess the user can do that in the system when needed. > He also should be shown the GPL license Is that really needed ? Also AFAIK the software in Fedora is licensed under many different open source licenses, not just GPL and even GPL has variants - v2, v3, LGPL, AGPL, etc. > and User Agreement. Fedora doesn't have anything like that, so I don't think we have currently any facilities for that. But Initial Setup displays the RHEL EULA on on RHEL, so that might be theoretically backported to the Fedora IS if really needed. This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle. Changing version to '26'. This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |