similar to: Redefine ethX interface names in CentOS 5.11?

Hi, I'm currently experimenting with CentOS 7 in order to get a grasp of everything that's new. After having read the FAQ entry on network interface names, I decided to revert to the tradictional interface naming scheme by adding the relevant kernel options to the bootloader. This went well, I have now two interfaces names 'eth0' and 'eth1' as expected. In my office

Nicolas Kovacs wrote: > Hi, > > I have a LAN server running CentOS 5.11 with two NICs eth0 and eth1. I'd > like to swap the interface names, but I don't know how to go about that > under CentOS. > > Here's what I would do on a Slackware server (I have one next to me in > my office). > > Open /etc/udev/rules.d/70-persistent-net.rules and edit it: > >

centos 5 had modprobe.conf entries for eth0 and if present eth1. something like: alias eth0 forcedeth alias eth1 e1000e For the new centos 6 (I have the rhel 6 client installed on my laptop) the modprobe.conf file is gone. Which is fine. I understand files can be created in /etc/modprobe.d and server the same purpose. My question is I dont see (doing a grep) any eth0 alias's in the files in

Hi, I've done my fair share of CentOS 7 installations, but this is the first time I have this kind of weird problem. Here goes. In my office I have a battered Dell Optiplex 320 PC with two NICs that I'm using as a bare metal sandbox server for testing purposes. The CentOS 7 installer sees the connected network card as eth0. But after the first reboot, the interface comes up as eth1.

There may be ways to force NIC naming, I've done so but only on Ubuntu so you'll need to do the research if it's important to you. Things to look for based on my experience: 70-persistent-net.rules, net.ifnames=0, biosdevname=0. ________________________________ From: CentOS <centos-bounces at centos.org> on behalf of Nicolas Kovacs <info at microlinux.fr> Sent: Sunday,

Ian Campbell <ijc at hellion.org.uk> writes: #I think at a minimum to make any progress we would need to see some #logs. Probably the dom0 dmesg (perhaps compared to the native boot #dmesg) and the set of modules which are loaded would be a good start. #Probably xen's dmesg would be useful too. Lastly, it would be good to #mention what sort of keyboard this is (USB, PS2?) # #Also the

Control: tag -1 +moreinfo On Tue, 2014-05-13 at 08:55 -0700, Mike Egglestone wrote: > After booting into kernel 3.13 dom0, the keyboard no longer works. > All other aspects work, ssh is needed to login to the system to > start working with the domU's. > They keyboard works at the grub menu just fine, and > works normal when booting into the non xen kernel. I think at a minimum

Hi, I'm running CentOS on all kinds of setups: servers, workstations, desktops and laptops. Up until now, I'm only using NetworkManager on laptops, since it makes sense to use it there. On servers and desktop clients, I usually remove it and configure the network "traditionally" by simply editing /etc/sysconfig/network-scripts/ifcfg-whatever, /etc/resolv.conf, /etc/hosts,

Hi, I'm just migrating some stuff from Slackware Linux to CentOS, and I have a question about the orthodox way of configuring a network connection. On a desktop or workstation, I usually get rid of NetworkManager: # systemctl stop NetworkManager # yum remove NetworkManager Then I edit the /etc/sysconfig/network-scripts/ifcfg-XXXXX file corresponding to my network interface. Here's

Hi, I have a few identical Dell Optiplex 7010 machines that I want to use for our school's computer room. I tried to clone these installations (like I did before on CentOS 5 and various versions of Slackware), but this time I ran into a problem. Here's what I did. 1. Install one computer and zero unused hard disk sectors with dd. 2. Send the image to a local FTP server using G4L

Le 18/02/2020 ? 12:28, Anand Buddhdev a ?crit?: > Neither. The DNS configuration should not normally be bound to a > specific interface, so don't configure it with any interface. If you do, > and that interface goes down, your DNS config also disappears. I would like to do that very much, only NetworkManager makes you jump through burning loops to do so. With network-scripts, it

Hi, I'm currently installing CentOS 5.11 i386 on an old PC. Is the ELRepo third-party repository still active and maintained? Cheers, Niki Kovacs -- Microlinux - Solutions informatiques 100% Linux et logiciels libres 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32

Hi, I'm currently experimenting with CentOS 7 on a couple of installations. I'm reasonably proficient with CentOS 5.x and 6.x. I'd like to manage networking using a more traditional approach (Keep It Simple Stupid). Here's what I tried so far, starting from a minimal install: Install net-tools (to be able to use ifconfig). Get rid of NetworkManager: # yum remove

dmesg -t | grep -i nvidia nouveau 0000:02:00.0: NVIDIA G98 (098200a2) input: HDA NVidia Rear Mic as /devices/pci0000:00/0000:00:07.0/sound/card0/input6 input: HDA NVidia Front Mic as /devices/pci0000:00/0000:00:07.0/sound/card0/input7 input: HDA NVidia Line as /devices/pci0000:00/0000:00:07.0/sound/card0/input8 input: HDA NVidia Line Out Front as /devices/pci0000:00/0000:00:07.0/sound/card0/input9

Hey all I''m new to Linux and Virtualizing. I''m trying to dedicate my nic''s to each virtual server. For instance, virt server A would use nic1 and virt server B would use nic2 and so on. I''ve been reading some stuff for this list and to tell you the truth I''m a bit overwhelmed. We are going to run SLES10.1 and Xen. I would appreciate any assistance.

Hi, A couple months ago, I migrated our local school (two servers, 20 desktop clients) from Slackware 14.1 to CentOS 7. The desktop clients are running a customized lightweight desktop based on Xfce: https://blog.microlinux.fr/poste-de-travail-xfce-centos-7/ Home directories are all on the server, and authentication is centralized. Everything works fine so far. With Slackware I had found a

Hello CentOS gurus, and a belated Happy New Year (or an early Happy Chinese New Year). I'm in the process of building a CentOS-6 KVM host machine whose only function will be to run four independent 'm0n0wall' firewall guest instances. I have a couple of quad-port Intel NICs to provide four WAN-side and four LAN-side ports, which will not be shared with any other guests. Remote

This patch lets interrupt handler functions have their natural type (ie. exactly match the data pointer type); for transition it allows the old irq_handler_t type as well. To do this it uses a gcc extension, cast-to-union, which allows a type to be cast to any type within the union. When used in a wrapper macro, it's a simple way of allowing one of several types. (Some drivers now need to

This patch lets interrupt handler functions have their natural type (ie. exactly match the data pointer type); for transition it allows the old irq_handler_t type as well. To do this it uses a gcc extension, cast-to-union, which allows a type to be cast to any type within the union. When used in a wrapper macro, it's a simple way of allowing one of several types. (Some drivers now need to

Hi, I'm running CentOS 7 on all my servers, in three different contexts : 1. simple local server 2. public facing server 3. router/gateway/firewall I'm currently in the process of moving my KISS-style network-scripts-style configurations to something more orthodox based on NetworkManager. Scenarios (1) and (2) caused no problems, but (3) is giving me some headache. Let me