similar to: CentOS 7 kickstart repo directive

On 2019-10-03, isdtor writes: > Is the kickstart repo directive broken under CentOS 7? Every attempt with a repo directive in the kickstart file fails during the software selection step. Removing the repo directives and the packages from those repos under %packages makes it work. > > On console 2, I have verified that the (NFS) repos specified in the kickstart file are mounted and that

On Fri, Dec 14, 2018 at 10:04 AM isdtor <isdtor at gmail.com> wrote: > > > > So the syntax looks to be > > > > > > repo --name=epel --baseurl=nfs://server:/path > > > > > > that colon after server is not a spelling error. > > > https://pykickstart.readthedocs.io/en/latest/kickstart-docs.html#id48 > > > > That seems to work

Stephen John Smoogen writes: > On Fri, 14 Dec 2018 at 05:02, isdtor <isdtor at gmail.com> wrote: > > > > Is it not possible to use an nfs based repo for kickstart under CentOS 7.5? > > > > E.g. > > > > repo --name=epel --baseurl=file://server/path/to/local/copy/of/epel > > > > So the syntax looks to be > > repo --name=epel

Is it not possible to use an nfs based repo for kickstart under CentOS 7.5? E.g. repo --name=epel --baseurl=file://server/path/to/local/copy/of/epel With trial and error I figured out that this is the correct syntax to use for an nfs-based repo. But packages from this repo in the %packages section are not found. You have specificed that the package 'bla' should be installed. This

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

To reduce memory consumption clobbered registers are handled with RegisterMask machine operands which contain a bitset of all registers clobbered. - Matthias > On Jul 29, 2015, at 3:00 PM, Daniel Sanders <daniel.sanders at imgtec.com> wrote: > > I believe I've identified the problem with almabench but I haven't found the root cause in the compiler yet. > > The

Thanks. This is making a lot more sense now and it's looking like this issue isn't Mips specific. Here's the IR dump before simple register coalescing (note: I've patched the IR printer to print the contents of the regmask): 4480B %vreg260<def> = LDC1 %vreg253, <cp#3>[TF=6]; mem:LD8[ConstantPool] AFGR64:%vreg260 GPR32:%vreg253 4496B %vreg261<def> = FMUL_D32

Has anyone managed to create an encrypted disk partition with CentOS 8 kickstart? 1 reqpart --add-boot 2 part /boot --fstype ext3 --size=1024 --ondrive=sda 3 part pv.1 --size=1 --grow --ondrive=sda --encrypted --pashphrase="bla" 4 volgroup vol0 pv.100000 5 logvol / --vgname=vg_00 --name=lv_root --size=102400 --fstype=ext4 ... No matter what I specify in line 3, the installer bombs out.

Both BaseOS and AppStream are needed. --- virt-p2v-make-kickstart.in | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/virt-p2v-make-kickstart.in b/virt-p2v-make-kickstart.in index 779ba62..cbbfb8a 100644 --- a/virt-p2v-make-kickstart.in +++ b/virt-p2v-make-kickstart.in @@ -176,6 +176,16 @@ repo --name=rhel6_${minor}_server_optional --baseurl=$baseurl/Server/optional/$a

Pete Biggs writes: > On Tue, 2019-07-30 at 13:24 -0400, John Chludzinski wrote: > > I've been doing a CentOS 7.6.1810 net-install since last night. The machine > > seems ok but has been stuck with "performing post-installation setup tasks" > > for hours. This is an old Dell T5400 box, so it isn't blazing fast but ... > > > > Is there a way to

Attempting to PXE boot from the BaseOS/x86_64/kickstart/images/pxeboot/ files results in repeating messages Invalid or corrupt kernel image eventually changing to Could not find kernel image: centos8.2.x86_64/vmlinuz I downloaded the files again, from a different mirror, and they are all the same. Wiped the files and recreated /tftpboot/linux-install/centos8.2.x86_64/. No dice. First mirror

Hello all - (Please forgive me if I sent this msg twice, first one didn't seem to go through) I searched through the archives and did not see anything about this (along with google), but if I missed something please don't hesitate to send me some links. Basically I have hit a problem that I cannot figure out at this point and seemed to have ran out of ideas via Google or the

Hello, Our environment: CentOS 5.2 (updated over time with "yum update", current "yum update" lists about 7 packages out of date), x86_64. Running Xen, building Xen DomU's with kickstart. We are trying to debug the %post part of the kickstart process for DomU and are hitting difficulties in accessing the output. For a start, the "cmdline" directive in the

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

Am 08.05.20 um 13:53 schrieb isdtor: > Here's another interesting observation. > > For previous versions, I was able to reduce the size of the updates mirror significantly by running repomange -o and deleting the resulting files on next sync. With the AppStream repo, this no longer works, the anaconda installer will complain that at least one package has an incorrect checksum, and

Hi, The CentOS 5.2 release notes contain this warning: "A kickstart installation that attempts to use the *repo* directive (where that *repo* points to an updates repository) may fail to properly install." This is exactly the method that I had been using with CentOS 5.1 :-) What is the right way to achieve this now? Is adding a repository in the %post section of the kickstart file and

I'm testing doing kickstart installations on Xen VMs. This is the first time I'm trying out kickstart at all, so I rather think I'm doing something wrong in the kickstart configuration than it is a Xen issue. I use a modified kickstart file from an earlier manual installation with a very basic filesystem setup. It fails with "SystemError: vgcreate failed for VolGroup00".

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

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, I'm testing new "minimal" kickstarts files for CentOS6 and CentOS7. The CentOS6 kickstart works fine, but i've a dependency problem with the CentOS7 equivalent. In my kickstarts, i use network install with following repos/packages (for the repo, the only change is version number 6 <-> 7): url --url="http://mirror.in2p3.fr/ftp/linux/CentOS/7/os/x86_64/"