Hello Tom,
thank you very much for the review, it is very appreciated. I've sent
out the patch to get a feedback on a general approach, since there are
no objections to it, I will hack up the rest, inaccessible dirs, man
page etc...
Cheers,
Michal
_
Hello,
Looking forward to mount custom partitions I decided to use unit.mount
files to define my new fs. Everything works perfectly, so I tried to
do the same with all my mounted filesystems and removing /etc/fstab.
But unfortunatly, creating a -.mount file in
/etc/systemd/system/local-fs.target.
On Sat, Feb 02, 2013 at 03:24:44PM +0100, Sébastien Luttringer wrote:
> Hello,
>
> Looking forward to mount custom partitions I decided to use unit.mount
> files to define my new fs. Everything works perfectly, so I tried to
> do the same with all my mounted filesystems and removing /etc/fstab.
>
Current one:
- If StopWhenUnneeded=yes and RequiredBy=, WantedBy=, BoundBy= empty
Then stop unit.
The side effect is:
- If user starts unit, that not wanted by any started target, then unit
will be immediately stopped.
The problems are:
- The user can not be sure that the launch of a uni
В Sat, 2 Feb 2013 15:24:44 +0100
Sébastien Luttringer пишет:
> Hello,
>
> Looking forward to mount custom partitions I decided to use unit.mount
> files to define my new fs. Everything works perfectly, so I tried to
> do the same with all my mounted filesystems and removing /etc/fstab.
>
> But
Hello systemd developers
TL;DR: On a VT which X is running, messing with KDSKBMODE on
underneath X at best has no affect and at worst breaks keyboard input
badly. In the short term, systemd should stop calling this ioctl
because it has no benefit and makes no sense.
--
There is a bit of back sto
