public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Jon TURNEY <jon.turney@dronecode.org.uk>
To: cygwin-xfree@cygwin.com
Cc: fergus@bonhard.uklinux.net
Subject: Re: Starting XWin from a portable CD
Date: Sun, 13 Mar 2011 19:46:00 -0000	[thread overview]
Message-ID: <4D7D1F2E.20705@dronecode.org.uk> (raw)
In-Reply-To: <4D7C86BF.6060305@bonhard.uklinux.net>

On 13/03/2011 08:56, Fergus wrote:
> I'm running Cygwin-X from a portable device.
> From a write-able stick the start command
> bin\run bin\XWin -nolock -nolisten local -logfile /dev/null -multiwindow &
> works perfectly well. Notice the switch -logfile /dev/null which means the
> file XWin.0.log is not written.
> (Slightly odd I know. The switch -logfile should specify a filename  not a
> directoryname, but it seems to work?)

/dev/null is not a directory

> However using an identical architecture as on the stick, but on a CD, the same
> start command results in
> "Failed to activate core devices".
> So is there something else that needs to be written and cannot be diverted to
> /dev/null (or somewhere write-able).
> Or, if I know what it is, can I divert it or otherwise turn it off?

You didn't attach the XWin output, so I'm guessing here, but during server
startup the mandatory XKB extension needs to invoke xkbcomp to compile the
keymap into a temporary file in /var/lib/xkb/ which it then reads and deletes.

You should be able to confirm that is the case by reading the XWin output, or
running your XWin commmand under strace, in which case you will need to
arrange for /var to be mounted somewhere read/write.

> (Oh woe woe woe. I've lost count of the things that worked so easily on 1.5
> and somehow don't on 1.7, this start command on a portable CD being one of the
> list.)

Whilst I appreciate the therapeutic power of having a whine, this doesn't
really add anything to your email.

-- 
Jon TURNEY
Volunteer Cygwin/X X Server maintainer

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/


      reply	other threads:[~2011-03-13 19:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-13  8:57 Fergus
2011-03-13 19:46 ` Jon TURNEY [this message]

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=4D7D1F2E.20705@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-xfree@cygwin.com \
    --cc=fergus@bonhard.uklinux.net \
    /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).