From fnaumann@mail.cs.uni-magdeburg.de Thu Jul 22 15:34:16 2004 X-Authentication-Warning: laura.studionet: maurits owned process doing -bs Date: Thu, 22 Jul 2004 15:30:43 +0200 (CEST) From: Maurits van de Kamp X-X-Sender: maurits@laura.studionet To: mintlist Subject: Re: [MiNT] vlogin In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new-20030616-p7 (Debian) at fishpool.fi Delivered-To: mint@fishpool.com Delivered-To: mint@lists.fishpool.fi X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: maurits@bassment.nu Precedence: bulk List-help: List-unsubscribe: List-ID: X-List-ID: X-Milter: ClamAV 0.70/0.70kjel X-Milter: ClamAV 0.70/0.70kjel On Thu, 22 Jul 2004, Frank Naumann wrote: > > Yes, it is way how to do it, but then you can use one AES only. Also there > > is MyAES other interesting option to XaAES. Should we add login > > functionality to all existing AESes? > > The moose.adi is an XaAES specific interface. Sou you already depend on > XaAES and this interface (and the interface version). The dilemma is that you either hack your way into a premature AES environment (like Xboot does too for example), or indeed add login functionality to all AESes. OR.. you'd have to run the AES as root and vlogin as AES shell (instead of a desktop), which in turn launches the desktop as the logged-in user. But I have a feeling this is too far away from reality to actually work. :o) Maurits.