Bug 1321368 - [Request] Anaconda doesn't provide OEM install option
Summary: [Request] Anaconda doesn't provide OEM install option
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 26
Hardware: All
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-25 20:00 UTC by Denis Donici
Modified: 2018-05-29 12:11 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-05-29 12:11:22 UTC
Type: Bug


Attachments (Terms of Use)

Description Denis Donici 2016-03-25 20:00:13 UTC
Description of problem:

At the moment there is no straightforward way to make a OEM installation for end users from Anaconda. There is Kickstart and other scripts that help with that. 

Expected results:
Provide an option to install a Fedora Workstation in OEM mode. 


Additional info:
This is how it's done in Ubuntu

https://help.ubuntu.com/community/Ubuntu_OEM_Installer_Overview

This will be useful for vendors that want to ship hardware with Fedora Workstation preinstalled.

Comment 1 David Shea 2016-03-28 13:38:04 UTC
What exactly are you looking for you that is not provided by kickstart, image and dir installs, or tools such as livemedia-creator?

Comment 2 David Shea 2016-03-31 19:14:34 UTC
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.

Comment 3 Denis Donici 2016-09-21 21:08:57 UTC
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.

Comment 4 Martin Kolman 2016-09-22 12:47:56 UTC
(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.

Comment 5 Fedora End Of Life 2017-02-28 09:56:32 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle.
Changing version to '26'.

Comment 6 Fedora End Of Life 2018-05-03 08:28:42 UTC
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.

Comment 7 Fedora End Of Life 2018-05-29 12:11:22 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.