From mint-bounce@lists.fishpool.fi Tue Mar 10 09:13:40 2009 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:from:to :in-reply-to:content-type:content-transfer-encoding:mime-version :subject:x-priority:date:references:x-mailer; bh=VcZHf0vDuvbcjJOfJwapt279GUDicQX8hNi6x6D42rY=; b=AiaavpB1wFCssLqsfGUxficbyWxLWEyAYmSzGoBD+yOF70dQ0Oa83qPtrGHMa60LWX ilqN/YlxS4H2lefGqgwylHtdi2k0TplyzEnp9U4vfRj+hhCkqlEn6mgVvdYBGM3gNVb0 aLxgNBxUFZh1V868ueqpH9+V0rZGGwYqVQR1A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:in-reply-to:content-type :content-transfer-encoding:mime-version:subject:x-priority:date :references:x-mailer; b=sk+cxENsjIjKaffnkR/DoU9Fle3GZHbuZUmAOrgj1wSFeArxDwjuE0cI9wX3bTMUfa Rc48pdcP2SkH7V5UtAhLvMBdbeEiESpTGxvpgxtMHDoa/dB2QVqEDGUTUKd6GAY9TOVE K8xDUn049OBodEitt57d7oCYe0fBOME4kpXl8= Message-Id: <9BF81908-2DCA-4920-99C6-AE4A5352063A@gmail.com> From: Peter Persson To: mint@fishpool.com In-Reply-To: <00080c25.019676d6c58e@mail.gmx.net> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Subject: Re: [MiNT] XaAES and multiuser setup X-Priority: 3 Date: Tue, 10 Mar 2009 14:11:45 +0100 References: <00080c25.019676d6c58e@mail.gmx.net> X-Mailer: Apple Mail (2.930.3) X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: pep.fishmoose@gmail.com Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Hi, I've noticed this too. My workaround is to start XaAES using SUDO. At least I get the right home folder... When I need to test stuff using "normal" privilege, I login on a TosWin console and start the app in question from there. Not nice, but atm it seems to be the only solution, since loading kernel modules require root access? -- PeP 10 mar 2009 kl. 13.02 skrev Lars Schmidbauer: > Hello, > i posted this some time ago (MinT 1.16.3/XaAES 0.998alpha/TeraDesk): > It's not possible to start XaAES when logged in as a 'normal > user' (not root). > Even if i set access-rights of U:/c to '775' (in fstab) and /dev/km > to '755' > (with sudo), i always get the error-message > 'xaloader: No /dev/km found. Please update your kernel'. > Is there a solution for this? Starting XaAES with 'sudo' does not > work, because > LOGNAME is then set to 'root' and XaAES and all other apps are > started with > root privilegies/paths. > For testing, i installed XaAES in /opt, set global read/write > permissions and > changed the path of /usr/bin/xaaes to the new location of xaloader- > it's > always the same problem. > Can anybody help (or at least confirm this)? > > Thanks, > Lars > > > > >