POSIX names for drive letters

[Schwarz, Konrad]

Hi,

I know that it is kind of late :-), but I would like to suggest an
alternative/additional mapping of drive letters to the MinGW and Cygwin
file-system name space.

The proposed mapping for directory `C:\' is `//./C$/' (or perhaps
`//./C/').

The reasons for this mapping are:

* POSIX allows paths that begin with exactly two slashes to be
"special": they do not have to obey normal file system path semantics
(see XBD 4.11).  E.g., POSIX requires `/x/my_file' to be referenced from
`/y/my_dir' as `../../x/my_file', but this is does not work in MinGW.
By beginning the path with two slashes, POSIX compliant code knows that
this transformation should not be attempted in general.

* The notation `//./something' is in line with standard Windows API
names for system devices.  See the documentation for the CreateFile()
function in the Windows SDK for those names.  In particular,
CreateFile() uses `\\.\C:\' to represent the root directory of that
volume and `\\.\C:' to represent the volume (raw device).  Since colon
is used in POSIX to separate paths in the PATH environment variable,
`//./C:/' is not a good mapping.

* The notation is in line with the Windows Universal Naming Convention
(UNC) insofar as it consists of two components and begins with two
directory separation characters.  Therefore, Windows-special cased code
that does not need to differentiate between "local" and "network" drives
(which should be the majority of cases) can stay unaware of the
differentiation.

* `//host/C$' is the standard share name for drives under Windows that
are mounted from a different machine.

* Shells do not attempt to expand the substring `$/' as a variable.
Other languages, e.g., make(1), will attempt to expand such a reference,
so `//./C/' might be better than `//./C$/'.  `//./C/' also has the
benefit of using only letters from the POSIX portable filename character
set.  However, `//./C/' might be used by Microsoft for some different
purpose in the future.

Note that for Windows, `/' is a reserved letter in the file system.  It
is, as far as I know, never a problem to replace `\' with `/' in paths
when dealing directly with the operating system (cmd.exe is something
else), and the Windows SDK functions will even do this for you, except
for paths prefixed with '\\?\'.

Regards,

Konrad Schwarz

--
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: copying and pasting in the terminal window?

[G.W. Haywood]

Hi there,


On Fri, 25 Aug 2006, Gary R. Van Sickle wrote:

> ...  The main trick is (or at least used to be) getting your delete,
> home, end, etc keys working right, and I can send you my magical
> .initrc to take care of that post-haste.

Please cc me on that one, huh?  Or better, post it to the list, my
mailserver might block your ISP.

--

73,
Ged.  (Devoted rxvt user, new to Cygwin.)

--
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: copying and pasting in the terminal window?

[Owen Rees]

--On 24 August 2006 10:39 -0700 Eric Hanchrow wrote:


Igor> FWIW, my main gripe with Console is that it doesn't
Igor> understand line wrapping, so cutting and pasting a line that
Igor> wraps multiple times results in multiple lines.

Yup.  And as far as I know, there's no way to tell the console "please
save the accumulated scrollback into a file".  But then I don't think
rxvt can do that either :-)


You can select all the available scrolled text with both Console and rxvt 
(Console scrolls when you drag off the top/bottom and extends the 
selection, rxvt extends the selection with a right mouse click so you can 
select, scroll, right click).


Once you have copied it all, "cat >somefile" then paste, CR ^D will get it 
into a file. Perhaps not quite as simple as having a 'save' option, but not 
too hard to do.


If you are using rxvt, long lines that wrapped on display will be long 
lines in the file, With Console, there will be line breaks wherever it 
wrapped.


In the context of copying and pasting in a window, I find rxvt far superior 
to Console because of the way it handles long lines (as well 
copying/pasting the way X does without requiring that X be running).


--
Owen Rees
Hewlett Packard Laboratories, Bristol, UK



--
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: POSIX names for drive letters

[Eric Blake]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

