手机版
你好,游客 登录 注册 搜索
背景:
阅读新闻

systemd 234发布,支持Meson构建系统及一些改进

[日期:2017-07-14] 来源:Linux公社  作者:Linux [字体: ]

经过四个半月内开发,systemd 234发布了,但它不是主要版本,只带来几个新功能和几个引擎盖下的改进,以及一系列错误修复和安全增强功能。

有一件事情必须要说,这就是对Meson构建系统的支持。没错,systemd加入了Meson的潮流,像许多其他的开源软件应用程序一样,它让OS集成商用Meson来构建它,尽管现在仍然支持Automake。

“我们的计划是在下一个版本中删除Automake,从而使Meson成为我们的独家构建系统,”Lennart Poettering在邮件列表中公布。 “因此,请在您的包中开始使用Meson构建系统。有关如何使用Meson的大量文档。”

systemd-networkd学习了一些新的技巧

除了systemd 234更新之外的其他值得注意的更改中,我们可以提到systemd-networkd学习了一些新的技巧,包括.network文件的[VXLAN]部分中的FlowLabel= setting in the [VXLAN] section of .network files, a Priority= setting in [Bridge], GVRP=, MVRP=, LooseBinding=, and ReorderHeader= settings in [VLAN], as well as GatewayOnlink=, IPv6Preference=, and Protocol= settings in [Route].

此外,systemd-networkd的DHCP支持获得域搜索列表(DHCP选项119)的支持,并通过路由器通告协议支持IPv6地址范围。此外,单元文件支持几个新的选项和设置,还有其他一些小的改进,以确保你学习下面的完整的更新日志。

Additionally, systemd-networkd's DHCP support received support for domain search list (DHCP option 119) and got support for serving IPv6 address ranges through the Router Advertisement protocol. Moreover, unit files received support for a few new options and settings, and there are a few other small improvements for other components so make sure you study the full changelog attached below.

下载systemd 234

更新日志:

Meson is now supported as build system in addition to Automake. It is our plan to remove Automake in one of our next releases, so that Meson becomes our exclusive build system. Hence, please start using the Meson build system in your downstream packaging. There's plenty of documentation around how to use Meson, the extremely brief summary:
 ./autogen.sh && ./configure && make && sudo make install
 becomes:
 meson build && ninja -C build && sudo ninja -C build install
 Unit files gained support for a new JobRunningTimeoutUSec= setting, which permits configuring a timeout on the time a job is running. This is particularly useful for setting timeouts on jobs for .device units.
 Unit files gained two new options ConditionUser= and ConditionGroup= for conditionalizing units based on the identity of the user/group running a systemd user instance.
 systemd-networkd now understands a new FlowLabel= setting in the [VXLAN] section of .network files, as well as a Priority= in [Bridge], GVRP= + MVRP= + LooseBinding= + ReorderHeader= in [VLAN] and GatewayOnlink= + IPv6Preference= + Protocol= in [Route]. It also gained support for configuration of GENEVE links, and IPv6 address labels. The [Network] section gained the new IPv6ProxyNDP= setting.
 .link files now understand a new Port= setting.
 systemd-networkd's DHCP support gained support for DHCP option 119 (domain search list).
 systemd-networkd gained support for serving IPv6 address ranges using the Router Advertisment protocol. The new .network configuration section [IPv6Prefix] may be used to configure the ranges to serve. This is implemented based on a new, minimal, native server implementation of RA.
 journalctl's --output= switch gained support for a new parameter "short-iso-precise" for a mode where timestamps are shown as precise ISO date values.
 systemd-udevd's "net_id" builtin may now generate stable network interface names from IBM PowerVM VIO devices as well as ACPI platform devices.
 MulticastDNS support in systemd-resolved may now be explicitly enabled/disabled using the new MulticastDNS= configuration file option.
 systemd-resolved may now optionally use libidn2 instead of the libidn for processing internationalized domain names. Support for libidn2 should be considered experimental and should not be enabled by default yet.
 "machinectl pull-tar" and related call may now do verification of downloaded images using SUSE-style .sha256 checksum files in addition to the already existing support for validating using Ubuntu-style SHA256SUMS files.
 sd-bus gained support for a new sd_bus_message_appendv() call which is va_list equivalent of sd_bus_message_append().
 sd-boot gained support for validating images using SHIM/MOK.
 The SMACK code learnt support for "onlycap".
 systemd-mount --umount is now much smarter in figuring out how to properly unmount a device given its mount or device path.
 The code to call libnss_dns as a fallback from libnss_resolve when the communication with systemd-resolved fails was removed. This fallback was redundant and interfered with the [!UNAVAIL=return] suffix. See nss-resolve(8) for the recommended configuration.
 systemd-logind may now be restarted without losing state. It stores the file descriptors for devices it manages in the system manager using the FDSTORE= mechanism. Please note that further changes in other components may be required to make use of this (for example Xorg has code to listen for stops of systemd-logind and terminate itself when logind is stopped or restarted, in order to avoid using stale file descriptors for graphical devices, which is now counterproductive and must be reverted in order for restarts of systemd-logind to be safe. See https://cgit.freedesktop.org/xorg/xserver/commit/?id=dc48bd653c7e101.)
 All kernel install plugins are called with the environment variable KERNEL_INSTALL_MACHINE_ID which is set to the machine ID given by /etc/machine-id. If the file is missing or empty, the variable is empty and BOOT_DIR_ABS is the path of a temporary directory which is removed after all the plugins exit. So, if KERNEL_INSTALL_MACHINE_ID is empty, all plugins should not put anything in BOOT_DIR_ABS.

CentOS7进程管理systemd详解  http://www.linuxidc.com/Linux/2016-09/135464.htm

CentOS7/RHEL7 systemd详解   http://www.linuxidc.com/Linux/2015-04/115937.htm

为什么systemd会被如此迅速的采用? http://www.linuxidc.com/Linux/2014-08/105789.htm

systemd 与 sysVinit 彩版对照表 http://www.linuxidc.com/Linux/2014-09/106455.htm

太有用了!用systemd命令来管理Linux系统!  http://www.linuxidc.com/Linux/2014-09/106490.htm

浅析 Linux 初始化 init 系统,第 3 部分: Systemd  http://www.linuxidc.com/Linux/2014-12/110383.htm

本文永久更新链接地址http://www.linuxidc.com/Linux/2017-07/145672.htm

linux
本文评论   查看全部评论 (0)
表情: 表情 姓名: 字数

       

评论声明
  • 尊重网上道德,遵守中华人民共和国的各项有关法律法规
  • 承担一切因您的行为而直接或间接导致的民事或刑事法律责任
  • 本站管理人员有权保留或删除其管辖留言中的任意内容
  • 本站有权在网站内转载或引用您的评论
  • 参与本评论即表明您已经阅读并接受上述条款