edee65a6a4
I think this makes it much easier to figure out what information sources were used to generate the names, and why certain names were not generated. On my laptop: Using default interface naming scheme 'v250'. ID_NET_NAMING_SCHEME=v250 wwp0s20f0u2i12: addr_assign_type=3, MAC address is not permanent. wwp0s20f0u2i12: Parsing slot information from sysname "0000:00:14.0": success wwp0s20f0u2i12: dev_port=0 wwp0s20f0u2i12: PCI path identifier: domain=0 bus=0 slot=20 func=0 phys_port= dev_port=0 → p0s20f0 wwp0s20f0u2i12: USB name identifier: ports=2 config=1 interface=12 → u2i12 ID_NET_NAME_PATH=wwp0s20f0u2i12 Using default interface naming scheme 'v250'. ID_NET_NAMING_SCHEME=v250 ID_NET_NAME_MAC=en54ee75cb1dc0 enp0s31f6: MAC address identifier: hw_addr=54:ee:75:cb:1d:c0 → 54ee75cb1dc0 ID_OUI_FROM_DATABASE=Wistron InfoComm(Kunshan)Co.,Ltd. enp0s31f6: Parsing slot information from sysname "0000:00:1f.6": success enp0s31f6: dev_port=0 enp0s31f6: PCI path identifier: domain=0 bus=0 slot=31 func=6 phys_port= dev_port=0 → p0s31f6 ID_NET_NAME_PATH=enp0s31f6 Using default interface naming scheme 'v250'. ID_NET_NAMING_SCHEME=v250 ID_NET_NAME_MAC=en0050b6856d36 hub0: MAC address identifier: hw_addr=00:50:b6:85:6d:36 → 0050b6856d36 ID_OUI_FROM_DATABASE=GOOD WAY IND. CO., LTD. hub0: Parsing slot information from sysname "0000:00:14.0": success hub0: dev_port=0 hub0: PCI path identifier: domain=0 bus=0 slot=20 func=0 phys_port= dev_port=0 → p0s20f0 hub0: USB name identifier: ports=4.1.3 config=2 interface=0 → u4u1u3c2 ID_NET_NAME_PATH=enp0s20f0u4u1u3c2 Using default interface naming scheme 'v250'. ID_NET_NAMING_SCHEME=v250 wlp4s0: addr_assign_type=3, MAC address is not permanent. wlp4s0: Parsing slot information from sysname "0000:04:00.0": success wlp4s0: dev_port=0 wlp4s0: PCI path identifier: domain=0 bus=4 slot=0 func=0 phys_port= dev_port=0 → p4s0 ID_NET_NAME_PATH=wlp4s0 |
||
---|---|---|
.github | ||
.lgtm/cpp-queries | ||
.semaphore | ||
catalog | ||
coccinelle | ||
docs | ||
factory/etc | ||
hwdb.d | ||
LICENSES | ||
man | ||
mkosi.default.d | ||
modprobe.d | ||
network | ||
po | ||
presets | ||
rules.d | ||
shell-completion | ||
src | ||
sysctl.d | ||
sysusers.d | ||
test | ||
tmpfiles.d | ||
tools | ||
units | ||
xorg | ||
.clang-format | ||
.ctags | ||
.dir-locals.el | ||
.editorconfig | ||
.gitattributes | ||
.gitignore | ||
.lgtm.yml | ||
.mailmap | ||
.packit.yml | ||
.vimrc | ||
.ycm_extra_conf.py | ||
configure | ||
LICENSE.GPL2 | ||
LICENSE.LGPL2.1 | ||
Makefile | ||
meson_options.txt | ||
meson.build | ||
mkosi.build | ||
mkosi.postinst | ||
NEWS | ||
README | ||
README.md | ||
TODO |
System and Service Manager
Details
Most documentation is available on systemd's web site.
Assorted, older, general information about systemd can be found in the systemd Wiki.
Information about build requirements is provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the Code Map for information about this repository's layout and content.
Please see the Hacking guide for information on how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list or join our IRC channel.
Stable branches with backported patches are available in the stable repo.