On Sun, Feb 09, 2020 at 10:13:37 +0100, Jan Rękorajski wrote:
> What about plugging all this symlinking into geninitrd / dracut?
> This way we would have everything sorted before we even start booting to
> the filesystem in question.
Won't work on systems without initrd, won't be functional
On Thu, 06 Feb 2020, Arkadiusz Miśkiewicz wrote:
>
> Hi.
>
> We need to finally do this while still keeping sysvinit compatibility
> (using symlinks).
>
> Migrate
>
> /var/run to /run and keep /var/run -> /run symlink
> /var/lock to /run/lock and /var/lock -> /run/lock symlink
> /run/shm ->
On Sat, 08 Feb 2020, Jacek Konieczny wrote:
> On 2/8/20 6:52 PM, Tomasz Pala wrote:
> > On Thu, Feb 06, 2020 at 19:20:26 +0100, Arkadiusz Miśkiewicz wrote:
> >
> >> We need to finally do this while still keeping sysvinit compatibility
> >> (using symlinks).
> >
> > Why do we need to do this?
On Sat, Feb 08, 2020 at 20:00:47 +0100, Jacek Konieczny wrote:
> New systemd won't even boot properly when /run is a symlink. And many
How about mount --bind?
> That is why the /var/run -> /run symlink should be provided.
Yes, what is I'm afraid is that our rpm doesn't handle dir->symlink
On 2/8/20 6:52 PM, Tomasz Pala wrote:
> On Thu, Feb 06, 2020 at 19:20:26 +0100, Arkadiusz Miśkiewicz wrote:
>
>> We need to finally do this while still keeping sysvinit compatibility
>> (using symlinks).
>
> Why do we need to do this? Legacy SysVinit uses /var/run and works,
> while systemd
On Thu, Feb 06, 2020 at 19:20:26 +0100, Arkadiusz Miśkiewicz wrote:
> We need to finally do this while still keeping sysvinit compatibility
> (using symlinks).
Why do we need to do this? Legacy SysVinit uses /var/run and works,
while systemd systems are already handled well (tmpfiles etc.) in
Hi.
We need to finally do this while still keeping sysvinit compatibility
(using symlinks).
Migrate
/var/run to /run and keep /var/run -> /run symlink
/var/lock to /run/lock and /var/lock -> /run/lock symlink
/run/shm -> /dev/shm symlink
(any other?)
I wonder what is the best approach to do
