similar to: Help with dracut install CentOS 8

I am trying to boot a grub entry for CentOS 8 menuentry "Server Install CentOS 8" { linux /boot/vmlinuz noverifyssl ks= https://devgeis.LayeredSolutionsInc.com:443/kickstart/ks_update_to_server8.cfg biosdevname=0 net.ifnames=0 ksdevice=eth0 ip=192.168.1.13 gateway=192.168.1.1 netmask=255.255.255. 0 nameserver=192.168.1.1 inst.sshd sshd=1 initrd /boot/initrd.img

On 2019-11-18 12:45, Stephen John Smoogen wrote: > On Mon, 18 Nov 2019 at 13:22, Jerry Geis <jerry.geis at gmail.com> wrote: >> >> I am trying to boot a grub entry for CentOS 8 >> >> menuentry "Server Install CentOS 8" { >> linux /boot/vmlinuz noverifyssl ks= >>

On Fri, Nov 29, 2019 at 11:06 AM Orion Poplawski <orion at nwra.com> wrote: > On 11/29/19 6:55 AM, Jerry Geis wrote: > >> I am trying to specify a static IP on the new dracut format. I was using > >> this: > >> http://man7.org/linux/man-pages/man7/dracut.cmdline.7.html > >> > >> So my grub entry consists > >> menuentry "Install

On 11/29/19 6:55 AM, Jerry Geis wrote: > I am trying to specify a static IP on the new dracut format. I was using > this: > http://man7.org/linux/man-pages/man7/dracut.cmdline.7.html > > So my grub entry consists > menuentry "Install CentOS 8" { > linux /boot/vmlinuz noverifyssl ks=https://something >

On Mon, 18 Nov 2019 at 13:22, Jerry Geis <jerry.geis at gmail.com> wrote: > > I am trying to boot a grub entry for CentOS 8 > > menuentry "Server Install CentOS 8" { > linux /boot/vmlinuz noverifyssl ks= > https://devgeis.LayeredSolutionsInc.com:443/kickstart/ks_update_to_server8.cfg > biosdevname=0 net.ifnames=0 ksdevice=eth0 ip=192.168.1.13 >

This should be easy to answer (I hope).? We routinely kickstart boxes to use for managing our customers RADIUS/DHCP configurations (along with other things).? We've had a C7 kickstart in place since I built one in May and are finally starting to roll it out for new installations.? But, I'm curious as to what ksdevice= actually does. With the C6 we routinely used ksdevice=eth0 since we

Hello All Up until now we have been using standard PXE boot to do kick start installs of centos boxes. With recent machines however they come by default as EFI boot. We can set them to legacy but I would like to solve this before this option goes away. Just wondering if anyone has any experience setting up a net boot server that can be used to kickstart EFI machines? Thanks Grant

https://bugs.freedesktop.org/show_bug.cgi?id=57034 Priority: medium Bug ID: 57034 Assignee: nouveau at lists.freedesktop.org Summary: [Quadro FX 4800] display port connectors not recognized QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All)

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

With dovecot-2.2.36-3.el7.x86_64 we had a couple hours where mail_plugins did not properly include zlib for all of the needed services. This seems to have led to some corruption in our mdbox mailboxes. I've run doveadm force-resync on a number of users, but I'm still seeing messages like this: dovecot[13563]: imap(USER): Error: Corrupted record in index cache file

I'm trying to figure out a puzzling thing that we are seeing with some recently joined or re-joined samba servers. Our linux servers are in a different DNS domain than our AD machines (nwra.com or cora.nwra.com vs ad.nwra.com for the AD machines). Generally when we've joined a machine to AD the DNS name recorded in AD is their regular linux FQDN. But a couple machines have ended up with

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

I want to use fprobe-ulog (http://fprobe.sourceforge.net/) to generate NetFlow information about traffic going through my router. The question is how to get the logging rules added to the appropriate chains (I''m assuming eth2_in and eth2_out in my case)? I''m using the perl version of shorewall 4.0.6. -- Orion Poplawski Technical Manager 303-415-9701

Looks like the GPG key we use to sign our RPMs is not longer good with EL9: # rpm --import RPM-GPG-KEY-nwra error: RPM-GPG-KEY-nwra: key 1 import failed gpg key info: sec rsa2048/35DDB0B86218AC2F created: 2017-08-16 expires: never usage: SC trust: ultimate validity: ultimate ssb rsa2048/6A7FBC1E9DB22E8E created: 2017-08-16 expires: never usage: E Can someone

Good morning, I'm try to install KDE on C8. I can see the grouplist for KDE: yum grouplist Last metadata expiration check: 0:06:07 ago on Sat 25 Jan 2020 11:43:01 AM EST. Available Environment Groups: Server with GUI Server Minimal Install KDE Plasma Workspaces Virtualization Host Custom Operating System Installed Environment Groups: Workstation Installed Groups:

Please see https://bugzilla.redhat.com/show_bug.cgi?id=727648 for more info. Shorewall executes some bash code like the following: while read address interface external haveroute; do qt $IP -4 neigh del proxy $address dev $external [ -z "${haveroute}${g_noroutes}" ] && qt $IP -4 route del $address/32 dev $interface

On 6/1/22 13:43, Fabian Arrotin wrote: > On 01/06/2022 19:51, Orion Poplawski wrote: >> Looks like the GPG key we use to sign our RPMs is not longer good with EL9: >> >> # rpm --import RPM-GPG-KEY-nwra >> error: RPM-GPG-KEY-nwra: key 1 import failed >> >> gpg key info: >> >> sec? rsa2048/35DDB0B86218AC2F >> ????? created: 2017-08-16?

On Fri, 3 Nov 2017, Mark Haney wrote: > On 11/01/2017 05:02 PM, James A. Peltier wrote: >> Leaving ksdevice= off the command line will prompt you for the location of >> the kickstart file and the device you want to use to kickstart >> > Well, things just got weird with this.? The first couple of times I included > the biosdevname etc, on the command line with

Nux! wrote: > Hello, > > ksdevice specifies which NIC to be used during the network install. > > The new naming conventions indeed make this more complicated than it needs > to be. To go back to the old naming scheme (eth0, eth1 ...) just add this > to boot parameters (kernel cmdline): > biosdevname=0 net.ifnames=0 Yes! Actually, the other admin I work with and I were just

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