According to Schwarz, Konrad on 8/25/2006 1:57 AM:
> Hi,
> 
> I know that it is kind of late :-), but I would like to suggest an
> alternative/additional mapping of drive letters to the MinGW and Cygwin
> file-system name space.
> 
> The proposed mapping for directory `C:\' is `//./C$/' (or perhaps
> `//./C/').

Sorry, but I don't like this for cygwin (I don't care how msys decides on
the issue, though).  Cygwin already has /cygdrive/c mapping to c:\ in a
default installation, and that is configurable through mount to be
whatever a user wants (even /c).  Cygwin also already has support for
//server/share, and mixing in //./c would make that code path much more
difficult to maintain.

You probably won't get very far with this proposal in cygwin without
actual patches and a LOT more convincing.

- --
Life is short - so eat dessert first!

Eric Blake [EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFE7ulu84KuGfSFAYARAlLKAJ93RP1wysFqN0icYugjY2tOtPm6WwCgndPN
+w0eOK25ljfNfJAyL2+STAQ=
=m7fj
-END PGP SIGNATURE-

--
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: copying and pasting in the terminal window?

[Marko Bozikovic]

Owen Rees wrote:
> -snip-
> In the context of copying and pasting in a window, I find rxvt far
> superior to Console because of the way it handles long lines (as well
> copying/pasting the way X does without requiring that X be running).

As the author of Console, I'd like to know how does rxvt handle long lines
when copying. I might be able to improve Console :-)

Cheers,
-- 
Marko
ICQ: 5990814

I'm not under the alkafluence of inkahol
that some thinkle peep I am.
It's just the drunker I sit here the longer I get.

--
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: copying and pasting in the terminal window?

[Igor Peshansky]

On Fri, 25 Aug 2006, Owen Rees wrote:

> --On 24 August 2006 10:39 -0700 Eric Hanchrow wrote:
>
> > Igor> FWIW, my main gripe with Console is that it doesn't
> > Igor> understand line wrapping, so cutting and pasting a line that
> > Igor> wraps multiple times results in multiple lines.
> >
> > Yup.  And as far as I know, there's no way to tell the console "please
> > save the accumulated scrollback into a file".  But then I don't think
> > rxvt can do that either :-)
>
> You can select all the available scrolled text with both Console and
> rxvt (Console scrolls when you drag off the top/bottom and extends the
> selection, rxvt extends the selection with a right mouse click so you
> can select, scroll, right click).

In Console, you can extend the selection with Shift-left click.

> Once you have copied it all, "cat >somefile" then paste, CR ^D will get
> it into a file. Perhaps not quite as simple as having a 'save' option,
> but not too hard to do.

Even simpler: "cat /dev/clipboard > somefile" (no need to paste).  This
works immediately with Console and rxvt in W11 mode, but may not work in X
until you switch to and from a Windows app (because X has to copy the X
selection to clipboard).

> If you are using rxvt, long lines that wrapped on display will be long
> lines in the file, With Console, there will be line breaks wherever it
> wrapped.

That's exactly the gripe I mentioned above.

> In the context of copying and pasting in a window, I find rxvt far
> superior to Console because of the way it handles long lines (as well
> copying/pasting the way X does without requiring that X be running).

Right.  It also keeps the colors better, whereas Console sometimes fails
to redraw correctly under heavy CPU loads.
Igor
-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED] | [EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_Igor Peshansky, Ph.D. (name changed!)
 |,4-  ) )-,_. ,\ (  `'-'   old name: Igor Pechtchanski
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"

--
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: no message or dialog when a DLL is missing

[Pierre Baillargeon]

Thanks for the information. I will not submit a patch because I suspect 
the current behavior is prefered by the majority: having a dialog pop-up 
 in the middle of scripts is much more catastrophic is most case than 
having a return code, for unattended processing. So I expect the patch 
to be badly received by end users.


--
Pierre Baillargeon
Innobec

--
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: copying and pasting in the terminal window?

[Owen Rees]

--On Friday, August 25, 2006 14:25:00 +0200 Marko Bozikovic wrote:


