On 9/9/21 19:53, Florian Eckert wrote:
* resolv.conf -> /tmp/resolv.conf
* /tmp/TZmtab -> /proc/mounts
For consistency, this should also apply to `/usr/lib/os-release`.
Is there any other reason than consistency to change this?
Yes, I have to elaborate on that.
I have a small script that
* resolv.conf -> /tmp/resolv.conf
* /tmp/TZmtab -> /proc/mounts
For consistency, this should also apply to `/usr/lib/os-release`.
Is there any other reason than consistency to change this?
Yes, I have to elaborate on that.
I have a small script that boots the system into a called it
Hi,
> Did you check that none of the build scripts try to access this file? In
> case they do, they'd fail since an absolute path wouldn't exists on the
> building host system.
apart from that it might break 3rd party workflows for no obvious
reason. The existing absolute symlinks mentioned all
On 9/8/21 2:50 PM, Florian Eckert wrote:
The file `/etc/os-release` is currently a relative link to
`../usr/lib/os-release`.
The follwing links on my `/etc` are also absolute:
* localtime -> /tmp/localtime
* resolv.conf -> /tmp/resolv.conf
* /tmp/TZmtab -> /proc/mounts
For consistency, this
On 9/8/21 02:50, Florian Eckert wrote:
The file `/etc/os-release` is currently a relative link to
`../usr/lib/os-release`.
The follwing links on my `/etc` are also absolute:
* localtime -> /tmp/localtime
* resolv.conf -> /tmp/resolv.conf
* /tmp/TZmtab -> /proc/mounts
For consistency, this
The file `/etc/os-release` is currently a relative link to
`../usr/lib/os-release`.
The follwing links on my `/etc` are also absolute:
* localtime -> /tmp/localtime
* resolv.conf -> /tmp/resolv.conf
* /tmp/TZmtab -> /proc/mounts
For consistency, this should also apply to `/usr/lib/os-release`.
