Re: Whither = and whence?

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

 



Philip Prindeville wrote:
BTW, am I the only person confused by the parameter
syntax, i.e. that some arguments take an '=' and some don't?

part / --fstype ext3 --size=1024

firewall --enabled --trust=eth0 --http --ssh
network --device eth0 --bootproto dhcp

bootloader --location=mbr

When do you need '=' and when don't you?  Or how about, we
get rid of them altogether?

-Philip

Actually, it's worst than that.  Looking at:

http://fedoraproject.org/wiki/AnacondaKickstartIntegration?highlight=%28kickstart%29

I see:

network --bootproto dhcp

for instance, but looking at:

https://www.redhat.com/docs/manuals/linux/RHL-9-Manual/custom-guide/s1-kickstart2-options.html

I see:


network (optional)

    Configures network information for the system. If the kickstart
    installation does not require networking (in other words, it is
    not installed over NFS, HTTP, or FTP), networking is not
    configured for the system. If the installation does require
    networking and network information is not provided in the
    kickstart file, the Red Hat Linux installation program assumes
    that the installation should be done over eth0 via a dynamic IP
    address (BOOTP/DHCP), and configures the final, installed system
    to determine its IP address dynamically. The network option
    configures networking information for kickstart installations via
    a network as well as for the installed system.

    --bootproto=

        One of dhcp, bootp, or static.

        It default to dhcp. bootp and dhcp are treated the same.

        The DHCP method uses a DHCP server system to obtain its
        networking configuration. As you might guess, the BOOTP method
        is similar, requiring a BOOTP server to supply the networking
        configuration. To direct a system to use DHCP:

        network --bootproto=dhcp

        To direct a machine to use BOOTP to obtain its networking
        configuration, use the following line in the kickstart file:

        network --bootproto=bootp




Writing a syntactically correct ks.cfg for FC5 is turning out to be
full of twisty little mazes, all alike.

Someone please tell me that the '=' are optional, and that the parser will
happily accept them if present and not complain if they aren't...

-Philip




[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