As the author of Console, I'd like to know how does rxvt handle long lines
when copying. I might be able to improve Console :-)


The trouble with having chosen "Console" as the name of your project is 
that Microsoft refers to the thing you get by default in a standard Windows 
system when you ask for a command prompt as "windows console" if they are 
being explicit, and "console" when being less explicit. This can lead to 
confusion and misunderstandings.


I was referring to Microsoft's "Windows Console" (as it appears in headings 
of various MSDN articles), the thing you get running bash if you start up a 
shell window in a conventional Cygwin installation.


As for rxvt, it's available as a cygwin package if you want to know more 
about it.


--
Owen Rees
Hewlett Packard Laboratories, Bristol, UK


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

Good bye, Cygwinners

[Marcel Telka]

Hi all.

I am no longer working with Windows, so I have no free resources (including
time) to maintain my Cygwin packages. The list (I hope that it is complete) of
my packages follows:

docbook-xml412
docbook-xml42
docbook-xml43
docbook-xml44
docbook-xsl
hexedit
ioperm
stunnel
xmlto

If there is anyone willing to adopt these package, (s)he is welcome. If there
are any questions about some of my old packages or packaging, just ask me.
Please use my private e-mail because I will unsubscribe from Cygwin mailing
lists shortly.

Maybe, the things could change in the near or far future, but now I must say:

Good bye, Cygwinners. Cygwin was really a 'must have' software for me during
working with Windows. Thank you everybody for your work on Cygwin.

-- 
+---+
| Marcel Telka   e-mail:   [EMAIL PROTECTED]  |
|homepage: http://telka.sk/ |
|jabber:   [EMAIL PROTECTED] |
+---+

--
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: copying and pasting in the terminal window?

[Marko Bozikovic]

Owen Rees wrote:
> --On Friday, August 25, 2006 14:25:00 +0200 Marko Bozikovic wrote:
> 
>> As the author of Console, I'd like to know how does rxvt handle long
>> lines
>> when copying. I might be able to improve Console :-)
> 
> The trouble with having chosen "Console" as the name of your project is
> that Microsoft refers to the thing you get by default in a standard
> -snip-

I had a creative moment, what can I say :-)

-- 
Marko
ICQ: 5990814

I'm not under the alkafluence of inkahol
that some thinkle peep I am.
It's just the drunker I sit here the longer I get.

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

[ANNOUNCEMENT] Updated: m4-1.4.6-1

[Eric Blake]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

A new release of m4, 1.4.6-1, is available, replacing 1.4.5-1 as current.

NEWS

This is a new upstream release.  From the NEWS file, the changes since
1.4.5 are listed below.  See also /usr/share/doc/m4-1.4.6/.

You must rebuild from source if you want the experimental changeword
feature enabled, as using it can slow down normal operation, and since it
will disappear from the eventual m4 2.0.

DESCRIPTION
===
m4 is an implementation of the traditional Unix macro processor. It is
mostly SVR4 compatible although it has some extensions (for example,
handling more than 9 positional parameters to macros). GNU m4 also has
built-in functions for including files, running shell commands, doing
arithmetic, etc.

UPDATE
==
To update your installation, click on the "Install Cygwin now" link on the
http://cygwin.com/ web page.  This downloads setup.exe to your system.
Save it and run setup, answer the questions and pick up 'm4' from the
'Interpreters' category.

DOWNLOAD:
=
Note that downloads from sources.redhat.com (aka cygwin.com) aren't
allowed due to bandwidth limitations.  This means that you will need to
find a mirror which has this update, please choose the one nearest to you:
http://cygwin.com/mirrors.html

QUESTIONS:
==
If you want to make a point or ask a question the Cygwin mailing list is
the appropriate place.

- --
Eric Blake
volunteer cygwin m4 maintainer

CYGWIN-ANNOUNCE UNSUBSCRIBE INFO:
=
To unsubscribe to the cygwin-announce mailing list, look at the
"List-Unsubscribe: " tag in the email header of this message.  Send email
to the address specified there.  It will be in the format:

[EMAIL PROTECTED]

If you need more information on unsubscribing, start reading here:

http://sources.redhat.com/lists.html#unsubscribe-simple

Please read *all* of the information on unsubscribing that is available
starting at this URL.

NEWS file extract:
==
Version 1.4.6 - 25 August 2006, by Eric Blake  (CVS version 1.4.5a)

* Fix buffer overruns in regexp and patsubst macros when handed a trailing
  backslash in the replacement text, or when handling \n substitutions
  beyond the number of \(\) groups.
* Fix memory leak in regexp, patsubst, and changeword macros.
* The format macro now understands %F, %g, and %G.
* When loading frozen files, m4 now exits with status 63 if version
  mismatch is detected.
* Fix bugs that occurred when invoked with stdout or stderr closed,
  and detect write failures to stdout or to the target of the
  debugfile macro.  In particular, the syscmd and esyscmd macros can
  no longer interfere with the debug stream or diversions.
* The m4exit macro now converts values outside the range 0-255 to 1.
* It is now an error if a command-line input file ends in the middle of a
  comment, matching the behavior of mid-string and mid-argument
  collection.
* The dnl macro now warns if end of file is encountered instead of a
  newline.
* The error message when end of file is encountered now uses the file and
  line where the dangling construct started, rather than `NONE:0:'.
* The debugmode and __file__ macros, and the -s/--synclines option, now
  show what directory a file was found in when the -I/--include option or
  M4PATH variable had an effect.
* The changequote and changecom macros now work with 8-bit characters, and
  quotes and comments that begin with `(' are properly recognized
  following a word.
* The new macro __program__ is added, which allows the input file to issue
  an error message that resembles messages from m4.  Warning and error
  messages have been reformatted to comply with GNU Coding Standards.
* The errprint, m4wrap, and shift macros are now recognized only with
  arguments.
* The index, substr, translit, regexp, and patsubst macros now produce
  output when given only one argument, but still warn about a missing
  second argument.
* The patsubst macro now reliably finds zero-length matches at the end
  of a string.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFE7xJc84KuGfSFAYARAjX8AJ9kQIP+y3ZO3VLm9lgJz4rgfItnjQCbBMzC
TdakkQHALS3JAjM2/HDaHPM=
=thig
-END PGP SIGNATURE-

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

cygserver blocking on semctl(SETVAL) call

[Ethan Tira-Thompson]

[Slightly modified from version previously sent on cygwin-developers,  
who suggest this is a better forum for discussion]


I've discovered what I believe to be a internal deadlock issue in  
cygserver.


I have a piece of code:
void SemaphoreManager::setValue(semid_t id, int x) const {
semun params;
params.val=x;
cout << "SEMCTL..." << flush;
if(semctl(semid,id,SETVAL,params)<0) {
perror("ERROR: SemaphoreManager::setValue (semctl)");
exit(EXIT_FAILURE);
}
cout << "done" << endl;
}

This is part of a function which gets called a number of times  
throughout the life of the program.  It works just fine up until one  
particular call (with x=0) which reliably causes it to block between  
the two cout's.  Not just my program either -- all IPC is blocked at  
this point.  So bringing up new cygwin windows, running 'ipcs', etc.,  
all hang.  Once I kill any one process in the group that are using  
the semaphore, it seems to jump start things a bit and may run a bit  
more, but usually eventually blocks again until all of my program's  
processes are killed.


My code runs fine under Linux and Mac OS X, it's only now that we're  
nearing release that I'm testing under cygwin and finding something  
has gone wrong in the past 9 months or so -- either something updated  
on your end, or a change in our code that's now tickling an issue.


The kicker to note here -- is there any reason a *SETVAL* operation  
could be blocked???  It should either go through or return an error.   
I'm fairly convinced it's *not* this particular semctl call that's  
causing the block, it just gets hung up because some *other*,  
previous, operation has hung cygserver, and it's that operation  
that's causing the trouble.


One nuisance is that when I run cygserver with -d, it doesn't block  
in the same place -- something about all that debugging output  
changes the race conditions.  In any case, I've attached the  
cygserver output leading up to a block, in hopes it means something  
to you.


Thanks for taking a look -- I'm afraid I'm stumped.  (doesn't help  
gdb only reports '??' for all function calls when I attach to a  
process, so I can't tell what any of my code is doing.  And yes, I do  
have -g enabled)


Our code can be checked out from CVS, but before running you'll need  
to increase the semmns and semmsl parameters as described in step 5:

http://www.cs.cmu.edu/~tekkotsu/cygwin-install.html

After that's set up:
cvs -d :pserver:[EMAIL PROTECTED]:/cvs checkout -P Tekkotsu
cd Tekkotsu;
setenv TEKKOTSU_ROOT `pwd` || export TEKKOTSU_ROOT=`pwd`
cd project
make sim
./sim-ERS7 Speed=0

When launched, the simulator forks into four processes, using IPC to  
communicate between them.  'Speed=0' pauses our simulator so it  
shouldn't be trying to process anything.  When launched, it goes  
through a series of runlevels CONSTRUCTING, STARTING, RUNNING,  
STOPPING, DESTRUCTING, DESTRUCTED.  Passing InitialRunlevel=X on the  
command line will stop in a runlevel other than "running", and then  
you can use the 'runlevel' command within the simulator to advance.   
It reliably gets into the "starting" runlevel, but something about  
the "running" runlevel triggers the problem.  SemaphoreManager (from  
the code displayed above) is found in the root IPC directory.
Beware leaked semaphores sets btw, since this problem also causes the  
signal handler to block when trying to remove the set on being  
killed, you'll need to kill -9 it, and use 'ipcs' to check for any  
leftover sets, and then 'ipcrm' them manually between runs.  
(Actually, I find it easier to just kill/relaunch cygserver itself  
which releases all of the blocked processes and clears leftover  
semaphores at the same time)


-ethan

The following trace corresponds to the 'cygserver -d' activity  
following entering the 'runlevel' command to move from STARTING to  
RUNNING, and the block that occurs in that runlevel.
cygserver: /netrel/src/cygwin-1.5.21-2/winsup/cygserver/process.cc, line 287: 
Try hold(2508)
cygserver: /netrel/src/cygwin-1.5.21-2/winsup/cygserver/process.cc, line 287: 
holding (2508)
cygserver: /netrel/src/cygwin-1.5.21-2/winsup/cygserver/sem.cc, line 81: 
leaving (2508)
cygserver: /netrel/src/cygwin-1.5.21-2/winsup/cygserver/sysv_sem.cc, line 1001: 
call to semop(131072
, 0x22C620, 2)

cygserver: /netrel/src/cygwin-1.5.21-2/winsup/cygserver/sysv_sem.cc, line 1031: 
Try locking mutex se
mid[0] (2508) (hold: 0)
cygserver: /netrel/src/cygwin-1.5.21-2/winsup/cygserver/sysv_sem.cc, line 1031: 
Locked  mutex se
mid[0]/1090 (2508)
cygserver: /netrel/src/cygwin-1.5.21-2/winsup/cygserver/sysv_sem.cc, line 1086: 
semop: semaptr=687FA
0, sem_base=686798, semptr=6867C8, sem[4]=0 : op=0, flag=wait

cygserver: /netrel/src/cygwin-1.5.21-2/winsup/cygserver/sysv_sem.cc, line 1086: 
semop: semaptr=687FA
0, sem_base=686798, semptr=6867C8, sem[4]=0 : op=1, flag=wait

cygserver: /netrel/s

Re: POSIX names for drive letters

[Christopher Faylor]

On Fri, Aug 25, 2006 at 06:13:34AM -0600, Eric Blake wrote:
>According to Schwarz, Konrad on 8/25/2006 1:57 AM:
>>I know that it is kind of late :-), but I would like to suggest an
>>alternative/additional mapping of drive letters to the MinGW and Cygwin
>>file-system name space.
>>
>>The proposed mapping for directory `C:\' is `//./C$/' (or perhaps
>>`//./C/').
>
>Sorry, but I don't like this for cygwin (I don't care how msys decides
>on the issue, though).  Cygwin already has /cygdrive/c mapping to c:\
>in a default installation, and that is configurable through mount to be
>whatever a user wants (even /c).  Cygwin also already has support for
>//server/share, and mixing in //./c would make that code path much more
>difficult to maintain.
>
>You probably won't get very far with this proposal in cygwin without
>actual patches and a LOT more convincing.

Yes.  What he said.

Thanks for putting it so succinctly, Eric.
--
Christopher Faylor  spammer? -> [EMAIL PROTECTED]
Cygwin Co-Project Leader[EMAIL PROTECTED]
TimeSys, Inc.

--
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: POSIX names for drive letters

[mwoehlke]

Schwarz, Konrad wrote:

Hi,

I know that it is kind of late :-), but I would like to suggest an
alternative/additional mapping of drive letters to the MinGW and Cygwin
file-system name space.

The proposed mapping for directory `C:\' is `//./C$/' (or perhaps
`//./C/').

The reasons for this mapping are:
[snip]


So... why exactly do you need this? The only thing I might actually 
support here (keeping in mind Eric's comments and CGF's clear agreement 
with them) would be treating '//./' as a special case of '//127.0.0.1/', 
at which point '//./C$/' is the UNC mapping of the default 'C$' share on 
the local machine. But I still fail to see why that is useful.


Or you could change your mount prefix to '/dev/fs', and have 
'/dev/fs/c', etc, which seems more "natural" and is also what Interix 
uses (so you have compatibility in case you ever use that POS).


--
Matthew
'$ time make world' -> real 5d:14h:37m:5.291s  user 0m:0.000s  sys 
4d:2h:14m:43.712s



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

1.5.20 and 1.5.21 break XEmacs UTF-8 support

[Mirko Streckenbach]

cygcheck.out
Description: output of \"cygcheck -s -v -r\"
--
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/

1.5.20 and 1.5.21 break XEmacs UTF-8 support (error description)

[Mirko Streckenbach]

Hi,

First of all, sorry that there are two posts.

The latest two updates of cygwin.dll make XEmacs crash when loading
its support for UTF-8.

How to reproduce? Start XEmacs (console or x11 does not matter), press
M-x, type "eval-expr" + RETURN, then type "(require 'un-define)" +
RETURN (this is supposed to load utf-8 support into XEmacs). After
that watch XEmacs creash with "Fatal error (11)". It creates a
detailed stack trace, but as it is about 1 MB long, I have not
included it. I can send to anyone interested, of course.

Going back to 1.5.19-4 solves this problem.


Any hints or advice?

Yours,
Mirko

(cygcheck.out installation info attached in the other mail)


--
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.20 and 1.5.21 break XEmacs UTF-8 support

[Eric Blake]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

According to Mirko Streckenbach on 8/25/2006 12:42 PM:
> --
> 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/

Your mailer is horribly broken.  Because it botched the mime types,
Thunderbird displayed it as an empty message.  Also, we ask for cygcheck
output as a text mime type, so that mailers can display it inline; by
sending it application/octet-stream, I have to save it to disk and open it
in an external program to see its contents (sometimes renaming the file
with a .txt extension will help broken mailers give the right mime type).

However, full source to the rescue:

> Hi,
>
> The latest two updates of cygwin.dll make XEmacs crash when loading
> its support for UTF-8.
>
> How to reproduce? Start XEmacs (console or x11 does not matter), press
> M-x, type "eval-expr" + RETURN, then type "(require 'un-define)" +
> RETURN (this is supposed to load utf-8 support into XEmacs). After
> that watch XEmacs creash with "Fatal error (11)". It creates a
> detailed stack trace, but as it is about 1 MB long, I have not
> included it. I can send to anyone interested, of course.
>
> Going back to 1.5.19-4 solves this problem.
>
>
> Any hints or advice?

Besides fixing your mailer?  I'll let the xemacs maintainer take a shot at
it from here.

>
> Yours,
> Mirko

- --
Life is short - so eat dessert first!

Eric Blake [EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFE70hc84KuGfSFAYARAsfbAKCKUhfjmnh9qfk7Skm9ATd2nF+oUgCeK5SU
gXFRVSMZhoaoJ9NNEwaJHAE=
=4s14
-END PGP SIGNATURE-

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

Windows XP network lockup, when using rsync

[Howard Thomson]

Hi all,

I have installed the latest version of Cygwin to a WinXP machine (with 10/100 
Mbps builtin Ethernet) and to an older Win2000 machine (with 10 Mbps CardBus 
i/f) and am working on the rsync source to add Win32 native backup/restore of 
the security info.

*Every* time that I run rsync, both the Cygwin default 2.6.6 version and my 
2.6.9cvs patched version, rsync failes to complete a transfer from WinXP to 
Win2000 and reports that the other end disconnected.

With 100% success rate, WinXP is subsequently unable to: ping, browse 
internet, respond to ping, ipconfig /renew..., in fact all networking fails 
and the machine hangs in attempting to hibernate and mostly hangs in 
attempting to shutdown.

I had had *no* problems, at all, prior to attempting to use rsync !

Has anyone else had similar experiences ?

The sending machine is an Evesham laptop X86_64 running the standard 32-bit 
WinXP Professional, updated to the latest patches from MS as of two days ago 
(which didn't fix anything).

The receiving machine is an ancient Tecra laptop 120MHz 144Mb machine running 
Win2000, which hasn't had any problems (so far).

Cheers,

Howard Thomson

--
"Only two things are infinite, the universe and human stupidity,
and I'm not sure about the former." -- Albert Einstein 


--
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: Windows XP network lockup, when using rsync

[Christopher Faylor]

On Fri, Aug 25, 2006 at 08:15:16PM +0100, Howard Thomson wrote:
>I have installed the latest version of Cygwin to a WinXP machine (with
>10/100 Mbps builtin Ethernet) and to an older Win2000 machine (with 10
>Mbps CardBus i/f) and am working on the rsync source to add Win32
>native backup/restore of the security info.
>
>*Every* time that I run rsync, both the Cygwin default 2.6.6 version
>and my 2.6.9cvs patched version, rsync failes to complete a transfer
>from WinXP to Win2000 and reports that the other end disconnected.
>
>With 100% success rate, WinXP is subsequently unable to: ping, browse
>internet, respond to ping, ipconfig /renew..., in fact all networking
>fails and the machine hangs in attempting to hibernate and mostly hangs
>in attempting to shutdown.
>
>I had had *no* problems, at all, prior to attempting to use rsync !

Regardless of this data point, if you are having this type of problem
there is something wrong with either your Windows installation, the
driver for your network card, or your computer.

This isn't a Cygwin problem.  A user mode program like rsync should not
be able to cause this type of behavior.  If it could, that's an exploit
just waiting to happen.

cgf

--
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: ssh startup failure

[Larry Hall (Cygwin)]

Auteria Wallace Winzer Jr. wrote:

Originally my Windows filesystem was FAT32 before I
converted to NTFS. I re-installed Cygwin 1.5.21-1.
After configuring sshd and starting the service I get
the following error within /var/log/OpenSSH-sshd.log:

[EMAIL PROTECTED] ~
$ cat /var/log/OpenSSH-sshd.log
3877 [main] sshd 19552
fhandler_dev_zero::fixup_mmap_after_fork: requested
0x35 != 0x0 mem alloc base 0x35, state 0x1000,
size 12288, Win32 error 487
16314 [main] sshd 19552 D:\cygwin\usr\sbin\sshd.exe:
*** fatal error - D:\cygwin\usr\sbin\sshd.exe: ***
recreate_mmaps after_fork_failed

On my old laptop I don't have this problem whatsoever.



Get the rebase package, read the README, and run rebaseall in
the prescribed way.

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

--
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: cygserver blocking on semctl(SETVAL) call

[Larry Hall (Cygwin)]

On 08/25/2006, Ethan Tira-Thompson wrote:
Thanks for taking a look -- I'm afraid I'm stumped.  (doesn't help gdb only 
reports '??' for all function calls when I attach to a process, so I can't 
tell what any of my code is doing.  And yes, I do have -g enabled)




You will likely get better results here if you build the cygwin1.dll locally
as debug or download cygwin1.dbg for a snapshot cygwin1.dll.  See


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

--
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: Windows XP network lockup, when using rsync

[Howard Thomson]

Christopher Faylor  cygwin.com> writes: 
 
> >*Every* time that I run rsync, both the Cygwin default 2.6.6 version 
> >and my 2.6.9cvs patched version, rsync failes to complete a transfer 
> >from WinXP to Win2000 and reports that the other end disconnected. 
> > 
> >With 100% success rate, WinXP is subsequently unable to: ping, browse 
> >internet, respond to ping, ipconfig /renew..., in fact all networking 
> >fails and the machine hangs in attempting to hibernate and mostly hangs 
> >in attempting to shutdown. 
> > 
> >I had had *no* problems, at all, prior to attempting to use rsync ! 
>  
> Regardless of this data point, if you are having this type of problem 
> there is something wrong with either your Windows installation, the 
> driver for your network card, or your computer. 
>  
> This isn't a Cygwin problem.  A user mode program like rsync should not 
> be able to cause this type of behavior.  If it could, that's an exploit 
> just waiting to happen. 
 
I agree that it isn't a bug in Cygwin. However the machine, apart from the 
Cygwin download and very little other software (no drivers), is a pristine 
WinXP install as supplied with the machine. I e-mailed this list because I 
hoped someone with a similar experience would be able to point me to a 
solution, Google and MS having failed (so far) to find anything relevant. 
 
 
 


--
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: copying and pasting in the terminal window?

[Gary R. Van Sickle]

> From: G.W. Haywood
> Sent: Friday, August 25, 2006 4:53 AM
> Subject: RE: copying and pasting in the terminal window?
> 
> Hi there,
> 
> 
> On Fri, 25 Aug 2006, Gary R. Van Sickle wrote:
> 
> > ...  The main trick is (or at least used to be) getting 
> your delete, 
> > home, end, etc keys working right, and I can send you my magical 
> > .initrc to take care of that post-haste.
> 
> Please cc me on that one, huh?  Or better, post it to the 
> list, my mailserver might block your ISP.
>

Ask and ye shall receive my good man!  I'm currently using the attached.  Be
sure though to check what gets installed by default - ISTR that at some
point at least some of this got into the distribution.

-- 
Gary R. Van Sickle
  


.inputrc
Description: Binary data
--
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: chmod, chown doesn't work with 1.5.21-1 (FAQ alert)

[Joshua Daniel Franklin]

On 8/24/06, Igor Peshansky wrote:

FWIW, I was going to suggest that you look at the relevant FAQ entry
(), but then I
realized that the entry is horribly out of date, and doesn't mention
filesystem types at all (the only place they are mentioned is the
description of the "ntea" setting in the CYGWIN environment variable:
).  I don't have the
time to create the proper FAQ patch, but Joshua, if you are reading this,
please take note.



Duly noted, I'll write a patch at some point soon.

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

Does gcc on cygwin support thread local storage with __declspec(thread)?

[Wang Yiping]

Dear Readers:

Recently  I am trying to compile mozilla on cygwin, the gcc gives me
such warnings:

../../../dist/include/nspr/md/_winnt.h:507: warning: `thread' attribute directiv
e ignored

Does this mean  it does not support TLS? then how to use Thread-local
storage on cygwin?

Best Regards

Andy

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