I've never done one of these before so I really can't help. I usually serve my kickstart via nfs in which case I want the network manager to set up the nic with dhcp. If the machine is to be a server, I will override the network config in the kickstart.
My guess is that you have to mount the boot.iso image that's distributed with SL6x, read-write, on a loopback, and copy your ks.cfg file to it. That is, the boot.iso image needs to be modified. It's not enough to to copy write the iso and the ks.cfg to the usb key.
Or you need to modify the initrd image that's on the boot.iso image. It's not clear from the documentation which root (/) it refers to - the syslinux image or the initrd image. My guess is it's the initrd image.
Is this what you did?
On 08/10/2011 02:44 PM, Johnson, Kent A (GE Healthcare) wrote:
> I'm booting from the ISO DVD and entering TAB at the install splash
> screen and then adding ks=hd:/dev/sdb1:/ks.cfg to read the kickstart
> from a USB key. The kickstart is below (the latest attempt)...
>
> #platform=x86, AMD64, or Intel EM64T
> #version=DEVEL
> # Firewall configuration
> firewall --enabled --ssh
> # Install OS instead of upgrade
> install
> # Use CDROM installation media
> cdrom
> # Root password
> rootpw --iscrypted $1$Qp/kIHFC$d/jWHGmcg5jeiwIAt/82P1
> # System authorization information
> auth --useshadow --passalgo=sha512
> # Use text mode install
> text
> firstboot --disable
> # System keyboard
> keyboard us
> # System language
> lang en_US
> # SELinux configuration
> selinux --disabled
> # Installation logging level
> logging --level=info
> # Reboot after installation
> reboot
> # System timezone
> timezone --isUtc America/Chicago
> # System bootloader configuration
> bootloader --location=mbr
> # Clear the Master Boot Record
> zerombr
> # Partition clearing information
> clearpart --drives=sda --all
> # Disk partitioning information
> part /boot --fstype="ext4" --ondisk=sda --size=700
> part / --fstype="ext4" --ondisk=sda --size=20000
> part /export/home1 --fstype="ext4" --ondisk=sda --size=50000
> part swap --fstype="swap" --ondisk=sda --size=4096
>
> %packages
> @additional-devel
> @base
> @basic-desktop
> @client-mgmt-tools
> @compat-libraries
> @debugging
> @desktop-debugging
> @desktop-platform
> @desktop-platform-devel
> @development
> @directory-client
> @eclipse
> @fedora-packager
> @fonts
> @general-desktop
> @graphical-admin-tools
> @ha
> @ha-management
> @hardware-monitoring
> @ice-desktop
> @infiniband
> @input-methods
> @internet-applications
> @internet-browser
> @java-platform
> @large-systems
> @legacy-unix
> @legacy-x
> @load-balancer
> @misc-sl
> @network-file-system-client
> @network-tools
> @nfs-file-server
> @performance
> @perl-runtime
> @print-client
> @scalable-file-systems
> @scientific
> @security-tools
> @server-platform
> @server-platform-devel
> @spins
> @storage-client-fcoe
> @storage-client-iscsi
> @storage-client-multipath
> @system-admin-tools
> @system-management
> @system-management-messaging-client
> @tex
> @virtualization
> @virtualization-client
> @virtualization-platform
> @virtualization-tools
> @x11
>
> %end
>
> thanks& regards,
> kent
>
> -----Original Message-----
> From: Ken Teh [mailto:[log in to unmask]]
> Sent: Wednesday, August 10, 2011 2:38 PM
> To: Johnson, Kent A (GE Healthcare)
> Cc: [log in to unmask]
> Subject: Re: SL6.1 kickstart persistent networkmanager prevents
> unattended install
>
> Can you tell us what you type (the kernel parameters) in order to
> specify that you are installing from a kickstart?
>
>
>
> On 08/10/2011 02:18 PM, Johnson, Kent A (GE Healthcare) wrote:
>> Greetings,
>>
>> Sorry to bother but I've tried to do my homework first, to no avail...
>>
>> I'm kickstarting the standard SL6.1 install DVD from a USB key to
>> provide an unattended install.
>>
>> I've tried everything I can find to try to prevent the networkmanager
>> popup to configure the ethernet interface during the install (occurs
>> immediately after disk partitioning).
>>
>> I've tried many different forms of the kickstart network command to
>> fully configure eth0 or leaving the network line out completely but
> the
>> nm popup persists. The only way that I've been able to stop the nm
> popup
>> during the kickstart install is to disable the ethernet hardware in
> the
>> BIOS! I've read all the RH/SL docs and searched the web far and
> wide...
>>
>> So, it seems that anaconda starts networkmanager any time that it
> finds
>> an ethernet device (active or not) whether the kickstart references
>> network or not. I'm not adding any external repos or anything else
> that
>> would require network. What am I missing?
>>
>> thanks in advance for any guidance,
>> Kent
|
