On Mon, Jul 01, 2002 at 11:28:42PM -0400, Harold Hunt wrote:
Doh. system_printf != syscall_printf. I've checked in a fix and am
rebuilding the snapshot.
>>>
>>>And, additionally, I put Pierre's patch in the wrong place in the code.
>>>Sigh. I had to interpret it because the formatting w
Chris,
> >>Doh. system_printf != syscall_printf. I've checked in a fix
> >>and am rebuilding the snapshot.
> >
> >And, additionally, I put Pierre's patch in the wrong place in the code.
> >Sigh. I had to interpret it because the formatting was GNU standard and
> >I interpreted it wrong.
> >
>
hallenged by the 2043 EDT
>>>cygwin1-20020701.dll snapshot. Output follows. (Remote host ip obscured as
>>>all 0's for privacy).
>>>
>>>Harold
>>>
>>>Administrator@NUCFAC13 ~
>>>$ ssh [EMAIL PROTECTED]
>>> 64 [ma
At 09:03 PM 7/1/2002 EDT, Harold L Hunt wrote:
>Chris, Pierre,
>
>Oh yeah, and now ssh seems to be challenged by the 2043 EDT
>cygwin1-20020701.dll snapshot. Output follows. (Remote host ip obscured as
>all 0's for privacy).
>
>Harold
>
>Administrator@NU
At 08:59 PM 7/1/2002 EDT, Harold L Hunt wrote:
>Chris, Pierre,
>
>> >I sent a patch to cygwin that should take care of the
>> >symptom.
>>
>> There is a new snapshot available which incorporates this patch.
>
>I got my machine back to a state where it produced the xterm error by I
>uninstalling a
On Mon, Jul 01, 2002 at 09:04:44PM -0400, Harold L Hunt wrote:
>No, it won't go into the documentation. It is a bug that will be fixed
>soon.
Right, (as Harold knows) that's kinda the whole point of several threads
in this mailing list.
There is no way that we should have to tell anyone to stan
On Mon, Jul 01, 2002 at 09:43:14PM -0400, Christopher Faylor wrote:
>On Mon, Jul 01, 2002 at 09:03:30PM -0400, Harold L Hunt wrote:
>>Chris, Pierre,
>>
>>Oh yeah, and now ssh seems to be challenged by the 2043 EDT
>>cygwin1-20020701.dll snapshot. Output follows.
On Mon, Jul 01, 2002 at 09:03:30PM -0400, Harold L Hunt wrote:
>Chris, Pierre,
>
>Oh yeah, and now ssh seems to be challenged by the 2043 EDT
>cygwin1-20020701.dll snapshot. Output follows. (Remote host ip obscured as
>all 0's for privacy).
>
>Harold
>
>Admini
Martin,
No, it won't go into the documentation. It is a bug that will be fixed soon.
Harold
Martin Bosticky <[EMAIL PROTECTED]> said:
> Yah, It seems like this problem is really common. it should go into the
> documentation ASAP
>
> i am a beginner, so i don't know what to do to do that.
>
Chris, Pierre,
Oh yeah, and now ssh seems to be challenged by the 2043 EDT
cygwin1-20020701.dll snapshot. Output follows. (Remote host ip obscured as
all 0's for privacy).
Harold
Administrator@NUCFAC13 ~
$ ssh [EMAIL PROTECTED]
64 [main] ssh 1044 seteuid32: special case, return
Yah, It seems like this problem is really common. it should go into the
documentation ASAP
i am a beginner, so i don't know what to do to do that.
Martin.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Friday, 28 June 2002 1:16
To: [EMAIL PROTECTED]
Subject:
ne 691712 Jan 21 08:59 xterm.exe
=
I downloaded and installed the cygwin1-20020701.dll snapshot at 20:43 EDT.
Now when I run startxwin.bat or startxwin.sh, Cygwin/XFree86 (XWin.exe),
twm.exe and xsetroot.exe all startup, but xter
At 08:26 PM 7/1/2002 EDT, Harold L Hunt wrote:
>
>Pierre,
>
>> Don't worry, Cygwin won't require users to run mkpasswd or to edit passwd
>> by hand. The patch I have sent will satisfy you.
>
>Sounds good.
>
>> Just out of curiosity, could you run mkgroup -d ?
>
>Domain Users:S-1-5-21-2139319003-11
Pierre,
> Don't worry, Cygwin won't require users to run mkpasswd or to edit passwd
> by hand. The patch I have sent will satisfy you.
Sounds good.
> Just out of curiosity, could you run mkgroup -d ?
Domain Users:S-1-5-21-2139319003-1153703952-439713625-513:10513:
This is really interesting.
On Mon, Jul 01, 2002 at 06:42:28PM -0400, Pierre A. Humblet wrote:
>Harold L Hunt wrote:
>>
>> Pierre,
>>
>> Before setting CYGWIN=ntsec:
>> =
>> hunt@NUCFAC13 /usr/X11R6/bin
>> $ id
>> uid=15136(hunt) gid=10513(Administrators)
>> =
At 06:39 PM 7/1/2002 EDT, Harold L Hunt wrote:
>Pierre,
>
>I've gotten a success and I propose a solution, at least for now... skip to
>the bottom if you just want the meat and potatoes.
Harold,
Don't worry, Cygwin won't require users to run mkpasswd or to edit passwd
by hand. The patch I have s
Harold L Hunt wrote:
>
> Pierre,
>
> Before setting CYGWIN=ntsec:
> =
> hunt@NUCFAC13 /usr/X11R6/bin
> $ id
> uid=15136(hunt) gid=10513(Administrators)
> =
>
> After setting CYGWIN=ntsec:
> =
Pierre,
I've gotten a success and I propose a solution, at least for now... skip to
the bottom if you just want the meat and potatoes.
> Cygwin thinks that your gid is 10513 but Windows only puts
> you in Everyone and Users.
Interesting.
> Editing /etc/passwd to change your gid to 545 should s
Pierre,
Do you have a Windows NT/2000 machine that you can either
1) Create a local account that is not a member of Administrators and that has
restricted priveleges... basically, an account that is only a member of Users.
2) Logon to a domain account that has restricted priveleges?
Those (espe
Harold L Hunt wrote:
>
> Pierre,
>
> After setting CYGWIN=ntsec:
> ===
> hunt@NUCFAC13 ~
> $ id
> uid=15136(hunt) gid=10513 groups=0(Everyone),545(Users)
> ===
Cygwin thinks that your gid is
Unfortunately it works fine for me.
462 4673072 [main] xterm 420 seteuid32: uid: 11054 myself->gid: 10513
998 4674070 [main] xterm 420 seteuid32: Process token verified
Harold, I will send you privately a token analysis program.
Pierre
Chris,
> Yep, understood. I thought it was funny that I supposed something that
> actually turned out to be the case from the strace log.
Ah ha...
> I have forwarded your strace to cygwin-developers and Pierre Humblet (who has
> recently been making some major changes to the setuid code) will
Pierre,
Before setting CYGWIN=ntsec:
=
hunt@NUCFAC13 /usr/X11R6/bin
$ id
uid=15136(hunt) gid=10513(Administrators)
=
After setting CYGWIN=ntsec:
===
hunt@NUCFAC13 ~
On Mon, Jul 01, 2002 at 05:16:00PM -0400, Harold L Hunt wrote:
>I actually took a look at the strace log and saw the problems with creating
>registry keys and I sent my email with that note before I read your email
Yep, understood. I thought it was funny that I supposed something that
actually t
Harold L Hunt wrote:
>
> Pierre,
>
> We're going to have to make this discussion public because I don't know enough
> about setuid, getuid, and xterm to answer all questions. I'll be sure to cc
> you on any replies and I ask the anyone else replying do the same (Pierre is
> not subscribed to th
Pierre,
We're going to have to make this discussion public because I don't know enough
about setuid, getuid, and xterm to answer all questions. I'll be sure to cc
you on any replies and I ask the anyone else replying do the same (Pierre is
not subscribed to the [EMAIL PROTECTED] mailing list).
Chris,
I actually took a look at the strace log and saw the problems with creating
registry keys and I sent my email with that note before I read your email that
mentioned the fact that I may not be able to write to HKLM. So it may still
be worth considering that something along the path to an x
On Mon, Jul 01, 2002 at 04:51:19PM -0400, Harold L Hunt wrote:
>Chris,
>
>Sorry, I've been running around like a chicken with its head cut off
>this last week trying to get the car repaired for a 1200 mile trip this
>weekend and all the things that go along with that... I forgot that
>you sent me
Chris,
Yup, as in my other followup, I don't have permission to write to HKLM on this
machine (nor can I get it).
I added the -u parameter and got the mount command to work.
However, the new mount made no difference. The problem still exists.
Strace with new mount:
http://www.msu.edu/~huntha
On Mon, Jul 01, 2002 at 04:41:42PM -0400, Harold L Hunt wrote:
>Chris,
>
>> Hmm. If you do a:
>>
>> mount -f -X -b c:\cygwin\usr\X11R6\bin /usr/X11R6/bin
>>
>> does the problem go away, perchance? I would expect it to.
>
>Tried it, didn't work. See below. Any other syntax hints?
Yeah, if yo
Yep, its that same weirdo that posts from a couple of other emails.
Its Wayne, dockeen, [EMAIL PROTECTED]
Did you try the regeneration of the /etc/passwd that I mumbled about
last week? It has worked for several people with the permission
denied problem.
I am getting frustrated for you because
Chris,
Sorry, I've been running around like a chicken with its head cut off this last
week trying to get the car repaired for a 1200 mile trip this weekend and all
the things that go along with that... I forgot that you sent me information on
how to do an strace.
Here is the strace:
http://www.
Chris,
> Hmm. If you do a:
>
> mount -f -X -b c:\cygwin\usr\X11R6\bin /usr/X11R6/bin
>
> does the problem go away, perchance? I would expect it to.
Tried it, didn't work. See below. Any other syntax hints?
(My user name is 'hunt' on this machine.)
Harold
hunt@NUCFAC13 ~
$ mount -f -X -
On Mon, Jul 01, 2002 at 04:15:18PM -0400, Harold L Hunt wrote:
>Huh... the subject says it all.
>
>Same error as before:
>
>setuid failed: Permission denied
>
>You know, xterm is calling perror ("setuid failed")... so perror must know the
>last errno... ah, I don't know what else to say...
Since
Huh... the subject says it all.
Same error as before:
setuid failed: Permission denied
You know, xterm is calling perror ("setuid failed")... so perror must know the
last errno... ah, I don't know what else to say...
Harold
Thomas,
Wait for the next real release in a day or two, I believe the next release
will fix your problem. The changes that we have made to fix the KDE 3.0 icon
bug required lots of changes to the way that we handle the depth and bits per
pixel variables and a few of those changes got missed or m
I just installed the latest test version of XWin.exe (4.2.0-8) using the
Cygwin setup program and found that it is doing something very funky!
I'm running XWin in windowed mode (with -nodecoration flag) under Windows
2000 @ 1024x768 and 24bpp.
I tried it in fullscreen mode @ 24bpp and there is
Please check my posts from last week. The problem which you describe sounds
exactly like the one I fought,
and my later posts describe exactly how I fixed it (with a lot of help from
the community).
Wayne Keen
Hi,
Can you post the contents of /tmp/XWin.log from after the cygwin
installer version has crashed?
Thanks,
Stuart
> -Original Message-
> From: Siddhartha Shivshankar [mailto:[EMAIL PROTECTED]]
> Sent: 01 July 2002 15:24
> To: [EMAIL PROTECTED]
> Subject: X-Free doesnt work, shady work
Hello all, hope you're doing good.
XFree86 wouldnt load up on my Windows XP
machine. I installed practically all of cygwin
again because I didnt know what the problem was.
(no use of that though)
It keeps giving me the error that there was no
X server to service requests. The X background
app
Hi there,
To those of you interested, I modified my x-launcher program to work
with a stock cygwin-xfree install, without needing an install program.
It should find where everything is by using the registry, then stores
its own settings there too (in a different key!).
xlauncher is a program whi
Hi Sebastian,
Somebody else reported this a couple of days ago - along with a long
explanation and why it was happening. The subject of the post is
"Win95B TrackMouseEvent not in User32.dll"
Harold Hunt replied saying "opps - I'll fix that in the next release".
Regards
Stuart
-Origin
Hello!
Sorry for the inconvenience, but I got a problem with xfree on cygwin at a win95 box.
I'm using the current versions of both and everything seemed to work quite well, but
suddenly X doesn't start anymore.
Whenever I start "startx", a message window pops up telling me, that the file XWIN.
43 matches
Mail list logo
