On 5/28/22 12:15 PM, Dallin Dahl wrote:
> It turns out I had the same issue as Rio, since my login shell was still
> controlling my terminal. If I run:
>
> exec s6-setsid X :3 vt3
>
> while logged into tty3, I get an X display. However, I still can't
> seem to get it to work with s6-svscan. If
It turns out I had the same issue as Rio, since my login shell was still
controlling my terminal. If I run:
exec s6-setsid X :3 vt3
while logged into tty3, I get an X display. However, I still can't
seem to get it to work with s6-svscan. If I exec into s6-svscan from
my login shell, svscan the
Samuel Holland wrote:
> It also works if X has permission to open the tty device read/write. Opening a
> tty as a session leader without a controlling terminal will set the
> controlling
> terminal to that tty. Relevant kernel code:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/li
yianiris said on Mon, 23 May 2022 13:05:51 +0300
>Unbelievable, on this particular list, someone suggesting that dbus or
>systemd (elogind is the most invasive of all parts of systemd) is
>needed to run X, or wayland for that matter.
[snip]
>If you have compiled X to require those, then it is y
Hello, yianiris / fungal-net
El lun, 23 may 2022 a las 7:07, yianiris escribió:
>
> Unbelievable, on this particular list, someone suggesting that dbus or
> systemd (elogind is the most invasive of all parts of systemd) is needed
> to run X [...]
Oh, I'm not suggesting it, I am stating it as a fa
reply Guillermo:
> Hello, Samuel.
>
> I had a look at your s6-rc service definitions, and it seems that you
> don't have one for the system-wide message bus (D-Bus) and elogind.
> That, in addition to having the tmpfs whose path is stored in
> XDG_RUNTIME_DIR mounted by a "user-setup@" system serv
On 5/22/22 10:07 AM, Guillermo wrote:
> Hello, Samuel.
>
> El sáb, 14 may 2022 a las 23:44, Samuel Holland escribió:
>>
>> X is started at boot from my user supervision tree[1], which is started by
>> the
>> user-* services in my system supervision tree[2].
>>
>> [1]: https://github.com/smaeul/rc
Hello, Samuel.
El sáb, 14 may 2022 a las 23:44, Samuel Holland escribió:
>
> X is started at boot from my user supervision tree[1], which is started by the
> user-* services in my system supervision tree[2].
>
> [1]: https://github.com/smaeul/rc-user
> [2]: https://github.com/smaeul/rc
I had a lo
This thread has inspired me to move my desktop setup under s6 this weekend.
Here's what I got:
General flow: boot to tty1 -> login -> bash starts bashrc -> bashrc sets
DISPLAY and TTY env vars then exec into s6-svscan -> s6-svscan starts xserver,
window manager, and other desktop services.
Rea
El sáb, 14 may 2022 a las 22:52, Laurent Bercot escribió:
>
> [...] it *is* possible to run Xorg under s6; several users are
> doing so, and I hope they will post their setup.
I actually don't run Xorg as a supervised process. I don't know what
systemd-based GNU/Linux distributions do, but on Gent
On 5/13/22 10:47 PM, Guillermo wrote:
> Hello,
>
> El mié, 11 may 2022 a las 0:43, dallinjdahl escribió:
>>
>> I tried to run X under s6 with the following run file:
>>
>> ~~~
>> #!/usr/bin/execlineb
>> [...]
>> X :${screen} vt${screen}
>> ~~~
>> [...]
>> (WW) xf86OpenConsole: VT_ACTIVATE failed:
Is the purpose of executing setsid() in s6-supervise to allow for the
services to continue beyond the termination of the supervision tree?
It's actually the opposite: it's to protect the supervision tree
against misbehaved services. :) setsid() makes sure the service is
isolated, and a killpg()
Hello,
Guillermo wrote:
> If the Xorg process does not run as root, the tty specified in the vt
> argument must be its controlling terminal. It works if you run X from
> an interactive shell (perhaps indirectly through 'startx'), because it
> inherits the shell's controlling terminal. It doesn't
Hello,
El mié, 11 may 2022 a las 0:43, dallinjdahl escribió:
>
> I tried to run X under s6 with the following run file:
>
> ~~~
> #!/usr/bin/execlineb
> [...]
> X :${screen} vt${screen}
> ~~~
> [...]
> (WW) xf86OpenConsole: VT_ACTIVATE failed: Operation not permitted
> (EE)
> Fatal server error:
>
I had the thought to start up all my personal services with s6, and it's
going well. However, looking at the xinit source code, it appears to
start the X server, wait until it's up, start a client program, wait
until it shuts down, and then kill the X server. It seems to me that
xinit is effectiv
15 matches
Mail list logo
