similar to: Duplicating an install

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

So I took the anaconda cfg, commented out the partition/disk pieces and ran it off my repo server and it almost worked. Little things like not including things I had done on network setup. No first boot.... :) So now I am reading up on building a kickstart cfg http://wiki.centos.org/TipsAndTricks/KickStart http://www.centos.org/docs/5/html/5.2/Installation_Guide/s1-kickstart2-howuse.html

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

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

Well I now have a 4.0 server at a solid checkpoint. Before I start the chore of setting up SAMBA and LDAP. Part of the delay was I did not copy all of the needed DNS files, and I have to reerad the BIND book. So I want to be able to get to this point again easily. I did not note down what options I had selected during install. Is there some way in the install log to figure that out? Is

I've recently been dealing with various CentOS images on AWS, and am being forcibly reminded that the "/root/anaconda-ks.cfg" has only a passing resemblance to whatever the kickstart configuration file actually contained. But getting a copy of the actual "ks.cfg" is invaluable for updating and testing variations of the kickstart setup, especially when manipulating disk

Hi, Is is possible to use kickstart file to install rhel from dvd drive? Mainly idea is to clone one anaconda.ks file to about twenty machines.? examples? ftp/http/dhcp is not possible due to network limitations. -- Eero

Since neither anaconda nor system-config-kickstart can give a list of all packages that has been installed, waht is the recommended way to replicate one system for another new installation (without using hd cloning) ? Is it possible to simply do 'rpm -qa >> my-ks.cfg' ? When running anaconda installer, it gives system selection as well as package grouping (desktop vs server ->

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

I am building three identical systems. Well they will have different host names, and with time the software setups will drift. But at install time they are identical. Is there some way, (with dd I might guess) to do a hardare level copy? All three drives are Hitachi DK23DA-40F (40Gb). Supposedly factory reconditioned (they are in sealed bags with a drive sticker stating: "Refurbished

I'm having what appears at first glance to be a kickstart+anaconda issue on CentOS 7.4. As near as I can tell in the program.log in the anaconda environment, the partitioning instructions downloaded with the kickstart from cobbler appear to simply not be applied. Then /mnt/sysimage is not mounted, the logs are not copied to /mnt/sysimage/root and the installation stalls due to the anamon

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

Hello, I have a CentOS install that has updated packages, and different users with certain privileges and modified GNOME menus. When a user logs in they are very limited to what they can do. i.e. browse the internet, run some php scripts on the local MySQL database I have set and that's about it. I would like to take the stuff I setup and make it extremely easy for someone to duplicate the

Hello, I need to automate installation of CentOS 7.0 using PXE and kickstart. My server is diskless, I'm installing CentOS on a 25GB LUN on a FC SAN with 4 paths. This LUN is the only one accessible by the server. Anaconda processes successfully the installation. But on reboot, I get stuck on a prompt after BIOS. I think I have an issue with storage configuration / bootloader

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

I realize that the @everything packages option is now gone in CentOS 5.0 (ix86 and x86_64), but my experiments to date don't show how to practically simulate the same effect (and I have a good reason for doing so). I want all packages, all languages. If one installs from CD, and selects all packages and options, the resulting anaconda-ks.cfg file does not have a complete package list. For

On Tue, 23 Aug 2016 at 02:18 Gordon Messmer <gordon.messmer at gmail.com> wrote: > On 08/21/2016 11:56 PM, Phil Manuel wrote: > > part /boot/efi --fstype="efi" --size=200 --ondisk=sda > > And I have tried the latter with location as mbr still fails > > What am I missing ? > > > I very vaguely remember struggling with this as well, but I can't find

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

Hello, I am trying to build a PXE boot image for CentOS 7. livemedia-creator --make-pxe-live --ks=ks --no-virt It runs the entire process and then it says: losetup: /dev/: detach failed: Inappropriate ioctl for device 2019-12-26 11:49:47,293: Disk Image install successful 2019-12-26 11:49:47,293: working dir is /var/tmp/tmpKwqC77 mount: /dev/loop0 is write-protected, mounting read-only mount: