Re: Problem with rebaseall

[Brian Dessent]

Yongtao Cui wrote:

> "rebaseall: only ash processes are allowed during rebasing

This is the same issue as
, wherein a change in
behavior of '/proc/pid/exename' caused the rebaseall script to stop
functioning.  You can just make the indicated edit until the rebase
package is updated.

Brian

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

Problem with rebaseall

[Yongtao Cui]

I got an error message like "unable to remap C:\cygwin\bin\tk84.dll"
when I tried to install Python Imaging Library.
I searched the website and found that could be resolved by rebasing the system.
Following the instruction on rebaseall, I closed all of the cygwin
windows, opened a new ash shell and ran rebaseall. But I got a message
"rebaseall: only ash processes are allowed during rebasing

"
I even tried restarting system and executing rebaseall immediately. I
wonder what else processes I should close. Can anyone give me a help?
Thanks in advance.

Regards,
Yongtao

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

RE: How to get more than one X-window?

[Stepp, Charles]

I have the following in my .sh_profile. This ensures that my DISPLAY
gets set correctly in each shell:

# --
# Added - Tue May 30 12:26:30 EDT 2006
# --
DISPLAY=$("$HOME"/SetDisplay)
export DISPLAY
&&

And the SetDisplay script:

$ cat SetDisplay 
#!/usr/bin/ksh

IP=$(nslookup $(hostname) | sed -n '/Name:/,$s/Address:[ ]*//p')
//g')print $IP | sed 's/
DISPLAY=${IP}:0
print $DISPLAY
^^

Here's a script I use to create a new xterm. It calls stuff that sets
rotating colors out of a list of colors I use, but that stuff can be
ripped out and this can be simplified.
#!/usr/bin/ksh
export DISPLAY=127.0.0.1:0.0
cd "$HOME"
trap "exit;exit" 1
if [[ ! -f "$HOME/Colors.txt" ]]
then
cp /usr/local/bin/Colors.txt "$HOME"
fi
if [[ ! -f "$HOME/geometries.rot" ]]
then
cp /usr/local/bin/geometries.rot "$HOME"
fi


COLORS=$(./rotate.pl ./Colors.txt | awk '{print $1 " " $2}' | sed 's/
/~/')
G=$(./rotate.pl ./geometries.rot)

FG=${COLORS%%~*}
BG=${COLORS##*~}
export DISPLAY
print -- "-fg $FG -bg $BG"
xterm -fg $FG -bg $BG -geometry "$G" -ls -sb -sl 2000 -cr red -fn
8x13bold &

-Original Message-
From: Vanguard [mailto:[EMAIL PROTECTED] 
Sent: Friday, July 07, 2006 4:15 PM
To: cygwin@cygwin.com
Subject: How to get more than one X-window?

I did the install of Cygwin a couple days ago but have been fumbling
around trying to get more than one X-windows session opened on the
screen.  I will open Cygwin (which loads a bash shell) and then run
"xwin -query " to get a login session on that host (on the
particular host to which I am currently connecting, I get logged in
under KDE).  I then want another X-window opened to another host.  I
work on several hosts at a time.  If it were just the one host, I can
open xterms inside the one X-windows session shown on my Windows host.

When, in a bash shell, I try to run another "xwin -query
", a bunch of text pops up which basically tells me that
the X server is already running.  Well, yeah, it got started by the
first xwin command.  Doesn't the Cygwin X-server handle more than one X
session at a time?

I'm actually used to using Reflection X or Exceed X to connect to Unix
hosts from my Windows box but I don't have those available at some
locations and they said to use Cygwin (because it was free).





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

Re: [ANNOUNCEMENT] Updated: gdb-20060706-1 (also includes GUI "insight" debugger)

[Hans Horn]

What is your problem, Larry?

In any case, I noticed that 
http://mirrors.kernel.org/sources.redhat.com/cygwin/release/gdb has been 
updated - now in fact including insight.

thx Chris,
H.

"Larry Hall (Cygwin)" <[EMAIL PROTECTED]> wrote in message 
news:[EMAIL PROTECTED]
> Hans Horn wrote:
>> Folks,
>> Even though I'm expecting to get redirected, I'd like to report that this 
>> package does in fact NOT contain/install insight, despite being 
>> advertised as such!
>
> Indeed, this is completely unacceptable.  To pay good money for something
> that's falsely advertised is... wait a minute, this stuff is free.  So 
> much
> for outrage.  Now I have to find somewhere else to vent all my 
> frustrations.
>
> It really sucks that Cygwin is free.  Someone should really fix that.




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

Re: 1.5.21 release imminent - please test latest snapshot

[Corinna Vinschen]

On Jul  7 12:11, Christopher Faylor wrote:
> I've just created a snapshot which may, barring any conflagrations, be
> very close to what will show up as 1.5.21.  If there are no major
> regressions from 1.5.20, I plan on releasing cygwin 1.5.21 on Monday.
> 
> The fixes that I can infer from the ChangeLog are:
> 
>   - block current signal while executing in a signal handler.
> 
>   - remove previously broken ability to store symlink info in extended 
> attributes.
> 
>   - rexec rewrite
> 
>   - temporarily remove SA_RESTART functionality from blocking signals calls in
> preparation for a 1.5.22 socket rewrite.
> 
>   - implement setmetamode handling (see linux man page for more details).
> 
>   - allow listening on an unbound INET socket.
> 
> (I'm sure Corinna will clarify some of the above or add to the list)

Only two points:

- Not only rexec, but also inet_aton, inet_addr, inet_ntoa, inet_network
  are new functions.  These are FreeBSD implementations which get us rid
  of the equal Winsock calls.

- socklen_t is a typedef now.  The socket functions using socklen_t
  are now declared with socklen_t instead of int in /usr/include/sys/socket.h.

> Please test this (or any newer) snapshot and report any regressions from
> 1.5.20 to this thread.
> 
>   http://cygwin.com/snapshots/
> 
> cgf


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  cygwin AT cygwin DOT com
Red Hat

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

RE: Using du.exe to calculate disk usage on a Microsoft cluster server

[Jim Easton]

Hi,

On Fri, 07 Jul 2006 Will Beldman wrote:
> 1. I have explained how I got long filenames (From another message):
> "I don't own the files. One example is 259 characters long. They are 
> caused by users who have chosen to name their files the same thing as 
> the first sentence of their MS Word doc."
> 2. Most of the text you have quoted was my first message sent in. Some 
> of my follow ups helped explain your questions I'm sure.
> 3. Understand I cannot simply give out the names of offending files. I 
> am already standing on the borderline traversing other user's private 
> files let alone share the names online. Nonetheless, do not concern 
> yourself with these issues. The one I care about is the fts_read which 
> kills du. Even in the worst case, I would at least like to see du keep 
> going through other files until there are none left to do.

So the details are confidential.  However if you expect to get help
you must answer questions and do what is requested of you.

My suggestion is to generate your own directory structure similar to the
"real" stuff but containing no "confidential" information and see if you
can duplicate the problem in that.  You probably won't have to use the
same names nor include collateral files.  Chances are good that by so
constructing a simpler structure you'll figure it out for yourself.

If you can duplicate the problem then you can disclose all the details.

HTH
Jim

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