openSUSE Leap 15.0

o

openSUSE Leap O@ӦۥѪ Linux @~tΡAiB@bzWqBO
qάOACziHΥsB޲zzqllPۤBiͲOu@B
vέ֡CϥΥzRֽI

^m: Chao-Hsiung LiaoBCraig JeffaresBJoe ManBRay ChenBRamax Lo
XG2019-11-26, G15.0.20191126

1 w
2 tΤɯ
3 Mܰ
4 Xʵ{Pw
5 ୱ
6 w
7 ޳NĳD
8 hTPX

{b openSUSE Leap 15.0 @wCnϨtΫO̷sMwAФɯŨe
 openSUSE Cb}lɯŤeAнTOMΤF openSUSE Leap 15.0 Ҧ@
sC

ɯŨe openSUSE ԲӸTAгyX http://en.opensuse.org/
SDB:Distribution-UpgradeC

pGzqª openSUSE o檩ɯšAХѦdݤeoơGhttp://
en.opensuse.org/openSUSE:Release_NotesC

MתTШ https://www.opensuse.orgC

1 w

`]tFwˬnICԲӪɯűоǡAаѾ\bhttps://
doc.opensuse.org/documentation/leap/startup/html/book.opensuse.startup/
part.basics.htmlC

аȥ˾\ 4 `uXʵ{PwvC

1.1 ϥηstΨAҴѪlɯ

w˵{{bi䴩stΨA (Transactional Server)AoO
openSUSE Kubic MתVOGCӨƤ@ӷsɯŨtΡAHl覡MΧ
s (@ާ@)AåBݭnɤ]iHa^_W@ʧ@Coӥ\O SUSE P
openSUSE o檩ҥ઺M޲zuӧCoNjib openSUSE Leap
15.0 LtΨ̹B@ RPM M]iB@bAtΨ⤤C

`N

`NGۮeM

@ǮM|b̪ RPM %post }ק /var άO /srv eCoǮMOۮe
CpGzJoǮMAЦ^~C

ɯŨtΨ̿HUSʥHѳoǥ\G

 E Btrfs ַӡG  btΧs}leA@ӷs root ɮרtΪ Btrfs ַӷ|QإߡC
    MҦӦ۸ӧsק|w˦bo Btrfs ַӤCnosAziH
    ҨtΥHϥθӧַӡC

    nosAuݱqe@ӧַӶ}YiC

 E Ū root ɮרtΡG  FקK]syDPƿ򥢡Aroot ɮרtΥ
    TgJCOG root ɮרtΦb`ާ@UOHŪ覡C

    nӳ]woHB@Aݭn[Jt~GɮרtΪܧGn\b /etc gJϥ
    ̳]wɡAӥؿ۰ʳ]wϥ OverlayFSC/var {bhܦlHѨL
    {gJC

n

nGTransactional Server Needs At Least 12 GB of Disk Space

The system role Transactional Server needs a disk size of at least 12 GB to
accommodate Btrfs snapshots.

nϥΥsAШϥΫO transactional-update ӫD YaST P Zypper ӶiM
޲zG

 E stΡGtransactional-update up

 E wˮMGtransactional-update pkg in PACKAGE_NAME

 E MGtransactional-update pkg rm PACKAGE_NAME

 E n̫@ӧַӹ root ɮרtΩҰܧAХT{ztάOϥγ̫@
    ӧַӤeַӶ}AMG transactional-update rollback

    Ϊ̡AbO̫[Wַ ID H^_ܯSwַӡC

When using this system role, by default, the system will perform a daily update
and reboot between 03:30 am and 05:00 am. Both of these actions are
systemd-based and if necessary can be disabled using systemctl:

tux@linux > sudo systemctl disable --now transactional-update.timer rebootmgr.service

nFѧhsӸ`AШ openSUSE Kubic 峹 https://
kubic.opensuse.org/blog/2018-04-04-transactionalupdates/ H https://
kubic.opensuse.org/blog/2018-04-20-transactionalupdates2/C

