public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: "Mike Ayers" <mike_ayers@tvworks.com>
To: <cygwin-xfree@cygwin.com>
Subject: RE: Can't start X after upgrading to cygwin1.7
Date: Thu, 04 Feb 2010 22:06:00 -0000	[thread overview]
Message-ID: <83E753BE7B6A324ABB336245BAF1DAAC0DE3F6B3@mailserver.metatv-ds.metatv.com> (raw)
In-Reply-To: <4B69D1F3.704@dronecode.org.uk>

> From: cygwin-xfree-owner@cygwin.com [mailto:cygwin-xfree-
> owner@cygwin.com] On Behalf Of Jon TURNEY
> Sent: Wednesday, February 03, 2010 11:44 AM

> > 1.  Added a line in /etc/profile, just before the "chmod 1777 /tmp"
> line:
> >       mount -f "$USERPROFILE/Local Settings/Temp" /tmp

	I think it would be better to find the actual /tmp directory and change the Windows permissions to give "Full Control" to "Everyone".  This should make the problem 

> >
> > 2.  Changed the XWin Server icon so instead of just startxwin.exe, it
> says:
> >       ... "startxwin.exe -- -logfile ~/XWin.log"
> > (Don't take out the beginning of the command that runs startxwin
> > through bash, or the /etc/profile won't get run.  The quotes are
> > needed because this is the argument to bash's -c option.)

	This isn't bad at all.  An alternative is to change the permissions on /var/log as above, if you don't mind letting all your users see, and be able to delete or modify, all the cygwin logfiles, but I don't see it as any better.


	HTH,

Mike


  parent reply	other threads:[~2010-02-04 22:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4d810821001160955i5026ff4cyd6ec87b960d6adc7@mail.gmail.com>
     [not found] ` <4d810821001160956n77aaf352n7b391176a03eb096@mail.gmail.com>
2010-01-17  1:43   ` Fwd: " Larry Hall (Cygwin X)
2010-01-19  4:27   ` Andrew Senior
2010-01-23 14:02     ` Andrew Senior
2010-01-23 15:37       ` Jeff Spirko
2010-02-03 19:43         ` Jon TURNEY
2010-02-03 22:51           ` Tim Prince
2010-02-04 22:06           ` Mike Ayers [this message]
2010-02-09 18:20           ` Jon TURNEY

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=83E753BE7B6A324ABB336245BAF1DAAC0DE3F6B3@mailserver.metatv-ds.metatv.com \
    --to=mike_ayers@tvworks.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).