/etc/os-release isn't created

[Conrad Meyer]

Hi,

Did you run etcupdate or mergemaster as part of updating your host?

Best,
Conrad

On Sat, Nov 23, 2019 at 1:15 PM Yasuhiro KIMURA <yasu at utahime.org> wrote:
>
> Hello,
>
> Yesterday I updated my 13-CURRENT host from r354592 to r355028 and
> /etc/os-release symbolic link wasn't created.
>
> yasu at rolling-vm-freebsd1[2061]% uname -a
> FreeBSD rolling-vm-freebsd1.home.utahime.org 13.0-CURRENT FreeBSD 13.0-CURRENT #0 r355028: Sat Nov 23 22:35:58 JST 2019     rootz at rolling-vm-freebsd1.home.utahime.org:/usr0/freebsd/base/obj/usr0/freebsd/base/head/amd64.amd64/sys/GENERIC  amd64
> yasu at rolling-vm-freebsd1[2062]% ls -l /etc/os-release
> ls: /etc/os-release: No such file or directory
> yasu at rolling-vm-freebsd1[2063]%
>
> But after that I made same update of 13-CURRENT poudriere jail and
> then /etc/os-release was created in it.
>
> yasu at rolling-vm-freebsd1[2063]% ls -l /usr/local/poudriere/jails/curamd64/etc/os-release
> lrwxr-xr-x  1 root  wheel  21 Nov 24 05:04 /usr/local/poudriere/jails/curamd64/etc/os-release@ -> ../var/run/os-releaseyasu at rolling-vm-freebsd1[2064]%
>
> Why such difference happens?
>
> ---
> Yasuhiro KIMURA
> _______________________________________________
> freebsd-current at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"