1.2 ̤ptΦw

̤ptΦw˯ʤ֤@ǳQ{zҷM\G

 E ]An騾eݤCziHt~w firewalld MC

 E ]A YaSTCziHt~w patterns-yast-yast2_basis ˦C

1.3 Installing on Hard Disks With Less Than 12 GB of Capacity

The installer will only propose a partitioning scheme if the available hard
disk size is larger than 12 GB. If you want to set up, for example, very small
virtual machines images, use the guided partitioner to tune partitioning
parameters manually.

1.4 UEFI - Τ@i餶

bw openSUSE ϥ UEFI (Τ@i餶) }tΤeAjPĳz
ݬO_wsyөҫĳså[HwˡCYztΦw Windows 8 Χs
Aq`NNztΨϥ UEFI }C

IѡG UEFI 馳ʳAɭPӦhƳQgJ UEFI xsϰɡA|
oͰDCOSHDsgJhָƤ~uӦhvC

openSUSE ǥѥugJҰʨtΪֻ̤ݭnƶqAӭCoӭICgJƦ
֭niD UEFI  openSUSE Ұʵ{mCx Linux ֤ߴѨϥ UEFI xs
ϨӼgJ}ηT\ (pstore)Abw]QΡCLצpAĳw˥w
syӫĳsC

1.5 UEFIAGPT P MS-DOS ϺФΰ

b EFI/UEFI WѤ@ӷsκϺЪ覡GGPT]GUID Partition Table
^Coӷs覡ϥ GUID]128줸ܦb32ӤQiƦrW^ѧO˸mΤ
ΰC

~AUEFI WdO\ǲΪ MBR]MS-DOS^ΰϡC Linux ޾ɥ[]ELILO 
GRUB2^հw墨ǶǲΪΰϦ۰ʲͤ@ GUID Aç⥦̼giCo˪@
 GUID iHWcܧAɭP骺gJC@gJ]AؤPާ@GR
ءAHγЫؤ@ӷsإHNĤ@ӶءC

{N鳣@өU]garbage collector^AiHQRiJI]
entries^AåBӫOd¶iJI]entries^OCG٪餣ব
άOoǶiJI]entries^ɡAtαN|X{DA̲ױNytεLk}C

²檺NѨM׬OGഫǲΪ MBR ΰϦs GPT ΰϥH㪺קK
DC

1.6 btƦ DPI ùqWYw˵{ϥΪ̤

YaST w˵{w]| DPI ùYϥΪ̤CYz֦tư DPI ùq
AziH]w YaST ۰YϥΪ̤CYn]wAЦb}޾ɵ{ROC[J
Ѽ QT_AUTO_SCREEN_SCALE_FACTOR=1C

2 tΤɯ

oӤp`CXFPtΤɯŦ`NƶCFѸԲӪɯŨBJAШ https://
doc.opensuse.org/documentation/leap/startup/html/book.opensuse.startup/
cha.update.osuse.html 󻡩C

аȥ˾\ 4 `uXʵ{PwvC

t~AШ 3 `uMܰʡvC

2.1 q openSUSE Leap 42.3 ɯ

2.1.1 tΤɯŮɵoͮM󭰪p

The RPM package information of packages shipped in openSUSE Leap 15.0 contain
an added openSUSE Leap version string. For this reason, packages that contain
the same upstream version of software as shipped in openSUSE Leap 42.3 will be
displayed as downgrades, even though they actually contain the same software
but compiled for a newer operating system.

2.1.2 cryptconfig Mw

e openSUSE Leap zL cryptconfig M䴩aؿ[KCӥ\P 
cryptconfig Mb openSUSE Leap 15.0 wA䴩C

nb openSUSE Leap 15.0 [KϥΪ̸ơAХ[K]taؿӤΰϩΤlC



ܡGɯūeѱK

We encourage you to decrypt encrypted home directories before performing an
upgrade from openSUSE Leap 42.3. While under openSUSE Leap 15.0, existing
encrypted home directories can still be used (the underlying technology, 
pam_mount, is still available), there may not be an easy upgrade path in the
future.

There is also no way to individually encrypt the home directories of users
added after the upgrade to openSUSE Leap 15.0.

2.1.3 Postfix Admin Uses Backwards-Incompatible Directory Layout

Starting with the version 3.2, as shipped in openSUSE Leap 15.0, Postfix Admin
(package postfixadmin) uses a new and backwards-incompatible directory layout:

 E ]wɲ /etc/postfixadminC

 E PHP {X /usr/share/postfixadminC

 E Smarty ֨ /var/cache/postfixadminC

Postfix Admin no longer reads configuration files from their previous locations
and the configuration is not migrated automatically. Therefore, you need to
migrate the following items manually:

 E N config.local.php q /srv/www/htdocs/postfixadmin h /etc/
    postfixadminC

 E Yzb config.inc.php ۭqקAzQpUiHNoǭקX֦^ /etc/
    postfixadmin/config.local.phpCLڭ̫ĳnק config.inc.phpC

 E b Apache ]wɤA[Jαҥ /postfixadmin OWG

      nbҦDWϥΧOWAаG

        tux@linux > sudo a2enflag POSTFIXADMIN && rcapache2 restart

      YunbSwDWϥΧOWAбNӧOW[JD]wYiC

2.1.4 [KϺХHW٨ӹɡAuɯŷ|

bϥΦw˴C骺uɯť\ɡAYq]t[KƤΰϡAp /homeA
etΦwˮɷ|ϱo YaST w˵{YC

oӱpoͩ[KƤΰϦb /etc/fstab H device mapper W٦CXAp /
dev/mapper/cr_homeCbwҤUAYaST LkNӸ|P۰ʰ쪺lC

nϥuɯť\AbɯūeAק /etc/fstab eӨϥθ˸m UUID ӫD
mW١CnoT˸m UUIDAШϥΥHUROG

tux@linux > blkid | grep "DEVICE_MAPPER_NAME"

өROX|]tHAA_Ӫ UUID (br UUID= )C

2.1.5 GPG ϥηs_Ʈw榡

openSUSE Leap 42.3 shipped with GPG 2.0, while openSUSE Leap 15.0 includes
GPG 2.2. In between these GPG versions, a new key database format was
introduced. GPG 2.2 will automatically upgrade your key ring to the new format.
However, the upgraded key ring cannot be used by older versions of GPG anymore.

If you need to keep the older version of your key database available, back up
the directory ~/.gnupg before starting the upgrade to openSUSE Leap 15.0.

2.1.6 ntpd Has Been Replaced With Chrony

The time server synchronization daemon ntpd has been replaced with the more
modern daemon Chrony.

This change means that AutoYaST files with an ntp_client section need to be
updated to a new format for this section. For more information about the new
AutoYaST ntp_client format, see https://doc.opensuse.org/projects/autoyast/#
Configuration.Network.Ntp.

To synchronize time in intervals, YaST sets up a cron configuration file. From
openSUSE Leap 15.0 on, the configuration file used for this is owned by the
package yast2-ntp-client (previously no package owned it). The configuration
file has been renamed from novell.ntp-synchronization to
suse-ntp_synchronization to be consistent with other cron configuration files.
The upgrade from previous versions of openSUSE Leap is performed automatically:
If a file with the old name is found, it will be renamed and references to ntpd
in it will be replaced by chrony references.

3 Mܰ

3.1 ĳM

ĳM٬O|o檩@AåBbU@ openSUSE Leap |QC
oǮMsb]OFUEAĳϥΡAӥB̤|AsC

nˬdww˪MO_wA@AХT{O_ww lifecycle-data-openSUSE M
AۨϥΥHUOG

tux@linux > zypper lifecycle

3.2 M

MNAHo檩@_oC

 E cryptconfig: Was not maintained anymore. Use partition encryption instead.
    For more information, see  2.1.2 `ucryptconfig Mwv.

 E SuSEfirewall2: Replaced by firewalld. For information about migrating to 
    firewalld, see https://en.opensuse.org/Firewalld and https://
    doc.opensuse.org/documentation/leap/security/html/book.security/
    cha.security.firewall.html#sec.security.firewall.firewalld.

 E php7-imap: The optional IMAP PHP extension is no longer shipped as the UW
    IMAP reference implementation is no longer maintained.

4 Xʵ{Pw

4.1 ϥ Nvidia ϧγBzMVXϧξ_D

H openSUSE Leap 15.0 GM f֡ANvidia ܥd Nouveau Xʥibs
ʡBBΦbq޲zʧ@ɾɭP_CDDnvTVXϧΪtΡAҦpf
 Intel XϧλP Nvidia WܥdOqC

DN|b֪@s״_C]wˬM౵sAҥHoӰDi
N|oͦbw˹L{Χs᪺Ĥ@}CoرpU{ɤסANOH
nouveau.modeset=0 ﶵ}CwˤF]tץ֫AzYiﶵC

4.2 M Nvidia Xʵ{䴩b Wayland W KDE

KDE Plasma Wayland 涥q䴩M Nvidia Xʵ{CYzbϥ KDE PM
Nvidia Xʵ{A~ϥ X 涥qC

5 ୱ

oӤp`CX openSUSE Leap 15.0 ୱҪDPܰʡC

5.1 Sw] Compose զX

b openSUSE eAcompose զXOΨӿJݩзLGrCҦp
AnJu?vrAziHU Shift?Right CtrlA۫U a ⦸C

b openSUSE Leap 15.0Aѩ Shift?Right Ctrl wpwaB@AGAѹww
q compose զXC

 E nwq@ӨtΥ쪺Ȩ compose զXAж} /etc/X11/Xmodmap ɮר÷jM
    UC]wG

    [...]
    !! Third example: Change right Control key to Compose key.
    !! To do Compose Character, press this key and afterwards two
    !! characters (e.g. `a' and `^' to get 342).
    !remove  Control  = Control_R
    !keysym Control_R = Multi_key
    !add     Control  = Control_R
    [...]

    nѡAв]w}Y ! rCMӽЪ`NYzbϥ setxkbmapA
    Xmodmap ]wN|Qл\C

 E nwq@ӨϥΪ̯Sw compose զXAШϥήୱҪL]wuάO
    setxkbmap ROCuG

    tux@linux > setxkbmap [...] -option compose:COMPOSE_KEY

    䤤 COMPOSE_KEYAШϥαznAp ralt (k Alt )Blwin ( Win
    )Brwin (k Win )Bmenu ()Brctl (k Alt )AάO caps (jgw
    )C

 E ~A]iHϥ IBus JkӿJzݭnrӤݨϥ compose C

5.2 Use update-alternatives to Set Display Manager and Desktop Session

In the past, you could use /etc/sysconfig or the YaST module /etc/sysconfig
Editor to define the display manager (also called the login manager) and
desktop session. Starting with openSUSE Leap 15.0, the values are not defined
using /etc/sysconfig anymore but with the alternatives system.

nܧw]ȡAШϥΥHU alternativesG

 E Display manager: default-displaymanager

 E Wayland 涥qGdefault-waylandsession.desktop

 E X ୱҰ涥qGdefault-xsession.desktop

ҦpAnd default-displaymanager ȡAШϥΡG

tux@linux > sudo update-alternatives --display default-displaymanager

n default-displaymanager  xdmAШϥΡG

tux@linux > sudo update-alternatives --set default-displaymanager \
  /usr/lib/X11/displaymanagers/xdm

nҥ alternatives ϧκ޲zAШϥ YaST Ҳ Alternatives (iw 
yast2-alternatives M)C

5.3 ϥ GNOME Shell ϥ GDM ɡAùw|@

 GNOME Shell MLD GDM nJ޲z@Pϥή (p SDDM  LightDM)Aù
|ܶ©wCt~A]LkbnXpUϥΪ̡C

nb GNOME Shell UwùAбҥ GDM @znJ޲zG

 1. нT{ww gdm MC

 2. ]w GDM ܺ޲zG

    tux@linux > sudo update-alternatives --set default-displaymanager \
      /usr/lib/X11/displaymanagers/gdm

 3. sҰʨtΡC

5.4 btư DPI ùqWY SDDM ϥΤ

KDE w]nJ޲z SDDM w]| DPI ùYϥΪ̤CYz֦tư
DPI ùqAziHϥ /etc/sddm.conf ӳ]w SDDM ۰YϥΪ̤G

[X11]
EnableHiDPI=true
ServerArguments=-nolisten tcp -dpi DPI_VALUE

Replace DPI_VALUE with an appropriate DPI value, such as 192. For best scaling
results, use a DPI value that is a multiple of the default 96 DPI.

5.5 btư DPI ùqWY YaST ϥΪ̤

YaST w]| DPI ùYϥΪ̤CYz֦tư DPI ùqAzi
H]w YaST ۰YϥΪ̤CYnpAг]wܼ
QT_AUTO_SCREEN_SCALE_FACTOR=1C

5.6 bVX DPI P@ DPI ùҤUb Qt ε{ϥΦ۰Y

Qt b X ҤU䴩ӧOù۰YCϥε X screen  DPI ȨӭpDn
һݪrjpCӭȹw] 96 DPICϥΥDnù۹ DPI ӱXLù
r DPI ȡC

HUGؼsxϥΪୱҷ|л\ Qt 欰AGƶ復̤AΡG

 E GNOME will set Xft.dpi to the configured multiple of 96 DPI.

 E KDE Plasma | Qt ۰YӧΥۤvYպAC

On other desktops, this behavior of Qt can lead to undesirable situations such
as the following: If the primary display is High-DPI (>= 144 DPI), fonts in Qt
applications that request scaling, such as VLC, are effectively scaled to half
the desired size on all monitors. Applications which do not request scaling,
such as YaST (with default settings), use the same DPI value on all monitors.
Hence, they will look smaller on the High-DPI monitor.

ziHϥΥHU䤤@ӼȮɸѮMרӳBzoӰDG

 E ϥΤ@ DPI ùDnùCݭnYε{Nb DPI ùW
    TYC

 E ]wAr DPI (Xft.dpi)CziHϥαzୱҩҴѪպAuӳ]w
    CΪ̬ObCnJAHUOG

    tux@linux > echo Xft.dpi:DPI_VALUE | xrdb -nocpp -merge

     DPI_VALUE AXDnù DPI ȡC

5.7 ù@ɵLkb Wayland U Firefox  Chromium B@

Firefox P Chromium q`\H¦u (pT|ĳε{) Ұʥù
άOWε{@ɡCb Wayland 涥qUAިϥΨsAoӥ\
ثeä䴩C

nb Firefox  Chromium U@ɱzùAЧ X 涥qC

5.8  MP3 Cɮ

 MP3 CɮשһݪѽXзǮMwC

nbH gstreamer ¦ε{ζ}oج[ϥθѽX (p Rhythmbox άO
Totem)AЦw gstreamer-plugins-ugly MC

5.9 LibreOffice A䴩 Type-1 r

LibreOffice 5.3 HWA䴩ª Type-1 rF (ɦW .afm P .pfb r
)Cثerq`O TrueType (.ttf) άO OpenType (.otf) 榡A]j
Ϊ̨ä|vTC

pGzvTAбN Type-1 rഫ䴩r榡 (p TrueType)AAϥθ
ഫ᪺rCziHϥ openSUSE ҥ]t FontForge ε{ (fontforge M)
ӰഫCQFpϥθ}Ӧ۰ʤഫTAШ https://
fontforge.github.io/en-US/documentation/scripting/C

5.10 FreeType rVܰ

FreeType 2.6.4 @ӷsw]rηLոѪR ( 38) PL@~tΪ欰
Ab@ǨtΤWݰ_ӡuҽkvCn^_He FreeType 欰AziHܦb
Nh (tΥBϥΪ̯SwAε{Sw) ]wHUܼơG

FREETYPE_PROPERTIES="truetype:interpreter-version=35"

5.11 ҥ KDE Plasma sX

Firefox P Chromium/Chrome  Plasma sX\ϥ KDE tΤuӺʱhC
PUAåBb KDE Plasma ୱҪ Run Command uCѧֳts\
C

sX\]tFݭnPB@GӳG

 E ୱҳiHw plasma-browser-integration tήMC

 E shݭnqzs[өwˡG

      Firefox: https://addons.mozilla.org/firefox/addon/plasma-integration/

      Chromium/Chrome: https://chrome.google.com/webstore/detail/
        plasma-integration/cimiefiiaegbelhefglklhhakcgmhkai

Ъ`N\ऴB}oqAopenSUSE Leap 15.0 ȦF䦭C

5.12 J Emacs psgml Ҳ

ѩMӦ Emacs w]w˪Ҳլ۽ĬAopenSUSE Leap 15.0 Lk۰ʸJ psgml 
աCFѸԱAШ psgml M󤤪 README ɮסC

6 w

oӤp`CX openSUSE Leap 15.0 wʥ\譱ܰʡC

6.1 GPG Does Not Support GPG V3 Keys Anymore, Resulting in Zypper/rpm Warnings

openSUSE Leap 42.3 shipped with GPG 2.0, while openSUSE Leap 15.0 includes GPG
2.2. In between these GPG versions, support for GPG V3 keys was removed. If
your system's key database still contains GPG V3 keys, you may receive warnings
about this when executing Zypper or rpm commands, as these commands are
checking the integrity of the package database. These warnings take the form
warning: Unsupported version of key: V3.

Usually, these warnings are benign, as these keys may have been used for
repositories that are no longer enabled on the system or that have since had
key updates. However, if these keys are still in active use by the upstream
repository, they must be replaced as soon as possible:

 E Package management tools in openSUSE Leap 15.0 can no longer use them to
    verify package integrity.

 E The keys in themselves are insecure. Hence, even though older package
    management tools will use them to verify integrity of packages, the result
    of this check cannot be trusted anymore.

To delete such keys, perform the following:

 1. Run an rpm command with high verbosity and check its output:

    tux@linux > rpm -vv -qf /etc
    ufdio: 1 reads, 18883 total bytes in 0.000006 secs
    [...]
    D: read h# 168 Header sanity check: OK
    warning: Unsupported version of key: V3
    [...]

    In the example, header 168 is associated with an outdated key?the warning
    appears directly after the message that this specific header is being
    checked.

 2. Find out the key number associated with the header:

    tux@linux > rpm -q --querybynumber HEADER

    Replace HEADER with the required header number. In the example, that would
    be 168.

    This command returns a key identifier starting with gpg-pubkey-.

 3. (Optional) Use the key identifier (KEY_ID) to learn more about the key:

    tux@linux > rpm -qi KEY_ID

 4. Remove the key from the system:

    tux@linux > sudo rpm -e KEY_ID

 5. If you continue to see warnings on subsequent uses of package management
    tools, repeat the procedure.

6.2 systemctl stop apparmor S@

bLhΩާ@ AppArmor  systemctl D`lRO reload P restart i
g`HVcG

 E systemctl reload apparmor Ω󥿽TasJҦ AppArmor պAC(@O
    sJ AppArmor պAĳkANӤ]|OpC)

 E systemctl restart apparmor N AppArmor |B@AG|saҦ
    AppArmor պAAþɭPҦ{s{|ACusҰʪ{~|A
    QC

OAsystemd åb椸ɮ׮榡 (unit file format) Ѧ] restart 
ҩҾɭPDѪkסC

q AppArmor 2.12 }lAsystemctl stop apparmor ON|ġC] systemctl
restart apparmor NiHTasJ AppArmor պAC

nҦ AppArmor պAAШϥηsO aa-teardownCӫOP systemctl stop
apparmor ¦欰ۦPĪGC

Ш https://bugs.freedesktop.org/show_bug.cgi?id=996520 P https://
bugzilla.opensuse.org/show_bug.cgi?id=853019 HFѧhӸ`C

7 ޳NĳD

7.1 s᪺ Btrfs l

openSUSE Leap 15.0 ɤJ@ӷs Btrfs lw]ADnFHUҶqG

 E ²ƧַӻP^_

 E קKN~ƿ

 E xs /var ƮwPMHɦnį

PLh /var UlؿϥΦh Btrfs l覡AopenSUSE Leap 15.0 
Ҧ /var eҨϥγ@lCoӤlFugɽƻsv\C

SkΤɯŪ覡ಾs Btrfs lCOGYzQnϥθӥ\AнT
OOsw openSUSE Leap 15.0 ӫDɯŨtΡC

ܧe/ Btrfs w]lԲӸTAгyX https://en.opensuse.org/
SDB:BTRFSC

