similar to: CentOS 8 - auto-loading kickstart from USB doesn't work

I have been building up a script to quickly and easily make CentOS/RHEL and Fedora VMs from kickstart files for a long time, and thought I'd see if anyone else was interested. It's especially useful IMHO if you are working on building kickstarts, because you can fairly rapidly iterate and test. I've got it built as an RPM, so if others think this is useful, I might submit it to

Hi All, I am attempting to create a custom USB drive for kickstart install. I found this: 1. get the ISO file of CentOS 7 2. mount -o loop CentOS-7.0*.iso /mnt/ 3. mkdir -p /CentOS-7-ISO-respin/{CentOS-7-unpacked,CentOS-7-iso} 4. rsync -avz /mnt/ /CentOS-7-ISO-respin/RHEL-7-unpacked 5. put your kickstart file into

Hey Everyone, I was wondering if anyone has managed to do a network install where the kickstart file is located either on an FTP site (which is also where the packages are stored) or on a USB flash drive. I've tried starting the installer with "linux ks=/dev/sda/ks.cfg" or "linux ks=/dev/sda1/ks.cfg" or "linux ks=ftp://what.ever.Ip.address/pub/ks.cfg" but

----- On 1 Nov, 2017, at 13:07, Chris Adams linux at cmadams.net wrote: | Once upon a time, Mark Haney <mark.haney at neonova.net> said: |> On 11/01/2017 03:25 PM, Chris Adams wrote: |> >Once upon a time, Mark Haney <mark.haney at neonova.net> said: |> >>Okay, so it looks like I can simply change ksdevice=eth0? to |> >>bootdev=eth0, correct? |> >I

Is anybody else having problems with CentOS 5 not loading the usb drivers for kickstart installations? I'm passing "linux ks=hd:sdb1:/ks.cfg," but I get a message saying it can't find the ks.cfg file and I should enter another path. I use the exact same boot options with CentOS 4 without any problems. What am I missing with CentOS 5? Thanks for any tips. -- Jiann-Ming Su

Is there an easy way to specify the proper device location for the kickstart configuration file if it is on a USB flash or USB floppy drive? Depending on the hard disk configuration they might by /dev/sda, /dev/sdb, etc. On SuSE'autoyast instalattions, the system searches all available devices for an ``info'' configuration file. Does CentOS 5.x do something similar to find a

I'm trying to set up a custom installation of CentOS using kickstart i tried many thing from how to's and tutorial web pages but nothing worked ;( Here is my USB key tree : |-- CentOS | |-- all my rpms | `-- last rpm |-- TRANS.TBL |-- boot.cat |-- boot.msg |-- custom.iso |-- general.msg |-- images | |-- README | |-- TRANS.TBL | |-- boot.iso | |-- diskboot.img | |-- minstg2.img | |--

This should be easy to answer (I hope).? We routinely kickstart boxes to use for managing our customers RADIUS/DHCP configurations (along with other things).? We've had a C7 kickstart in place since I built one in May and are finally starting to roll it out for new installations.? But, I'm curious as to what ksdevice= actually does. With the C6 we routinely used ksdevice=eth0 since we

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, I usually use DHCP to install CentOS boxes via kickstart. For a first install, I boot the machine on the CentOS first CD, I type "linux ks" at the prompt and the rest is automatic. I have already use USB pen to boot some servers that don't have CD-ROM drive and all went well with the diskboot.img of CentOS 5.1. But the

Hi, all. I'm trying to customize a CentOS installation cd, but got trouble with kickstart. I want to use dialog[1] for command line based user interface, but it can't display correctly in kickstart with CentOS 5.5. Same ks file works with CentOS 5.3 (both i386 and x86_64). What's the different between CentOS 5.3/5.5? I can't find it in release notes. And how can i fix it? Thanks

Dear Friends, I have centos 6.2 64 bit os in my dell server. When I try to install centos or scientific linux using NFS so it is not working and getting me error = "unable to download kickstart file". My kickstart file configuration is : #platform=x86, AMD64, or Intel EM64T #version=DEVEL # Firewall configuration firewall --disabled # Install OS instead of upgrade install # Use NFS

Hello, I've been trying to kickstart a install centos from a USB memory stick. Everything with that is working fine, but I seem to be having a problem with the ks.cfg file. When I boot the install media from the usb drive, the the boot prompt I type linux ks=hd:/dev/uba1/ks.cfg Then I peek at the logs and it even says * getting kickstart file * getting kickstart file from harddrive *

Ok, so some of this now works, but I'm still having problems. With the bootif option, the system now correctly configures and uses the same interface to get its kickstart file. However, when the system is done and boots up, the interfaces are still messed up. So this is what I have in the kickstart file: # On-Board Port 1 with public IP configuration network --noipv6 --onboot yes --bootproto

I am trying to add a kickstart file to my automatic installation and make it more automatic. However, when I comment out the append ks=... line in the example below, the computer boots properly. If I uncomment that line, then I get a kernel panic: VFS: Cannot open root device "" or 09:02 Please append a correct "root=" boot option Kernel panic: VFS: Unable to mount root

On 18/04/2017 15:54, Frank Thommen wrote: > Hi, > > I am currently struggling with the right way to configure a bonding > device via kickstart (via PXE). > > I am installing servers which have "eno" network interfaces. Instead of > the expected bonding device with two active slaves (bonding mode is > balance-alb), I get a bonding device with only one active slave

Here's what I'm currently doing in ks.cfg: %pre #!/bin/sh echo -n "Please enter blah: " read blah echo $blah > /tmp/ks-blah I know that "read blah" works fine, because after that I see the variable in the /tmp file. The problem is, echo doesn't seem to work at this stage. This pretty much kills the idea of an interactive %pre script. I was thinking to

>Bryan J. Smith wrote: > >>Yes. DHCP is the successor to BOOTP that offers a superset of its >>functionality. But in the original BOOTP functionality, you would pass >>the filename the BOOTP client would retrieve from a TFTP server so it >>could boot. The file was then booted. >> >>This is how we have been installing workstations/servers in the UNIX

I am trying to use kickstart for automated builds from a DVD. Some of the machines have DVD's drives and some have CDRom drives only. With the CDRom only machines I would like to plug in an external DVD drive via USB and use this to kickstart. The DVD only machines work correctly with a isolinux.cfg as label test kernel vmlinuz append initrd=initrd.img ramdisk_size=8192

Thanks for that Jason but it didn't solve the problem. The system is still coming up with the interfaces shuffled. It seems to *always* want to use the added ethernet card as eth0. On Wed, Feb 25, 2015 at 1:37 PM, Jason Warr <jason at warr.net> wrote: > Starting back in RHEL/Cent 5 I found that the only way to make sure your > interface enumeration was consistent after install

On Mon, 13 Feb 2006, Omer Faruk Sen wrote: > Is it possible to embed more than one kickstart that will match the > installation interface's MAC address. What I want is to use boot system > using virtual CD (using iLO) to install multiple systems but matching > kickstart conf file will be used with the matching MAC address. I would look at creating special programs for syslinux