Try:lachlanp wrote:Can you suggest what I still need to change to get the auto-login
Code: Select all
# systemctl set-default multi-user.target
Try:lachlanp wrote:Can you suggest what I still need to change to get the auto-login
Code: Select all
# systemctl set-default multi-user.target
Code: Select all
/etc/systemd/system/getty.target.wants/getty@tty1.service
OK, thanks for bringing that up.milomak wrote:I am finding after doing updates (using sid), thatreverts to default.Code: Select all
/etc/systemd/system/getty.target.wants/getty@tty1.service
Code: Select all
[Service]
ExecStart=
ExecStart=-/sbin/agetty --autologin <user name> --noclear %I $TERM
Code: Select all
[UPGRADE] systemd:amd64 229-5 -> 229-6
[UPGRADE] systemd-sysv:amd64 229-5 -> 229-6
Code: Select all
#ExecStart=-/sbin/agetty --noclear %I $TERM
ExecStart=-/sbin/agetty --autologin root --noclear %I $TERM
... the above file did not exist. I created it and added the stated line with no luck.For automatic login, edit the file at /etc/systemd/system/getty.target.wants/getty@tty1.service and changed the "ExecStart=" line in the "[Service]" section to this:
Code: Select all
[Service]
Type=oneshot
ExecStart=/bin/systemctl --no-block start getty@tty2.service getty@tty3.service getty@tty4.service getty@tty5.service getty@tty6.service
RemainAfterExit=true
Did you notice and read, the Category /topic header, before posting ?Docs, Howtos, Tips & Tricks
Share your own howto's etc. Not for support questions!
No , they don't, it was easier on older Debian versions.From:http://forums.debian.net/viewtopic.php? ... 62#p615329
Postby Head_on_a_Stick » 2016-05-09 13:43
I agree with Gary but briefly:
No big deal, but also did you actually read, carefully the entire thread,lachlanp wrote:
Can you suggest what I still need to change to get the auto-login [/qutoe]
Try:If there are any problems, open a new thread and link back to this one in the OPCode: Select all
# systemctl set-default multi-user.target
especially the how to parts,..?
I know you said you did, but if you missed what it says, about
"Not for support questions!"
There is a pretty good chance you missed some other inportant
details, as well,....
They don't make this simple, do they?
Please read the thread title again and start your own version for testing...rayandrews wrote:Running testing
i run sid . and this worksrayandrews wrote:Gentlemen:
Running testing,
Code: Select all
debian ~ # cat /etc/systemd/system/getty@tty1.service.d/override.conf
[Service]
ExecStart=
ExecStart=-/sbin/agetty --autologin mythtv --noclear %I $TERM
debian ~ #
Code: Select all
debian ~ # systemctl set-default multi-user.target
debian ~ #
Code: Select all
$ cat ~/.profile
[[ -z $DISPLAY && $XDG_VTNR -eq 1 ]] && exec startx /usr/bin/kodi
$
Will it startx from a console log in?milomak wrote:it boots into x when it's set to graphical.target
Code: Select all
systemctl cat getty@tty1
Code: Select all
$ systemctl cat getty@tty1
# /lib/systemd/system/getty@.service
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
[Unit]
Description=Getty on %I
Documentation=man:agetty(8) man:systemd-getty-generator(8)
Documentation=http://0pointer.de/blog/projects/serial-console.html
After=systemd-user-sessions.service plymouth-quit-wait.service
After=rc-local.service
# If additional gettys are spawned during boot then we should make
# sure that this is synchronized before getty.target, even though
# getty.target didn't actually pull it in.
Before=getty.target
IgnoreOnIsolate=yes
# IgnoreOnIsolate causes issues with sulogin, if someone isolates
# rescue.target or starts rescue.service from multi-user.target or
# graphical.target.
Conflicts=rescue.service
Before=rescue.service
# On systems without virtual consoles, don't start any getty. Note
# that serial gettys are covered by serial-getty@.service, not this
# unit.
ConditionPathExists=/dev/tty0
[Service]
# the VT is cleared by TTYVTDisallocate
ExecStart=-/sbin/agetty --noclear %I $TERM
Type=idle
Restart=always
RestartSec=0
UtmpIdentifier=%I
TTYPath=/dev/%I
TTYReset=yes
TTYVHangup=yes
TTYVTDisallocate=yes
KillMode=process
IgnoreSIGPIPE=no
SendSIGHUP=yes
# Unset locale for the console getty since the console has problems
# displaying some internationalized messages.
Environment=LANG= LANGUAGE= LC_CTYPE= LC_NUMERIC= LC_TIME= LC_COLLATE= LC_MONETARY= LC_MESSAGES= LC_PAPER= LC_NAME= LC_ADDRESS= LC_TELE
[Install]
WantedBy=getty.target
DefaultInstance=tty1
# /etc/systemd/system/getty@tty1.service.d/override.conf
[Service]
ExecStart=
ExecStart=-/sbin/agetty --autologin mythtv --noclear %I $TERM
Code: Select all
[ "$(tty)" = "/dev/tty1" ] && exec startx /usr/bin/kodi
BunsenWhat?Peripatus wrote:I can confirm that the procedure works, without modification, for my system running BunsenLabs Helium (i.e. ~Debian Stretch).
Are you kidding me? Just noticed a rather active head on a stick over at the BunsenLabs forums...Head_on_a_Stick wrote: BunsenWhat?
Not any morePeripatus wrote:rather active
Oh Should we take heed?Head_on_a_Stick wrote:Not any morePeripatus wrote:rather active