mirror of
https://github.com/systemd/systemd.git
synced 2024-12-26 03:22:00 +03:00
f7e81fd96f
With this we can stabilize how naming works for network interfaces. A user can request through a kernel cmdline option or an env var which scheme to follow. The idea is that installers use this to set into stone (a very soft stone though) the scheme used during installation so that interface naming doesn't change afterwards anymore. Why use env vars and kernel cmdline options, and not a config file of its own? Well, first of all there's no obvious existing one to use. But more importantly: I have the feeling that this logic is kind of an incomplete hack, and I simply don't want to do advertise this as a perfectly working solution. So far we used env vars for the non-so-official options and proper config files for the official stuff. Given how incomplete this logic is (i.e. the big variable for naming remains the kernel, which might expose sysfs attributes in newer versions that we check for and didn't exist in older versions — and other problems like this), I am simply not confident in giving this first-class exposure in a primary configuration file. Fixes: #10448 |
||
|---|---|---|
| .. | ||
| sysvinit | ||
| var-log | ||
| _config.yml | ||
| AUTOMATIC_BOOT_ASSESSMENT.md | ||
| BLOCK_DEVICE_LOCKING.md | ||
| BOOT_LOADER_INTERFACE.md | ||
| BOOT_LOADER_SPECIFICATION.md | ||
| CGROUP_DELEGATION.md | ||
| CNAME | ||
| CODE_OF_CONDUCT.md | ||
| CODE_QUALITY.md | ||
| CODING_STYLE.md | ||
| CONTRIBUTING.md | ||
| DISTRO_PORTING.md | ||
| ENVIRONMENT.md | ||
| HACKING.md | ||
| index.md | ||
| PORTABLE_SERVICES.md | ||
| PREDICTABLE_INTERFACE_NAMES.md | ||
| RELEASE.md | ||
| TRANSIENT-SETTINGS.md | ||
| TRANSLATORS.md | ||
| UIDS-GIDS.md | ||