Bug 85847

Summary:	Allow you to go through Anaconda menus on another system
Product:	[Retired] Red Hat Linux	Reporter:	Brian "netdragon" Bober <netdragon>
Component:	anaconda	Assignee:	Michael Fulbright <msf>
Status:	CLOSED WONTFIX	QA Contact:	Mike McLean <mikem>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8.0	Keywords:	FutureFeature
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2003-03-10 22:21:33 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Brian "netdragon" Bober 2003-03-09 06:07:22 UTC

There should be a way to allow Anaconda to log all the system information to a
disk pre-install. You take that disk to another system, go through all the menus
based on the logged hardware information, and then bring it back to the former
system with all your choices and it runs through an unattended install. This
would help in two cases:

A) Your computer is in a place you don't want to sit around in (i.e. its a
firwall in a cold basement

B) Your computer is so darned slow its aggravating, or doesn't have a mouse.

C) Insert your reason here.

Maybe an extension to kickstart?

Comment 1 Michael Fulbright 2003-03-10 22:21:33 UTC

We do store most the settings into the anaconda-ks.cfg file after you complete
an install.  We don't have plans to use this data for scripted install sections.
 If you want you can take the anaconda-ks.cfg and tweak it by hand, and then
insert 'interactive' in it as well and you will have something close to what you
are describing.