search for: cent6

...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 the kernel boot for the installed system. PXE boot options: label c6inst-sda kernel /linux-boot/cent6-x64/vmlinuz append initrd=/linux-boot/cent6-x64/initrd.img ksdevice=bootif ip=dhcp ks=http://xx.xx.xx.xx/install/linux/ks/basic-cent6-sda.cfg ipappend 2 In kickstart: BOOTOPTS="biosdevname=0" Also in kickstart I do not specify the config for ANY network interfaces. I let...

tl;dr - a renamed dummy interface is not persisting across reboots on Cent6. I have a situation where I need to rename a dummy interface on my system. I have a total of 3 dummy interfaces: dummy0 dummy1 adummy0 I've been doing some puppet testing in a vbox VM to get this all sorted out to deploy to a group of boxes. Every time I reboot my VM, it comes up WITHOUT a...

...t >> based on >> how anaconda has seen them. >> >> In order for this to work on Cent 6 you have to set biosdevname=0 on the >> kernel boot for the installed system. >> >> PXE boot options: >> >> label c6inst-sda >> kernel /linux-boot/cent6-x64/vmlinuz >> append initrd=/linux-boot/cent6-x64/initrd.img ksdevice=bootif >> ip=dhcp ks=http://xx.xx.xx.xx/install/linux/ks/basic-cent6-sda.cfg >> ipappend 2 >> >> In kickstart: >> >> BOOTOPTS="biosdevname=0" >> >> Also in...

...o 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 the > kernel boot for the installed system. > > PXE boot options: > > label c6inst-sda > kernel /linux-boot/cent6-x64/vmlinuz > append initrd=/linux-boot/cent6-x64/initrd.img ksdevice=bootif > ip=dhcp ks=http://xx.xx.xx.xx/install/linux/ks/basic-cent6-sda.cfg > ipappend 2 > > In kickstart: > > BOOTOPTS="biosdevname=0" > > Also in kickstart I do not specify the confi...

...;>> In order for this to work on Cent 6 you have to set biosdevname=0 on >>>> the >>>> kernel boot for the installed system. >>>> >>>> PXE boot options: >>>> >>>> label c6inst-sda >>>> kernel /linux-boot/cent6-x64/vmlinuz >>>> append initrd=/linux-boot/cent6-x64/initrd.img ksdevice=bootif >>>> ip=dhcp ks=http://xx.xx.xx.xx/install/linux/ks/basic-cent6-sda.cfg >>>> ipappend 2 >>>> >>>> In kickstart: >>>> >>>> BOOTO...

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

...ow anaconda has seen them. >>> >>> In order for this to work on Cent 6 you have to set biosdevname=0 on the >>> kernel boot for the installed system. >>> >>> PXE boot options: >>> >>> label c6inst-sda >>> kernel /linux-boot/cent6-x64/vmlinuz >>> append initrd=/linux-boot/cent6-x64/initrd.img ksdevice=bootif >>> ip=dhcp ks=http://xx.xx.xx.xx/install/linux/ks/basic-cent6-sda.cfg >>> ipappend 2 >>> >>> In kickstart: >>> >>> BOOTOPTS="biosdevname=0&quot...

Frank Even wrote: > On Wed, May 27, 2015 at 1:37 AM, Frank Even > <lists+centos.org at elitists.org> wrote: >> tl;dr - a renamed dummy interface is not persisting across reboots on >> Cent6. >> >> I have a situation where I need to rename a dummy interface on my >> system. >> >> I have a total of 3 dummy interfaces: >> >> dummy0 >> dummy1 >> adummy0 >> >> I've been doing some puppet testing in a vbox VM to get this...

...s to work on Cent 6 you have to set biosdevname=0 on >>>>> the >>>>> kernel boot for the installed system. >>>>> >>>>> PXE boot options: >>>>> >>>>> label c6inst-sda >>>>> kernel /linux-boot/cent6-x64/vmlinuz >>>>> append initrd=/linux-boot/cent6-x64/initrd.img ksdevice=bootif >>>>> ip=dhcp ks=http://xx.xx.xx.xx/install/linux/ks/basic-cent6-sda.cfg >>>>> ipappend 2 >>>>> >>>>> In kickstart: >>>>&gt...

...to set biosdevname=0 >>>>>> on the >>>>>> kernel boot for the installed system. >>>>>> >>>>>> PXE boot options: >>>>>> >>>>>> label c6inst-sda >>>>>> kernel /linux-boot/cent6-x64/vmlinuz >>>>>> append initrd=/linux-boot/cent6-x64/initrd.img ksdevice=bootif >>>>>> ip=dhcp ks=http://xx.xx.xx.xx/install/linux/ks/basic-cent6-sda.cfg >>>>>> ipappend 2 >>>>>> >>>>>> In kickstart: &...

On Wed, May 27, 2015 at 1:37 AM, Frank Even <lists+centos.org at elitists.org> wrote: > tl;dr - a renamed dummy interface is not persisting across reboots on Cent6. > > I have a situation where I need to rename a dummy interface on my system. > > I have a total of 3 dummy interfaces: > > dummy0 > dummy1 > adummy0 > > I've been doing some puppet testing in a vbox VM to get this all > sorted out to deploy to a group of boxes...

Hi, I am having problems installing Puppet Server. My gem list follows and then the attempt to install puppet-server. The specific errors are: Error: Package: puppet-3.2.1-1.el6.noarch (puppetlabs) Requires: ruby-augeas Error: Package: hiera-1.2.1-1.el6.noarch (puppetlabs) Requires: rubygem-json Error: Package: puppet-3.2.1-1.el6.noarch (puppetlabs)

...lar on debian boxes in the past and it surprisingly worked. This is the least bad of the terrible options I've provided (assuming it works). Install centos 7 in a vm. Get your app over there and see if it runs. If it does, run ldd on the box and copy all the dependencies to a directory on your cent6 box. You will have to run ldd on all the libraries you copy as well to get their dependencies. You will want to script that. Actually don't script it. You will give up with in 20 libraries. If you do get all the dependencies, you can override the library path by running your app like LD_LIBRARY...

I have a broadcom bcm5722 and a dual intel pro/1000 pt nic in a dell t110. The setup sees the cards and i put them into automatic mode. After the install no cards are detected at all. Astaro 8.01 detects and utilizes all of these cards just fine. I have also tried ubuntu server 10.04 lts and they work fine. I'm curious if this is a bug with Centos 6?

We have a third party shared library from a vendor that requires glib 2.15 or newer. We are using CentOS 6.6 which comes with glibc 2.12, and I know it can?t be replaced as it?s an integral part of the OS. However, is it possible to build a glib 2.15 RPM from source to be installed in /opt/centos (or somewhere else other than /usr/lib) so that I can link the one application that requires the