From: jbranso@dismail.de
To: "Raghav Gururajan" <rg@raghavgururajan.name>
Cc: jbranso@gnucode.me, help-guix@gnu.org
Subject: Re: Auto-Login to a Specific TTY
Date: Tue, 15 Nov 2022 15:55:17 +0000 [thread overview]
Message-ID: <be4073b00ec05f49030eb6e71097799a@dismail.de> (raw)
In-Reply-To: <9a39212e-48c8-9bb5-558f-f460ab0b04b5@raghavgururajan.name>
November 14, 2022 11:56 PM, "Raghav Gururajan" <rg@raghavgururajan.name> wrote:
> Joshua,
>
>> This has been broken for me for at least a year. :(
>
> I see.
>
>> I've since moved to seatd, which apparently doesn't support autologin.
>> So for now, I am just not worrying about autologin to tty. :)
>
> Are you using seatd as system service?
>
Yup. no elogind here. :)
I think pkill9 help me set it up:
https://notabug.org/jbranso/guix-config/src/master/bare-bones-sway.scm
> Regards,
> RG.
prev parent reply other threads:[~2022-11-15 15:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 14:00 Auto-Login to a Specific TTY Raghav Gururajan
2022-11-14 14:34 ` Joshua Branson
2022-11-15 4:56 ` Raghav Gururajan
2022-11-15 15:55 ` jbranso [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=be4073b00ec05f49030eb6e71097799a@dismail.de \
--to=jbranso@dismail.de \
--cc=help-guix@gnu.org \
--cc=jbranso@gnucode.me \
--cc=rg@raghavgururajan.name \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).