On Fedora 21, I created a unit file in which I included
'PrivateDevices=true'.When I attempt to start the unit from the text
console, the unit fails, and 'systemctl status -l' reports:
startx[2754]: (EE) xf86OpenConsole: Cannot open /dev/tty0 (No such file or
directory)
When I take
On Friday 26 December 2014 at 13:37:58, Alison Chaiken wrote:
On Fedora 21, I created a unit file in which I included
'PrivateDevices=true'.When I attempt to start the unit from the text
console, the unit fails, and 'systemctl status -l' reports:
startx[2754]: (EE) xf86OpenConsole:
Hi,
Alison Chaiken:
Isn't /dev/tty0 a pseudo TTY?
It's an alias to the current real TTY, which is not exactly the same thing.
IMHO PrivateDevices=yes is supposed to make sure that this job cannot
mess up any real device. Writing junk to /dev/tty0 can mess up my console
quite easily. Therefore,
On Fri, 26.12.14 13:37, Alison Chaiken (ali...@she-devel.com) wrote:
On Fedora 21, I created a unit file in which I included
'PrivateDevices=true'.When I attempt to start the unit from the text
console, the unit fails, and 'systemctl status -l' reports:
startx[2754]: (EE)
On Fri, 26.12.14 23:38, Matthias Urlichs (matth...@urlichs.de) wrote:
Hi,
Alison Chaiken:
Isn't /dev/tty0 a pseudo TTY?
It's an alias to the current real TTY, which is not exactly the same
thing.
Not really. /dev/tty0 is an alias for the current VT (i.e. the virtual
terminal that's on
On Sat, 27.12.14 01:38, Ivan Shapovalov (intelfx...@gmail.com) wrote:
On Friday 26 December 2014 at 13:37:58, Alison Chaiken wrote:
On Fedora 21, I created a unit file in which I included
'PrivateDevices=true'.When I attempt to start the unit from the text
console, the unit fails, and
