similar to: NetworkManager icon not showing

Hi, I'm currently using Thunderbird synced to OwnCloud on my main workstation running Slackware64 14.1. I just installed CentOS 7 on my Asus S300 laptop. It's running nicely, and I'm spending some time getting acquainted with it. I wonder if I should stick with Thunderbird or go with the default Evolution application, since this seems to be better integrated into the desktop, namely

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 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 just installed CentOS 7 + GNOME on my Asus S300 laptop. So far everything runs very nice and smoothly, and I'm quite happy with it. Curiously enough, I can't seem to be able to set a custom wallpaper. I tried various locations like /usr/share/backgrounds, /usr/share/backgrounds/gnome and /usr/share/backgrounds/images, but the images don't appear in the wallpaper selection

Le 11/02/2020 ? 14:11, Jonathan Billings a ?crit?: > I've mentioned on this list countless times about how NetworkManager > is actually pretty good for a general server. Automatic link > detection and activation/deactivation, a dispatch service on link > activation/deactivation, support for bringing up secondary interfaces > after a primary goes up, a dbus interface for

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

Hi, I have to do some maintenance on a CentOS 7 proxy installed on a routerboard without a video card. The only way to access this machine directly is via Minicom and serial port. I'm using NetworkManager TUI (nmtui) to configure network interfaces, but Ncurses rendering in Minicom works in the sense that chickens fly and horses swim. What you get is a forest of question marks with a few

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

Hi, I just sanded down the remaining edges of my CentOS 7 post-install configuration script and published it on a Github repository, along with some detailed instructions. * https://github.com/kikinovak/centos-setup Feel free to use it (and/or adapt it to your needs). Cheers from the sunny South of France, Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise -

Gnome's control-center now requires NetworkManager-wifi. But it's only a soft requirement, no shared libs involved. To keep your workstation NM-free, you want to install a dummy package that provides NetworkManager-wifi but actually contains nothing, ideally before updating to 7.5. Here's a script to create such a dummy: https://github.com/larsks/fakeprovide If you do this,

Hi, I just upgraded one of my CentOS 7 + GNOME desktops from the CR repo. After the upgrade, it seems like all of the icon themes are broken. Missing icons everywhere. Any idea what's going on here ? Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : info at

Hi: I always use network-scripts to start network at EL7. NetworkManager is not as good as network scripts under that OS. but now EL8 said that network-scripts is depreciated. I wonder if I should still use network-scripts to start network? I am afraid there will be new bugs for the network-scripts, like systemd service unit dependency. although it is solid at EL7.

Le 18/02/2020 ? 17:43, Jonathan Billings a ?crit?: > According to 'man nm-settings-ifcfg-rh', PEERDNS=no is the old > network-services services mechanism for not changing /etc/resolv.conf, > while in NM it just means never add automatic nameservers to > resolv.conf from DHCP, PPP, VPN, etc. Turning off all DNS > updates means adding: > > [main] > dns=none >

The recommended method for undo an update is https://access.redhat.com/solutions/64069, but it's not supported if glibc, kernel, or selinux are changed. I'd give it a try if the system is not critical. Make backups first. Some other people's experience on downgrading a point release: https://access.redhat.com/discussions/2933711 If you couldn't read that article, just search

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

Le 23/05/2018 ? 16:36, Nux! a ?crit?: > Try "iptables -I INPUT" for your FTP rule. Doesn't work. I redirected all my errors to /var/log/messages, so here's what I get when I try to connect Filezilla to that server. May 23 16:48:58 c7-server kernel: +++ IPv4 packet rejected +++ IN=enp0s3 OUT= MAC=08:00:27:00:00:03:d4:85:64:b2:b2:1b:08:00 SRC=192.168.2.2 DST=192.168.2.12

Hi, I'm currently reading the upstream "Considerations in adopting RHEL 8" document. The chapter about networking states that traditional networking scripts (shipped with the network-scripts package) are considered obsolete. I bluntly admit I don't see the point in this. As far as I'm concerned, I've been a happy user of NetworkManager since the early days (when

> On 09/02/2020 23:55, Nicolas Kovacs wrote: > > Hi Nicolas, > > [snip] > >> Maybe there's a reason to make NetworkManager more or less mandatory >> from now on, but I don't see it. So I thought I'd rather ask on this >> list. > > Like you, I read about NetworkManager becoming the default tool for > CentOS 8. So I sat down with a colleague

Le 13/02/2020 ? 17:50, Stephen John Smoogen a ?crit?: > In the end, the problem is that NetworkManager, FirewallD, and other > 'automatic' helpers are 'part' of the OS.. and while it was easy to tear > them out in earlier versions.. as time goes on it is not. > > For a car analogy, it was much easier to convert any 1970 car from > automatic back to manual as many