similar to: anaconda pgp rpm verification

I'am running into this https://bugzilla.redhat.com/show_bug.cgi?id=1206101 while trying to handcraft a kickstart file for CentOS7. Does anybody knowns a workaround? -- LF

Am 05.04.2017 um 15:02 schrieb Johnny Hughes <johnny at centos.org>: > > We are pleased to announce the immediate availability of CentOS Linux > 6.9 and install media for i386 and x86_64 Architectures. Release Notes > for 6.9 are available at: > > http://wiki.centos.org/Manuals/ReleaseNotes/CentOS6.9 > > CentOS Linux 6.9 is derived from source code released by Red

On 10/11/2020 17:18, Leon Fauster via CentOS wrote: > Hi folks, > > years ago I had no problem installing CentOS7 on my > iMac workstation (iMac Late 2015). The installation > worked out of the box. Today I wanted to upgrade to > CentOS8 and while configuring the partitions I get an > error that the installation can not start because: > "HFS+ ESP needed and mounted on

Hi all, I wonder if the gpgchecks are done while installing a system via anaconda? Any experts here? I was playing with the livemedia-creator and had a 3rd party repo in my ks file. The packages were installed without any problems although having not any key in the rpm db imported. So that leads me to the assumption that the gpgchecks are not done. How to get the integrity check done?

Hi folks, years ago I had no problem installing CentOS7 on my iMac workstation (iMac Late 2015). The installation worked out of the box. Today I wanted to upgrade to CentOS8 and while configuring the partitions I get an error that the installation can not start because: "HFS+ ESP needed and mounted on /boot/efi". In fact they are the same partition as for CentOS7. Is this a regression

> Am 08.05.2019 um 19:20 schrieb mark <m.roth at 5-cent.us>: > > Leon Fauster via CentOS wrote: >> Hi all, >> >> >> I still use the following kickstart partition scheme for C7 installations >> (via virt-install): >> Briefly, fixed size for /root and /boot, and the rest is filled up for >> /srv. >> >> The same kickstart

I have a kickstart file with the following partitioning directives: part /boot --fstype ext3 --onpart=sda1 part pv.100000 --onpart=sda2 --noformat volgroup vol0 pv.100000 --noformat logvol / --vgname=vol0 --name=lvol1 --useexisting --fstype=ext4 logvol /tmp --vgname=vol0 --name=lvol2 --useexisting --fstype=ext4 logvol swap --vgname=vol0 --name=lvol3 --useexisting logvol /data --vgname=vol0

Am 09.10.2016 um 19:41 schrieb John R Pierce <pierce at hogranch.com>: > On 10/9/2016 5:33 AM, Leon Fauster wrote: >> Interesting pointers. Are there somewhere any ks files for EL6? > > look in /root :) anaconda-ks.conf is a generated ks file for > the options you chose during that system's installation. :-) I had the creation of a EL6 livemedia in mind ... --

Am 10.10.2016 um 13:45 schrieb Johnny Hughes <johnny at centos.org>: > On 10/09/2016 06:15 PM, Leon Fauster wrote: >> Am 09.10.2016 um 19:41 schrieb John R Pierce <pierce at hogranch.com>: >>> On 10/9/2016 5:33 AM, Leon Fauster wrote: >>> >>> look in /root :) anaconda-ks.conf is a generated ks file for >>> the options you chose during

Hello, I think you can use anaconda for this task, you can configure some actions after the installation. Best regards, El dt, 8 nov 2016 a les 18:44 Leon Fauster <leonfauster at googlemail.com> va escriure: > Am 08.11.2016 um 16:47 schrieb cpolish at surewest.net: > > On 2016-11-07 14:35, Bernard Fay wrote: > >> Hi, > >> > >> We have a virtual

Leon Fauster via CentOS wrote: > I'am running into this > > https://bugzilla.redhat.com/show_bug.cgi?id=1206101 > > while trying to handcraft a kickstart file for CentOS7. > > Does anybody knowns a workaround? > Are you saying you have an existing partition on the system(s) that you want to run the install against already have an encrypted partition? Can't you

How you could do this with scripts: *CentOS 7* 1. Deploy a VM from your base CentOS 7 template 2. Copy your "my-firstboot.sh" script (or whatever its called) to a location such as /root/scripts/ 1. This scripts only job should be to mount a NFS location and execute any post install scripts you have stored there, and provide a log file. 2. This script

I am building a latest CentOS5 and every newest stuff is ready. All are in directory "/linux/CentOS/5-respin/os/x86_64". My OS is CentOS5 too. I want to add some other pictures during installation process, so anaconda adjustment is needed. When I run command "anaconda --test --method=http://192.168.0.3/linux/CentOS/5-respin/os/x86_64", a error message followed: Traceback (most

I have a bunch of HP BL465c G5 blades, with additional dual-port network adapters. The onboard interfaces use the bnx2 driver, while the expansion card uses tg3. All 4 interfaces are detected by both Anaconda and the installed system, but Anaconda is reversing the ordering: Anaconda: eth0 Card 2, Port 1 eth1 Card 2, Port 2 eth2 Card 1, Port 1 eth3 Card 1, Port 2 BIOS and Installed Kernel:

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

Am 16.04.2015 um 11:46 schrieb Leon Fauster <leonfauster at googlemail.com>: > Am 16.04.2015 um 11:43 schrieb Eero Volotinen <eero.volotinen at iki.fi>: >> Is there any nice way to get tlsv1.2 support to centos 5? >> upgrading os to 6 is not option available. > > > Unfortunately not. https://bugzilla.redhat.com/show_bug.cgi?id=1066914 -- LF

Kickstart fails for statically built custom booting kernel, although the custom kernel is built form the same version stock kernel source. My anaconda and kernel source are both of stock versions on Centos 5. At the kickstart 'F3' screen, the following error messages appear: Modules to insert tg3 ... ... ERROR: no network devices in choose network device! ERROR: no network drivers

Am 22.02.2015 um 07:20 schrieb Robert Arkiletian <robark at gmail.com>: > On Fri, Feb 20, 2015 at 6:47 AM, Leon Fauster <leonfauster at googlemail.com> > wrote: > >> Am 20.02.2015 um 13:53 schrieb "Phelps, Matthew" <mphelps at cfa.harvard.edu >>> : >>> Any new information here? >> >> maybe some cooperation with the fedora

Forgot to mention. After this is setup, shutdown the VM and create a template from it. Then, any VMs created from this new template will auto execute your scripts. Bill On Wed, Nov 9, 2016 at 7:01 AM, Bill Howe <howe.bill at gmail.com> wrote: > How you could do this with scripts: > > *CentOS 7* > > 1. Deploy a VM from your base CentOS 7 template > 2. Copy your

I did a quick search through the archive and couldn't find anything that mapped to my need, so I figured I should ping the community and see if anyone has the requisite knowledge and could point me in the right direction. *Succinct Version* Is there a way to, using updates.img, monkey patching or swapping in a newer Anaconda (>= 16) to force all disks to have gpt labels and not just