7.2 Wicked: Using RFC 4361 DHCPv4 client-id on Ethernet

RFC 4361 sF RFC 2132  9.14  client-id wqAHۮe DHCP 6
client-id (duid)Cb Infiniband (RFC 4390) Wϥ RFC 4361AB DHCP 4 P
DHCP 6 PϰΦuW檺 DNS Osާ@]ݭnC

openSUSE Leap 15.0 G

 E ISC DHCP 4.3.x A䴩Fs RFC 4361]ݭnΩ DNS s^

 E Wicked provides an option to send such a client-id and to automatically use
    a DHCPv6-based client-id in DHCPv4 (used on Infiniband).

To send the client-id during the installation, use linuxrc (also see https://
en.opensuse.org/SDB:Linuxrc) with the following ifcfg:

ifcfg=eth0=dhcp,DHCLIENT_CLIENT_ID=01:03:52:54:00:02:c2:67,DHCLIENT6_CLIENT_ID=00:03:52:54:00:02:c2:67

For more information, see the documentation for the options dhcp4 "create-cid",
dhcp6 "default-duid" in man 5 wicked-config, wicked duid --help, and wicked
iaid --help.

The traditionally used RFC 2132 DHCPv4 client-id on Ethernet is constructed
from the hardware type (01 for Ethernet) and followed by the hardware address
(the MAC address), for example:

