similar to: Kickstart Tips and Tricks

Good Evening. I am currently working on a translation of a wiki page where parameter descriptions are used in the following form: --parameter:: the description of the parameter The problem is that the description is not always formatted correctly. (take a look at http://wiki.centos.org/de/TipsAndTricks/KickStart ) Using: --parameter:: the description of the parameter works correctly but

Good Evening. As the 'translation community' is growing I would like to suggest to add the 'revision number' of the original article on which the translation is based on, so someone else could easily diff to keep translations up to date. It would be great if translators add something like: 'translation based on #N' as footnote where N is the version of the original

Good Evening, I am trying to set up an iptables forward rule in order to forward all packages that are routed throgh the internal device eth0: iptables -A FORWARD -i eth0 -o eth0 -m state --state NEW -j ACCEPT but the packages are still dropped. Best Regards Marcus

Good Evening, I am trying to forward packages on an internal device using iptables: /sbin/iptables -A FORWARD -i eth0 -o eth0 -m state --state NEW,RELATED,ESTABLISHED -j ACCEPT but the packages are still blocked, e.g.: Feb 6 20:58:28 firewall kernel: DROP-TCP IN=eth0 OUT=eth0 SRC=192.168.100.177 DST=172.28.2.184 LEN=40 TOS=0x00 PREC=0x00 TTL=127 ID=16609 PROTO=TCP SPT=7166 DPT=3590 WINDOW=0

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

Is there a way to use kickstart to boot a machine into a manual setup process? Basically what I'm getting to is this, the machine doesn't not have a CD drive in it (nor can I add one), but I can boot it via kickstart. The install media is on the network. What I'd like to do is boot this machine up and rather than have kickstart do everything for me as far as installing the OS and

Hi all, This the latest output from anaconda.log:- 06:08:54,828 DEBUG anaconda: new disk order: [] 06:08:54,832 DEBUG anaconda: new disk order: [] 06:08:54,851 DEBUG anaconda: stage1 device cannot be of type disk 06:08:54,865 DEBUG anaconda: _is_valid_disklabel(sda1) returning True 06:08:54,867 DEBUG anaconda: _is_valid_size(sda1) returning True 06:08:54,867 DEBUG anaconda:

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've searched around but haven't found a definitive answer yet, is it possible to kickstart from a tagged VLAN? I found this bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=431915 But I can't find out how far the vlan support goes. I haven't found anything about it in any kickstart docs. I have two tagged vlans: Vlan 100 - server subnet Vlan 101 - backup subnet From

I'd like to automate the upgrade from CentOS 4.6 to 5.1 as much as possible. Since upgrades per se are not really recommended, I'm planning to do a kickstart installation. However, I want to leave one of the existing partitions (/scratch) untouched during the installation. Here is my current layout (LogVol00 is swap so not shown in the df output below): # df -hl

Ray Van Dolson wrote: > On Tue, Apr 22, 2008 at 12:47:39PM +0100, Plant, Dean wrote: >> I would like one of my kickstart scripts to prompt for disk and >> networking only. Commenting out the disk and network settings makes >> the installer prompt for disk settings but not for network settings, >> they default to DHCP. Any idea's how to fix this? > > I'm

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

Does anyone know how anaconda partitioning enumerates disk partitions when specified in kickstart? I quickly browsed through the anaconda installer source on github but didn't see the relevant bits. I'm using the centOS 6.10 anaconda installer. Somehow I am ending up with my swap partition on sda1, /boot on sda2, and root on sda3. for $REASONS I want /boot to be the partition #1 (sda1)

----- 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

I recently built a CentOS from the 4.3 ISOs. Now I'm ready to build another 10 systems using kickstart. I took the anaconda-ks.cfg file from the first system I built manually, modified it slightly (see below), and made it available via http. I booted the new system from the first CentOS 4.3 CD and typed the following: boot: linux ks=http://hostname/test-ks.cfg Here are the

On Fri, Aug 26, 2016 at 10:39 AM, Gordon Messmer <gordon.messmer at gmail.com> 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

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

I am testing a CentOS 7.6 kickstart installation. After kickstart was initiated, the installation stops at some point where a sort of table is printed under "Installation", and the item that fails is 4 - Software selection, Error checking software selection. I have checked /tmp/packaging.log and /tmp/anaconda.log, but cannot find any errors here that would prevent installation. Poor

Hi, I am struggling with kickstart. What I want to achieve is a reinstall, but some data partitions should survive the install, i.e. they should not be formatted. With a single disk this works, here is the relevant part from the kickstart file (I shortened the name of the volume group) ... zerombr clearpart --none --initlabel part /boot --fstype="xfs" --label=boot --onpart=vda1 part

Hi everyone, I am trying to set up an automated CentOS installation system. My idea is to use PXE to boot the kernel/initrd and pass the kickstart options to the kernel from there. This works correctly until it boots up Linux. As soon as it does that it makes a DHCP request and, unsurprisingly, it gets the same one (same MAC) but it also gets the filename and next-server details. Then Anaconda