1.7 - what's the right way to start X?

1.7 - what's the right way to start X?

[Fredrik Staxeng]

What is the recommended/preferred way to start X in 1.7? In 1.5
I used a modified version of startxwin.bat. And where do I 
put my .xinitrc/.xsession script?
-- 
Fredrik Stax\"ang | rot13: sfgk@hcqngr.hh.fr
This is all you need to know about vi: ESC : q ! RET


--
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/

Re: 1.7 - what's the right way to start X?

[Larry Hall (Cygwin X)]

On 12/03/2009 04:07 PM, Fredrik Staxeng wrote:
> What is the recommended/preferred way to start X in 1.7? In 1.5
> I used a modified version of startxwin.bat. And where do I
> put my .xinitrc/.xsession script?

What about startxwin.bat doesn't work for you?  There shouldn't be
differences between 1.5 and 1.7 here.

-- 
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
216 Dalton Rd.                          (508) 893-9889 - FAX
Holliston, MA 01746

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

--
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/

Re: 1.7 - what's the right way to start X?

[Fredrik Staxeng]

"Larry Hall (Cygwin X)" <reply-to-list-only-lh-x@cygwin.com> writes:

>On 12/03/2009 04:07 PM, Fredrik Staxeng wrote:
>> What is the recommended/preferred way to start X in 1.7? In 1.5
>> I used a modified version of startxwin.bat. And where do I
>> put my .xinitrc/.xsession script?
>
>What about startxwin.bat doesn't work for you?  There shouldn't be
>differences between 1.5 and 1.7 here.

Well, I did not find it, so I assumed it had been replaced with 
something better. Something that 
a) does not pop up a command window and
b) calls .xinitrc or something

I have to admit I did not look at the Cygwin site before posting the
question. I did so after, and saw the Cygwin/X section.

-- 
Fredrik Stax\"ang | rot13: sfgk@hcqngr.hh.fr
This is all you need to know about vi: ESC : q ! RET


--
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/

Re: 1.7 - what's the right way to start X?

[Fredrik Staxeng]

"Larry Hall (Cygwin X)" <reply-to-list-only-lh-x@cygwin.com> writes:

>On 12/03/2009 04:07 PM, Fredrik Staxeng wrote:
>> What is the recommended/preferred way to start X in 1.7? In 1.5
>> I used a modified version of startxwin.bat. And where do I
>> put my .xinitrc/.xsession script?
>
>What about startxwin.bat doesn't work for you?  There shouldn't be
>differences between 1.5 and 1.7 here.

Now I have gotten startxwin.bat to work, and modified it to run my bash
script. I had some strange problems on the way though. Previously, I had
used the Cygwin Bash Shell to make some changes. I use mount -c /, change
/etc/passwd to refer to right home directory /c/home/fstx, and put in
my .profile and .bash_rc files. I don't remember doing the mkpasswd/mkgroup 
thing, but I could have.

When I double-clicked startxwin.bat for the first time, it failed. I think
XWin.exe did not start dfor some reason. But I immediately tried again, and
this time I got an XTerm. However, I was in /home/fstx, not /c/home/fstx,
and I got the mkpasswd message. 

When I tried to fix things, I discovered that the mount prefix was set back
to /cygdrive. I can change it, but when I restart cygwin it goes back to
/cygdrive. I can live with that (at least for now)

But starting xterms seems to be very slow, and about 25% of time it fails
with 
      2 [main] xterm 3128 fork: child -1 - died waiting for longjmp 
before initialization, retry 0, exit code 0xC0000005, errno 11
xterm: Error 29, errno 11: Resource temporarily unavailable
Reason: spawn: fork() failed

I have seen this problem before, and the solution was to run rebaseall, 
which broke emacs, and then reinstall libncurses to fix emacs. 

Is this the way to do it? 
Will it still break emacs? 
Will other things break?
Will it break again when updating cygwin?

I am running Windows 7 64-bit Enterprise.