01:52:54:00:02:c2:67

The RFC 4361 client-id starts with 0xff (instead of the hardware type),
followed by the DHCPv6 IAID (the interface-address association ID that
describes the interface on the machine), followed by the DHCPv6 DUID (client-id
which identifies the machine).

Using the above hardware type-based and hardware address-based DUID (LLT type
used by default), the new RFC 4361 DHCPv4 client-id would be:

 E Using the last bytes of the MAC address as the IAID:
    ff:00:02:c2:67:00:01:xx:xx:xx:xx:52:54:00:02:c2:67

 E When the IAID is a simple incremented number:
    ff:00:00:00:01:00:01:xx:xx:xx:xx:52:54:00:02:c2:67

The xx:xx:xx:xx in the DUID-LLT is a creation timestamp. A DUID-LL
(00:03:00:01:MAC) does not have a timestamp.

8 hTPX

 E о\Ūw˴CW README C

 E qM RPM ˵YӮMԲӪܰʾvTG

    tux@linux > rpm --changelog -qp FILENAME.rpm

    N FILENAME N RPM W١C

 E Ьdݦbw˴C̤WhؿU ChangeLog ɮץHFѩҧsMܰʾv]
    ɶƧǡ^C

 E bw˴C餤 docu ؿihTC

 E LΧsAаѾ\ https://doc.opensuse.org/C

 E nFѦ openSUSE ̷s~sDAгyX https://www.opensuse.orgC

vҦ ? SUSE LLC

? 2019 SUSE

