Re: loader/stage2 interaction

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Chris Lumens wrote:


Now for the more controversial stuff.  Here's what I would like to see
happen in this area for F10.  All these things are open for discussion,
so jump right in.

As a user, I'd like to see automatic installations easier. Here are some ideas I have. 1. Look at local media (floppy, usb, ??) for a ks file. If one is found, use it. By way of reference to another authority, this is what Windows does.

2. Request, and use if supplied, information from DHCP. Vendor Options are specified - http://www.iana.org/assignments/bootp-dhcp-parameters see tag 43 - as available for vendors (Red Hat, Fedora, Debian) to request and obtain information from a DHCP server. Anaconda already sets the option vendor-class-identifier and I use that to provide a special range of IP addresses for installation:
 class "anaconda"
        {
match if substring (option vendor-class-identifier, 0, 8) = "anaconda";
                option vendor-class-identifier "anaconda";
        }

and
        pool {
                allow members of "anaconda";
                deny  members of "pxeclients";
                default-lease-time 900;
                filename "http://Fedora.demo.lan/5/i386/os/Fedora/";;
                max-lease-time 1800;
                range 192.168.9.170 192.168.9.179;
                option log-servers 192.168.9.4;
        }

This illustrates how ISC DHCP 3 may be configured to provide information to Anaconda.

A sane value for filename might be the install URL, or the ks file. Use of other information such as log-servers, time-offset and ntp-servers would be beneficial (the filesystem would have correct timestamps that really reflect the time of the install).

Implementation of one or both of these would mean that users could do automatic installs with standard media, without having to key potentially long and fairly meaningless strings of data such as the URL to an install server.

  Problem:  If the user booted off a CD and we don't have any method
  configuration screen, the implied updates.img and product.img checks
  will never work.

In the case of a ks install, this info could be in the ks file. If DHCP were used, the DHCP server could be configured to provide the information.





--

Cheers
John

-- spambait
1aaaaaaa@xxxxxxxxxxxxxxxx  Z1aaaaaaa@xxxxxxxxxxxxxxxx
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375

You cannot reply off-list:-)

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list

[Index of Archives]     [Kickstart]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]
  Powered by Linux