Despite the troubles I have had, I must say that I admire Cygwin for
doing a very good job at an almost impossible task, and the developers
for the heroic efforts to bring Cygwin to each new version of Windows,
despite that Microsoft apparently couldn't care less about breaking it.
 
-- 
Fredrik Stax\"ang | rot13: sfgk@hcqngr.hh.fr
This is all you need to know about vi: ESC : q ! RET


--
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/

Re: 1.7 - what's the right way to start X?

[DePriest, Jason R.]

On Fri, Dec 4, 2009 at 10:12 AM, Fredrik Staxeng <> wrote:
> "Larry Hall (Cygwin X)" <> writes:
>
>>On 12/03/2009 04:07 PM, Fredrik Staxeng wrote:
>>> What is the recommended/preferred way to start X in 1.7? In 1.5
>>> I used a modified version of startxwin.bat. And where do I
>>> put my .xinitrc/.xsession script?
>>
>>What about startxwin.bat doesn't work for you?  There shouldn't be
>>differences between 1.5 and 1.7 here.
>

1.7 makes some pretty significant changes on how 'mount' works.

Basically, Cygwin 1.7 uses a real fstab file instead of a bunch of
registry entries and 'mount' only creates temporary mounts.  If you
want a permanent mount, use the fstab file.

In a little bit more detail, see below.

From: http://cygwin.com/1.7/cygwin-ug-net/ov-new1.7.html
- Mount points are no longer stored in the registry.  Use /etc/fstab
  and /etc/fstab.d/$USER instead.  Mount points created with mount(1)
  are only local to the current session and disappear when the last
  Cygwin process in the session exits.
- Cygwin creates the mount points for /, /usr/bin, and /usr/lib automatically
  from it's own position on the disk.  They don't have to be specified in
  /etc/fstab.

This discusses the mount table in more detail:
http://cygwin.com/1.7/cygwin-ug-net/using.html#mount-table

This is the help information for mount under 1.7:
http://cygwin.com/1.7/cygwin-ug-net/using-utils.html#mount

Thanks.

-Jason

--
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/

Re: 1.7 - what's the right way to start X?

[Ken Brown]

On 12/4/2009 11:12 AM, Fredrik Staxeng wrote:
> I have seen this problem before, and the solution was to run rebaseall, 
> which broke emacs, and then reinstall libncurses to fix emacs. 
> 
> Is this the way to do it? 
> Will it still break emacs? 

I haven't seen any reports of emacs problems in 1.7 after rebasing.

Ken Brown
Cygwin's emacs 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/

Re: 1.7 - what's the right way to start X?

[Yaakov (Cygwin/X)]

On 04/12/2009 10:12, Fredrik Staxeng wrote:
> I have seen this problem before, and the solution was to run rebaseall,
> which broke emacs, and then reinstall libncurses to fix emacs.
>
> Is this the way to do it?
> Will it still break emacs?
> Will other things break?
> Will it break again when updating cygwin?

This was only true with the old version of emacs which depended on 
libncurses7, as the latter was not rebase-able.  This is no longer an 
issue with the latest version of emacs; just rebase and you should be fine.


Yaakov
Cygwin/X

--
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/

Re: 1.7 - what's the right way to start X?

[Fredrik Staxeng]

"Yaakov (Cygwin/X)" <yselkowitz@users.sourceforge.net> writes:

>On 04/12/2009 10:12, Fredrik Staxeng wrote:
>> I have seen this problem before, and the solution was to run rebaseall,
>> which broke emacs, and then reinstall libncurses to fix emacs.
>>
>> Is this the way to do it?
>> Will it still break emacs?
>> Will other things break?
>> Will it break again when updating cygwin?
>
>This was only true with the old version of emacs which depended on
>libncurses7, as the latter was not rebase-able.  This is no longer an
>issue with the latest version of emacs; just rebase and you should be
>fine.

Thanks. 

I just upgraded to the version released this Friday, and I haven't seen the 
message yet. But if I do, I know what to do. 

-- 
Fredrik Stax\"ang | rot13: sfgk@hcqngr.hh.fr
This is all you need to know about vi: ESC : q ! RET


--
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/