>> After touching those files you need to run »systemd
>> deamon-reload« to tell systemd, that you touched them.
>
> This worked
>
> $ sudo systemctl daemon-reload
>
> and after copying the tty1 directory and renaming it, there is
> autologin everywhere!
>
> :)
How to do it,
https://dataswamp
Silvio Knizek wrote:
> After touching those files you need to run »systemd
> deamon-reload« to tell systemd, that you touched them.
This worked
$ sudo systemctl daemon-reload
and after copying the tty1 directory and renaming it, there is
autologin everywhere!
:)
--
underground experts unit
Silvio Knizek wrote:
> So, if you have this setup, I really suggest that you use
> specialised units
Hm... what "units" do you refer to here?
> for every terminal and a graphical login manager for the
> X stuff. So instead of starting agetty you can directly
> start emacs or tmux as the User= yo
My other message doesn't seem to have come yet, but to answer
that message, yes, it does work on tty!
I need one such directory and file for each tty?
--
underground experts united
https://dataswamp.org/~incal
___
systemd-devel mailing list
systemd-de
Silvio Knizek wrote:
> /etc/systemd/system/getty@tty1.service.d/10-autologin.conf
> [Service]
> ExecStart=
> ExecStart=-/sbin/agetty -a incal --noclear %I $TERM
I tried it in tty2 and it didn't work. Is it because it only
works for tty1 as is mentioned, of for some other reason,
I don't know. I'l
Silvio Knizek wrote:
>
> your path is wrong. You want the following:
>
> /etc/systemd/system/getty@tty1.service.d/10-autologin.conf
I don't have that file or even directory, but I can put it
there manually, of course.
> Do you need this auto login for debug reasons (than maybe
> debug- shell.ser
I do autologin like this:
ExecStart=-/sbin/agetty -a incal --noclear %I $TERM
/etc/systemd/system/getty.target.wants/getty@tty1.service # line ~39
$ sudo systemctl daemon-reload
However, it seems to disappear after a while, maybe when
systemd gets updated?
So my question is how do I m
Mantas Mikulėnas writes:
> ~/.zprofile seems just fine for this task – it
> *is* the zsh "run things on login" script after
> all. (And since these are your personal processes,
> especially the X stuff, it's much better to have
> them running *inside* the login session along with
> everything els
I would like to start different processes in
different ttys on boot, automatically and with
autologin first, and then have them run as normal
programs, with the I/O intact, including quitting
and get the shell - i.e., just as you would if you
did it all manually. (The autologin part of the
above qu
