Bug 85847 - Allow you to go through Anaconda menus on another system
Allow you to go through Anaconda menus on another system
Status: CLOSED WONTFIX
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
8.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Michael Fulbright
Mike McLean
: FutureFeature
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-03-09 01:07 EST by Brian "netdragon" Bober
Modified: 2007-04-18 12:51 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-03-10 17:21:33 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Brian "netdragon" Bober 2003-03-09 01:07:22 EST
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 17:21:33 EST
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.

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