similar to: password protect kickstart ftp

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 *

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

>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 asking this here, that although a kickstart question, may have something to do with the Centos install? I took my Anaconda-ks.cfg from my system, turned it into a ks.cfg and did the install. Everything SEEMS ok, but why? First the partitioning information: ks.cfg supplied: clearpart --all --drives=hda part /boot --fstype ext3 --size=100 --ondisk=hda part / --fstype ext3 --start=14

Hi listers i tried to kickstart-install CentOS 6.0 64 in a Virtualbox (Virtualbox Version 4.12). I used a local CDROM with the net-install ISO on it to boot from. The ISO distribution file was provided on a server in the LAN as was the kickstart file. When starting the installation i aded the following to the kernel line of the grub menu: ks=http://install.mydomain.com/ks/centos.6.64.cfg

I'm trying to kickstart a Centos 4.1 system with the minimum set of packages. I have no use for ypbind so I'm trying to prevent from being installed, but kickstart/anaconda always insist on its installation (complaining that the package is missing). This is the %packages section of my ks file so far: %packages #-@ dialup kernel grub e2fsprogs lvm2 -slocate -bluez-utils -bluez-bluefw

I have to say that I was more that a bit surprised, if not to say dismayed when I booted a system with CentOS 5 installed to test a kickstart CD in interactive mode, took it to the custom partitioning screen, then rebooted without saving anything only to come up with a grub prompt, and the disk's partition table wiped. The ks.cfg file did say to wipe the disk when installing, but I would

I took my anaconda-ks.cfg file, cp to ks.cfg and copied to a floppy The isos have been copied to an ftp server. So I had the following lines in my ks.cfg intall url ftp://10.1.1.1// (yes the ftp server's directory is the Centos directory) This is along with all the appropriate network command to get the ethernet setup. I issue the linux ks=floppy (also tried linux

Hi, I?m trying kickstart on CentOS Below is my ks.cfg *[root at localhost ~]# cat /root/ks.cfg* * * #Generated by Kickstart Configurator #platform=x86, AMD64, or Intel EM64T #System language lang en_US #Language modules to install langsupport en_US #System keyboard keyboard us #System mouse mouse #Sytem timezone timezone Asia/Dili #Root password rootpw --iscrypted

I've been using kickstart for a while now, but today I tried to kickstart a system and it's just not working at all. I can't figure out why it's hanging. I booted from the CentOS 4.5 CD #1 and typed "linux ks=http:// centosmirror/ks/sys20.cfg". If I check my web server's log, I can see that sys20.cfg was accessed. This file begins with the following

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

Hi, I am working on a kickstart install method and it works fine with cdrom as installation media. I would like change this media to an online resource. I saw option as - 'url --url http://<server>/<dir>'. I am not sure what should be the directory contents? Should we put all ISOs in that directory or what? Any insights? Thanks, CS.

I've set up a local webserver to store kickstart files for domUs. All parameters are respected apart from the network settings. DomU always gets DHCP. Can any one help to unwrap this one? Does one add hostname, ip, netmask and gateway values to the /etc/xen/blah.cfg file? # ---- domU kickstart file ----# url --url http://192.168.1.120/centos/5/os/i386 lang en_US.UTF-8 keyboard uk network

On Thu, August 4, 2016 7:13 pm, Paul Heinlein wrote: > On Thu, 4 Aug 2016, Valeri Galtsev wrote: > >> Dear Experts, >> >> Could somebody point to kicstart HOWTO specific for CentOS 7? >> >> On CentOS 7 I somehow am always given human intervention questions >> about drive which defeats unattended ks install. >> >> At least one snag I hit

How does one use virt-install and kickstart ? I've seen others have success but I've had no joy thus far. BTW, my interactive virt-installs for centos6 guests work just fine AND I can do unattended kickstarts for vms by booting from centos6 install dvd and typing the kickstart commands from the boot: prompt. However, kickstart commands in --extra-args when used w/ virt-install just

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

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

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

Dear Experts, Could somebody point to kicstart HOWTO specific for CentOS 7? On CentOS 7 I somehow am always given human intervention questions about drive which defeats unattended ks install. <rant ??> I'm doing kickstart installations for quite some time, normally I was just installing system when new release comes, and am basing kickstart file on anaconda-ks.cfg - with some