public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Jim Scheef <jscheef@yahoo.com>
To: cygwin-xfree@cygwin.com
Subject: Re: Cygwin/xFree from 2 users
Date: Thu, 04 Mar 2004 23:28:00 -0000 [thread overview]
Message-ID: <20040304232828.80593.qmail@web41507.mail.yahoo.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0403020915300.11345@odoaker.hrz.tu-chemnitz.de>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 2498 bytes --]
Alexander and all,
I guess I wasn't clear. I'm sitting at my notebook looking at the XP login
screen. If I log in using js@domainname, Xwin works fine, but fails to start
when I log on using js@machinename. The machine and the Cygwin/Xfree
installation are one and the same in both cases. I use the same username (js)
in both cases for convenience and I was hoping that this would make it easy
to use the same Cygwin home directory (/home/js) for both logins. How can I
make this work?
Jim
--- Alexander Gottwald <alexander.gottwald@s1999.tu-chemnitz.de> wrote:
> On Mon, 1 Mar 2004, Jim Scheef wrote:
>
> > Hello.
> >
> > I use a notebook computer so I can carry my computing environment around.
> > This is WinXP and current versions of Cygwin and xFree as of a few weeks
> ago.
> >
> > I have several user 'accounts' that belong to various domains. Most of
> these
> > accounts are 'js', as in js@machinename, js@domain1.com, js@domain2.org,
> etc.
> > I want all of these to use the same Cygwin home directory.
> >
> > Cygwin and X were installed from js@domain1.com. When I'm not connected
> to a
> > network, I use js@machinename. Cygwin seems to work with both user
> accounts
> > but X will not start from js@machinename. The attached xwin.log came from
> > running xinit. Trying to start kde gives an error that there is no write
> > access to .ICEauthority. I believe the X problem is related to
> permissions
> > within /home/js.
> >
> > I have tried to set up permissions for both user accounts on /home/js but
> I
> > can't seem to make them stick.
> >
> > What permissions are needed? What file permissions are critical, which
> mearly
> > convenient? Does the setup process replace the permissions on the user's
> home
> > directory? How can Cygwin and X be configured for multiple users on a
> > machine? and the big question - how can I configure Cygwin and X so that
> I
> > can use the same /home/js directory from multiple 'js' accounts?
>
> You can not start two xservers with the same display number (which is in
> fact the
> TCP/IP port used). Start the second with an additional parameter ":1". eg
> XWin :1
> or xinit -- :1
>
> bye
> ago
> --
> Alexander.Gottwald@s1999.tu-chemnitz.de
> http://www.gotti.org ICQ: 126018723
> Chemnitzer Linux-Tag 2004 - 6. und 7. März 2004
> http://www.tu-chemnitz.de/linux/tag
__________________________________
Do you Yahoo!?
Yahoo! Search - Find what youre looking for faster
http://search.yahoo.com
next prev parent reply other threads:[~2004-03-04 23:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-02 0:49 Cygwin Openbox queries Jophrey Lim
2004-03-02 4:47 ` Cygwin/xFree from 2 users Jim Scheef
2004-03-02 8:17 ` Alexander Gottwald
2004-03-04 23:28 ` Jim Scheef [this message]
2004-03-04 23:36 ` Harold L Hunt II
2004-03-05 22:52 ` Alexander Gottwald
2004-03-02 18:44 ` Cygwin Openbox queries Brian Ford
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040304232828.80593.qmail@web41507.mail.yahoo.com \
--to=jscheef@yahoo.com \
--cc=cygwin-xfree@cygwin.com \
/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).