similar to: CentOS 8 boot command line

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

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 ip=192.168.1.3::192.168.1.1:255.255.255.0::eth0:on:192.168.1.1 biosdevname=0 net.ifnames=0 ksdevice=eth0 inst.sshd sshd=1

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 >

So I have two CentOS 7 machines running. if I am on my server and I do "curl http://192.168.1.8" I get data. If I do "host devgeis.LayeredSolutionsInc.com" I get the correct address 192.168.1.8 if I goto another machine with CentOS 7. I do "curl http://192.168.1.8" I get data. I do "host devgeis.LayeredSolutionsInc.com" I get the correct address

Did you notice the address ? It is not the same IP. Patrick Le 02/11/2020 ? 17:48, Jerry Geis a ?crit?: > So I have two CentOS 7 machines running. > > if I am on my server and I do "curl http://192.168.1.8" I get data. > If I do "host devgeis.LayeredSolutionsInc.com" I get the correct address > 192.168.1.8 > > if I goto another machine with CentOS 7.

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

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

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 >

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

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

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

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

Here is my script for post install if you want to try it. In order for the shuffling to not occur you do need to create the udev rules file somehow. I am not sure how mangled this will be in email but it is worth a try. It should run OK with nothing else. I have a better version in the works but the enhancements are mainly useful for Fedora 19-21. I did forget to say I also block

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 23/02/15 08:16 PM, Steven Tardy wrote: > >> On Feb 23, 2015, at 6:34 PM, Ashley M. Kirchner >> <ashley at pcraft.com> wrote: >> >> I have a Dell server that has two built-in ethernet devices. When >> I kickstart the machine, they are correctly identified as eth0 >> and eth1 (correctly meaning they

Define out of order in this case just so I know for sure what you mean. What my solution does, or at least does reliably in my case, is make sure the interfaces are in the same order once installed as the install kernel saw them. It won't re-order them to be sequential based on bus, mac or driver. I am working on that but it will also include naming the devices based on the module

I have a Dell server that has two built-in ethernet devices. When I kickstart the machine, they are correctly identified as eth0 and eth1 (correctly meaning they correspond to the physical device ports 1 and 2). I need a third one and want that to come up as eth2. After adding the hardware, kickstart now fails because for some reason it goes through a rename process where it makes the newly added

> > We are not ready for "prime-time" though. > Using the "lpxelinux.0" file from 6.03-pre19 ... > > My RHEL5 installs, when using the "http://" for kernel, initrd and append lines, seem to be hitting some sort of parameter length limit. > The culprit seems to be the long "append" line. > > The same append line, when NOT using

El Lunes 01/02/2016, Daniel Ruiz Molina escribi?: > Hi, > > After installing CentOS 7 in a server with 2 NICs, system detects eth0 > and eth1 in reserve order. I would like to have eth1 as eth0 and eth0 as > eth1. I have forced HWADDR attribute in > /etc/sysconfig/network-scripts/ifcfg-etc{0,1}, but after rebooting, > order is the same... > > How can I solve it? >