But they are one-shot commands that do their task and quit. But the scripts can also start ISC’s dhclient to do DHCP, in which case the DHCP daemon keeps running in the background.Īs such, initscripts are a simple thing that work well for what they are. They do so by calling iproute2 (the ip tool) to setup interfaces and IP addresses in kernel. The network-scripts part of initscripts are really a bunch of shell scripts that parse ifcfg files (by executing them as shell scripts) and configure the network accordingly. These files are the “profiles” in the sense that they are configurations for a network interface. On Fedora and RHEL, users would edit files like /etc/sysconfig/network-scripts/ifcfg-eth0 according to the documentation. One part of initscripts is concerned about network and provides two scripts ifup and ifdown and a SysV-style init service network. For example, the Fedora variant is (un)maintained at github/fedora-sysv. The very short version of the history is that various Linux distributions use the System V “initscripts” for system configuration and management. Eliška no longer uses ifcfg files with NetworkManager. Let’s take a look at the history and future of the ifcfg-rh format. Currently two file formats exists for that purpose: keyfile and ifcfg-rh. A profile is just a bunch of settings and configuration values with defined keys and values, that can be sent over D-Bus or persisted to disk.
It’s all about connection profiles, which are created by the user and “activated” by NetworkManager. NetworkManager is a daemon for configuring the network on Linux.
0 kommentar(er)
