From mboxrd@z Thu Jan 1 00:00:00 1970 From: poma Subject: Re: [systemd-devel] Someone working on gui for multiseat? Date: Tue, 12 Feb 2013 15:50:30 +0100 Message-ID: <511A56B6.3010402@gmail.com> References: <20130129184745.GB28337@tango.0pointer.de> <20130204100600.GA12026@tango.0pointer.de> <20130208004310.GF625@tango.0pointer.de> <20130208155418.GA2902@tango.0pointer.de> <5118BC38.8050102@colin.guthr.ie> <20130211203047.GC1541@tango.0pointer.de> Mime-Version: 1.0 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20130211203047.GC1541@tango.0pointer.de> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org To: Lennart Poettering Cc: systemd Mailing List , DRI Development List-Id: dri-devel@lists.freedesktop.org On 02/11/13 21:30, Lennart Poettering wrote: [=85] > Of course, doing this via the command line is not user-frienldy, but > maybe this will one day get fixed and somebody writes a proper UI for > it... > = Regarding 'loginctl attach seat0 ', the only thing really missing is the 'sys' path completion, so one doesn't pars it via e.g. dmesg -t | grep -P '(?=3D.*devices)(?=3D.*USB)', grep -B1 sys /var/log/Xorg.0.log, tree /sys/class/drm, etc. Behind the wheel, dri/drm device 'sys' path doesn't show up in dmesg, nor in Xorg.*.log. - cc'ing dri-devel. Cheers, poma