similar to: stupid question about kickstart file

I would like to how how I can take the CentOS 4.4 Server Cd for example and modify the ISO to put on my anaconda-ks.cfg file and then modify the kernel parameters to automatically load the anaconda-ks.cfg file so that I can create a CD that I just stick into my machine it will format the drive, install the basic configuration I like without asking any questions. I need to install like 20

Hi, I have a kvm host and I try to install a centos 6 guest with a static ip address. When I do a manual install I eventually get to the network configuration and if I enter IP, gateway and DNS Server I can ping6 the guest from the host and I can ping6 the guest from outside. I do not want to do manual installation, so I have to specify a url to a kickstart file, but to download it the network

Hi, For the OLPC school server ("XS") we are planning to move from our dated F9 setup to CentOS 6.2. Thanks for all the effort involved in producing this distro. One important part of this project is a 'respin' of the install media - we need to add a handful of packages from external repositories, and maybe run a command late in the install. Are the scripts/configurations used

I have a kickstart file that basically runs the following: install nfs --server=nfserver.blah.local --dir=/vol/updts/staging/CentOS_4.3 #include %some_file.cfg I want to be able to access or "include" a file on the nfs share not the local CDROM I've got this on. How do I do that? === Al

Hi List, Are you really using firewalld and network-manager on Centos 7 production servers or old way disabling network manager and using pure iptables like on C6? -- Eero

I was just wondering how (or indeed if) people use the %include directive in Kickstart configuration files when building systems via NFS. I've been trying to modularise our Kickstart files a little to make things more readable, having generic defaults and role specific stuff split out into separate configs. I've tried this configuration... [root at archive kickstart]# cat

I am getting the following error on boot on a new install Centos 51: #/bin/sh ro no such file or directory then a kernel panic I have traced it to the call ''switchroot'' in the init script in the initrd. the exact same build without zen has no problems. the boot messages look like: Attaching to iSCSI storage iscsistart: transport class version 2.0-724. iscsid version 2.0-865

Gordon Messmer wrote: > On 08/25/2016 11:35 PM, Phil Manuel wrote: >> The relevant kickstart section is:- >> >> part /boot/efi --fstype efi --grow --maxsize=200 --size=20 --ondisk=sda >> bootloader --append=" crashkernel=auto" --location=mbr --boot-drive=sda1 >> autopart --type=lvm > > A couple of things to consider: > * The documentation for

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

On 2/17/2015 12:31 PM, Eero Volotinen wrote: > 2015-02-17 22:26 GMT+02:00 Eckert, Doug<doug.eckert at dowjones.com>: > >> >We have a DHCP/PXE server in a build environment, which is separate from >> >our Spacewalk v1.5 server. We direct builds to Satellite or Spacewalk based >> >as needed. It contains initrd & vmlinuz files for each version/arch we

I have a kickstart file that I am using to install multiple machines. If I install with no %post script, everything runs great. When I add the following %post section, if fails. I have been working on this for a few days now without luck, Any help would be appreciated. Here is the error, the script follows. Traceback (most recent call first): File

Hey, someone just told me yesterday that I can give my machine an initial IP address, gateway, dns server, and netmask via command line like this: linux ks=http://www.mydomain.com/kick.ks ip=192.168.1.5 netmask=255.255.255.0 gateway=192.168.1.1 dns=192.168.1.10 Is this true? Is the syntax wrong or right? If so, and I call my kick.ks file and it has install cdrom it'll pull the files

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

Hi, I have alot of kickstart and scripting going on as I provision lots of machines, and every now and then I run into a pesky machine or three that's still got that Adeptec zero-channel RAID card sitting on the board. Normally I like to rip it our and throw something more robust in, but if it's a cache machine or whatever, I leave it in. It makes my kickstart file useless until I

hello there, I wonder if you could help me: I am trying to install 50 diskless servers using PXE / kickstart, it all starts well, DHCP server issues a dynamic address, tftp issues the kickstart file, the client starts reading the KS file but at some point anaconda brings up an unhandled exception related to Python when reading Comps.xml?? What is really unsettling is the fact that if I plug

Starting back in RHEL/Cent 5 I found that the only way to make sure your interface enumeration was consistent after install with what you had during install was to create a udev rules file using the mac addresses as the key. It is easy to run a short script in postinstall to create it based on how anaconda has seen them. In order for this to work on Cent 6 you have to set biosdevname=0

Hi I have been trying to get puppet working with kickstart. I am trying to install Hadoop on the nodes. Installing puppet from kickstart work and when the machine restarts, certificates are pulled down and hadoop user is created and files are extracted. I want all the user creation etc to be done before the machine reboots so that I can set up init.d scripts to do a start of hadoop . So I

I have successfully set up a very nice kickstart install with the i386 version of CentOS 4.3 and it works great. I am using a custom kickstart script and the kernel and initrd from disc1/images. But when I try to duplicate this for a 64 bit setup (changing paths in my tftp server, ks.cfg, etc to point to the 64 bit stuff) it successfully tftp's everything just as it should (tethereal

<overly trimmed> On 02/25/2015 01:56 PM, Ashley M. Kirchner wrote: > 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 >

Hi All. I am curious if it is possible to reinstall linux distribution to centos (or another distro) if I have a remote linux server with no kvm access (i do not want to use virtualization). I know that for installation pxe, tftpboot and kickstart or a proper iso/cd and kickstart are standard options. But for such operations I would need kvm access. Are there any alternatives which do not need