* help on compiling perl/ nt with cygwin. gnu c lib missing
@ 1998-12-11 14:39 ` john z
1998-12-12 9:41 ` Michael Hirmke
` (2 more replies)
0 siblings, 3 replies; 222+ messages in thread
From: john z @ 1998-12-11 14:39 UTC (permalink / raw)
To: gnu-win32
im trying to install perl5.05_54 on a brand new nt box. it has a vanilla
setup. b20.1 full was installed and it seemed ok.
when i try the cygwin installation for perl, i get an error that 'gnu c
libary' not found. i modified ld2, and gcc2 and it seemed to pass that test.
can somebody tell me what i am missing. i did NOT install the gnu c library
(thought enough of it came over with full/ egcs.
am i missing some symbols?
(and please dont tell me i should switch to activestate perl). as is just
fine, but i want to use modules not yet supported.
tks
john z.
zephyr@wesell.com.NoJunkPad
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: help on compiling perl/ nt with cygwin. gnu c lib missing
1998-12-11 14:39 ` help on compiling perl/ nt with cygwin. gnu c lib missing john z
@ 1998-12-12 9:41 ` Michael Hirmke
1998-12-13 5:55 ` Peter Moulder
[not found] ` <3.0.5.32.19981213122803.00863b20@pciii>
2 siblings, 0 replies; 222+ messages in thread
From: Michael Hirmke @ 1998-12-12 9:41 UTC (permalink / raw)
To: gnu-win32
Hi John,
>im trying to install perl5.05_54 on a brand new nt box. it has a vanilla
Can't answer your question, but:
5.005_54 is a developers release, not a production release - is that,
what you want ?
AFAIK the latest production release is 5.005_02 (perhaps 03 meanwhile).
[...]
>tks
>john z.
Bye.
Michael.
--
Michael Hirmke | Telefon +49 (911) 557999
Georg-Strobel-Strasse 81 | FAX +49 (911) 557664
90489 Nuernberg | E-Mail mailto:mh@mike.franken.de
| WWW http://aquarius.franken.de/
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: help on compiling perl/ nt with cygwin. gnu c lib missing
1998-12-11 14:39 ` help on compiling perl/ nt with cygwin. gnu c lib missing john z
1998-12-12 9:41 ` Michael Hirmke
@ 1998-12-13 5:55 ` Peter Moulder
[not found] ` <3.0.5.32.19981213122803.00863b20@pciii>
2 siblings, 0 replies; 222+ messages in thread
From: Peter Moulder @ 1998-12-13 5:55 UTC (permalink / raw)
To: john z; +Cc: gnu-win32
I think when I compiled perl, I supplied ,the path of directory
containing libc` in response to one of the configuration questions,
i.e. the default answer did not include this information.
I don't know whether or not that is the solution to your problem.
pjm.
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 222+ messages in thread
[parent not found: <3.0.5.32.19981213122803.00863b20@pciii>]
* Re: help on compiling perl/ nt with cygwin. gnu c lib missing
[not found] ` <3.0.5.32.19981213122803.00863b20@pciii>
@ 1998-12-18 20:36 ` Peter Moulder
0 siblings, 0 replies; 222+ messages in thread
From: Peter Moulder @ 1998-12-18 20:36 UTC (permalink / raw)
To: john z; +Cc: gnu-win32
john z <zephyr@wesell.com> writes:
> tks for the idea. i just tried it and got a ton of messages before
> it hung. and the messages are kinda nasty. so i think maybe
> something else is going on. betcha the cygwin feature was working
> before but got broken. cause on the perl side it makes references
> to i386 instead of ther new i586 labeling.
Oh yes, another thing I did was to create some symlinks to satisfy
the perl configuration scripts.
pjm.
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: OpenGL and glut with B20.1
@ 1999-02-02 5:27 ` Suhaib M. Siddiqi
1999-02-02 5:44 ` Levon Saldamli
1999-02-28 23:02 ` Suhaib M. Siddiqi
0 siblings, 2 replies; 222+ messages in thread
From: Suhaib M. Siddiqi @ 1999-02-02 5:27 UTC (permalink / raw)
To: gnu-win32, Levon Saldamli
Brian Kasper last week sent me a set of Mesa 3.0 libraries for
Cygwin-B-20.
He did a really good job in porting Mesa to Cygwin-B20.
You can find precompiled LessTif 0.87 at
ftp://ftp.lesstif.org/pub/hungry/lesstif/bindir for
Cygnus-B-20. I compiled them. LessTif organization requested to
redistribute them
through LessTif ftp server instead of a third party site. The Cygnus
precompiled version in that
archive is missing libXlt.a and libXlt.dll. If you need Xlt port for
Cygnus-B20, let me know and I will
send it to you. Beware, it is a 1.78 MB big file.
Suhaib
----- Original Message -----
From: Levon Saldamli <levon@lysator.liu.se>
To: <gnu-win32@cygnus.com>
Sent: Monday, February 01, 1999 6:39 PM
Subject: OpenGL and glut with B20.1
>
>I'd like to use OpenGL and glut with cygwin32 B20.1, possibly together
>with lesstif. What OpenGL and glut libraries and include files should
>I use to make it work? I've tried different set of files without
>success, and I feel I didn't find the most update versions (found in
>mailing list archive at cygnus). I'd appreciate some links to
>information and/or download places for this.
>
>Thanks in advance.
>
>--
>/Levon Saldamli
>-
>For help on using this list (especially unsubscribing), send a message
to
>"gnu-win32-request@cygnus.com" with one line of text: "help".
>
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: OpenGL and glut with B20.1
1999-02-02 5:27 ` OpenGL and glut with B20.1 Suhaib M. Siddiqi
@ 1999-02-02 5:44 ` Levon Saldamli
[not found] ` < 7wsocoudi1.fsf@sandra.lysator.liu.se >
1999-02-28 23:02 ` OpenGL and glut with B20.1 Levon Saldamli
1999-02-28 23:02 ` Suhaib M. Siddiqi
1 sibling, 2 replies; 222+ messages in thread
From: Levon Saldamli @ 1999-02-02 5:44 UTC (permalink / raw)
To: gnu-win32; +Cc: Suhaib M. Siddiqi
> Brian Kasper last week sent me a set of Mesa 3.0 libraries for
> Cygwin-B-20.
> He did a really good job in porting Mesa to Cygwin-B20.
Where can I find these libraries?
--
/Levon Saldamli
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: OpenGL and glut with B20.1
1999-02-02 5:27 ` OpenGL and glut with B20.1 Suhaib M. Siddiqi
1999-02-02 5:44 ` Levon Saldamli
@ 1999-02-28 23:02 ` Suhaib M. Siddiqi
1 sibling, 0 replies; 222+ messages in thread
From: Suhaib M. Siddiqi @ 1999-02-28 23:02 UTC (permalink / raw)
To: gnu-win32, Levon Saldamli
Brian Kasper last week sent me a set of Mesa 3.0 libraries for
Cygwin-B-20.
He did a really good job in porting Mesa to Cygwin-B20.
You can find precompiled LessTif 0.87 at
ftp://ftp.lesstif.org/pub/hungry/lesstif/bindir for
Cygnus-B-20. I compiled them. LessTif organization requested to
redistribute them
through LessTif ftp server instead of a third party site. The Cygnus
precompiled version in that
archive is missing libXlt.a and libXlt.dll. If you need Xlt port for
Cygnus-B20, let me know and I will
send it to you. Beware, it is a 1.78 MB big file.
Suhaib
----- Original Message -----
From: Levon Saldamli <levon@lysator.liu.se>
To: <gnu-win32@cygnus.com>
Sent: Monday, February 01, 1999 6:39 PM
Subject: OpenGL and glut with B20.1
>
>I'd like to use OpenGL and glut with cygwin32 B20.1, possibly together
>with lesstif. What OpenGL and glut libraries and include files should
>I use to make it work? I've tried different set of files without
>success, and I feel I didn't find the most update versions (found in
>mailing list archive at cygnus). I'd appreciate some links to
>information and/or download places for this.
>
>Thanks in advance.
>
>--
>/Levon Saldamli
>-
>For help on using this list (especially unsubscribing), send a message
to
>"gnu-win32-request@cygnus.com" with one line of text: "help".
>
^ permalink raw reply [flat|nested] 222+ messages in thread
* First Cygwin Installation
@ 2001-01-04 13:09 ` Hough, Louis F
2001-01-04 13:12 ` DJ Delorie
0 siblings, 1 reply; 222+ messages in thread
From: Hough, Louis F @ 2001-01-04 13:09 UTC (permalink / raw)
To: 'cygwin@cygwin.com'
Cygwin,
Will any version work as a first time install or
do I have to have something else ??
My e-mail is
louhough@home.com
Louis Hough
206-655-6386 (206-416-4138 pager)
MS 4J-06
Louis.Hough@PSS.Boeing.com
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: First Cygwin Installation
2001-01-04 13:09 ` First Cygwin Installation Hough, Louis F
@ 2001-01-04 13:12 ` DJ Delorie
2001-01-04 13:21 ` David M. Karr
0 siblings, 1 reply; 222+ messages in thread
From: DJ Delorie @ 2001-01-04 13:12 UTC (permalink / raw)
To: Louis.Hough; +Cc: cygwin
> Will any version work as a first time install or
> do I have to have something else ??
For a first-time install, go to http://cygwin.com/ and click on the
"Install Cygwin Now" icon. The only choices you should have to make
are (0) that you want to install from the internet, (1) where to
install it on your machine, and (2) whether to use IE5, a direct
connection, or a proxy to access the internet.
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: First Cygwin Installation
2001-01-04 13:12 ` DJ Delorie
@ 2001-01-04 13:21 ` David M. Karr
2001-01-04 13:39 ` Larry Hall (RFK Partners, Inc)
0 siblings, 1 reply; 222+ messages in thread
From: David M. Karr @ 2001-01-04 13:21 UTC (permalink / raw)
To: cygwin
>>>>> "DJ" == DJ Delorie <dj@delorie.com> writes:
>> Will any version work as a first time install or
>> do I have to have something else ??
DJ> For a first-time install, go to http://cygwin.com/ and click on the
DJ> "Install Cygwin Now" icon. The only choices you should have to make
DJ> are (0) that you want to install from the internet, (1) where to
DJ> install it on your machine, and (2) whether to use IE5, a direct
DJ> connection, or a proxy to access the internet.
Note that the "Default text file type" might be important, depending
on what you're using this for. It will default to "Unix", as opposed
to "DOS". If you have non-cygwin programs that expect DOS line
endings, and they might be reading files you would create while using
Cygwin, then they might not work properly if you set it to "Unix".
Just make sure you understand the choice.
--
===================================================================
David M. Karr ; w:(425)487-8312 ; TCSI & Best Consulting
dkarr@tcsi.com ; Java/Unix/XML/C++/X ; BrainBench CJ12P (#12004)
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: First Cygwin Installation
2001-01-04 13:21 ` David M. Karr
@ 2001-01-04 13:39 ` Larry Hall (RFK Partners, Inc)
2001-01-04 13:55 ` David M. Karr
0 siblings, 1 reply; 222+ messages in thread
From: Larry Hall (RFK Partners, Inc) @ 2001-01-04 13:39 UTC (permalink / raw)
To: David M. Karr, cygwin
At 04:19 PM 1/4/2001, David M. Karr wrote:
> >>>>> "DJ" == DJ Delorie <dj@delorie.com> writes:
>
> >> Will any version work as a first time install or
> >> do I have to have something else ??
>
> DJ> For a first-time install, go to http://cygwin.com/ and click on the
> DJ> "Install Cygwin Now" icon. The only choices you should have to make
> DJ> are (0) that you want to install from the internet, (1) where to
> DJ> install it on your machine, and (2) whether to use IE5, a direct
> DJ> connection, or a proxy to access the internet.
>
>Note that the "Default text file type" might be important, depending
>on what you're using this for. It will default to "Unix", as opposed
>to "DOS". If you have non-cygwin programs that expect DOS line
>endings, and they might be reading files you would create while using
>Cygwin, then they might not work properly if you set it to "Unix".
>Just make sure you understand the choice.
>
>--
>===================================================================
>David M. Karr ; w:(425)487-8312 ; TCSI & Best Consulting
>dkarr@tcsi.com ; Java/Unix/XML/C++/X ; BrainBench CJ12P (#12004)
An example list of applications that have some trouble reading files with
only UNIX line endings (newline only) include notepad, just about any old
DOS (and I mean DOS, not Windows) program, and VC++ if the file in question
will also be edited by the class wizard. With the exception of the VC++
issue, which is rather obscure, there's a solution to each of the other
problems (i.e. replace them with programs that understand UNIX style line
endings - there's lots of good alternatives here). Every other Windows
program I've used can read UNIX line endings just fine, because the underlying
Win32 API call for accessing files supports reading newline-only line endings.
I'm sure there are some other utility programs out there that still trip over
UNIX line endings too but in general, this is pretty rare.
Larry Hall lhall@rfk.com
RFK Partners, Inc. http://www.rfk.com
118 Washington Street (508) 893-9779 - RFK Office
Holliston, MA 01746 (508) 893-9889 - FAX
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: First Cygwin Installation
2001-01-04 13:39 ` Larry Hall (RFK Partners, Inc)
@ 2001-01-04 13:55 ` David M. Karr
2001-01-04 14:14 ` Larry Hall (RFK Partners, Inc)
2001-01-04 14:41 ` Earnie Boyd
0 siblings, 2 replies; 222+ messages in thread
From: David M. Karr @ 2001-01-04 13:55 UTC (permalink / raw)
To: cygwin
>>>>> "Larry" == Larry Hall (RFK Partners, Inc) <lhall@rfk.com> writes:
Larry> At 04:19 PM 1/4/2001, David M. Karr wrote:
>> >>>>> "DJ" == DJ Delorie <dj@delorie.com> writes:
>>
>> >> Will any version work as a first time install or
>> >> do I have to have something else ??
>>
DJ> For a first-time install, go to http://cygwin.com/ and click on the
DJ> "Install Cygwin Now" icon. The only choices you should have to make
DJ> are (0) that you want to install from the internet, (1) where to
DJ> install it on your machine, and (2) whether to use IE5, a direct
DJ> connection, or a proxy to access the internet.
>>
>> Note that the "Default text file type" might be important, depending
>> on what you're using this for. It will default to "Unix", as opposed
>> to "DOS". If you have non-cygwin programs that expect DOS line
>> endings, and they might be reading files you would create while using
>> Cygwin, then they might not work properly if you set it to "Unix".
>> Just make sure you understand the choice.
Larry> An example list of applications that have some trouble reading files with
Larry> only UNIX line endings (newline only) include notepad, just about any old
Larry> DOS (and I mean DOS, not Windows) program, and VC++ if the file in question
Larry> will also be edited by the class wizard. With the exception of the VC++
Larry> issue, which is rather obscure, there's a solution to each of the other
Larry> problems (i.e. replace them with programs that understand UNIX style line
Larry> endings - there's lots of good alternatives here). Every other Windows
Larry> program I've used can read UNIX line endings just fine, because the underlying
Larry> Win32 API call for accessing files supports reading newline-only line endings.
Larry> I'm sure there are some other utility programs out there that still trip over
Larry> UNIX line endings too but in general, this is pretty rare.
Unless I'm misunderstanding something, the public domain Korn shell is
another application that can't deal with Unix line endings. For some
people, this is more likely to be an issue than notepad or vc++.
--
===================================================================
David M. Karr ; w:(425)487-8312 ; TCSI & Best Consulting
dkarr@tcsi.com ; Java/Unix/XML/C++/X ; BrainBench CJ12P (#12004)
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: First Cygwin Installation
2001-01-04 13:55 ` David M. Karr
@ 2001-01-04 14:14 ` Larry Hall (RFK Partners, Inc)
2001-01-04 14:41 ` Earnie Boyd
1 sibling, 0 replies; 222+ messages in thread
From: Larry Hall (RFK Partners, Inc) @ 2001-01-04 14:14 UTC (permalink / raw)
To: David M. Karr, cygwin
At 04:52 PM 1/4/2001, David M. Karr wrote:
> Larry> endings - there's lots of good alternatives here). Every other Windows
> Larry> program I've used can read UNIX line endings just fine, because the underlying
> Larry> Win32 API call for accessing files supports reading newline-only line endings.
> Larry> I'm sure there are some other utility programs out there that still trip over
> Larry> UNIX line endings too but in general, this is pretty rare.
>
>Unless I'm misunderstanding something, the public domain Korn shell is
>another application that can't deal with Unix line endings. For some
>people, this is more likely to be an issue than notepad or vc++.
Right. It depends on the utilities you use, how old they are, and whether
they make use of the Win32 API for opening text files or not. There are
some utilities out there which are poorly ported to Windows. Other than
utilities like these and the utilities I mentioned which are part of the
utilities that come with Windows (or its development environment), every
other Windows program that I've seen can read a text file with UNIX line
endings, even edlin!;-) (Yuck, who wants that!;-)) However, if you're
concerned about some obscure program you know you need to interact with
files created and manipulated with Cywgin tools, pick "DOS" files at Cygwin
install time. If you don't have reason to fear some utility you're using
won't work with Cygwin created/manipulated files, stick with the defaults.
Defaults exist because they generally give the best results for the majority.
YMMV!;-)
Larry Hall lhall@rfk.com
RFK Partners, Inc. http://www.rfk.com
118 Washington Street (508) 893-9779 - RFK Office
Holliston, MA 01746 (508) 893-9889 - FAX
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: First Cygwin Installation
2001-01-04 13:55 ` David M. Karr
2001-01-04 14:14 ` Larry Hall (RFK Partners, Inc)
@ 2001-01-04 14:41 ` Earnie Boyd
2001-01-04 14:55 ` David M. Karr
1 sibling, 1 reply; 222+ messages in thread
From: Earnie Boyd @ 2001-01-04 14:41 UTC (permalink / raw)
To: David M. Karr; +Cc: cygwin
"David M. Karr" wrote:
>
> Unless I'm misunderstanding something, the public domain Korn shell is
> another application that can't deal with Unix line endings. For some
> people, this is more likely to be an issue than notepad or vc++.
>
A Cygwin build of pdksh produces a ksh which understands UNIX file
endings. You may need to use the -mno-win32 switch though.
Cheers,
Earnie.
__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: First Cygwin Installation
2001-01-04 14:41 ` Earnie Boyd
@ 2001-01-04 14:55 ` David M. Karr
2001-01-04 15:10 ` Christopher Faylor
0 siblings, 1 reply; 222+ messages in thread
From: David M. Karr @ 2001-01-04 14:55 UTC (permalink / raw)
To: cygwin
>>>>> "Earnie" == Earnie Boyd <earnie_boyd@yahoo.com> writes:
Earnie> "David M. Karr" wrote:
>>
>> Unless I'm misunderstanding something, the public domain Korn shell is
>> another application that can't deal with Unix line endings. For some
>> people, this is more likely to be an issue than notepad or vc++.
Earnie> A Cygwin build of pdksh produces a ksh which understands UNIX file
Earnie> endings. You may need to use the -mno-win32 switch though.
The one I'm using is built with Cygwin, so perhaps the "-mno-win32"
option is needed. I don't believe I used that switch when I built it.
I'll keep this in mind.
--
===================================================================
David M. Karr ; w:(425)487-8312 ; TCSI & Best Consulting
dkarr@tcsi.com ; Java/Unix/XML/C++/X ; BrainBench CJ12P (#12004)
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: First Cygwin Installation
2001-01-04 14:55 ` David M. Karr
@ 2001-01-04 15:10 ` Christopher Faylor
0 siblings, 0 replies; 222+ messages in thread
From: Christopher Faylor @ 2001-01-04 15:10 UTC (permalink / raw)
To: cygwin
On Thu, Jan 04, 2001 at 02:52:58PM -0800, David M. Karr wrote:
>>>>>> "Earnie" == Earnie Boyd <earnie_boyd@yahoo.com> writes:
> Earnie> "David M. Karr" wrote:
> >>
> >> Unless I'm misunderstanding something, the public domain Korn shell is
> >> another application that can't deal with Unix line endings. For some
> >> people, this is more likely to be an issue than notepad or vc++.
>
> Earnie> A Cygwin build of pdksh produces a ksh which understands UNIX file
> Earnie> endings. You may need to use the -mno-win32 switch though.
>
>The one I'm using is built with Cygwin, so perhaps the "-mno-win32"
>option is needed. I don't believe I used that switch when I built it.
>I'll keep this in mind.
It probably needs to be compiled with -mno-win32 and linked with
/usr/lib/textmode.o .
cgf
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Drive with cygwin moved from "E:" to "D:", how to fix?
@ 2001-01-05 12:52 ` David M. Karr
2001-01-05 13:00 ` DJ Delorie
` (2 more replies)
0 siblings, 3 replies; 222+ messages in thread
From: David M. Karr @ 2001-01-05 12:52 UTC (permalink / raw)
To: cygwin
My colleague got a PC which was originally configured with the drive
with most of his work (including the cygwin installation) being "E:"
(the CD was "D:"). We realized it needed to be on "D:" to easily work
with some scripts we have. We had that done, but now I see that
"mount" still thinks that Cygwin is installed on drive "E:". This
causes some odd symptoms, although many things still work. What is
the easiest way to reset Cygwin to know it's installed on drive "D:"?
--
===================================================================
David M. Karr ; w:(425)487-8312 ; TCSI & Best Consulting
dkarr@tcsi.com ; Java/Unix/XML/C++/X ; BrainBench CJ12P (#12004)
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: Drive with cygwin moved from "E:" to "D:", how to fix?
2001-01-05 12:52 ` Drive with cygwin moved from "E:" to "D:", how to fix? David M. Karr
@ 2001-01-05 13:00 ` DJ Delorie
2001-01-05 13:40 ` David M. Karr
2001-01-05 13:50 ` Gerrit P. Haase
2001-01-06 11:30 ` Quick setup script "taxidermy.pl" Soren Andersen
2 siblings, 1 reply; 222+ messages in thread
From: DJ Delorie @ 2001-01-05 13:00 UTC (permalink / raw)
To: dkarr; +Cc: cygwin
> causes some odd symptoms, although many things still work. What is
> the easiest way to reset Cygwin to know it's installed on drive "D:"?
Just remount all the E: mounts to be D:, either with umount/mount or
with mount -f
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: Drive with cygwin moved from "E:" to "D:", how to fix?
2001-01-05 13:00 ` DJ Delorie
@ 2001-01-05 13:40 ` David M. Karr
2001-01-05 13:46 ` Larry Hall (RFK Partners, Inc)
0 siblings, 1 reply; 222+ messages in thread
From: David M. Karr @ 2001-01-05 13:40 UTC (permalink / raw)
To: cygwin
>>>>> "DJ" == DJ Delorie <dj@delorie.com> writes:
>> causes some odd symptoms, although many things still work. What is
>> the easiest way to reset Cygwin to know it's installed on drive "D:"?
DJ> Just remount all the E: mounts to be D:, either with umount/mount or
DJ> with mount -f
Ok, after fiddling with this for a while, I finally got his new mount
table to look the same, except the "e:"s changed to "d:". That looks
correct.
I see two odd symptoms on this new PC, however, which are probably
related. On my PC, when I do "ls /usr", it gives me a valid listing
of what's in "d:/cygwin/usr". On his PC, when I do "ls /usr", it says
"No such file or directory". When I list "/usr/bin" on my PC, it also
lists fine. When I list "/usr/bin" on his PC, it mostly is fine,
except it says "ls: ..: No such file or directory". What could be the
cause of this?
--
===================================================================
David M. Karr ; w:(425)487-8312 ; TCSI & Best Consulting
dkarr@tcsi.com ; Java/Unix/XML/C++/X ; BrainBench CJ12P (#12004)
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: Drive with cygwin moved from "E:" to "D:", how to fix?
2001-01-05 13:40 ` David M. Karr
@ 2001-01-05 13:46 ` Larry Hall (RFK Partners, Inc)
2001-01-05 14:04 ` David M. Karr
0 siblings, 1 reply; 222+ messages in thread
From: Larry Hall (RFK Partners, Inc) @ 2001-01-05 13:46 UTC (permalink / raw)
To: David M. Karr, cygwin
At 04:38 PM 1/5/2001, David M. Karr wrote:
> >>>>> "DJ" == DJ Delorie <dj@delorie.com> writes:
>
> >> causes some odd symptoms, although many things still work. What is
> >> the easiest way to reset Cygwin to know it's installed on drive "D:"?
>
> DJ> Just remount all the E: mounts to be D:, either with umount/mount or
> DJ> with mount -f
>
>Ok, after fiddling with this for a while, I finally got his new mount
>table to look the same, except the "e:"s changed to "d:". That looks
>correct.
>
>I see two odd symptoms on this new PC, however, which are probably
>related. On my PC, when I do "ls /usr", it gives me a valid listing
>of what's in "d:/cygwin/usr". On his PC, when I do "ls /usr", it says
>"No such file or directory". When I list "/usr/bin" on my PC, it also
>lists fine. When I list "/usr/bin" on his PC, it mostly is fine,
>except it says "ls: ..: No such file or directory". What could be the
>cause of this?
Hard to tell. Permissions? cygcheck -s -r -v might help...
Larry Hall lhall@rfk.com
RFK Partners, Inc. http://www.rfk.com
118 Washington Street (508) 893-9779 - RFK Office
Holliston, MA 01746 (508) 893-9889 - FAX
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: Drive with cygwin moved from "E:" to "D:", how to fix?
2001-01-05 13:46 ` Larry Hall (RFK Partners, Inc)
@ 2001-01-05 14:04 ` David M. Karr
0 siblings, 0 replies; 222+ messages in thread
From: David M. Karr @ 2001-01-05 14:04 UTC (permalink / raw)
To: cygwin
>>>>> "Larry" == Larry Hall (RFK Partners, Inc) <lhall@rfk.com> writes:
Larry> At 04:38 PM 1/5/2001, David M. Karr wrote:
>> >>>>> "DJ" == DJ Delorie <dj@delorie.com> writes:
>>
>> >> causes some odd symptoms, although many things still work. What is
>> >> the easiest way to reset Cygwin to know it's installed on drive "D:"?
>>
DJ> Just remount all the E: mounts to be D:, either with umount/mount or
DJ> with mount -f
>>
>> Ok, after fiddling with this for a while, I finally got his new mount
>> table to look the same, except the "e:"s changed to "d:". That looks
>> correct.
>>
>> I see two odd symptoms on this new PC, however, which are probably
>> related. On my PC, when I do "ls /usr", it gives me a valid listing
>> of what's in "d:/cygwin/usr". On his PC, when I do "ls /usr", it says
>> "No such file or directory". When I list "/usr/bin" on my PC, it also
>> lists fine. When I list "/usr/bin" on his PC, it mostly is fine,
>> except it says "ls: ..: No such file or directory". What could be the
>> cause of this?
Larry> Hard to tell. Permissions? cygcheck -s -r -v might help...
Ah. I figured it out. You probably would have seen it if I had
included the new mount table, which wasn't EXACTLY correct. The mount
for "/" should have been "d:\cygwin", but I had it as "d:\". Once I
redid that mount, I got "/usr" back.
Thanks again.
--
===================================================================
David M. Karr ; w:(425)487-8312 ; TCSI & Best Consulting
dkarr@tcsi.com ; Java/Unix/XML/C++/X ; BrainBench CJ12P (#12004)
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: Drive with cygwin moved from "E:" to "D:", how to fix?
2001-01-05 12:52 ` Drive with cygwin moved from "E:" to "D:", how to fix? David M. Karr
2001-01-05 13:00 ` DJ Delorie
@ 2001-01-05 13:50 ` Gerrit P. Haase
2001-01-06 11:30 ` Quick setup script "taxidermy.pl" Soren Andersen
2 siblings, 0 replies; 222+ messages in thread
From: Gerrit P. Haase @ 2001-01-05 13:50 UTC (permalink / raw)
To: David M. Karr; +Cc: cygwin
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
<5 Jan 2001, 12:49 Uhr wars, als David M. Karr folgendes schrub:>
< Drive with cygwin moved from "E:" t >
> My colleague got a PC which was originally configured with the drive
> with most of his work (including the cygwin installation) being "E:"
> (the CD was "D:"). We realized it needed to be on "D:" to easily work
> with some scripts we have. We had that done, but now I see that
> "mount" still thinks that Cygwin is installed on drive "E:". This
> causes some odd symptoms, although many things still work. What is
> the easiest way to reset Cygwin to know it's installed on drive "D:"?
Change the entries in windows registry by hand.
or:
delete /etc/setup/installed.db
delete setup.ini
run setup again, it will install all new, at the end of setup, when it
asks if there to make a link on the desktop and add to start menu,
choose both, then setup should update the registry also.
-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8 -- QDPGP 2.61c
Comment: =^..^=
iQA/AwUBOlY0BzBeUmEooFE3EQK4sQCgj/dwVhUS2szXyHVQ4aftUh2p/AgAoNLS
0L6easogbePwv5T0JdWkEHRr
=umYR
-----END PGP SIGNATURE-----
--
=^..^=
Gerrit Peter Haase
ID: 0x28A05137
FP: 875C 745E 01CF 8A34 2767 BE39 305E 5261 28A0 5137
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Quick setup script "taxidermy.pl"
2001-01-05 12:52 ` Drive with cygwin moved from "E:" to "D:", how to fix? David M. Karr
2001-01-05 13:00 ` DJ Delorie
2001-01-05 13:50 ` Gerrit P. Haase
@ 2001-01-06 11:30 ` Soren Andersen
2 siblings, 0 replies; 222+ messages in thread
From: Soren Andersen @ 2001-01-06 11:30 UTC (permalink / raw)
To: cygwin
[-- Attachment #1: Type: text/plain, Size: 2079 bytes --]
Hello,
I spent quite a bit of the recent holiday season setting up the latest Cygwin
on several systems (one Win98, one Win95, one WinNT) since it is much
more fun to work with now, that so much great effort has resulted in fewer
bugs. Playing (*laziness*).
I noticed that I wanted to have a fast way to just mount every logical drive
on each system to it's appropriate POSIX mount point ('X:' to '/x') and
that, being the incredibly *impatient* hacker I am, I disliked the repetitious
nature of that task when done manually.
Since I tend to have Perl installed on every system I can get my hands on
for even a few moments (*hubris*), I cooked up a little Perl script to make
this automatic. What it doesn't yet do is check for existing mounts and
`umount' them before re-mounting anything (or skip them entirely). That's
a future To-Do refinement. This is just a rough script but I thought maybe
somebody would want to use it especially on a brand-new Cygwin
installation.
One problem, however: the script uses a Perl module that isn't standard:
Win32::API. It's on CPAN and at http://dada.perl.it/#api (on that site is a
PPM package to make it an easy install to ActivePerl -- *laziness*). But
when I ran the script from Cygwin bash the perl process faulted (memory
access violation I think). So, *don't run it in bash* but rather from cmd.exe
(or command.com if you must use that brain-damaged shell*). I think it
likely that a Win32::API compiled for a Cygwin Perl might not have this
problem, but I don't know quite enough of these matters for that to be
more than a speculation at this time. As a matter of fact, I would love to
know if anyone else gets Win32::API -- a really powerful module to access
arbitrary Win32 API calls from system DLLs -- built from source using
Cygwin or MinGW.
I have attached the script to this message, since it is relative short.
Best,
soren andersen
* When you aren't using Cygwin.
P.S. "Why `taxidermy.pl'?" Aww come ON! "mounting"(as in hunting
trophies or monster trout) -> taxidermy, get it?
[-- Attachment #2: taxidermy.pl --]
[-- Type: text/plain, Size: 1796 bytes --]
#!perl -w
# Perl program Copyright (c)2001 Soren Andersen
# e-mail: <libertador@flashmail.com>
# Licensing: Perl Artistic License.
# L/M 1/6/01 4:09 AM
# requires Cygwin 1.1 or later, maybe -- has not been
# tested on earlier Cygwin versions. `mount' and `cygpath'
# must be in your PATH or fully qualified by hand-editing
# this script.
use Win32::API;
use Getopt::Std;
use strict;
use vars qw[ $opt_n $opt_f $opt_t $srt ];
sub DrivesInUse;
# ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
# Options:
# -n dry-run only
# -f mount floppy drives too
# -t just see existing mount points and exit
getopts( 'nft' ); $srt = 0;
# ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
if ($opt_t) {
my $rcd = system("mount");
exit 0;
}
my $floppies = ($opt_f)? '0' : '[a-b]';
my $cygprfx = join q[], grep( /\/[a-z]+/i,
`mount --show-cygdrive-prefixes` );
chomp $cygprfx;
$cygprfx =~s@^(/[a-z]+).+@$1@;
my $cygdrive = `cygpath -paw $cygprfx`;
chomp $cygdrive;
( $cygdrive =~s@^([A-Z]) \: .*@$1@xi ) or die qq[Careful, need good `cygdrive'.\n];
for (DrivesInUse()) {
next if /(?:$cygdrive | $floppies)/xi;
printf(qq[ %1.3s: mounting to %2.4s\n], $_, q[/]. lc);
( $srt = system( "mount -b -s -f", $_ .":","/". lc ) ) unless $opt_n;
warn qq[\n Trouble making the mounted drive with $_ - ] .
qq[ret code not zero: $srt\n $!] if $srt;
}
# from "Win32::DriveInfo.pm ver 0.03" by Mike Blazer
#===========================
sub DrivesInUse {
#===========================
no strict 'subs';
my (@dr, $i);
my $h = new Win32::API("kernel32", "GetLogicalDrives", [], N);
return undef unless $h =~/Win32::API/i;
my $bitmask = $h->Call();
for $i(0..25) {
push (@dr, (A..Z)[$i]) if $bitmask & 2**$i;
}
return @dr;
}
^ permalink raw reply [flat|nested] 222+ messages in thread
* NTEmacs shell/CygWin: should control-C work?
@ 2001-01-11 14:23 ` Daniel Barclay
2001-01-11 15:00 ` David M. Karr
0 siblings, 1 reply; 222+ messages in thread
From: Daniel Barclay @ 2001-01-11 14:23 UTC (permalink / raw)
To: cygwin
If I've missed this in the FAQ, user's manual, or (poorly searchable)
archives, please point me to what I've missed.
In a shell buffer in NTEmacs configured per the shell-setup instructions
in the CygWin FAQ at http://sources.redhat.com/cygwin/faq/faq.html#SEC5 ,
control-C doesn't seem to work.
That is, typing two control-C's in Emacs (to send a control-C to bash)
doesn't kill a long-running command (e.g., like "du /" or "sleep 10").
Emacs does seem to flash the window title bar, but I can't tell what it's
trying to indicate. Does this seem to be an NTEmacs/CygWin interaction
problem, or just an NTEmacs problem (not for the CygWin list)?
Is control-C still supported in CygWin and between NTEmacs and CygWin? (I
just upgraded from CygWin B20 (or so), and not yet used to how things work
now.)
Thanks,
Daniel
--
Daniel Barclay
Digital Focus
Daniel.Barclay@digitalfocus.com
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: NTEmacs shell/CygWin: should control-C work?
2001-01-11 14:23 ` NTEmacs shell/CygWin: should control-C work? Daniel Barclay
@ 2001-01-11 15:00 ` David M. Karr
2001-01-12 11:48 ` Daniel Barclay
0 siblings, 1 reply; 222+ messages in thread
From: David M. Karr @ 2001-01-11 15:00 UTC (permalink / raw)
To: cygwin
>>>>> "Daniel" == Daniel Barclay <Daniel.Barclay@digitalfocus.com> writes:
Daniel> If I've missed this in the FAQ, user's manual, or (poorly searchable)
Daniel> archives, please point me to what I've missed.
Daniel> In a shell buffer in NTEmacs configured per the shell-setup instructions
Daniel> in the CygWin FAQ at http://sources.redhat.com/cygwin/faq/faq.html#SEC5 ,
Daniel> control-C doesn't seem to work.
Daniel> That is, typing two control-C's in Emacs (to send a control-C to bash)
Daniel> doesn't kill a long-running command (e.g., like "du /" or "sleep 10").
Daniel> Emacs does seem to flash the window title bar, but I can't tell what it's
Daniel> trying to indicate. Does this seem to be an NTEmacs/CygWin interaction
Daniel> problem, or just an NTEmacs problem (not for the CygWin list)?
Daniel> Is control-C still supported in CygWin and between NTEmacs and CygWin? (I
Daniel> just upgraded from CygWin B20 (or so), and not yet used to how things work
Daniel> now.)
This bites me several times a day. It is a known problem, but I don't
know what the status on a fix is. I will be very glad to see it.
--
===================================================================
David M. Karr ; w:(425)487-8312 ; TCSI & Best Consulting
dkarr@tcsi.com ; Java/Unix/XML/C++/X ; BrainBench CJ12P (#12004)
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: NTEmacs shell/CygWin: should control-C work?
2001-01-11 15:00 ` David M. Karr
@ 2001-01-12 11:48 ` Daniel Barclay
2001-01-12 11:54 ` David M. Karr
2001-01-12 13:26 ` Ehud Karni
0 siblings, 2 replies; 222+ messages in thread
From: Daniel Barclay @ 2001-01-12 11:48 UTC (permalink / raw)
To: David M. Karr; +Cc: cygwin
"David M. Karr" wrote:
>
> >>>>> "Daniel" == Daniel Barclay <Daniel.Barclay@digitalfocus.com> writes:
>
...>
> Daniel> In a shell buffer in NTEmacs configured per the shell-setup instructions
> Daniel> in the CygWin FAQ at http://sources.redhat.com/cygwin/faq/faq.html#SEC5 ,
> Daniel> control-C doesn't seem to work.
...
> This bites me several times a day. It is a known problem...
Do you mean it's a known problem that crops up (for some people), or that
it simply doesn't work at all (for anyone combining Emacs and CygWin)?
Thanks,
Daniel
--
Daniel Barclay
Digital Focus
Daniel.Barclay@digitalfocus.com
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: NTEmacs shell/CygWin: should control-C work?
2001-01-12 11:48 ` Daniel Barclay
@ 2001-01-12 11:54 ` David M. Karr
2001-01-12 12:30 ` Larry Hall (RFK Partners, Inc)
2001-01-12 13:06 ` Daniel Barclay
2001-01-12 13:26 ` Ehud Karni
1 sibling, 2 replies; 222+ messages in thread
From: David M. Karr @ 2001-01-12 11:54 UTC (permalink / raw)
To: cygwin
>>>>> "Daniel" == Daniel Barclay <Daniel.Barclay@digitalfocus.com> writes:
Daniel> "David M. Karr" wrote:
>>
>> >>>>> "Daniel" == Daniel Barclay <Daniel.Barclay@digitalfocus.com> writes:
>>
...>
Daniel> In a shell buffer in NTEmacs configured per the shell-setup instructions
Daniel> in the CygWin FAQ at http://sources.redhat.com/cygwin/faq/faq.html#SEC5 ,
Daniel> control-C doesn't seem to work.
Daniel> ...
>> This bites me several times a day. It is a known problem...
Daniel> Do you mean it's a known problem that crops up (for some people), or that
Daniel> it simply doesn't work at all (for anyone combining Emacs and CygWin)?
I don't know the full answer to that. For me, certain shell processes
will die with ^C, some will not. I can kill "java", but I can't kill
"tail -f" or "perl" (I have to use Task Manager). I have seen other
people report this.
--
===================================================================
David M. Karr ; w:(425)487-8312 ; TCSI & Best Consulting
dkarr@tcsi.com ; Java/Unix/XML/C++/X ; BrainBench CJ12P (#12004)
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: NTEmacs shell/CygWin: should control-C work?
2001-01-12 11:54 ` David M. Karr
@ 2001-01-12 12:30 ` Larry Hall (RFK Partners, Inc)
2001-01-12 12:43 ` David M. Karr
2001-01-12 13:06 ` Daniel Barclay
1 sibling, 1 reply; 222+ messages in thread
From: Larry Hall (RFK Partners, Inc) @ 2001-01-12 12:30 UTC (permalink / raw)
To: David M. Karr, cygwin
At 02:51 PM 1/12/2001, David M. Karr wrote:
> >>>>> "Daniel" == Daniel Barclay <Daniel.Barclay@digitalfocus.com> writes:
> Daniel> "David M. Karr" wrote:
> >>
> >> >>>>> "Daniel" == Daniel Barclay <Daniel.Barclay@digitalfocus.com> writes:
> >>
> ...>
> Daniel> In a shell buffer in NTEmacs configured per the shell-setup instructions
> Daniel> in the CygWin FAQ at http://sources.redhat.com/cygwin/faq/faq.html#SEC5 ,
> Daniel> control-C doesn't seem to work.
> Daniel> ...
> >> This bites me several times a day. It is a known problem...
>
> Daniel> Do you mean it's a known problem that crops up (for some people), or that
> Daniel> it simply doesn't work at all (for anyone combining Emacs and CygWin)?
>
>I don't know the full answer to that. For me, certain shell processes
>will die with ^C, some will not. I can kill "java", but I can't kill
>"tail -f" or "perl" (I have to use Task Manager). I have seen other
>people report this.
Recently? Daniel's was the first report of this I've heard in months at
least (longer than that most likely but I tend to be conservative when it
comes to my memory). I might be wrong but I don't think this is a known
problem and its certainly something that I don't see.
Larry Hall lhall@rfk.com
RFK Partners, Inc. http://www.rfk.com
118 Washington Street (508) 893-9779 - RFK Office
Holliston, MA 01746 (508) 893-9889 - FAX
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: NTEmacs shell/CygWin: should control-C work?
2001-01-12 12:30 ` Larry Hall (RFK Partners, Inc)
@ 2001-01-12 12:43 ` David M. Karr
2001-01-12 13:12 ` Daniel Barclay
2001-01-12 13:13 ` Larry Hall (RFK Partners, Inc)
0 siblings, 2 replies; 222+ messages in thread
From: David M. Karr @ 2001-01-12 12:43 UTC (permalink / raw)
To: cygwin
>>>>> "Larry" == Larry Hall (RFK Partners, Inc) <lhall@rfk.com> writes:
Larry> At 02:51 PM 1/12/2001, David M. Karr wrote:
>> >>>>> "Daniel" == Daniel Barclay <Daniel.Barclay@digitalfocus.com> writes:
Daniel> "David M. Karr" wrote:
>> >>
>> >> >>>>> "Daniel" == Daniel Barclay <Daniel.Barclay@digitalfocus.com> writes:
>> >>
...>
Daniel> In a shell buffer in NTEmacs configured per the shell-setup instructions
Daniel> in the CygWin FAQ at http://sources.redhat.com/cygwin/faq/faq.html#SEC5 ,
Daniel> control-C doesn't seem to work.
Daniel> ...
>> >> This bites me several times a day. It is a known problem...
>>
Daniel> Do you mean it's a known problem that crops up (for some people), or that
Daniel> it simply doesn't work at all (for anyone combining Emacs and CygWin)?
>>
>> I don't know the full answer to that. For me, certain shell processes
>> will die with ^C, some will not. I can kill "java", but I can't kill
>> "tail -f" or "perl" (I have to use Task Manager). I have seen other
>> people report this.
Larry> Recently? Daniel's was the first report of this I've heard in months at
Larry> least (longer than that most likely but I tend to be conservative when it
Larry> comes to my memory). I might be wrong but I don't think this is a known
Larry> problem and its certainly something that I don't see.
Earnie Boyd indicated on 9/26 it was "fixed in snapshots", but I've
never seen any mention of a released fix for it. I recently upgraded
my cygwin (1-2 weeks ago), so if the fix was there, I should have it
(but I don't).
--
===================================================================
David M. Karr ; w:(425)487-8312 ; TCSI & Best Consulting
dkarr@tcsi.com ; Java/Unix/XML/C++/X ; BrainBench CJ12P (#12004)
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: NTEmacs shell/CygWin: should control-C work?
2001-01-12 12:43 ` David M. Karr
@ 2001-01-12 13:12 ` Daniel Barclay
2001-01-12 13:13 ` Larry Hall (RFK Partners, Inc)
1 sibling, 0 replies; 222+ messages in thread
From: Daniel Barclay @ 2001-01-12 13:12 UTC (permalink / raw)
To: David M. Karr; +Cc: cygwin
"David M. Karr" wrote:
>
> >>>>> "Larry" == Larry Hall (RFK Partners, Inc) <lhall@rfk.com> writes:
...
> Earnie Boyd indicated on 9/26 it was "fixed in snapshots", but I've
> never seen any mention of a released fix for it. I recently upgraded
> my cygwin (1-2 weeks ago), so if the fix was there, I should have it
> (but I don't).
I just upgraded yesterday or Wednesday, from the ftp.sunsite.utk.edu mirror
(and the latest Emacs as of yesterday or Wednesday).
Daniel
--
Daniel Barclay
Digital Focus
Daniel.Barclay@digitalfocus.com
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: NTEmacs shell/CygWin: should control-C work?
2001-01-12 12:43 ` David M. Karr
2001-01-12 13:12 ` Daniel Barclay
@ 2001-01-12 13:13 ` Larry Hall (RFK Partners, Inc)
1 sibling, 0 replies; 222+ messages in thread
From: Larry Hall (RFK Partners, Inc) @ 2001-01-12 13:13 UTC (permalink / raw)
To: David M. Karr, cygwin
At 03:40 PM 1/12/2001, David M. Karr wrote:
> >> I don't know the full answer to that. For me, certain shell processes
> >> will die with ^C, some will not. I can kill "java", but I can't kill
> >> "tail -f" or "perl" (I have to use Task Manager). I have seen other
> >> people report this.
>
> Larry> Recently? Daniel's was the first report of this I've heard in months at
> Larry> least (longer than that most likely but I tend to be conservative when it
> Larry> comes to my memory). I might be wrong but I don't think this is a known
> Larry> problem and its certainly something that I don't see.
>
>Earnie Boyd indicated on 9/26 it was "fixed in snapshots", but I've
>never seen any mention of a released fix for it. I recently upgraded
>my cygwin (1-2 weeks ago), so if the fix was there, I should have it
>(but I don't).
Hm, I don't know why you have this problem but I can say that you have the
fix Earnie was referring to. Anything in the nightly snapshots as of 9/26
would be in the current 1.1.7 "release", if not the 1.1.6 and 1.1.5
"releases". So it may be related but the problem is certainly different.
Larry Hall lhall@rfk.com
RFK Partners, Inc. http://www.rfk.com
118 Washington Street (508) 893-9779 - RFK Office
Holliston, MA 01746 (508) 893-9889 - FAX
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: NTEmacs shell/CygWin: should control-C work?
2001-01-12 11:54 ` David M. Karr
2001-01-12 12:30 ` Larry Hall (RFK Partners, Inc)
@ 2001-01-12 13:06 ` Daniel Barclay
1 sibling, 0 replies; 222+ messages in thread
From: Daniel Barclay @ 2001-01-12 13:06 UTC (permalink / raw)
To: David M. Karr; +Cc: cygwin
"David M. Karr" wrote:
>
....
> I don't know the full answer to that. For me, certain shell processes
> will die with ^C, some will not. I can kill "java", but I can't kill
> "tail -f" or "perl" (I have to use Task Manager). I have seen other
> people report this.
Hmm. I think I've seen Java behave differently, but in the opposite
direction. On my _old_ setup (Emacs ? with CygWin 20 or so), java (Sun's)
would sometimes print out some status dump when I tried a control-C.
I think Java specifically catches an alternate signal (SIGQUIT? on Unix,
something else on Windows) to do that.
Maybe Emacs and/or CygWin are sending different signals at different
times or under different configurations, or processes are vulnerable
to different signals under different conditions.
AAAAGGGGHHHH!! Reinstalling a machine's worth of software is bad
enough without failures between critical areas (for me) like Emacs and
Unix commands.
Could someone who has Emacs C-c C-c working working post information
about your configuration OS version, NTEmacs version, relevant .emacs
contents, whatever version information now characterizes CygWin, relevant
cygwin.bat contents, environment variables, etc.)?
Here are my statistics:
- Windows NT 4.0, service pack 6a
- NT Emacs version:
"GNU Emacs 20.7.1 (i386-*-nt4.0.1381) of Tue Jun 13 2000 on buffy"
- HOME:
bash-2.04$ echo $HOME
/c/Daniel
- $HOME/.emacs (excerpts):
...
(setq exec-path (cons "C:/tools/cygwin/bin" exec-path))
(setenv "PATH" (concat "C:\\tools\\cygwin\\bin;" (getenv "PATH")))
;;TRYING:
(setenv "CYGWIN" (concat "tty " (getenv "CYGWIN")))
(setq process-coding-system-alist '(("bash" . undecided-unix)))
(setq w32-quote-process-args ?\")
(setq shell-file-name "bash")
(setenv "SHELL" shell-file-name)
(setq explicit-shell-file-name shell-file-name)
(add-hook 'comint-output-filter-functions
'comint-strip-ctrl-m)
...
- C:/tools/cygwin/cygwin.bat:
@echo off
set CYGWIN=tty
C:
chdir \tools\cygwin\bin
bash --login -i
- cygcheck:
$ cygcheck -s
Cygnus Win95/NT Configuration Diagnostics
Current System Time: Fri Jan 12 16:03:28 2001
WinNT Ver 4.0 build 1381 Service Pack 6
Path: /usr/bin
/c/WINNT/system32
/c/WINNT
SysDir: C:\WINNT\System32
WinDir: C:\WINNT
PWD = `/c/tools/emacs-20.7/bin'
CYGWIN = `tty '
HOME = `/c/Daniel'
Use `-r' to scan registry
a: fd N/A N/A
c: hd NTFS 4094Mb 53% CP CS UN PA FC C
d: hd NTFS 1592Mb 99% CP CS UN PA FC D
e: hd NTFS 4094Mb 85% CP CS UN PA FC E
f: cd N/A N/A
C:\tools\cygwin\bin /usr/bin system textmode
C:\tools\cygwin\lib /usr/lib system textmode
C:\tools\cygwin / system textmode
C: /c user textmode
D: /d user textmode
E: /e user textmode
Found: C:\tools\cygwin\bin\bash.exe
Found: C:\tools\cygwin\bin\cat.exe
Found: C:\tools\cygwin\bin\cpp.exe
Found: C:\tools\cygwin\bin\find.exe
Found: C:\tools\cygwin\bin\gcc.exe
Found: C:\tools\cygwin\bin\gdb.exe
Found: C:\tools\cygwin\bin\ld.exe
Found: C:\tools\cygwin\bin\ls.exe
Found: C:\tools\cygwin\bin\make.exe
Found: C:\tools\cygwin\bin\sh.exe
56k 2000/12/03 C:\tools\cygwin\bin\cygbz21.0.dll
45k 2000/12/07 C:\tools\cygwin\bin\cygform5.dll
18k 2000/10/23 C:\tools\cygwin\bin\cyggdbm.dll
17k 2001/01/07 C:\tools\cygwin\bin\cyghistory4.dll
14k 2000/10/23 C:\tools\cygwin\bin\cygintl.dll
81k 2000/12/05 C:\tools\cygwin\bin\cygitcl30.dll
35k 2000/12/05 C:\tools\cygwin\bin\cygitk30.dll
45k 2000/10/22 C:\tools\cygwin\bin\cygjbig1.dll
119k 2000/10/23 C:\tools\cygwin\bin\cygjpeg6b.dll
26k 2000/12/07 C:\tools\cygwin\bin\cygmenu5.dll
159k 2000/12/07 C:\tools\cygwin\bin\cygncurses++5.dll
225k 2000/12/07 C:\tools\cygwin\bin\cygncurses5.dll
15k 2000/12/07 C:\tools\cygwin\bin\cygpanel5.dll
162k 2000/10/23 C:\tools\cygwin\bin\cygpng2.dll
108k 2001/01/07 C:\tools\cygwin\bin\cygreadline4.dll
390k 2000/12/05 C:\tools\cygwin\bin\cygtcl80.dll
5k 2000/12/05 C:\tools\cygwin\bin\cygtclpip80.dll
10k 2000/12/05 C:\tools\cygwin\bin\cygtclreg80.dll
243k 2000/10/23 C:\tools\cygwin\bin\cygtiff3.dll
623k 2000/12/05 C:\tools\cygwin\bin\cygtk80.dll
41k 2000/11/20 C:\tools\cygwin\bin\cygXpm-noX4.dll
45k 2000/11/20 C:\tools\cygwin\bin\cygXpm-X4.dll
49k 2000/10/23 C:\tools\cygwin\bin\cygz.dll
611k 2000/12/25 C:\tools\cygwin\bin\cygwin1.dll
Cygwin DLL version info:
dll major: 1001
dll minor: 7
dll epoch: 19
dll bad signal mask: 19005
dll old termios: 5
dll malloc env: 28
api major: 0
api minor: 31
shared data: 3
dll identifier: cygwin1
mount registry: 2
cygnus registry name: Cygnus Solutions
cygwin registry name: Cygwin
program options name: Program Options
cygwin mount registry name: mounts v2
cygdrive flags: cygdrive flags
cygdrive prefix: cygdrive prefix
cygdrive default prefix:
build date: Mon Dec 25 12:39:48 EST 2000
shared id: cygwin1S3
Use -h to see help about each section
$
Daniel
--
Daniel Barclay
Digital Focus
Daniel.Barclay@digitalfocus.com
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: NTEmacs shell/CygWin: should control-C work?
2001-01-12 11:48 ` Daniel Barclay
2001-01-12 11:54 ` David M. Karr
@ 2001-01-12 13:26 ` Ehud Karni
2001-01-12 13:57 ` Larry Hall (RFK Partners, Inc)
1 sibling, 1 reply; 222+ messages in thread
From: Ehud Karni @ 2001-01-12 13:26 UTC (permalink / raw)
To: cygwin
On Fri, 12 Jan 2001 14:46:36 -0500, Daniel Barclay <Daniel.Barclay@digitalfocus.com> wrote:
>
> "David M. Karr" wrote:
> >
> > Daniel> In a shell buffer in NTEmacs configured per the shell-setup instructions
> > Daniel> in the CygWin FAQ at http://sources.redhat.com/cygwin/faq/faq.html#SEC5 ,
> > Daniel> control-C doesn't seem to work.
> ...
> > This bites me several times a day. It is a known problem...
>
> Do you mean it's a known problem that crops up (for some people), or that
> it simply doesn't work at all (for anyone combining Emacs and CygWin)?
I think he meant it is a general problem for everyone. The base of this
is that the emacs shell buffer is not a tty. You can check it by doing
`stty', you'll get: "stty: standard input: Not a character device".
And hence, it is not a tty ==> it will not generate SIGINT for ^C.
Ehud.
--
@@@@@@ @@@ @@@@@@ @ @ Ehud Karni Simon & Wiesel Insurance agency
@ @ @ @@ @ Tel: +972-3-6212-757 Fax: +972-3-6292-544
@ @ @ @ @ @@ (USA) Fax and voice mail: 1-815-5509341
@ @ @ @ @ @ Better Safe Than Sorry
http://www.simonwiesel.co.il mailto:ehud@unix.simonwiesel.co.il
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: NTEmacs shell/CygWin: should control-C work?
2001-01-12 13:26 ` Ehud Karni
@ 2001-01-12 13:57 ` Larry Hall (RFK Partners, Inc)
2001-01-16 11:14 ` Daniel Barclay
0 siblings, 1 reply; 222+ messages in thread
From: Larry Hall (RFK Partners, Inc) @ 2001-01-12 13:57 UTC (permalink / raw)
To: ehud, cygwin
At 04:25 PM 1/12/2001, Ehud Karni wrote:
>On Fri, 12 Jan 2001 14:46:36 -0500, Daniel Barclay <Daniel.Barclay@digitalfocus.com> wrote:
> >
> > "David M. Karr" wrote:
> > >
> > > Daniel> In a shell buffer in NTEmacs configured per the shell-setup instructions
> > > Daniel> in the CygWin FAQ at http://sources.redhat.com/cygwin/faq/faq.html#SEC5 ,
> > > Daniel> control-C doesn't seem to work.
> > ...
> > > This bites me several times a day. It is a known problem...
> >
> > Do you mean it's a known problem that crops up (for some people), or that
> > it simply doesn't work at all (for anyone combining Emacs and CygWin)?
>
>I think he meant it is a general problem for everyone. The base of this
>is that the emacs shell buffer is not a tty. You can check it by doing
>`stty', you'll get: "stty: standard input: Not a character device".
>
>And hence, it is not a tty ==> it will not generate SIGINT for ^C.
>
>Ehud.
Forgive me for coming late to the party. I didn't digest that this
conversation was about NTEmacs (i.e. the Windows port). I'll leave
aside whether or not ^C should work in this context. I really don't
know whether it should/would/ever did. I don't use Emacs. However,
I can say you'll have better luck with a Cygwin version of Emacs, like
XEmacs. You'll find Cygwin applications work much better with other
Cygwin applications, especially in areas of detail like this.
YMMV. Void where prohibited.
Larry Hall lhall@rfk.com
RFK Partners, Inc. http://www.rfk.com
118 Washington Street (508) 893-9779 - RFK Office
Holliston, MA 01746 (508) 893-9889 - FAX
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: NTEmacs shell/CygWin: should control-C work?
2001-01-12 13:57 ` Larry Hall (RFK Partners, Inc)
@ 2001-01-16 11:14 ` Daniel Barclay
2001-01-16 11:27 ` Larry Hall (RFK Partners, Inc)
0 siblings, 1 reply; 222+ messages in thread
From: Daniel Barclay @ 2001-01-16 11:14 UTC (permalink / raw)
To: Larry Hall (RFK Partners, Inc); +Cc: ehud, cygwin
"Larry Hall (RFK Partners, Inc)" wrote:
>
...
> ... However,
> I can say you'll have better luck with a Cygwin version of Emacs, like
> XEmacs. You'll find Cygwin applications work much better with other
> Cygwin applications, especially in areas of detail like this.
How different is XEmacs from GNU/NTEmacs?
(I don't do much (any) Lisp programming, so I guess I'm just asking about
default configuration and about compatibility of add-ons like JDE.)
Thanks,
Daniel
--
Daniel Barclay
Digital Focus
Daniel.Barclay@digitalfocus.com
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: NTEmacs shell/CygWin: should control-C work?
2001-01-16 11:14 ` Daniel Barclay
@ 2001-01-16 11:27 ` Larry Hall (RFK Partners, Inc)
2001-01-18 8:21 ` Daniel Barclay
0 siblings, 1 reply; 222+ messages in thread
From: Larry Hall (RFK Partners, Inc) @ 2001-01-16 11:27 UTC (permalink / raw)
To: Daniel Barclay; +Cc: ehud, cygwin
At 02:15 PM 1/16/2001, Daniel Barclay wrote:
>"Larry Hall (RFK Partners, Inc)" wrote:
> >
>...
> > ... However,
> > I can say you'll have better luck with a Cygwin version of Emacs, like
> > XEmacs. You'll find Cygwin applications work much better with other
> > Cygwin applications, especially in areas of detail like this.
>
>How different is XEmacs from GNU/NTEmacs?
>
>(I don't do much (any) Lisp programming, so I guess I'm just asking about
>default configuration and about compatibility of add-ons like JDE.)
Sorry, I was a little unclear. AFAIK, there is a Cygwin version of XEmacs
but there isn't one for NTEmacs. My main point was that signal functionality
can be handled by Cygwin (and is) or by the O/S. However, the signal coming
from a Win32 app doesn't get the same response out of Cygwin as one coming
from a Cygwin app. If you have problems in this area, your best bet is to
use Cygwin-enabled versions of apps when available.
Larry Hall lhall@rfk.com
RFK Partners, Inc. http://www.rfk.com
118 Washington Street (508) 893-9779 - RFK Office
Holliston, MA 01746 (508) 893-9889 - FAX
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: NTEmacs shell/CygWin: should control-C work?
2001-01-16 11:27 ` Larry Hall (RFK Partners, Inc)
@ 2001-01-18 8:21 ` Daniel Barclay
2001-01-18 8:27 ` Larry Hall (RFK Partners, Inc)
0 siblings, 1 reply; 222+ messages in thread
From: Daniel Barclay @ 2001-01-18 8:21 UTC (permalink / raw)
To: Larry Hall (RFK Partners, Inc); +Cc: ehud, cygwin
"Larry Hall (RFK Partners, Inc)" wrote:
>
> At 02:15 PM 1/16/2001, Daniel Barclay wrote:
> >"Larry Hall (RFK Partners, Inc)" wrote:
> > >
> >...
> > > ... However,
> > > I can say you'll have better luck with a Cygwin version of Emacs, like
> > > XEmacs. You'll find Cygwin applications work much better with other
> > > Cygwin applications, especially in areas of detail like this.
> >
> >How different is XEmacs from GNU/NTEmacs?
> >
> >(I don't do much (any) Lisp programming, so I guess I'm just asking about
> >default configuration and about compatibility of add-ons like JDE.)
>
> Sorry, I was a little unclear. AFAIK, there is a Cygwin version of XEmacs
> but there isn't one for NTEmacs. My main point was that signal functionality
> can be handled by Cygwin (and is) or by the O/S. However, the signal coming
> from a Win32 app doesn't get the same response out of Cygwin as one coming
> from a Cygwin app. If you have problems in this area, your best bet is to
> use Cygwin-enabled versions of apps when available.
I just meant how different is XEmacs from NTEmacs to the user? If I switch
from NTEmacs (which I'm used to) to XEmacs (which I don't know), how big a
change is that likely to been (from the Emacs user point of view)?
Daniel
--
Daniel Barclay
Digital Focus
Daniel.Barclay@digitalfocus.com
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: NTEmacs shell/CygWin: should control-C work?
2001-01-18 8:21 ` Daniel Barclay
@ 2001-01-18 8:27 ` Larry Hall (RFK Partners, Inc)
2001-01-18 16:47 ` Dr. Volker Zell
0 siblings, 1 reply; 222+ messages in thread
From: Larry Hall (RFK Partners, Inc) @ 2001-01-18 8:27 UTC (permalink / raw)
To: Daniel Barclay; +Cc: ehud, cygwin
At 11:22 AM 1/18/2001, Daniel Barclay wrote:
>"Larry Hall (RFK Partners, Inc)" wrote:
> >
> > At 02:15 PM 1/16/2001, Daniel Barclay wrote:
> > >"Larry Hall (RFK Partners, Inc)" wrote:
> > > >
> > >...
> > > > ... However,
> > > > I can say you'll have better luck with a Cygwin version of Emacs, like
> > > > XEmacs. You'll find Cygwin applications work much better with other
> > > > Cygwin applications, especially in areas of detail like this.
> > >
> > >How different is XEmacs from GNU/NTEmacs?
> > >
> > >(I don't do much (any) Lisp programming, so I guess I'm just asking about
> > >default configuration and about compatibility of add-ons like JDE.)
> >
> > Sorry, I was a little unclear. AFAIK, there is a Cygwin version of XEmacs
> > but there isn't one for NTEmacs. My main point was that signal functionality
> > can be handled by Cygwin (and is) or by the O/S. However, the signal coming
> > from a Win32 app doesn't get the same response out of Cygwin as one coming
> > from a Cygwin app. If you have problems in this area, your best bet is to
> > use Cygwin-enabled versions of apps when available.
>
>I just meant how different is XEmacs from NTEmacs to the user? If I switch
>from NTEmacs (which I'm used to) to XEmacs (which I don't know), how big a
>change is that likely to been (from the Emacs user point of view)?
I, of course, am not qualified to answer that question since I don't use
Emacs at all. Others might be able to help. You may be better off asking
this question on some Emacs list though...
Larry Hall lhall@rfk.com
RFK Partners, Inc. http://www.rfk.com
118 Washington Street (508) 893-9779 - RFK Office
Holliston, MA 01746 (508) 893-9889 - FAX
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: NTEmacs shell/CygWin: should control-C work?
2001-01-18 8:27 ` Larry Hall (RFK Partners, Inc)
@ 2001-01-18 16:47 ` Dr. Volker Zell
0 siblings, 0 replies; 222+ messages in thread
From: Dr. Volker Zell @ 2001-01-18 16:47 UTC (permalink / raw)
To: Larry Hall (RFK Partners, Inc); +Cc: Daniel Barclay, ehud, cygwin
>>>>> "RFK" == RFK Partners, Inc <Larry> writes:
RFK> At 11:22 AM 1/18/2001, Daniel Barclay wrote:
>> "Larry Hall (RFK Partners, Inc)" wrote:
>> >
>> > At 02:15 PM 1/16/2001, Daniel Barclay wrote:
>> > >"Larry Hall (RFK Partners, Inc)" wrote:
>> > > >
>> > >...
>> > > > ... However,
>> > > > I can say you'll have better luck with a Cygwin version of Emacs, like
>> > > > XEmacs. You'll find Cygwin applications work much better with other
>> > > > Cygwin applications, especially in areas of detail like this.
>> > >
>> > >How different is XEmacs from GNU/NTEmacs?
>> > >
>> > >(I don't do much (any) Lisp programming, so I guess I'm just asking about
>> > >default configuration and about compatibility of add-ons like JDE.)
>> >
>> > Sorry, I was a little unclear. AFAIK, there is a Cygwin version of XEmacs
>> > but there isn't one for NTEmacs. My main point was that signal functionality
>> > can be handled by Cygwin (and is) or by the O/S. However, the signal coming
>> > from a Win32 app doesn't get the same response out of Cygwin as one coming
>> > from a Cygwin app. If you have problems in this area, your best bet is to
>> > use Cygwin-enabled versions of apps when available.
>>
>> I just meant how different is XEmacs from NTEmacs to the user? If I switch
>> from NTEmacs (which I'm used to) to XEmacs (which I don't know), how big a
>> change is that likely to been (from the Emacs user point of view)?
RFK> I, of course, am not qualified to answer that question since I don't use
RFK> Emacs at all. Others might be able to help. You may be better off asking
RFK> this question on some Emacs list though...
I've done the switch a long time ago. NO big deal.
Just switch of the toolbar and it feels like Emacs.
Ciao
Volker
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
[parent not found: <14:02:23>]
[parent not found: <21:45:26>]
[parent not found: <1999>]
[parent not found: <;>]
* Problem with Windows .lnk files treated as Symlinks
@ 2001-05-03 6:27 Martin Oberhuber
2001-05-03 7:49 ` Larry Hall (RFK Partners, Inc)
0 siblings, 1 reply; 222+ messages in thread
From: Martin Oberhuber @ 2001-05-03 6:27 UTC (permalink / raw)
To: 'cygwin@cygwin.com'
Hello,
since cygwin-1.3, Windows *.lnk files are treated as UNIX
symbolic links by default.
We rean into a problem where we wanted to use the "cp"
command to copy a Windows *.lnk shortcut to a new place.
This worked alright with previous cygwin versions, but
with 1.3, the file referenced was copied instead of the
*.lnk file.
One problem with this behavour is that additional attributes
of the *.lnk file (like parameters passed to the program
referenced, or an icon associated) are not copied in that
case.
Looking at options of the CYGWIN environment variable as
well as options of the "cp" command, I found NO WAY of
copying the *.lnk file instead of the file referenced!
Even "cp -d", which is documented to preserve symbolic
links (and works like that on Linux) did not work.
Setting CYGWIN=nowinsymlinks only affects link creation,
but not link interpretation by "cp".
Taking into account that Windows Shortcuts are more than
UNIX symbolic links, and that thus a one-to-one mapping
is always problematic, I would suggest the following to
preserve a clean environment as well as backward
compatibility:
1.) Only *.lnk files created by Cygwin (with the special
cygwin header), should be treated as symbolic links when
they are read. If the *.lnk file is not a "cygwin *.lnk"
with its special header, it should be treated as a plain
file.
If this is not observed, important information may be lost
(also think about programs like tar that cannot reproduce
an exact image of the original file system if *.lnk files
are not completely copied).
2.) If CYGWIN=nowinsymlinks is set, not only symbolic link
creation but also symbolic link interpretation should
be "classical", i.e. *.lnk files are treated as files.
Please keep me informed on your plans regarding this issue.
Thanks in advance,
Martin Oberhuber
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: Problem with Windows .lnk files treated as Symlinks
2001-05-03 6:27 Problem with Windows .lnk files treated as Symlinks Martin Oberhuber
@ 2001-05-03 7:49 ` Larry Hall (RFK Partners, Inc)
2001-05-03 10:46 ` Christopher Faylor
0 siblings, 1 reply; 222+ messages in thread
From: Larry Hall (RFK Partners, Inc) @ 2001-05-03 7:49 UTC (permalink / raw)
To: Martin Oberhuber, 'cygwin@cygwin.com'
At 09:27 AM 5/3/2001, Martin Oberhuber wrote:
>Hello,
>
>since cygwin-1.3, Windows *.lnk files are treated as UNIX
>symbolic links by default.
>
>We rean into a problem where we wanted to use the "cp"
>command to copy a Windows *.lnk shortcut to a new place.
>This worked alright with previous cygwin versions, but
>with 1.3, the file referenced was copied instead of the
>*.lnk file.
>
>One problem with this behavour is that additional attributes
>of the *.lnk file (like parameters passed to the program
>referenced, or an icon associated) are not copied in that
>case.
>
>Looking at options of the CYGWIN environment variable as
>well as options of the "cp" command, I found NO WAY of
>copying the *.lnk file instead of the file referenced!
>Even "cp -d", which is documented to preserve symbolic
>links (and works like that on Linux) did not work.
>Setting CYGWIN=nowinsymlinks only affects link creation,
>but not link interpretation by "cp".
>
>Taking into account that Windows Shortcuts are more than
>UNIX symbolic links, and that thus a one-to-one mapping
>is always problematic, I would suggest the following to
>preserve a clean environment as well as backward
>compatibility:
>
>1.) Only *.lnk files created by Cygwin (with the special
> cygwin header), should be treated as symbolic links when
> they are read. If the *.lnk file is not a "cygwin *.lnk"
> with its special header, it should be treated as a plain
> file.
> If this is not observed, important information may be lost
> (also think about programs like tar that cannot reproduce
> an exact image of the original file system if *.lnk files
> are not completely copied).
Since the goal of making Cygwin symbolic links use the Windows short-cut
mechanism was to allow Windows and Cygwin to interoperate in this area, I
don't see any benefit to trying to break this with your suggestion.
Certainly, this is the way things worked prior to this change since short-cuts
were not understood by Cygwin and Cygwin symbolic links were not understood
by Windows. If you need this division, you want to use the old mechanism.
>2.) If CYGWIN=nowinsymlinks is set, not only symbolic link
> creation but also symbolic link interpretation should
> be "classical", i.e. *.lnk files are treated as files.
This may be indicative of a bug.
>Please keep me informed on your plans regarding this issue.
Watch the list and you'll see any discussion of this. Or send in a patch for
(2) for consideration.
Larry Hall lhall@rfk.com
RFK Partners, Inc. http://www.rfk.com
118 Washington Street (508) 893-9779 - RFK Office
Holliston, MA 01746 (508) 893-9889 - FAX
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: Problem with Windows .lnk files treated as Symlinks
2001-05-03 7:49 ` Larry Hall (RFK Partners, Inc)
@ 2001-05-03 10:46 ` Christopher Faylor
0 siblings, 0 replies; 222+ messages in thread
From: Christopher Faylor @ 2001-05-03 10:46 UTC (permalink / raw)
To: 'cygwin@cygwin.com'
On Thu, May 03, 2001 at 10:48:05AM -0400, Larry Hall (RFK Partners, Inc) wrote:
>>2.) If CYGWIN=nowinsymlinks is set, not only symbolic link
>> creation but also symbolic link interpretation should
>> be "classical", i.e. *.lnk files are treated as files.
>
>This may be indicative of a bug.
This isn't a bug. The setting is only to force creation of old style symlinks.
Either style is supposed to be recognized on "reading". I suppose the option
could have been "nocreatewinsymlinks"...
cgf
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* KSH is pdksh
@ 2001-01-24 13:36 Galen Boyer
2001-01-24 14:35 ` Larry Hall (RFK Partners, Inc)
` (2 more replies)
0 siblings, 3 replies; 222+ messages in thread
From: Galen Boyer @ 2001-01-24 13:36 UTC (permalink / raw)
To: cygwin
After reviewing some archives, I find that pdksh is cygwin's
version of ksh. Is this still available and where do I get it?
My c:/cygwin/bin doesn't contain it.
Thanks.
--
Galen Boyer
Fingers and toes, fingers and toes, forty things we share.
Forty one if you include, the fact that we don't care.
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: KSH is pdksh
2001-01-24 13:36 KSH is pdksh Galen Boyer
@ 2001-01-24 14:35 ` Larry Hall (RFK Partners, Inc)
2001-01-24 15:33 ` David Feustel
2001-01-24 15:30 ` Corinna Vinschen
2001-01-24 15:39 ` David M. Karr
2 siblings, 1 reply; 222+ messages in thread
From: Larry Hall (RFK Partners, Inc) @ 2001-01-24 14:35 UTC (permalink / raw)
To: Galen Boyer, cygwin
At 04:36 PM 1/24/2001, Galen Boyer wrote:
>After reviewing some archives, I find that pdksh is cygwin's
>version of ksh. Is this still available and where do I get it?
>My c:/cygwin/bin doesn't contain it.
pdksh is not Cygwin's version of ksh but rather an open-source version of
ksh which can be built and used under Cygwin. You can check the Cygwin
home page for pointers to related sites with ported software and you can
also look in the mail archives for indications that others have ported it
and made it available. Alternatively, you can just download the source
from your favorite GNU site and build it yourself.
Larry Hall lhall@rfk.com
RFK Partners, Inc. http://www.rfk.com
118 Washington Street (508) 893-9779 - RFK Office
Holliston, MA 01746 (508) 893-9889 - FAX
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: KSH is pdksh
2001-01-24 14:35 ` Larry Hall (RFK Partners, Inc)
@ 2001-01-24 15:33 ` David Feustel
0 siblings, 0 replies; 222+ messages in thread
From: David Feustel @ 2001-01-24 15:33 UTC (permalink / raw)
To: Galen Boyer, cygwin, Larry Hall (RFK Partners, Inc)
The ATT Korn Shell is now open source and should
compile with Cygwin. Get it at http://www.kornshell.com/
----- Original Message -----
From: "Larry Hall (RFK Partners, Inc)" <lhall@rfk.com>
To: "Galen Boyer" <galenboyer@yahoo.com>; <cygwin@sourceware.cygnus.com>
Sent: Wednesday, January 24, 2001 5:31 PM
Subject: Re: KSH is pdksh
> At 04:36 PM 1/24/2001, Galen Boyer wrote:
> >After reviewing some archives, I find that pdksh is cygwin's
> >version of ksh. Is this still available and where do I get it?
> >My c:/cygwin/bin doesn't contain it.
>
>
> pdksh is not Cygwin's version of ksh but rather an open-source version of
> ksh which can be built and used under Cygwin. You can check the Cygwin
> home page for pointers to related sites with ported software and you can
> also look in the mail archives for indications that others have ported it
> and made it available. Alternatively, you can just download the source
> from your favorite GNU site and build it yourself.
>
>
>
> Larry Hall lhall@rfk.com
> RFK Partners, Inc. http://www.rfk.com
> 118 Washington Street (508) 893-9779 - RFK Office
> Holliston, MA 01746 (508) 893-9889 - FAX
>
>
>
> --
> Want to unsubscribe from this list?
> Check out: http://cygwin.com/ml/#unsubscribe-simple
>
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: KSH is pdksh
2001-01-24 13:36 KSH is pdksh Galen Boyer
2001-01-24 14:35 ` Larry Hall (RFK Partners, Inc)
@ 2001-01-24 15:30 ` Corinna Vinschen
2001-01-24 15:39 ` David M. Karr
2 siblings, 0 replies; 222+ messages in thread
From: Corinna Vinschen @ 2001-01-24 15:30 UTC (permalink / raw)
To: cygwin
On Wed, Jan 24, 2001 at 04:36:33PM -0500, Galen Boyer wrote:
> After reviewing some archives, I find that pdksh is cygwin's
> version of ksh. Is this still available and where do I get it?
> My c:/cygwin/bin doesn't contain it.
Ooops, pdksh is _not_ the Cygwin version of ksh. Pdksh is an open
source implementation of ksh which isn't bound to a specific OS.
Latest sources are available in ftp://ftp.cs.mun.ca/pub/pdksh , an
OLD Cygwin binary which only supports binmode mounts is available in
ftp://ftp.franken.de/pub/win32/develop/gnuwin32/cygwin/porters/Vinschen_Corinna/B20
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Developer mailto:cygwin@cygwin.com
Red Hat, Inc.
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: KSH is pdksh
2001-01-24 13:36 KSH is pdksh Galen Boyer
2001-01-24 14:35 ` Larry Hall (RFK Partners, Inc)
2001-01-24 15:30 ` Corinna Vinschen
@ 2001-01-24 15:39 ` David M. Karr
2001-01-24 17:25 ` Earnie Boyd
2001-01-25 7:51 ` KSH is pdksh Galen Boyer
2 siblings, 2 replies; 222+ messages in thread
From: David M. Karr @ 2001-01-24 15:39 UTC (permalink / raw)
To: cygwin
>>>>> "Galen" == Galen Boyer <galenboyer@yahoo.com> writes:
Galen> After reviewing some archives, I find that pdksh is cygwin's
Galen> version of ksh. Is this still available and where do I get it?
Galen> My c:/cygwin/bin doesn't contain it.
As Larry explained, this is something different.
However, as I've come to discover after much pain, if you're already
using Cygwin, there isn't much point to installing pdksh. It's easy
enough to create a symlink from "/usr/bin/ksh.exe" to
"/usr/bin/bash.exe". Poof. You have Korn shell. As far as I can
tell, Bash can substitute for Korn shell in every area I'm familiar
with.
--
===================================================================
David M. Karr ; w:(425)487-8312 ; TCSI & Best Consulting
dkarr@tcsi.com ; Java/Unix/XML/C++/X ; BrainBench CJ12P (#12004)
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: KSH is pdksh
2001-01-24 15:39 ` David M. Karr
@ 2001-01-24 17:25 ` Earnie Boyd
2001-01-24 19:07 ` Mumit Khan
2001-01-25 7:51 ` KSH is pdksh Galen Boyer
1 sibling, 1 reply; 222+ messages in thread
From: Earnie Boyd @ 2001-01-24 17:25 UTC (permalink / raw)
To: David M. Karr; +Cc: cygwin
"David M. Karr" wrote:
>
> >>>>> "Galen" == Galen Boyer <galenboyer@yahoo.com> writes:
> Galen> After reviewing some archives, I find that pdksh is cygwin's
> Galen> version of ksh. Is this still available and where do I get it?
> Galen> My c:/cygwin/bin doesn't contain it.
>
> As Larry explained, this is something different.
>
> However, as I've come to discover after much pain, if you're already
> using Cygwin, there isn't much point to installing pdksh. It's easy
> enough to create a symlink from "/usr/bin/ksh.exe" to
> "/usr/bin/bash.exe". Poof. You have Korn shell. As far as I can
> tell, Bash can substitute for Korn shell in every area I'm familiar
> with.
>
I knew that once upon a time. Thanks for reminding me. Hey miss bash
maintainer how about a postinstall script to ln -s bash.exe ksh.exe?
Cheers,
Earnie.
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: KSH is pdksh
2001-01-24 17:25 ` Earnie Boyd
@ 2001-01-24 19:07 ` Mumit Khan
2001-01-25 8:25 ` David M. Karr
0 siblings, 1 reply; 222+ messages in thread
From: Mumit Khan @ 2001-01-24 19:07 UTC (permalink / raw)
To: Earnie Boyd; +Cc: David M. Karr, cygwin
On Wed, 24 Jan 2001, Earnie Boyd wrote:
> "David M. Karr" wrote:
> > "/usr/bin/bash.exe". Poof. You have Korn shell. As far as I can
> > tell, Bash can substitute for Korn shell in every area I'm familiar
> > with.
> >
Nope, bash is not ksh. There are quite a few ksh93 features that are not
implemented in bash (and possibly quite a few from ksh88 days, but I
don't have details on those).
> I knew that once upon a time. Thanks for reminding me. Hey miss bash
> maintainer how about a postinstall script to ln -s bash.exe ksh.exe?
Please don't. I personally very much dislike misleading links. If people
want ksh, they should go and port it using the AT&T's now open source
ksh93.
Regards,
Mumit
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: KSH is pdksh
2001-01-24 19:07 ` Mumit Khan
@ 2001-01-25 8:25 ` David M. Karr
2001-01-25 8:34 ` Larry Hall (RFK Partners, Inc)
0 siblings, 1 reply; 222+ messages in thread
From: David M. Karr @ 2001-01-25 8:25 UTC (permalink / raw)
To: cygwin
>>>>> "Mumit" == Mumit Khan <khan@nanotech.wisc.edu> writes:
Mumit> On Wed, 24 Jan 2001, Earnie Boyd wrote:
>> "David M. Karr" wrote:
>> > "/usr/bin/bash.exe". Poof. You have Korn shell. As far as I can
>> > tell, Bash can substitute for Korn shell in every area I'm familiar
>> > with.
Mumit> Nope, bash is not ksh. There are quite a few ksh93 features that are not
Mumit> implemented in bash (and possibly quite a few from ksh88 days, but I
Mumit> don't have details on those).
I'm not going to dispute that, but could you please give us some
examples of ksh88 and ksh93 features that aren't transparently
available in bash? I'd like to know exactly what problems I could run
into. I haven't noticed anything yet. Does someone know which
canonical ksh version (ksh88 or ksh93) the Solaris ksh matches?
Mumit> Please don't. I personally very much dislike misleading links. If people
Mumit> want ksh, they should go and port it using the AT&T's now open source
Mumit> ksh93.
It would sure be nice to bring a maintainable ksh into the Cygwin
fold, just for the sake of increased Unix compatibility.
--
===================================================================
David M. Karr ; w:(425)487-8312 ; TCSI & Best Consulting
dkarr@tcsi.com ; Java/Unix/XML/C++/X ; BrainBench CJ12P (#12004)
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: KSH is pdksh
2001-01-25 8:25 ` David M. Karr
@ 2001-01-25 8:34 ` Larry Hall (RFK Partners, Inc)
2001-01-25 12:52 ` Matthew Smith
0 siblings, 1 reply; 222+ messages in thread
From: Larry Hall (RFK Partners, Inc) @ 2001-01-25 8:34 UTC (permalink / raw)
To: David M. Karr, cygwin
At 11:21 AM 1/25/2001, David M. Karr wrote:
> Mumit> Please don't. I personally very much dislike misleading links. If people
> Mumit> want ksh, they should go and port it using the AT&T's now open source
> Mumit> ksh93.
>
>It would sure be nice to bring a maintainable ksh into the Cygwin
>fold, just for the sake of increased Unix compatibility.
Volunteers welcome!:-)
Larry Hall lhall@rfk.com
RFK Partners, Inc. http://www.rfk.com
118 Washington Street (508) 893-9779 - RFK Office
Holliston, MA 01746 (508) 893-9889 - FAX
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: KSH is pdksh
2001-01-25 8:34 ` Larry Hall (RFK Partners, Inc)
@ 2001-01-25 12:52 ` Matthew Smith
2001-01-25 13:32 ` Earnie Boyd
0 siblings, 1 reply; 222+ messages in thread
From: Matthew Smith @ 2001-01-25 12:52 UTC (permalink / raw)
To: Cygwin
For what it's worth, I started taking a stab at compiling AT&T's ksh. Man,
they certainly do use some wacky packaging tools. At any rate, here are
some of the problems that I encountered, and what I did about them.
1) The 'package' script wants to see getopts. Thus, I made sh a link to
bash to work around this.
2) The 'package' script always seemed to fail, complaining about not being
in the package root (when it was). I solved this by editing the package
script to not exit if that particular error happened.
3) I made a link from gcc->cc for convenience sake (read: laziness).
At this point the 'mamake' utility seems to start configuring/making things.
However, it spits out the following errors:
/home/matts/att/src/lib/libast/include/ast_std.h:672: conflicting types for
`rea
d'
/usr/include/sys/unistd.h:72: previous declaration of `read'
/home/matts/att/src/lib/libast/include/ast_std.h:690: conflicting types for
`wri
te'
/usr/include/sys/unistd.h:99: previous declaration of `write'
Can anyone suggest an elegant way around this?
thanks,
-Matt Smith
> >
> >It would sure be nice to bring a maintainable ksh into the Cygwin
> >fold, just for the sake of increased Unix compatibility.
>
>
> Volunteers welcome!:-)
>
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: KSH is pdksh
2001-01-25 12:52 ` Matthew Smith
@ 2001-01-25 13:32 ` Earnie Boyd
2001-01-25 14:31 ` Newlib's non-posix'ness [Re: KSH is pdksh] Mumit Khan
0 siblings, 1 reply; 222+ messages in thread
From: Earnie Boyd @ 2001-01-25 13:32 UTC (permalink / raw)
To: Matthew Smith; +Cc: Cygwin
Matthew Smith wrote:
>
> Can anyone suggest an elegant way around this?
>
Fix the code. Remove the redefinitions.
Earnie.
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Newlib's non-posix'ness [Re: KSH is pdksh]
2001-01-25 13:32 ` Earnie Boyd
@ 2001-01-25 14:31 ` Mumit Khan
2001-01-25 16:17 ` Earnie Boyd
2001-01-25 21:23 ` Christopher Faylor
0 siblings, 2 replies; 222+ messages in thread
From: Mumit Khan @ 2001-01-25 14:31 UTC (permalink / raw)
To: Cygwin; +Cc: Matthew Smith
On Thu, 25 Jan 2001, Earnie Boyd wrote:
> Matthew Smith wrote:
> >
> > Can anyone suggest an elegant way around this?
> >
>
> Fix the code. Remove the redefinitions.
FYI, it's newlib that provides the incorrect declaration. It's one of
those cases where newlib's declarations don't quite match POSIX/UNIX98,
but small enough that nobody has bothered to fix those. Mostly has to
do with signed vs unsigned (eg., size_t vs ssize_t) and those little
nits. Interestingly enough, someone, quite possibly Joel Scherrill, had
gone through newlib and fixed most of these, if not all, but only for
RTEMS!
POSIX:
ssize_t read (int, void *, size_t);
newlib:
#ifdef __rtems__
ssize_t read (int, void *, size_t);
#else
int read (int, void *, size_t);
#endif
Perhaps Chris and/or DJ know why that is the case.
When you have a conflict between Glenn Fowler's AT&T AST and another
library, chances are that AST is doing the right thing.
Regards,
Mumit
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: Newlib's non-posix'ness [Re: KSH is pdksh]
2001-01-25 14:31 ` Newlib's non-posix'ness [Re: KSH is pdksh] Mumit Khan
@ 2001-01-25 16:17 ` Earnie Boyd
2001-01-25 21:23 ` Christopher Faylor
1 sibling, 0 replies; 222+ messages in thread
From: Earnie Boyd @ 2001-01-25 16:17 UTC (permalink / raw)
To: Mumit Khan; +Cc: Cygwin, Matthew Smith, newlib
Mumit Khan wrote:
>
> On Thu, 25 Jan 2001, Earnie Boyd wrote:
>
> > Matthew Smith wrote:
> > >
> > > Can anyone suggest an elegant way around this?
> > >
> >
> > Fix the code. Remove the redefinitions.
>
> FYI, it's newlib that provides the incorrect declaration. It's one of
> those cases where newlib's declarations don't quite match POSIX/UNIX98,
> but small enough that nobody has bothered to fix those. Mostly has to
> do with signed vs unsigned (eg., size_t vs ssize_t) and those little
> nits. Interestingly enough, someone, quite possibly Joel Scherrill, had
> gone through newlib and fixed most of these, if not all, but only for
> RTEMS!
>
> POSIX:
> ssize_t read (int, void *, size_t);
>
> newlib:
> #ifdef __rtems__
> ssize_t read (int, void *, size_t);
> #else
> int read (int, void *, size_t);
> #endif
>
> Perhaps Chris and/or DJ know why that is the case.
>
> When you have a conflict between Glenn Fowler's AT&T AST and another
> library, chances are that AST is doing the right thing.
>
There's been other chatter about problems with __rtems__ and Cygwin on
the newlib list; but, it was wrt pthreads. I've CCed newlib on this.
Earnie.
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: Newlib's non-posix'ness [Re: KSH is pdksh]
2001-01-25 14:31 ` Newlib's non-posix'ness [Re: KSH is pdksh] Mumit Khan
2001-01-25 16:17 ` Earnie Boyd
@ 2001-01-25 21:23 ` Christopher Faylor
1 sibling, 0 replies; 222+ messages in thread
From: Christopher Faylor @ 2001-01-25 21:23 UTC (permalink / raw)
To: Cygwin
On Thu, Jan 25, 2001 at 04:30:52PM -0600, Mumit Khan wrote:
>On Thu, 25 Jan 2001, Earnie Boyd wrote:
>
>> Matthew Smith wrote:
>> >
>> > Can anyone suggest an elegant way around this?
>> >
>>
>> Fix the code. Remove the redefinitions.
>
>FYI, it's newlib that provides the incorrect declaration. It's one of
>those cases where newlib's declarations don't quite match POSIX/UNIX98,
>but small enough that nobody has bothered to fix those. Mostly has to
>do with signed vs unsigned (eg., size_t vs ssize_t) and those little
>nits. Interestingly enough, someone, quite possibly Joel Scherrill, had
>gone through newlib and fixed most of these, if not all, but only for
>RTEMS!
>
>POSIX:
> ssize_t read (int, void *, size_t);
>
>newlib:
> #ifdef __rtems__
> ssize_t read (int, void *, size_t);
> #else
> int read (int, void *, size_t);
> #endif
>
>Perhaps Chris and/or DJ know why that is the case.
Because the only thing that Joel cares about is RTEMS, basically. He
broke Cygwin builds a couple of times with his changes and, I assume,
rather than try to build Cygwin after a change, opted to just
conditionalize everything.
>When you have a conflict between Glenn Fowler's AT&T AST and another
>library, chances are that AST is doing the right thing.
Probably, but any package that doesn't build because it relies on read
being defined as ssize_t is not exactly portable.
cgf
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: KSH is pdksh
2001-01-24 15:39 ` David M. Karr
2001-01-24 17:25 ` Earnie Boyd
@ 2001-01-25 7:51 ` Galen Boyer
2001-01-25 13:01 ` Galen Boyer
1 sibling, 1 reply; 222+ messages in thread
From: Galen Boyer @ 2001-01-25 7:51 UTC (permalink / raw)
To: cygwin
On 24 Jan 2001, dkarr@tcsi.com wrote:
> However, as I've come to discover after much pain, if you're
> already using Cygwin, there isn't much point to installing
> pdksh. It's easy enough to create a symlink from
> "/usr/bin/ksh.exe" to "/usr/bin/bash.exe". Poof. You have
> Korn shell. As far as I can tell, Bash can substitute for Korn
> shell in every area I'm familiar with.
Well, if I could find the equivalent to getopts, I think I could
get along without kornshell. I found this feature to be
extremely useful when I was a heavy-duty KSH programmer, and now
I am coding a few scripts again and would like to take advantage
of it.
--
Galen Boyer
Fingers and toes, fingers and toes, forty things we share.
Forty one if you include, the fact that we don't care.
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: KSH is pdksh
2001-01-25 7:51 ` KSH is pdksh Galen Boyer
@ 2001-01-25 13:01 ` Galen Boyer
0 siblings, 0 replies; 222+ messages in thread
From: Galen Boyer @ 2001-01-25 13:01 UTC (permalink / raw)
To: cygwin
On 25 Jan 2001, galenboyer@yahoo.com wrote:
> Well, if I could find the equivalent to getopts, I think I
> could get along without kornshell. I found this feature to be
> extremely useful when I was a heavy-duty KSH programmer, and
> now I am coding a few scripts again and would like to take
> advantage of it.
I got notified of the man pages for bash. It looks really nice
for scripting. getopts is just how I expected. Whoa! Cygwin is
excellent!
Thanks a WHOLE BUNCH!
--
Galen Boyer
Fingers and toes, fingers and toes, forty things we share.
Forty one if you include, the fact that we don't care.
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: Cygwin commands crashes after ssh login
@ 2001-01-18 7:23 Yadin Goldschmidt
2001-01-18 8:18 ` Corinna Vinschen
0 siblings, 1 reply; 222+ messages in thread
From: Yadin Goldschmidt @ 2001-01-18 7:23 UTC (permalink / raw)
To: cygwin
Corinna,
I tried both -1 and -2. I think the problem is with the cygwin dll
since if I use 1.1.5 the problem disappears. What is also strange is
that if I run sshd -d from a shell the problem does not occur. It only
occurs with sshd run from srvany. Please read carefully my setup
1., 2., 3. 4. in my previous mail, maybe you can reproduce it.
The CYGWIN variable ntsec, tty is defined in NT Control Panel ->system
->environment. The files ssh_host_key and ssh_host_dsa_key have permissions
-rw------- and belong to user.Adminstrators.
What is also interesting is that after the exception occurs I can
still run cygwin commands and the connection is not lost.
Yadin.
>On Wed, Jan 17, 2001 at 10:08:08AM -0500, Yadin Goldschmidt wrote:
>SSH Version OpenSSH_2.3.0p1, protocol versions 1.5/2.0.
>Which one? -1 or -2? Did you try both? Did you try the
>experimental version 20001221?
>Corinna
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: Cygwin commands crashes after ssh login
2001-01-18 7:23 Cygwin commands crashes after ssh login Yadin Goldschmidt
@ 2001-01-18 8:18 ` Corinna Vinschen
0 siblings, 0 replies; 222+ messages in thread
From: Corinna Vinschen @ 2001-01-18 8:18 UTC (permalink / raw)
To: cygwin
On Thu, Jan 18, 2001 at 10:22:55AM -0500, Yadin Goldschmidt wrote:
>
> Corinna,
> I tried both -1 and -2. I think the problem is with the cygwin dll
> since if I use 1.1.5 the problem disappears. What is also strange is
> that if I run sshd -d from a shell the problem does not occur. It only
> occurs with sshd run from srvany. Please read carefully my setup
> 1., 2., 3. 4. in my previous mail, maybe you can reproduce it.
Same here. I _did_ read your mail!
> The CYGWIN variable ntsec, tty is defined in NT Control Panel ->system
> ->environment.
Ditto. (CYGWIN = binmode tty ntsec)
> ->environment. The files ssh_host_key and ssh_host_dsa_key have permissions
> -rw------- and belong to user.Adminstrators.
Ditto.
No problem here using different accounts, using tcsh or bash as
login shell.
Note that I reinstalled Cygwin from scratch here! On my developer box!
I'm using the old ssh key files of course but everything else is fresh
and new including all mount points (now according to the installation
default). I'm using the 20001221 version of OpenSSH, though, which you
can install using setup.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Developer mailto:cygwin@cygwin.com
Red Hat, Inc.
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* RE: Cygwin commands crashes after ssh login
@ 2001-01-17 13:43 frank.palazzolo
2001-01-17 13:54 ` Larry Hall (RFK Partners, Inc)
0 siblings, 1 reply; 222+ messages in thread
From: frank.palazzolo @ 2001-01-17 13:43 UTC (permalink / raw)
To: cygwin
>/bin/sh is bash in the standard gnu dist.. :-) So copy your compiled
>bash to /bin/sh..
>
> /Andy
Thanks Andy,
That's what I thought too, but when the file sizes were so different I looked around and realized my sh.exe came from ash-20001002.tar.gz, which is a different shell and codebase, I guess.
-Frank
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* RE: Cygwin commands crashes after ssh login
2001-01-17 13:43 frank.palazzolo
@ 2001-01-17 13:54 ` Larry Hall (RFK Partners, Inc)
0 siblings, 0 replies; 222+ messages in thread
From: Larry Hall (RFK Partners, Inc) @ 2001-01-17 13:54 UTC (permalink / raw)
To: frank.palazzolo, cygwin
At 04:42 PM 1/17/2001, frank.palazzolo@autodesk.com wrote:
> >/bin/sh is bash in the standard gnu dist.. :-) So copy your compiled
> >bash to /bin/sh..
> >
> > /Andy
>
>Thanks Andy,
>
>That's what I thought too, but when the file sizes were so different I looked around and realized my sh.exe came from ash-20001002.tar.gz, which is a different shell and codebase, I guess.
Absolutely. In Cygwin /bin/sh is NOT equivalent to /bin/bash. /bin/sh is
ash, which is an optimized version of the bourne shell. Its used instead of
bash for performance reasons (mostly noticeable in configures). However
ash does seem to have more bugs than bash (if the issues that arise on this
list are any indication). While the bugs that have been found have been
rapidly fixed, how many are left is uncertain (as always). If shell
performance is not you're major concern, you can use bash as /bin/sh.
However, recompiled or not, any version of bash is different enough from
ash to have a strong potential for reacting differently in any particular
case. Usually this means its more forgiving/works better. YMMV.
Larry Hall lhall@rfk.com
RFK Partners, Inc. http://www.rfk.com
118 Washington Street (508) 893-9779 - RFK Office
Holliston, MA 01746 (508) 893-9889 - FAX
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: Cygwin commands crashes after ssh login
@ 2001-01-17 13:12 frank.palazzolo
2001-01-18 6:07 ` Corinna Vinschen
2001-01-25 10:37 ` Erdely, Michael
0 siblings, 2 replies; 222+ messages in thread
From: frank.palazzolo @ 2001-01-17 13:12 UTC (permalink / raw)
To: cygwin
Hello,
I'm a newbie to cygwin, but I have this exact problem with sshd, and a little more info on it.
I'm running Win2K SP1 and using inetd to launch sshd.
I rebuilt bash.exe from the sources and the problem disappeared!
However, I also tried replacing the shell of the logon user with /bin/sh and the problem still occurs. I haven't rebuilt sh.exe.
Could there be something wrong with the bash.exe in the binary distribution..?
By the way, it seems that a few lines failed in the configure.in for bash:
dnl Use GNU m4 macros to get the distribution and patchlevel information
dnl into configure without requiring the files to be distributed
[BASHVERS=]dnl
esyscmd(cat _distribution)dnl
[BASHPATCH]dnl
esyscmd(cat _patchlevel)dnl
I had to to hack those two lines to get bash to build, is that normal?
Thanks,
Frank Palazzolo
frank.palazzolo@autodesk.com
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: Cygwin commands crashes after ssh login
2001-01-17 13:12 frank.palazzolo
@ 2001-01-18 6:07 ` Corinna Vinschen
2001-01-25 10:37 ` Erdely, Michael
1 sibling, 0 replies; 222+ messages in thread
From: Corinna Vinschen @ 2001-01-18 6:07 UTC (permalink / raw)
To: cygwin
On Wed, Jan 17, 2001 at 01:11:53PM -0800, frank.palazzolo@autodesk.com wrote:
> Hello,
>
> I'm a newbie to cygwin, but I have this exact problem with sshd, and a little more info on it.
>
> I'm running Win2K SP1 and using inetd to launch sshd.
> I rebuilt bash.exe from the sources and the problem disappeared!
> However, I also tried replacing the shell of the logon user with /bin/sh and the problem still occurs. I haven't rebuilt sh.exe.
>
> Could there be something wrong with the bash.exe in the binary distribution..?
I tried it and I *sigh* still can't reproduce that. When I'm using
bash or ash from the net distro as login shell, everything works.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Developer mailto:cygwin@cygwin.com
Red Hat, Inc.
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: Cygwin commands crashes after ssh login
2001-01-17 13:12 frank.palazzolo
2001-01-18 6:07 ` Corinna Vinschen
@ 2001-01-25 10:37 ` Erdely, Michael
2001-01-25 12:25 ` Ross Smith
1 sibling, 1 reply; 222+ messages in thread
From: Erdely, Michael @ 2001-01-25 10:37 UTC (permalink / raw)
To: cygwin
Frank's recompilation success has been repeated. And, I recompiled ASH as
well. Problem is gone on three machines.
Thanks, Frank (and Yadin).
If you're interested in pre-re-compiled binaries, check out
ftp://ftp.erdelynet.com/ftp/downloads/bash.exe.gz and
ftp://ftp.erdelynet.com/ftp/downloads/sh.exe.gz . If you want some
information about installing these files, look at
http://mike.erdelynet.com/sshd-error.asp#solution .
One note, when I re-compiled bash, I had to create _distribution and
_patchlevel files to work. After doing so, though, I was successful.
Please let me know if you have any questions/comments,
Mike Erdely
mailto:mike@erdelynet.com
http://mike.erdelynet.com/
----- Original Message -----
From: <frank.palazzolo@autodesk.com>
To: <cygwin@cygwin.com>
Sent: Wednesday, January 17, 2001 4:11 PM
Subject: Re: Cygwin commands crashes after ssh login
>
> Hello,
>
> I'm a newbie to cygwin, but I have this exact problem with sshd, and a
little more info on it.
>
> I'm running Win2K SP1 and using inetd to launch sshd.
> I rebuilt bash.exe from the sources and the problem disappeared!
> However, I also tried replacing the shell of the logon user with /bin/sh
and the problem still occurs. I haven't rebuilt sh.exe.
>
> Could there be something wrong with the bash.exe in the binary
distribution..?
>
> By the way, it seems that a few lines failed in the configure.in for bash:
>
> dnl Use GNU m4 macros to get the distribution and patchlevel information
> dnl into configure without requiring the files to be distributed
> [BASHVERS=]dnl
> esyscmd(cat _distribution)dnl
> [BASHPATCH]dnl
> esyscmd(cat _patchlevel)dnl
>
> I had to to hack those two lines to get bash to build, is that normal?
>
> Thanks,
> Frank Palazzolo
>
> frank.palazzolo@autodesk.com
>
>
> --
> Want to unsubscribe from this list?
> Check out: http://cygwin.com/ml/#unsubscribe-simple
>
>
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: Cygwin commands crashes after ssh login
2001-01-25 10:37 ` Erdely, Michael
@ 2001-01-25 12:25 ` Ross Smith
2001-01-25 12:34 ` Larry Hall (RFK Partners, Inc)
2001-01-25 13:36 ` Erdely, Michael
0 siblings, 2 replies; 222+ messages in thread
From: Ross Smith @ 2001-01-25 12:25 UTC (permalink / raw)
To: cygwin
"Erdely, Michael" wrote:
>
> Frank's recompilation success has been repeated. And, I recompiled ASH as
> well. Problem is gone on three machines.
>
> Thanks, Frank (and Yadin).
>
> If you're interested in pre-re-compiled binaries, check out
> ftp://ftp.erdelynet.com/ftp/downloads/bash.exe.gz and
> ftp://ftp.erdelynet.com/ftp/downloads/sh.exe.gz . If you want some
> information about installing these files, look at
> http://mike.erdelynet.com/sshd-error.asp#solution .
>
> One note, when I re-compiled bash, I had to create _distribution and
> _patchlevel files to work. After doing so, though, I was successful.
>
> Please let me know if you have any questions/comments,
> Mike Erdely
> mailto:mike@erdelynet.com
> http://mike.erdelynet.com/
I downloaded your binaries and was about to install Cygwin 1.1.7 and try
them, until I cycled through the versions available in the Setup list
and found that the mirrors are no longer carrying 1.1.5, only 1.1.6 and
1.1.7. That means that, if I try it and it doesn't work, I have no way
to revert to the last working version. I can't risk that.
To the Cygwin/Red Hat people: Please, could you make 1.1.5 available
until the sshd problem is resolved?
--
Ross Smith <ross.s@ihug.co.nz> The Internet Group, Auckland, New Zealand
========================================================================
"Normally he was insane, but he had lucid moments
when he was merely stupid." -- Heinrich Heine
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: Cygwin commands crashes after ssh login
2001-01-25 12:25 ` Ross Smith
@ 2001-01-25 12:34 ` Larry Hall (RFK Partners, Inc)
2001-01-25 13:57 ` Ross Smith
2001-01-25 13:36 ` Erdely, Michael
1 sibling, 1 reply; 222+ messages in thread
From: Larry Hall (RFK Partners, Inc) @ 2001-01-25 12:34 UTC (permalink / raw)
To: Ross Smith, cygwin
At 03:25 PM 1/25/2001, Ross Smith wrote:
>"Erdely, Michael" wrote:
> >
> > Frank's recompilation success has been repeated. And, I recompiled ASH as
> > well. Problem is gone on three machines.
> >
> > Thanks, Frank (and Yadin).
> >
> > If you're interested in pre-re-compiled binaries, check out
> > ftp://ftp.erdelynet.com/ftp/downloads/bash.exe.gz and
> > ftp://ftp.erdelynet.com/ftp/downloads/sh.exe.gz . If you want some
> > information about installing these files, look at
> > http://mike.erdelynet.com/sshd-error.asp#solution .
> >
> > One note, when I re-compiled bash, I had to create _distribution and
> > _patchlevel files to work. After doing so, though, I was successful.
> >
> > Please let me know if you have any questions/comments,
> > Mike Erdely
> > mailto:mike@erdelynet.com
> > http://mike.erdelynet.com/
>
>I downloaded your binaries and was about to install Cygwin 1.1.7 and try
>them, until I cycled through the versions available in the Setup list
>and found that the mirrors are no longer carrying 1.1.5, only 1.1.6 and
>1.1.7. That means that, if I try it and it doesn't work, I have no way
>to revert to the last working version. I can't risk that.
>
>To the Cygwin/Red Hat people: Please, could you make 1.1.5 available
>until the sshd problem is resolved?
You can always save your current cygwin1.dll as a backup...
Larry Hall lhall@rfk.com
RFK Partners, Inc. http://www.rfk.com
118 Washington Street (508) 893-9779 - RFK Office
Holliston, MA 01746 (508) 893-9889 - FAX
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: Cygwin commands crashes after ssh login
2001-01-25 12:34 ` Larry Hall (RFK Partners, Inc)
@ 2001-01-25 13:57 ` Ross Smith
2001-01-25 15:00 ` Larry Hall (RFK Partners, Inc)
0 siblings, 1 reply; 222+ messages in thread
From: Ross Smith @ 2001-01-25 13:57 UTC (permalink / raw)
To: cygwin
"Larry Hall (RFK Partners, Inc)" wrote:
>
> At 03:25 PM 1/25/2001, Ross Smith wrote:
> >
> >I downloaded your binaries and was about to install Cygwin 1.1.7 and try
> >them, until I cycled through the versions available in the Setup list
> >and found that the mirrors are no longer carrying 1.1.5, only 1.1.6 and
> >1.1.7. That means that, if I try it and it doesn't work, I have no way
> >to revert to the last working version. I can't risk that.
> >
> >To the Cygwin/Red Hat people: Please, could you make 1.1.5 available
> >until the sshd problem is resolved?
>
> You can always save your current cygwin1.dll as a backup...
Oh, thanks. I didn't realise that was all that was involved; I'd been
assuming that the package called "Cygwin" would be a big chunk of the
system with a whole bunch of files.
--
Ross Smith <ross.s@ihug.co.nz> The Internet Group, Auckland, New Zealand
========================================================================
"Normally he was insane, but he had lucid moments
when he was merely stupid." -- Heinrich Heine
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: Cygwin commands crashes after ssh login
2001-01-25 13:57 ` Ross Smith
@ 2001-01-25 15:00 ` Larry Hall (RFK Partners, Inc)
0 siblings, 0 replies; 222+ messages in thread
From: Larry Hall (RFK Partners, Inc) @ 2001-01-25 15:00 UTC (permalink / raw)
To: Ross Smith, cygwin
At 04:57 PM 1/25/2001, Ross Smith wrote:
>"Larry Hall (RFK Partners, Inc)" wrote:
> >
> > At 03:25 PM 1/25/2001, Ross Smith wrote:
> > >
> > >I downloaded your binaries and was about to install Cygwin 1.1.7 and try
> > >them, until I cycled through the versions available in the Setup list
> > >and found that the mirrors are no longer carrying 1.1.5, only 1.1.6 and
> > >1.1.7. That means that, if I try it and it doesn't work, I have no way
> > >to revert to the last working version. I can't risk that.
> > >
> > >To the Cygwin/Red Hat people: Please, could you make 1.1.5 available
> > >until the sshd problem is resolved?
> >
> > You can always save your current cygwin1.dll as a backup...
>
>Oh, thanks. I didn't realise that was all that was involved; I'd been
>assuming that the package called "Cygwin" would be a big chunk of the
>system with a whole bunch of files.
There's more in the package but for your purposes, this is the most important
change. You probably won't notice any difference in anything else. However,
if you're concerned (paraniod?;-)), you can always backup everything that
comes in the 1.1.7 cygwin tar ball and then you'll have exactly what was in
1.1.5.
Larry Hall lhall@rfk.com
RFK Partners, Inc. http://www.rfk.com
118 Washington Street (508) 893-9779 - RFK Office
Holliston, MA 01746 (508) 893-9889 - FAX
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: Cygwin commands crashes after ssh login
2001-01-25 12:25 ` Ross Smith
2001-01-25 12:34 ` Larry Hall (RFK Partners, Inc)
@ 2001-01-25 13:36 ` Erdely, Michael
2001-01-25 14:30 ` Earnie Boyd
1 sibling, 1 reply; 222+ messages in thread
From: Erdely, Michael @ 2001-01-25 13:36 UTC (permalink / raw)
To: cygwin
Look at http://mike.erdelynet.com/sshd-error.asp#solution . This will
explain how to install cygwin-1.1.5-7.
-ME
----- Original Message -----
From: "Ross Smith" <ross.s@ihug.co.nz>
To: <cygwin@cygwin.com>
Sent: Thursday, January 25, 2001 3:25 PM
Subject: Re: Cygwin commands crashes after ssh login
> "Erdely, Michael" wrote:
> >
> > Frank's recompilation success has been repeated. And, I recompiled ASH
as
> > well. Problem is gone on three machines.
> >
> > Thanks, Frank (and Yadin).
> >
> > If you're interested in pre-re-compiled binaries, check out
> > ftp://ftp.erdelynet.com/ftp/downloads/bash.exe.gz and
> > ftp://ftp.erdelynet.com/ftp/downloads/sh.exe.gz . If you want some
> > information about installing these files, look at
> > http://mike.erdelynet.com/sshd-error.asp#solution .
> >
> > One note, when I re-compiled bash, I had to create _distribution and
> > _patchlevel files to work. After doing so, though, I was successful.
> >
> > Please let me know if you have any questions/comments,
> > Mike Erdely
> > mailto:mike@erdelynet.com
> > http://mike.erdelynet.com/
>
> I downloaded your binaries and was about to install Cygwin 1.1.7 and try
> them, until I cycled through the versions available in the Setup list
> and found that the mirrors are no longer carrying 1.1.5, only 1.1.6 and
> 1.1.7. That means that, if I try it and it doesn't work, I have no way
> to revert to the last working version. I can't risk that.
>
> To the Cygwin/Red Hat people: Please, could you make 1.1.5 available
> until the sshd problem is resolved?
>
> --
> Ross Smith <ross.s@ihug.co.nz> The Internet Group, Auckland, New Zealand
> ========================================================================
> "Normally he was insane, but he had lucid moments
> when he was merely stupid." -- Heinrich Heine
>
> --
> Want to unsubscribe from this list?
> Check out: http://cygwin.com/ml/#unsubscribe-simple
>
>
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: Cygwin commands crashes after ssh login
2001-01-25 13:36 ` Erdely, Michael
@ 2001-01-25 14:30 ` Earnie Boyd
2001-01-25 14:52 ` Erdely, Michael
0 siblings, 1 reply; 222+ messages in thread
From: Earnie Boyd @ 2001-01-25 14:30 UTC (permalink / raw)
To: Erdely, Michael; +Cc: cygwin
"Erdely, Michael" wrote:
>
> Look at http://mike.erdelynet.com/sshd-error.asp#solution . This will
> explain how to install cygwin-1.1.5-7.
>
And if you have problems, please email Mike privately.
Earnie.
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: Cygwin commands crashes after ssh login
2001-01-25 14:30 ` Earnie Boyd
@ 2001-01-25 14:52 ` Erdely, Michael
2001-01-25 16:30 ` Earnie Boyd
0 siblings, 1 reply; 222+ messages in thread
From: Erdely, Michael @ 2001-01-25 14:52 UTC (permalink / raw)
To: Earnie Boyd
Is there a reason 1. that you sent this to me directly? and 2. why you felt
the need to say anything at all?
-ME
----- Original Message -----
From: "Earnie Boyd" <earnie_boyd@yahoo.com>
To: "Erdely, Michael" <mike@erdelynet.com>
Cc: <cygwin@cygwin.com>
Sent: Thursday, January 25, 2001 5:31 PM
Subject: Re: Cygwin commands crashes after ssh login
> "Erdely, Michael" wrote:
> >
> > Look at http://mike.erdelynet.com/sshd-error.asp#solution . This will
> > explain how to install cygwin-1.1.5-7.
> >
>
> And if you have problems, please email Mike privately.
>
> Earnie.
>
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
>
>
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: Cygwin commands crashes after ssh login
2001-01-25 14:52 ` Erdely, Michael
@ 2001-01-25 16:30 ` Earnie Boyd
0 siblings, 0 replies; 222+ messages in thread
From: Earnie Boyd @ 2001-01-25 16:30 UTC (permalink / raw)
To: Erdely, Michael; +Cc: Earnie Boyd
"Erdely, Michael" wrote:
>
> Is there a reason 1. that you sent this to me directly?
I `Replied All' you just happened to be the To and the list the Cc.
> and 2. why you felt the need to say anything at all?
>
This list supports the Cygwin distributions available via the "Install
Cygwin Now" icon at http://cygwin.com . If you're providing independent
distributions of the cygwin1.dll then you must resolve the problems. If
someone has a problem with older versions of Cygwin then the immediate
response will be to update via the "Install Cygwin Now" icon. If
someone acknowledges that they received the package from a private site
they will be immediately redirected to the site owner. I was being
proactive.
Earnie.
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: Cygwin commands crashes after ssh login
@ 2001-01-17 7:08 Yadin Goldschmidt
2001-01-18 6:10 ` Corinna Vinschen
0 siblings, 1 reply; 222+ messages in thread
From: Yadin Goldschmidt @ 2001-01-17 7:08 UTC (permalink / raw)
To: cygwin
Corina,
Here is the problem: I am running NT4.o sp6. cygwin 1.1.7
1. Im running sshd using srvany from a user who is part of administrator
group
2. This user has all the additional previleges.
3. There is a line in NT environment:
CYGWIN = ntsec tty
4. The files in /etc belong to user.Administrators where 'user' is
the user account from which sshd is run.
5. Everything is fine when I login as that user and use password
authentication. But when I login usind a different account an exception
occurs. Here is the debug from ssh -v. I only replaced the machine name by
XXX.XXX
$ssh -v XXX.XXX -l Administrator
SSH Version OpenSSH_2.3.0p1, protocol versions 1.5/2.0.
Compiled with SSL (0x0090581f).
debug: Reading configuration data /etc/ssh_config
debug: Applying options for *
debug: Seeding random number generator
debug: ssh_connect: getuid 1000 geteuid 1000 anon 0
debug: Connecting to XXX.XXX [XXX.XXX.XXX.XX] port 22.
debug: Seeding random number generator
debug: Allocated local port 955.
debug: Connection established.
debug: Remote protocol version 1.99, remote software version OpenSSH_2.3.0p1
debug: no match: OpenSSH_2.3.0p1
debug: Local version string SSH-1.5-OpenSSH_2.3.0p1
debug: Waiting for server public key.
debug: Received server public key (768 bits) and host key (1024 bits).
debug: Host 'XXX.XXX' is known and matches the RSA host key.
debug: Seeding random number generator
debug: Encryption type: 3des
debug: Sent encrypted session key.
debug: Installing crc compensation attack detector.
debug: Received encrypted confirmation.
debug: Doing password authentication.
Administrator@XXX.XXX's password:
debug: Requesting pty.
debug: Requesting shell.
debug: Entering interactive session.
0 [main] ?a 0 handle_exceptions: Exception: STATUS_ACCESS_VIOLATION
Exception: STATUS_ACCESS_VIOLATION at eip=61001B87
eax=00000069 ebx=352E3673 ecx=00000000 edx=352E367B esi=00000000
edi=0240FF74
ebp=0240FC2C esp=0240FECC program=?a
cs=001B ds=0023 es=0023 fs=0038 gs=0000 ss=0023
Stack trace:
Frame Function Args
0240FC2C 61001B87 (00000000, 00000000, 00000000, 00000000)
0240FEF4 61001B87 (00000038, 61000001, 0240FF44, 610032C9)
0240FF44 610033D8 (004072CC, 6107C13C, 00000000, 00000000)
0240FF74 61003AAD (00000000, 00000000, 00000000, 00000000)
0240FF94 61003AEC (00407230, 004011D0, 0240FFC0, 00401038)
0240FFA4 00405206 (004011D0, 8011C6C8, 77F1B9E7, FFFFFFFE)
0240FFC0 00401038 (00000000, 00000000, 7FFDF000, 7FFDF000)
0240FFF0 77F1B9EA (00401000, 00000000, 000000B0, 00000100)
In addition a Dr. Watson box appears with the following information:
id.exe
Exception: access violation (0xc0000005), Address 0x610045f4
Yadin.
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 222+ messages in thread
* [ANN] PW32 the (alternative) Posix-over-Win32 layer 0.3.0 released
@ 2000-03-13 5:16 Paul Sokolovsky
2000-03-13 8:05 ` Chris Faylor
0 siblings, 1 reply; 222+ messages in thread
From: Paul Sokolovsky @ 2000-03-13 5:16 UTC (permalink / raw)
To: cygwin
Hello cygwin,
I would like to introduce to gnu-win32 community new (yet
another) POSIX "emulation" layer. It is product of some thoughts and
ideas that were spoken, and sufficiently criticized, on cygwin list.
Standard description follows:
"PW32 is implementation of (subset of) POSIX/Unix API for Win32 systems. Its main
concerns are efficiency and full platform coverage, including adequate support for low-end
Win9x systems. PW32 is based on DJGPP's runtime library by DJ Delorie. PW32 is licensed
under LGPL."
PW32 is only month on public, but before that it was more than
year in development. That means it'd already has something to show,
though of course it's far from being complete. Also, as I hinted above,
it's based on solutions that might be considered questionable, if not
orthodox. Even besides that, I claim that their sole purpose is to get
rid of mean, chore problems plaguing existing implementations, and to
get efficient implementation. So, I took steps to describe these
traits, and provide means of coping with them and integrating with
"native" environment.
0.3.0 is second public and first 'full-fledged' (as for alpha)
release. Changes include:
* Many bugfixes.
* Tested and runs on 9x and NT. On 95, problems known and identified,
with workarounds provided.
* Binaries provided: build environment based on gcc-2.95.2-1-mingw32
(courtesy of Mumit Khan), ash, fileutils, textutils, sed, grep,
sh-utils, diffutils, make.
* Updated documentation.
Also, PW32 is currently in active development, for example, now
two serious problems with 0.3.0 had been fixed (and available from CVS).
PW32 is hosted on SourceForge, http://pw32.sourceforge.net/
Place to discuss PW32 is mingw32 mailing list,
http://www.egroups.com/list/mingw32
--
Paul Sokolovsky, IT Specialist
http://www.brainbench.com/transcript.jsp?pid=11135
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: [ANN] PW32 the (alternative) Posix-over-Win32 layer 0.3.0 released
2000-03-13 5:16 [ANN] PW32 the (alternative) Posix-over-Win32 layer 0.3.0 released Paul Sokolovsky
@ 2000-03-13 8:05 ` Chris Faylor
2000-03-13 9:03 ` Dr. Volker Zell
` (2 more replies)
0 siblings, 3 replies; 222+ messages in thread
From: Chris Faylor @ 2000-03-13 8:05 UTC (permalink / raw)
To: cygwin
Hmm. I would like to receive opinions on whether people consider this
announcement to be off-topic.
We don't see any DJGPP announcments here. We don't see any UWIN or Interix
traffic. Maybe I'm wrong, but I don't think that Mikey announced here, either.
(How's that for giving a plug to all of cygwin's competitors?)
I don't think that announcements of (alternative) Posix-over-Win32 layers are
on topic here but if everyone else disagrees, my opinion can be changed.
cgf
On Mon, Mar 13, 2000 at 03:10:26PM +0200, Paul Sokolovsky wrote:
>I would like to introduce to gnu-win32 community new (yet another)
>POSIX "emulation" layer. It is product of some thoughts and ideas that
>were spoken, and sufficiently criticized, on cygwin list. Standard
>description follows:
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: [ANN] PW32 the (alternative) Posix-over-Win32 layer 0.3.0 released
2000-03-13 8:05 ` Chris Faylor
@ 2000-03-13 9:03 ` Dr. Volker Zell
2000-03-13 10:05 ` Re[2]: " Paul Sokolovsky
2000-03-13 15:01 ` Michael Hirmke
2 siblings, 0 replies; 222+ messages in thread
From: Dr. Volker Zell @ 2000-03-13 9:03 UTC (permalink / raw)
To: cygwin
>>>>> "Chris" == Chris Faylor <cgf@cygnus.com> writes:
Chris> Hmm. I would like to receive opinions on whether people consider this
Chris> announcement to be off-topic.
It's off-topic.
Ciao
Volker
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re[2]: [ANN] PW32 the (alternative) Posix-over-Win32 layer 0.3.0 released
2000-03-13 8:05 ` Chris Faylor
2000-03-13 9:03 ` Dr. Volker Zell
@ 2000-03-13 10:05 ` Paul Sokolovsky
2000-03-13 15:01 ` Michael Hirmke
2 siblings, 0 replies; 222+ messages in thread
From: Paul Sokolovsky @ 2000-03-13 10:05 UTC (permalink / raw)
To: Chris Faylor
Hello Chris,
Chris Faylor <cgf@cygnus.com> wrote:
CF> Hmm. I would like to receive opinions on whether people consider this
CF> announcement to be off-topic.
CF> We don't see any DJGPP announcments here. We don't see any UWIN or Interix
CF> traffic. Maybe I'm wrong, but I don't think that Mikey announced here, either.
CF> (How's that for giving a plug to all of cygwin's competitors?)
CF> I don't think that announcements of (alternative) Posix-over-Win32 layers are
CF> on topic here but if everyone else disagrees, my opinion can be changed.
I greatly appologize! I wanted to include these possible
appologies in original announcement, but just thought: after all, we
all doing same thing, namely gnu-win32 (btw, isn't that trademark of
Cygnus, the Red Hat company?). While this list is of course dedicated
and owned by cygwin, it's de-facto mother list of all
Unix/Gnu-on-win32 lists, and have grown others (such as mingw32) off
itself. I also think my little stuff indebted to cygwin by its birth,
and hoped I could use that wonderful possibility - to announce it
once, and rejoice cygwin people with that announcement. And of course, my
little stuff is not competitor of cygwin (competitor? ridiculous. have
years of work of many people were put into it? does it offer that level
of support?), but rather an (spiritual) offspring targeted at niche
intentinally left out by cygwin. After all, that's what free software
is all about.
I once again would like to say that was one-time announcemnt for
information of gnu-win32 comminity. Under no circumstances I planned
to continue that announcing or start discussions here. If even that
was illicit, I would like to ask pardon from all cygwin community.
Thank you for your support.
CF> cgf
--
Paul Sokolovsky, IT Specialist
http://www.brainbench.com/transcript.jsp?pid=11135
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: [ANN] PW32 the (alternative) Posix-over-Win32 layer 0.3.0 released
2000-03-13 8:05 ` Chris Faylor
2000-03-13 9:03 ` Dr. Volker Zell
2000-03-13 10:05 ` Re[2]: " Paul Sokolovsky
@ 2000-03-13 15:01 ` Michael Hirmke
2000-03-13 15:05 ` Chris Faylor
2 siblings, 1 reply; 222+ messages in thread
From: Michael Hirmke @ 2000-03-13 15:01 UTC (permalink / raw)
To: cygwin
Hi Chris,
>Hmm. I would like to receive opinions on whether people consider this
>announcement to be off-topic.
>
[...]
>I don't think that announcements of (alternative) Posix-over-Win32 layers are
>on topic here but if everyone else disagrees, my opinion can be changed.
As long as an announcement is the only traffic generated by such an
alternative to Cygwin I'd be interested to read it in here.
>
>cgf
Bye.
Michael.
--
Michael Hirmke | Telefon +49 (911) 557999
Georg-Strobel-Strasse 81 | FAX +49 (911) 557664
90489 Nuernberg | E-Mail mailto:mh@mike.franken.de
| WWW http://aquarius.franken.de/
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: [ANN] PW32 the (alternative) Posix-over-Win32 layer 0.3.0 released
2000-03-13 15:01 ` Michael Hirmke
@ 2000-03-13 15:05 ` Chris Faylor
0 siblings, 0 replies; 222+ messages in thread
From: Chris Faylor @ 2000-03-13 15:05 UTC (permalink / raw)
To: cygwin
On Mon, Mar 13, 2000 at 11:56:00PM +0200, Michael Hirmke wrote:
>Hi Chris,
>
>>Hmm. I would like to receive opinions on whether people consider this
>>announcement to be off-topic.
>>
>[...]
>>I don't think that announcements of (alternative) Posix-over-Win32 layers are
>>on topic here but if everyone else disagrees, my opinion can be changed.
>
>As long as an announcement is the only traffic generated by such an
>alternative to Cygwin I'd be interested to read it in here.
There is no way to guarantee that.
cgf
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 222+ messages in thread
* uudecode?
@ 1999-01-31 23:52 John Cooper
1999-01-31 23:52 ` uudecode? Michael Hirmke
1999-01-31 23:52 ` uudecode? Corinna Vinschen
0 siblings, 2 replies; 222+ messages in thread
From: John Cooper @ 1999-01-31 23:52 UTC (permalink / raw)
To: gnu-win32
Can anyone point me to a reliable version of the command line
uudecode.exe/uuencode.exe utilities for NT 4.0?
Thanks,
--- John
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: uudecode?
1999-01-31 23:52 uudecode? John Cooper
@ 1999-01-31 23:52 ` Michael Hirmke
1999-01-31 23:52 ` uudecode? John Cooper
1999-01-31 23:52 ` uudecode? Corinna Vinschen
1 sibling, 1 reply; 222+ messages in thread
From: Michael Hirmke @ 1999-01-31 23:52 UTC (permalink / raw)
To: gnu-win32
Hi John,
>
>Can anyone point me to a reliable version of the command line
>uudecode.exe/uuencode.exe utilities for NT 4.0?
Don't know, what you mean by reliable, but you can get the
sharutils-4.2c package, which contains uuencode/uudecode among other
utilities
- on ftp.franken.de
- in /pub/win32/develop/gnuwin32/cygwin32/porters/Hirmke_Michael/B20
- as sharutils-4.2c-cygwin-b20-bin.tar.gz
- or sharutils-4.2c-cygwin-b20-bin.zip
>
>Thanks,
>
> --- John
Bye.
Michael.
--
Michael Hirmke | Telefon +49 (911) 557999
Georg-Strobel-Strasse 81 | FAX +49 (911) 557664
90489 Nuernberg | E-Mail mailto:mh@mike.franken.de
| WWW http://aquarius.franken.de/
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: uudecode?
1999-01-31 23:52 ` uudecode? Michael Hirmke
@ 1999-01-31 23:52 ` John Cooper
1999-01-31 23:52 ` uudecode? root
1999-01-31 23:52 ` uudecode? Glenn Spell
0 siblings, 2 replies; 222+ messages in thread
From: John Cooper @ 1999-01-31 23:52 UTC (permalink / raw)
To: Michael Hirmke; +Cc: gnu-win32
mh@mike.franken.de (Michael Hirmke) writes:
> >Can anyone point me to a reliable version of the command line
> >uudecode.exe/uuencode.exe utilities for NT 4.0?
>
> Don't know, what you mean by reliable, but you can get the sharutils-4.2c
> package, which contains uuencode/uudecode among other utilities
These just don't work at all:
$ cp c:/WINNT/NOTEPAD.EXE n.exe
$ ./n.exe # works fine!
$ uuencode n.exe n.exe > n.uu
$ rm n.exe
$ ls n.*
n.uu
$ uudecode n.uu
$ ls n.*
n.exe* n.uu
$ ./n.exe
zsh: exec format error: .\n.exe
$
$ ls -l n.exe
-rwxrwxrwx 1 JCooper Domain_Users 594 Jan 18 10:37 n.exe*
$
Any ideas what's wrong with it?
Thanks,
--- John
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: uudecode?
1999-01-31 23:52 ` uudecode? John Cooper
@ 1999-01-31 23:52 ` root
1999-01-31 23:52 ` uudecode? John Cooper
1999-01-31 23:52 ` uudecode? John Cooper
1999-01-31 23:52 ` uudecode? Glenn Spell
1 sibling, 2 replies; 222+ messages in thread
From: root @ 1999-01-31 23:52 UTC (permalink / raw)
To: John Cooper; +Cc: gnu-win32
Let's stop this uuencode/decode discussion.
Here are two small little programs in that old but powerful language we all
know somehow.
------------------------------------------------------cut here: uuencode.c
#include <stdio.h>
#define ENC(c) ((c) ? ((c) & 077) + ' ': '`')
static int uuencode(char *nom) /* nom means 'name' in french :-) */
{
int ch, n, idx;
register char *p;
char buf[80], outbuf[250];
FILE *in;
if ((in = fopen(nom, "rb")) == NULL)
return 1; /* please add some error checking/reporting */
printf("begin 0666 %s\n",nom);/* note: no attempt to fake any permissions */
while ((n = fread(buf, 1, 45, in)) != 0) {
idx = 0;
outbuf[idx++] = ENC(ch);
for (p = buf; n > 0; n -= 3, p += 3) {
ch = *p >> 2;
ch = ENC(ch);
outbuf[idx++] = ch;
ch = ((*p << 4) & 060) | ((p[1] >> 4) & 017);
ch = ENC(ch);
outbuf[idx++] = ch;
ch = ((p[1] << 2) & 074) | ((p[2] >> 6) & 03);
ch = ENC(ch);
outbuf[idx++] = ch;
ch = p[2] & 077;
ch = ENC(ch);
outbuf[idx++] = ch;
}
outbuf[idx++] = '\n';
outbuf[idx] = 0;
printf("%s", outbuf);
}
printf("%c\nend\n", ENC(0));
fclose(in);
return 0;
}
int main(int argc, char *argv[]) // add error checking here if you feel like
{
return uuencode(argv[1]);
}
---------------------------------------------------cut here uudecode.c
#include <stdio.h>
#include <string.h>
#define DEC(c) (((c) - ' ') & 077)
static int uudecode(char *fname)
{
register int n;
register char ch, *p;
char buf[2 * BUFSIZ],outname[512];
FILE *out, *in = fopen(fname, "rb");
if (in == NULL) {
fprintf(stderr,"Impossible to open %s\n",fname);
return 1;
}
while (fgets(buf, 80, in)) {
if (!strncmp(buf, "begin", 5))
goto decodeStart;
}
fprintf(stderr,"No 'begin' line found in %s\n",fname);
return 1;
decodeStart:
p = buf + sizeof("begin");
while (*p == ' ' || *p == '\t')
p++;
while (*p >= '0' && *p <= '9') // ignore any permissions setting
p++;
while (*p == ' ' || *p == '\t')
p++;
strcpy(outname, p);
p = outname;
while (*p >= ' ') // This supposes file name chars are >= ' '
p++;
*p = 0;
out = fopen(outname, "wb");
if (out == NULL) {
fprintf(stderr,"Impossible to open %s\n",outname);
return 1;
}
while (1) {
if (!fgets(buf, 80, in))
break;
if (!strncmp(buf, "end\r\n", 5))
break;
p = buf;
n = DEC(*p);
if (n <= 0)
break;
for (++p; n > 0; p += 4, n -= 3) {
if (n >= 3) {
ch = DEC(p[0]) << 2 | DEC(p[1]) >> 4;
fputc(ch, out);
ch = DEC(p[1]) << 4 | DEC(p[2]) >> 2;
fputc(ch, out);
ch = DEC(p[2]) << 6 | DEC(p[3]);
fputc(ch, out);
}
else {
if (n >= 1) {
ch = DEC(p[0]) << 2 | DEC(p[1]) >> 4;
fputc(ch, out);
}
if (n >= 2) {
ch = DEC(p[1]) << 4 | DEC(p[2]) >> 2;
fputc(ch, out);
}
}
}
}
fclose(out);
fclose(in);
return 0;
}
int main(int argc, char *argv[]) // Add error checking here if you feel like
{
return uudecode(argv[1]);
}
---------------------------------------------------------------------------
enjoy!
--
Jacob Navia Logiciels/Informatique
41 rue Maurice Ravel Tel 01 48.23.51.44
93430 Villetaneuse Fax 01 48.23.95.39
France
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: uudecode?
1999-01-31 23:52 ` uudecode? root
@ 1999-01-31 23:52 ` John Cooper
1999-01-31 23:52 ` uudecode? Pierre A. Humblet
1999-01-31 23:52 ` uudecode? John Cooper
1 sibling, 1 reply; 222+ messages in thread
From: John Cooper @ 1999-01-31 23:52 UTC (permalink / raw)
To: root; +Cc: John Cooper, gnu-win32
root@jacob.remcomp.fr (root) writes:
> Let's stop this uuencode/decode discussion. Here are two small little
> programs in that old but powerful language we all know somehow.
This source simply doesn't work for me - it generates all sorts of different
characters at the beginning of encoded lines, rather than the "M" that I see
with most uuencoders.
I finally pulled over the sharutils-4.2 source, got that to build under NT and
then carefully enabled (or disabled) the binary flag on the fopen calls. It
now seems to work fine - without mucking with mounts or using bash (I prefer
zsh).
Thanks for all the ideas...
--- John
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: uudecode?
1999-01-31 23:52 ` uudecode? John Cooper
@ 1999-01-31 23:52 ` Pierre A. Humblet
0 siblings, 0 replies; 222+ messages in thread
From: Pierre A. Humblet @ 1999-01-31 23:52 UTC (permalink / raw)
To: John Cooper, root; +Cc: John Cooper, gnu-win32
This has taken enough bandwidth that we might at least understand what
happened.
As stated in their README, the shareutils from ftp.franken.de require
binary mount. On a text mounted system the uuencode INPUT file gets
truncated at ^Z.
Ideally uuencode should binary open its input file AND setmode stdin to
binary (for use with cygwin shells, other shells always open stdin binary).
Similarly the output of uudecode should be binary.
It doesn't matter if the output of uuencode and the input of uudecode are
text or binary. Those programs encode the line length, usually taking in 45
characters at a time (they have to, to survive inclusion in e-mails).
uuencoded lines start with M because M is the 45th printable character
(above " "). Those 45 characters are expanded to 45 * 8/6 = 60 characters
per line, plus the length.
The uuencode.c program contributed in
http://www.cygnus.com/ml/gnu-win32/1999-Jan/0493.html has a bug: the first
ENC(ch) should have been ENC(n). That's why the uuencoded lines did not
start with M.
There is also a bug in uudecode.c
if (!strncmp(buf, "end\r\n", 5))
will fail when the file ends with "end\n". The bug is not exposed because
the program normally terminates at the next to last line, which has zero
length.
Pierre
At 02:22 PM 1/20/99 +0000, John Cooper wrote:
>I finally pulled over the sharutils-4.2 source, got that to build under NT
and
>then carefully enabled (or disabled) the binary flag on the fopen calls. It
>now seems to work fine - without mucking with mounts or using bash (I prefer
>zsh).
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: uudecode?
1999-01-31 23:52 ` uudecode? root
1999-01-31 23:52 ` uudecode? John Cooper
@ 1999-01-31 23:52 ` John Cooper
1999-01-31 23:52 ` uudecode? John Cooper
1 sibling, 1 reply; 222+ messages in thread
From: John Cooper @ 1999-01-31 23:52 UTC (permalink / raw)
To: root; +Cc: gnu-win32, john.cooper
root@jacob.remcomp.fr (root) writes:
> Let's stop this uuencode/decode discussion. Here are two small little
> programs in that old but powerful language we all know somehow.
These also don't work (see below).
This doesn't look like a "mount" problem? The cygwin FAQ states about mount:
"The '-b' option to mount mounts the mountpoint in binary mode where text and
binary files are treated equivalently. This should only be necessary for badly
ported Unix programs where binary flags are missing from open calls."
... and your code does open the files in binary mode, so shouldn't it work
regardless of mount?
It even seems to fail when I do mount a directory in binary mode...
If nobody has a solution, I guess I'll try debugging it when I get time.
--- John
$ cp c:/winnt/NOTEPAD.EXE n.exe
$ ls -l n.exe
-rwxrwxrwx 1 JCooper Domain_Users 45328 Jan 19 10:28 n.exe*
$
$ ./uuencode n.exe n.exe > n.uu
$ ls -l n.uu
-rw-rw-rw- 1 JCooper Domain_Users 62479 Jan 19 10:28 n.uu
$
$ ./uudecode n.uu
$ ls -l n.exe
-rwxrwxrwx 1 JCooper Domain_Users 261 Jan 19 10:28 n.exe*
$
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: uudecode?
1999-01-31 23:52 ` uudecode? John Cooper
@ 1999-01-31 23:52 ` John Cooper
0 siblings, 0 replies; 222+ messages in thread
From: John Cooper @ 1999-01-31 23:52 UTC (permalink / raw)
To: John Cooper; +Cc: root, gnu-win32, john.cooper
"John Cooper" <John.Cooper@citrix.com> writes:
> These also don't work (see below).
Oddly, if I use the combination of the sharutils uuencode.exe and the
uudecode.exe that I compiled from the source posted here, it works.
Other combinations don't seem to work...
I've also hacked the uudecode source to read from stdin when given no args, so
I can use uudecode.exe with Emacs' call-process-region. At last uuencoded
attachments from Outlook can be quickly decoded from pGnus!
--- John
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: uudecode?
1999-01-31 23:52 ` uudecode? John Cooper
1999-01-31 23:52 ` uudecode? root
@ 1999-01-31 23:52 ` Glenn Spell
1 sibling, 0 replies; 222+ messages in thread
From: Glenn Spell @ 1999-01-31 23:52 UTC (permalink / raw)
To: gnu-win32
John Cooper wrote:
>
> mh@mike.franken.de (Michael Hirmke) writes:
>
> > >Can anyone point me to a reliable version of the command line
> > >uudecode.exe/uuencode.exe utilities for NT 4.0?
> >
> > Don't know, what you mean by reliable, but you can get the sharutils-4.2c
> > package, which contains uuencode/uudecode among other utilities
>
> These just don't work at all:
For decode only, you might try uu.com from:
< http://www.walbeehm.com/mrcode.html >.
(That was: http://www.walbeehm.com/mrcode.html ).
-glenn
--
Glenn Spell <glenn@gs.fay.nc.us>
Fayetteville, North Carolina, U. S. A.
____________________________________________________
... blue skies ... happy trails ... sweet dreams ...
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: uudecode?
1999-01-31 23:52 uudecode? John Cooper
1999-01-31 23:52 ` uudecode? Michael Hirmke
@ 1999-01-31 23:52 ` Corinna Vinschen
1 sibling, 0 replies; 222+ messages in thread
From: Corinna Vinschen @ 1999-01-31 23:52 UTC (permalink / raw)
To: John Cooper, gnu-win32
John Cooper wrote:
>
> Can anyone point me to a reliable version of the command line
> uudecode.exe/uuencode.exe utilities for NT 4.0?
Try sharutils-4.2 from http://www.gnu.org/software/software.html
It compiles out of the box.
Corinna
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 222+ messages in thread
* long long vs long
@ 1998-07-21 1:55 Graham Murray
1998-07-22 6:17 ` Harry Broomhall
` (4 more replies)
0 siblings, 5 replies; 222+ messages in thread
From: Graham Murray @ 1998-07-21 1:55 UTC (permalink / raw)
To: 'gnu-win32@cygnus.com'
This is probably a silly question, but rather than having long long for
64 bit, why was long not made 64bit? The standard (AFAIK) states that
short <= int <= long. So, it should be possible for long to be 64 bit
rather than 32. This would give a simple progression from 8bit chars to
64bit longs.
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: long long vs long
1998-07-21 1:55 long long vs long Graham Murray
@ 1998-07-22 6:17 ` Harry Broomhall
1998-07-22 13:57 ` Nicholas R LeRoy
` (3 subsequent siblings)
4 siblings, 0 replies; 222+ messages in thread
From: Harry Broomhall @ 1998-07-22 6:17 UTC (permalink / raw)
To: Graham Murray; +Cc: gnu-win32
Graham Murray said:
>
> This is probably a silly question, but rather than having long long for
> 64 bit, why was long not made 64bit? The standard (AFAIK) states that
> short <= int <= long. So, it should be possible for long to be 64 bit
> rather than 32. This would give a simple progression from 8bit chars to
> 64bit longs.
This is a frequent question. I am told that while it would
be thoreticaly a good idea, so much existing code would break as
to make it unviable. (This from a member of the C9x committee.)
Regards,
Harry.
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: long long vs long
1998-07-21 1:55 long long vs long Graham Murray
1998-07-22 6:17 ` Harry Broomhall
@ 1998-07-22 13:57 ` Nicholas R LeRoy
1998-07-22 13:57 ` Michael H. Warfield
` (2 subsequent siblings)
4 siblings, 0 replies; 222+ messages in thread
From: Nicholas R LeRoy @ 1998-07-22 13:57 UTC (permalink / raw)
To: Graham Murray, 'gnu-win32@cygnus.com'
On Jul 21, 8:01am, Graham Murray wrote:
> Subject: long long vs long
> This is probably a silly question, but rather than having long long for
> 64 bit, why was long not made 64bit? The standard (AFAIK) states that
> short <= int <= long. So, it should be possible for long to be 64 bit
> rather than 32. This would give a simple progression from 8bit chars to
> 64bit longs.
Several reasons, actually.
Technically, it doesn't make sense, at least in the PC world, where
all processors are <=32bits. Any 64-bit operation takes 2 separate
accesses and math, etc., becomes more complicated (and requires more
instructions and time).
Probably the more pervasive reason, however, is that there exists A
LOT of code out there which expects sizeof(long)==4. It's sort-of an
un-official C standard. In particular, legacy code dealing with
networking, etc., is frequently very loaded with such assumptions.
IIRC, the original CRAY C compiler used a 32-bit long and a 64-bit
int, just because so much code had this expectation. IMHO: C should
have included standard data sizes, as well as it's generic types. It
would have made many things a lot simpler.
Just my $.02 worth.
-Nick
--
+-------------------------------+--------------------------------------------+
| /`--_ Nicholas R LeRoy | In a world without fences, Who needs Gates?|
|{ }/ Norland Corporation | ---- Experience Linux! ---- |
| \ * / W6340 Hackbarth Rd | http://www.linux.org | http://www.ssc.com |
| |___| Fort Atkinson, WI 53538 +--------------------------------------------+
| nick.leroy@norland.com | #include <disclaimer.h> |
| http://www.norland.com/~nleroy | These are my own ideas, not my employer's. |
+----------------------------------------------------------------------------+
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: long long vs long
1998-07-21 1:55 long long vs long Graham Murray
1998-07-22 6:17 ` Harry Broomhall
1998-07-22 13:57 ` Nicholas R LeRoy
@ 1998-07-22 13:57 ` Michael H. Warfield
1998-07-23 6:15 ` Harry Broomhall
` (3 more replies)
1998-07-22 16:50 ` Michael Weiser
1998-07-22 17:12 ` Andrew Sharp
4 siblings, 4 replies; 222+ messages in thread
From: Michael H. Warfield @ 1998-07-22 13:57 UTC (permalink / raw)
To: Graham Murray; +Cc: gnu-win32
Graham Murray enscribed thusly:
> This is probably a silly question, but rather than having long long for
> 64 bit, why was long not made 64bit? The standard (AFAIK) states that
> short <= int <= long. So, it should be possible for long to be 64 bit
> rather than 32. This would give a simple progression from 8bit chars to
> 64bit longs.
Unfortunately the standard also specifies the length of several
types. Specifically char is 8 bits, short is 16 bits, and long is 32 bits.
The int type is NOT a specific length but is platform dependent, so an int
on earlier (XENIX and MS-DOS) systems use to be 16 bits while on modern
systems it's 32 bits. Specifically, an int is defined as the "native"
integer number representation. Of course, all of these types are "signed"
and have "unsigned" equivalences. And before have the list jumps on me,
yes I know that unsigned and signed char's get into some interesting
ambiguities, particularly with old code that assumed that a char was
unsigned...
Most code uses "int" where it wants the native number
representation. That same code uses "short" and "long" where it wants
specific field lengths. Imagine the havock that will transpire in code
with masks such as "foo = bar & 0xffff0000L" if you were to expand
long to be 64 bits. The porting nightmare would make a sequel to
"Nightmare on Elm Street".
Mike
--
Michael H. Warfield | (770) 985-6132 | mhw@WittsEnd.com
(The Mad Wizard) | (770) 925-8248 | http://www.wittsend.com/mhw/
NIC whois: MHW9 | An optimist believes we live in the best of all
PGP Key: 0xDF1DD471 | possible worlds. A pessimist is sure of it!
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: long long vs long
1998-07-22 13:57 ` Michael H. Warfield
@ 1998-07-23 6:15 ` Harry Broomhall
1998-07-23 13:02 ` Matthew Donadio
` (2 subsequent siblings)
3 siblings, 0 replies; 222+ messages in thread
From: Harry Broomhall @ 1998-07-23 6:15 UTC (permalink / raw)
To: Michael H. Warfield; +Cc: GMurray, gnu-win32
Michael H. Warfield said:
>
[SNIP]
> Unfortunately the standard also specifies the length of several
> types.
Really? Can you give the paras where it does this? AFAIK
short, int and long are nowhere defined in length.
Regards,
Harry.
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: long long vs long
1998-07-22 13:57 ` Michael H. Warfield
1998-07-23 6:15 ` Harry Broomhall
@ 1998-07-23 13:02 ` Matthew Donadio
1998-07-23 15:30 ` Timothy Writer
1998-07-24 12:58 ` Benjamin Riefenstahl
3 siblings, 0 replies; 222+ messages in thread
From: Matthew Donadio @ 1998-07-23 13:02 UTC (permalink / raw)
To: Michael H. Warfield; +Cc: gnu-win32
Michael H. Warfield wrote:
> Unfortunately the standard also specifies the length of several
> types. Specifically char is 8 bits, short is 16 bits, and long is 32 bits.
Not to be picky, but to quote K&R II pg. 36:
"Each compiler is free to choose appropriate sizes for its own hardware,
subject only to the restriction that shorts and ints are at least 16
bits, longs are at least 32 bits, and short is no longer than int, which
is no longer than long."
Also, chars are not limited to be only 8 bits, but they must be at least
8 bits. I routinely work on processors (C40, C44) where CHAR_BIT is
32. This results in the pecularity that
sizeof(char) = sizeof(long) = 1
which is perfectly legal. I think there is a lot more code in the world
that asumes that CHAR_BIT is 8 than sizeof(long) is 4.
--
Matt Donadio (donadio@isptechinc.com) | 43 Leopard Rd, Suite 102
Sr. Software Engineer | Paoli, PA 19301-1552
Image & Signal Processing, Inc. | Phone: +1 610 407 4391
http://www.isptechinc.com | FAX: +1 610 407 4405
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: long long vs long
1998-07-22 13:57 ` Michael H. Warfield
1998-07-23 6:15 ` Harry Broomhall
1998-07-23 13:02 ` Matthew Donadio
@ 1998-07-23 15:30 ` Timothy Writer
1998-07-24 12:58 ` Matthew Donadio
1998-07-25 0:08 ` Larry Hall
1998-07-24 12:58 ` Benjamin Riefenstahl
3 siblings, 2 replies; 222+ messages in thread
From: Timothy Writer @ 1998-07-23 15:30 UTC (permalink / raw)
To: Michael H. Warfield; +Cc: Graham Murray, gnu-win32
"Michael H. Warfield" <mhw@alcove.wittsend.com> writes:
> Graham Murray enscribed thusly:
> > This is probably a silly question, but rather than having long long for
> > 64 bit, why was long not made 64bit? The standard (AFAIK) states that
> > short <= int <= long. So, it should be possible for long to be 64 bit
> > rather than 32. This would give a simple progression from 8bit chars to
> > 64bit longs.
>
> Unfortunately the standard also specifies the length of several
> types. Specifically char is 8 bits, short is 16 bits, and long is 32 bits.
The standard says no such thing. In section 5.2.4.2.1 Sizes of integral
types <limits.h>, it says
The values given below shall be replaced by constant expressions
suitable for use in #if preprocessing directives.... Their
implementation defined values shall be EQUAL or GREATER [emphasis
mine] in magnitude (absolute value) to those shown, with the same
sign.
-- number of bits for smallest object that is not a bit field (byte)
CHAR_BIT 8
....
-- minimum value for an object of type short int
SHRT_MIN -32767
-- maximum value for an object of type short int
SHRT_MAX +32767
....
-- minimum value for an object of type int
INT_MIN -32767
-- maximum value for an object of type int
INT_MAX +32767
....
-- minimum value for an object of type long int
LONG_MIN -2147483647
-- maximum value for an object of type long int
LONG_MAX +2147483647
The first paragraph clearly states that these values are implementation
defined and that the sample values are suitable minimums.
Furthermore, in section 6.1.2.5 the Standard states, "There are four signed
integer types, designated as signed char, short int, int, and long int." It
then goes on to say, "In the list of signed integer types above, the range of
values of each type is a subrange of the values of the next type in the
list."
In other words,
sizeof(char) <= sizeof(short) <= sizeof(int) <= sizeof(long)
and
sizeof(char) == 1
sizeof(short) >= 2
sizeof(int) >= 2
sizeof(long) >= 4
While I agree that there is a large body of code that assumes long is 32
bits, such code is not portable. And not because of a flaw in the Standard,
but because the programmer(s) responsible either didn't know the above or
didn't care.
--
Tim Writer Tim.Writer@ftlsol.com
FTL Solutions Inc.
Toronto, Ontario, CANADA
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: long long vs long
1998-07-23 15:30 ` Timothy Writer
@ 1998-07-24 12:58 ` Matthew Donadio
1998-07-25 0:08 ` Larry Hall
1 sibling, 0 replies; 222+ messages in thread
From: Matthew Donadio @ 1998-07-24 12:58 UTC (permalink / raw)
To: Timothy Writer; +Cc: gnu-win32
Timothy Writer wrote:
> sizeof(char) <= sizeof(short) <= sizeof(int) <= sizeof(long)
> and
> sizeof(char) == 1
> sizeof(short) >= 2
> sizeof(int) >= 2
> sizeof(long) >= 4
Not necessarilly. By definition sizeof(char) is always 1 no matter what
CHAR_BIT is defined to be. But the values for the other sizeof's are
not correct for all machines.
For example, on the TMS320C3x and TMS320C4x families, the minimum
addressable memory unit is 32 bits, so CHAR_BIT for this machine is 32.
It also happens that all other intergral types (short, int, and long)
are 32 bits (the exact size of char), so
sizeof(char) == sizeof(short) == sizeof(int) == sizeof(long) == 1
Weird, but legal.
--
Matt Donadio (donadio@isptechinc.com) | 43 Leopard Rd, Suite 102
Sr. Software Engineer | Paoli, PA 19301-1552
Image & Signal Processing, Inc. | Phone: +1 610 407 4391
http://www.isptechinc.com | FAX: +1 610 407 4405
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: long long vs long
1998-07-23 15:30 ` Timothy Writer
1998-07-24 12:58 ` Matthew Donadio
@ 1998-07-25 0:08 ` Larry Hall
1998-07-25 1:22 ` Timothy Writer
1 sibling, 1 reply; 222+ messages in thread
From: Larry Hall @ 1998-07-25 0:08 UTC (permalink / raw)
To: Timothy Writer, Michael H. Warfield; +Cc: Graham Murray, gnu-win32
At 01:48 PM 7/23/98 -0400, Timothy Writer wrote:
>Furthermore, in section 6.1.2.5 the Standard states, "There are four signed
>integer types, designated as signed char, short int, int, and long int." It
>then goes on to say, "In the list of signed integer types above, the range of
>values of each type is a subrange of the values of the next type in the
>list."
>
>In other words,
>
> sizeof(char) <= sizeof(short) <= sizeof(int) <= sizeof(long)
>
>and
>
> sizeof(char) == 1
> sizeof(short) >= 2
> sizeof(int) >= 2
> sizeof(long) >= 4
>
Sorry but this doesn't seem to follow. I agree with the interpretation of
the standard, namely:
sizeof(char) <= sizeof(short) <= sizeof(int) <= sizeof(long)
However, this does NOT imply what follows (the sizeof lines after the "and".)
The implication from the standard is:
sizeof(char) <= sizeof(short) <= sizeof(int) <= sizeof(long)
AND
sizeof(char) == 1
sizeof(short) >= 1
sizeof(int) >= 1
sizeof(long) >= 1
which someone on this list pointed out previously. I think the key words
here are that "the range of values of each type is a subrange of the values
of the next type in the list." Are we getting a little too far off topic
for this list?
Larry Hall lhall@rfk.com
RFK Partners, Inc. (781) 239-1053
8 Grove Street (781) 239-1655 - FAX
Wellesley, MA 02181 http://www.rfk.com
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: long long vs long
1998-07-25 0:08 ` Larry Hall
@ 1998-07-25 1:22 ` Timothy Writer
0 siblings, 0 replies; 222+ messages in thread
From: Timothy Writer @ 1998-07-25 1:22 UTC (permalink / raw)
To: Larry Hall; +Cc: Michael H. Warfield, Graham Murray, gnu-win32
Larry Hall <lhall@rfk.com> writes:
> At 01:48 PM 7/23/98 -0400, Timothy Writer wrote:
> >Furthermore, in section 6.1.2.5 the Standard states, "There are four signed
> >integer types, designated as signed char, short int, int, and long int." It
> >then goes on to say, "In the list of signed integer types above, the range of
> >values of each type is a subrange of the values of the next type in the
> >list."
> >
> >In other words,
> >
> > sizeof(char) <= sizeof(short) <= sizeof(int) <= sizeof(long)
> >
> >and
> >
> > sizeof(char) == 1
> > sizeof(short) >= 2
> > sizeof(int) >= 2
> > sizeof(long) >= 4
> >
>
> Sorry but this doesn't seem to follow. I agree with the interpretation of
> the standard, namely:
>
> sizeof(char) <= sizeof(short) <= sizeof(int) <= sizeof(long)
>
> However, this does NOT imply what follows (the sizeof lines after the "and".)
> The implication from the standard is:
>
> sizeof(char) <= sizeof(short) <= sizeof(int) <= sizeof(long)
>
> AND
>
> sizeof(char) == 1
> sizeof(short) >= 1
> sizeof(int) >= 1
> sizeof(long) >= 1
>
> which someone on this list pointed out previously. I think the key words
> here are that "the range of values of each type is a subrange of the values
> of the next type in the list." Are we getting a little too far off topic
> for this list?
This follows from the earlier section of the standard I posted which states
the minimum ranges for each type, namely -127 to +127 for signed char, -32767
to +32767 for signed short, etc. These imply that char is at least 8 bits,
short is at least 16 bits, and int and long are at least 32 bits. Assuming a
char is exacly eight bits (it's not clear to me whether the standard requires
that or not) it follows that:
sizeof(char) == 1
sizeof(short) >= 2
sizeof(int) >= 2
sizeof(long) >= 4
As to whether we're getting off topic. Clearly this group is about
portability and I was disturbed by the number of misinformed posters
spreading incorrect information about something so fundamental to porability.
--
Tim Writer Tim.Writer@ftlsol.com
FTL Solutions Inc.
Toronto, Ontario, CANADA
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: long long vs long
1998-07-22 13:57 ` Michael H. Warfield
` (2 preceding siblings ...)
1998-07-23 15:30 ` Timothy Writer
@ 1998-07-24 12:58 ` Benjamin Riefenstahl
3 siblings, 0 replies; 222+ messages in thread
From: Benjamin Riefenstahl @ 1998-07-24 12:58 UTC (permalink / raw)
To: gnu-win32
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2360 bytes --]
Hi Michael,
Michael H. Warfield wrote:
> Unfortunately the standard also specifies the length of several
> types. Specifically char is 8 bits, short is 16 bits, and long is 32 bits.
No, it only specifies the *minimum* ranges that each type must cover and
it gives some relations like all values representable by "short" must
also be representable by "int" and "long" etc. The net result for most
current architectures are the conditions (I hope I don't miss anything
important)
sizeof(char) == 1 // that's a definition actually, not a condition
sizeof(char) * CHAR_BITS >= 8
sizeof(short) * CHAR_BITS >= 16
sizeof(int) * CHAR_BITS >= 16
sizeof(long) * CHAR_BITS >= 32
sizeof(int) >= sizeof(short)
sizeof(long) >= sizeof(int)
The language standard does not say that "int" must be similar to one of
"short" or "long", so an implementation that does
sizeof(short) * CHAR_BITS == 16
sizeof(int) * CHAR_BITS == 32
sizeof(long) * CHAR_BITS == 64
is prefectly comforming.
The main argument for a new type "long long" as I understood it in the
Newsgroup discussions was that there was just too much code out there
that relies on binary compatibility for the "long" type. A compiler that
wants binary compatibility *and* a 64 bits type must introduce a new
type.
One argument against was that the current standard guarantees that
"long" is the type with the largest range of them all. This makes code
like this legal and portable:
size_t size = sizeof(someobject);
fprintf( somefile, "%lu", (unsigned long) size );
with the guarantee that the cast will not truncate the value. The new
type can change this code without warning, because with a new type
size_t might be an alias for "long long" instead of maximally "long".
This was probably considered a rather obscure point by some. But than I
sometimes feel like portability issue often are about rather obscure
points, which is probably why they get missed so often.
I can only recommend to search the comp.std.c newsgroup for the topic in
Dejanews.
so long, benny
======================================
Benjamin Riefenstahl (benny@crocodial.de)
Crocodial Communications EntwicklungsGmbH
RuhrstraÃe 61, D-22761 Hamburg, Germany
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: long long vs long
1998-07-21 1:55 long long vs long Graham Murray
` (2 preceding siblings ...)
1998-07-22 13:57 ` Michael H. Warfield
@ 1998-07-22 16:50 ` Michael Weiser
1998-07-23 8:33 ` Harry Broomhall
1998-07-23 8:33 ` Brian Osman
1998-07-22 17:12 ` Andrew Sharp
4 siblings, 2 replies; 222+ messages in thread
From: Michael Weiser @ 1998-07-22 16:50 UTC (permalink / raw)
To: gnu-win32
Hi Graham,
You wrote:
>This is probably a silly question, but rather than having long long for
>64 bit, why was long not made 64bit? The standard (AFAIK) states that
>short <= int <= long. So, it should be possible for long to be 64 bit
>rather than 32. This would give a simple progression from 8bit chars to
>64bit longs.
No because the standard says
short == 16 bit
long == 32 bit
int == 16 or 32 depending on the machine's architecture
For example: Under DOS int is 16 bit while under Win32 und UN*X it is
32 bit.
So there's no way for long to be 64 bit while conforming to the
standard.
bye
Michael
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: long long vs long
1998-07-22 16:50 ` Michael Weiser
@ 1998-07-23 8:33 ` Harry Broomhall
1998-07-23 19:01 ` Michael Weiser
1998-07-24 0:25 ` massimo morara
1998-07-23 8:33 ` Brian Osman
1 sibling, 2 replies; 222+ messages in thread
From: Harry Broomhall @ 1998-07-23 8:33 UTC (permalink / raw)
To: Michael Weiser; +Cc: gnu-win32
Michael Weiser said:
>
[SNIP]
> No because the standard says
> short == 16 bit
> long == 32 bit
> int == 16 or 32 depending on the machine's architecture
>
> For example: Under DOS int is 16 bit while under Win32 und UN*X it is
> 32 bit.
> So there's no way for long to be 64 bit while conforming to the
> standard.
Oh dear - this seems to be a common belief. Can you give the
para in the standard where it says this?
Regards,
Harry.
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: long long vs long
1998-07-23 8:33 ` Harry Broomhall
@ 1998-07-23 19:01 ` Michael Weiser
1998-07-24 5:20 ` Harry Broomhall
1998-07-25 1:22 ` Timothy Writer
1998-07-24 0:25 ` massimo morara
1 sibling, 2 replies; 222+ messages in thread
From: Michael Weiser @ 1998-07-23 19:01 UTC (permalink / raw)
To: Harry Broomhall; +Cc: gnu-win32
Hi Harry,
You wrote:
>> No because the standard says
>> short == 16 bit
>> long == 32 bit
>> int == 16 or 32 depending on the machine's architecture
>>
>> For example: Under DOS int is 16 bit while under Win32 und UN*X it is
>> 32 bit.
>> So there's no way for long to be 64 bit while conforming to the
>> standard.
> Oh dear - this seems to be a common belief. Can you give the
>para in the standard where it says this?
Unfortunately not. I didn't know that this matters so much.
BTW: Do you love splitting hairs? ;)
bye
Michael
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: long long vs long
1998-07-23 19:01 ` Michael Weiser
@ 1998-07-24 5:20 ` Harry Broomhall
1998-07-25 0:08 ` Mumit Khan
1998-07-27 14:23 ` Michael Weiser
1998-07-25 1:22 ` Timothy Writer
1 sibling, 2 replies; 222+ messages in thread
From: Harry Broomhall @ 1998-07-24 5:20 UTC (permalink / raw)
To: Michael Weiser; +Cc: gnu-win32
Michael Weiser said:
>
> Hi Harry,
>
[SNIP]
> Unfortunately not. I didn't know that this matters so much.
>
> BTW: Do you love splitting hairs? ;)
No - but I *do* dislike wrong information! <grin> And for
portable programming (which I have to do a lot of) you have to
be *very* clear on the rules.
Regards,
Harry.
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: long long vs long
1998-07-24 5:20 ` Harry Broomhall
@ 1998-07-25 0:08 ` Mumit Khan
1998-07-26 9:27 ` sjm
[not found] ` <9807261625.AA18550.cygnus.gnu-win32@frodo>
1998-07-27 14:23 ` Michael Weiser
1 sibling, 2 replies; 222+ messages in thread
From: Mumit Khan @ 1998-07-25 0:08 UTC (permalink / raw)
To: gnu-win32
Long long vs long debate ...
Please take this elsewhere! There's comp.lang.c, which is a much better
forum than this mailing list.
I implore you to spare the rest of us from this inane discussion. Would
be nice if some of the posters would bother opening up a standard C
reference before posting.
Regards,
Mumit
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: long long vs long
1998-07-25 0:08 ` Mumit Khan
@ 1998-07-26 9:27 ` sjm
[not found] ` <9807261625.AA18550.cygnus.gnu-win32@frodo>
1 sibling, 0 replies; 222+ messages in thread
From: sjm @ 1998-07-26 9:27 UTC (permalink / raw)
To: gnu-win32
It was written:
> Long long vs long debate ...
>
> Please take this elsewhere! There's comp.lang.c, which is a much better
> forum than this mailing list.
>
> I implore you to spare the rest of us from this inane discussion. Would
> be nice if some of the posters would bother opening up a standard C
> reference before posting.
Suggestion: Add "Re: long long vs long" to your kill file or filter or
whatever you use. Alternatively consider deleting anything with that subject
without reading. I measured the time on my keyboard for deleting similar email
messages. Using vm under emacs I was able to delete in an average of .3
seconds per message if I did not bother to read the message. That's frankly
what I do with 95% of the traffic on this list. If it takes you longer I
suggest changing mailers.
Also I have found that not reading mail makes it impossible to be annoyed by
the innanity of that mail because I cannot then tell if the mail is innane or
not. Fortunately I have never seen a mailer that forced me to read mail on an
uninteresting topic.
In other words I suggest you lighten up. This is a support group, not a
private list for insiders. Since gcc supports "long long" the argument could
be made that this is a vaguely on point topic. I could also make an arguement
based on its relatedness to portability. Less on point topics have been
discussed here without complaint.
As long as there is resistance to turning this list into a newsgroup where it
would be easier to split into subgroups then I have little sympathy for
complaints about off point discussion. Since this is the only forum for
discussing cygwin related stuff we shouldn't be too restrictive about how
closely related the discussion must be.
Steve Morris
sjm@judgement.com
PS. I agree that we have beaten this one nearly to death and will personally
be relieved when the topic finally dies out.
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 222+ messages in thread
[parent not found: <9807261625.AA18550.cygnus.gnu-win32@frodo>]
* Re: long long vs long
[not found] ` <9807261625.AA18550.cygnus.gnu-win32@frodo>
@ 1998-07-28 0:57 ` Christopher G. Faylor
0 siblings, 0 replies; 222+ messages in thread
From: Christopher G. Faylor @ 1998-07-28 0:57 UTC (permalink / raw)
To: gnu-win32
In article <9807261625.AA18550.cygnus.gnu-win32@frodo>,
sjm <sjm@judgement.com> wrote:
>
>It was written:
> > Long long vs long debate ...
> >
> > Please take this elsewhere! There's comp.lang.c, which is a much better
> > forum than this mailing list.
> >
> > I implore you to spare the rest of us from this inane discussion. Would
> > be nice if some of the posters would bother opening up a standard C
> > reference before posting.
>
>Suggestion: Add "Re: long long vs long" to your kill file or filter or
>whatever you use. Alternatively consider deleting anything with that subject
>without reading. I measured the time on my keyboard for deleting similar email
>messages. Using vm under emacs I was able to delete in an average of .3
>seconds per message if I did not bother to read the message. That's frankly
>what I do with 95% of the traffic on this list. If it takes you longer I
>suggest changing mailers.
I agree with whoever posted this. The "long long" topic has very little
to do with gnu-win32. When a message thread starts moving outside of
the purpose of a mailing list, the polite thing to do is to move it
elsewhere.
>As long as there is resistance to turning this list into a newsgroup where it
>would be easier to split into subgroups then I have little sympathy for
>complaints about off point discussion. Since this is the only forum for
>discussing cygwin related stuff we shouldn't be too restrictive about how
>closely related the discussion must be.
Resistance? Where is there resistance? If you'd like to spearhead the
campaign to turn this into a newsgroup, please feel free to do so.
The fact that this is not a newsgroup is one more reason why off-topic
threads such as this one should be squashed. Some people who are
subscribed to the gnu-win32 mailing list are actually paying for their
connections. There's no reason for such people to pay for "long long"
discussions.
--
cgf@cygnus.com "Everything has a boolean value, if you stand
http://www.cygnus.com/ far enough away from it." -- Galena Alyson Canada
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: long long vs long
1998-07-24 5:20 ` Harry Broomhall
1998-07-25 0:08 ` Mumit Khan
@ 1998-07-27 14:23 ` Michael Weiser
1 sibling, 0 replies; 222+ messages in thread
From: Michael Weiser @ 1998-07-27 14:23 UTC (permalink / raw)
To: Harry Broomhall; +Cc: gnu-win32
Hi Harry,
You wrote:
>[SNIP]
>> Unfortunately not. I didn't know that this matters so much.
>>
>> BTW: Do you love splitting hairs? ;)
>
> No - but I *do* dislike wrong information! <grin> And for
>portable programming (which I have to do a lot of) you have to
>be *very* clear on the rules.
Okay, got me. As I've never seen a system that uses longs with more or
less than 32 bits I simply thought that it's pretty useless to argue
about whether the standard says this or that when nearly all code
relys on that fact. But after reading this thread on the list it seems
to me that there are even a lot systems with incredibly long longs and
so I now think you're right. ;)
Yours
Micha
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: long long vs long
1998-07-23 19:01 ` Michael Weiser
1998-07-24 5:20 ` Harry Broomhall
@ 1998-07-25 1:22 ` Timothy Writer
1998-07-28 0:57 ` Michael Weiser
1 sibling, 1 reply; 222+ messages in thread
From: Timothy Writer @ 1998-07-25 1:22 UTC (permalink / raw)
To: Michael Weiser; +Cc: Harry Broomhall, gnu-win32
michael@weiser.saale-net.de (Michael Weiser) writes:
> Hi Harry,
>
> You wrote:
>
> >> No because the standard says
> >> short == 16 bit
> >> long == 32 bit
> >> int == 16 or 32 depending on the machine's architecture
> >>
> >> For example: Under DOS int is 16 bit while under Win32 und UN*X it is
> >> 32 bit.
> >> So there's no way for long to be 64 bit while conforming to the
> >> standard.
> > Oh dear - this seems to be a common belief. Can you give the
> >para in the standard where it says this?
> Unfortunately not. I didn't know that this matters so much.
>
> BTW: Do you love splitting hairs? ;)
In defense of the original poster, this is not splitting hairs. You yourself
invoked the _Standard_ to assert:
1. short is 16 bits and long is 32 bits
2. a conforming implementation cannot use a 64 bit long
Both statements are incorrect and such commonly held misbeliefs are a
frequent source of portability problems. Since this group is very much about
portability, its important not to spread misinformation where portability is
concerned.
BTW, I'm not speaking from an "Ivory tower". I recently had the job of
porting an application from NT to Digital UNIX with, you guessed it, 64 bit
longs. The code is full of assumptions that a short is exactly 16 bits and a
long is exactly 32 bits. Furthermore, the programmers never use int because
they don't know its size. Needless to say the port was costly. So, you see,
such distinctions do matter.
--
Tim Writer Tim.Writer@ftlsol.com
FTL Solutions Inc.
Toronto, Ontario, CANADA
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: long long vs long
1998-07-25 1:22 ` Timothy Writer
@ 1998-07-28 0:57 ` Michael Weiser
0 siblings, 0 replies; 222+ messages in thread
From: Michael Weiser @ 1998-07-28 0:57 UTC (permalink / raw)
To: Timothy Writer; +Cc: gnu-win32
Hello Timothy,
You wrote:
[SNIP]
>> Unfortunately not. I didn't know that this matters so much.
>>
>> BTW: Do you love splitting hairs? ;)
>
>In defense of the original poster, this is not splitting hairs. You yourself
>invoked the _Standard_ to assert:
>
> 1. short is 16 bits and long is 32 bits
> 2. a conforming implementation cannot use a 64 bit long
>
>Both statements are incorrect and such commonly held misbeliefs are a
>frequent source of portability problems. Since this group is very much about
>portability, its important not to spread misinformation where portability is
>concerned.
Okay okay, I said Jehova and now everyone is throwing stones at me. ;)
I now know that my statement about the standard was thoughtless,
sorry. In my little world I thought that longs are 32 bits and that
almost all code relys on this. I simply didn't know about the world
around my little universe. :)
So sorry and till the next mindless mistake...
Micha
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: long long vs long
1998-07-23 8:33 ` Harry Broomhall
1998-07-23 19:01 ` Michael Weiser
@ 1998-07-24 0:25 ` massimo morara
1 sibling, 0 replies; 222+ messages in thread
From: massimo morara @ 1998-07-24 0:25 UTC (permalink / raw)
To: gnu-win32
Can be useful (I hope so)
http://www.UNIX-systems.org/version2/whatsnew/login_64bit.html
massimo
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: long long vs long
1998-07-22 16:50 ` Michael Weiser
1998-07-23 8:33 ` Harry Broomhall
@ 1998-07-23 8:33 ` Brian Osman
1998-07-27 14:23 ` Michael Weiser
1 sibling, 1 reply; 222+ messages in thread
From: Brian Osman @ 1998-07-23 8:33 UTC (permalink / raw)
To: gnu-win32
Michael Weiser wrote:
>
> No because the standard says
> short == 16 bit
> long == 32 bit
> int == 16 or 32 depending on the machine's architecture
>
> For example: Under DOS int is 16 bit while under Win32 und UN*X it is
> 32 bit. So there's no way for long to be 64 bit while conforming to > the standard.
>
> bye
>
> Michael
Hmmm. I don't have a copy of the standard laying around, but I do have
Kernighan & Ritchite (2nd ed.) which says
Section 2.2:
...
Each compiler is free to choose appropriate sizes for its own hardware,
subject only to the restriction that shorts and ints are at least 16
bits, longs are at least 32 bits, and short is no longer than int, which
is no longer than long.
...
-Brian
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: long long vs long
1998-07-23 8:33 ` Brian Osman
@ 1998-07-27 14:23 ` Michael Weiser
0 siblings, 0 replies; 222+ messages in thread
From: Michael Weiser @ 1998-07-27 14:23 UTC (permalink / raw)
To: Brian Osman; +Cc: gnu-win32
Hello Brian,
You wrote:
>Each compiler is free to choose appropriate sizes for its own hardware,
>subject only to the restriction that shorts and ints are at least 16
>bits, longs are at least 32 bits, and short is no longer than int, which
>is no longer than long.
>...
I've already been intensively kicked for that mistake. ;)
Sorry...
Micha
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: long long vs long
1998-07-21 1:55 long long vs long Graham Murray
` (3 preceding siblings ...)
1998-07-22 16:50 ` Michael Weiser
@ 1998-07-22 17:12 ` Andrew Sharp
4 siblings, 0 replies; 222+ messages in thread
From: Andrew Sharp @ 1998-07-22 17:12 UTC (permalink / raw)
To: 'gnu-win32@cygnus.com'
Graham Murray wrote:
>
> This is probably a silly question, but rather than having long long for
> 64 bit, why was long not made 64bit? The standard (AFAIK) states that
> short <= int <= long. So, it should be possible for long to be 64 bit
> rather than 32. This would give a simple progression from 8bit chars to
> 64bit longs.
You're right, it is a silly question. ~:^) I did a lot of 64bit unix
kernel porting work a few years back, and the reason that something
other than 'long' had to be used is that there is about 6 trillion lines
of C code in the world that would seriously break if long's suddenly
became 64 bits, because coders have been using 'long' for more than a
decade with the belief that they are the same size as 'int'. Avoiding
the discussion of why they didn't use 'int' all those times, suffice it
to say that a new type was created for the sake of expediency. Everyone
who has written code that might require some fixin' if long's changed to
64 bits, raise your hand.
The irony is that types like 'long long' are usually accomplished in
some basic header, not as a base compiler type. The base compiler 64bit
types are almost always of the form '_int64' or some such. It seems we
just can't ever separate int's and long's!
a
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: Why text=binary mounts (Re: Gnu-win32 (b18), coolview and NTEmacs)
@ 1998-01-07 5:29 Earnie Boyd
1998-01-07 12:35 ` Scott Blachowicz
` (2 more replies)
0 siblings, 3 replies; 222+ messages in thread
From: Earnie Boyd @ 1998-01-07 5:29 UTC (permalink / raw)
To: sab; +Cc: gnu-win32
>From: Scott Blachowicz <sab@seanet.com>
>Date: 06 Jan 1998 11:25:43 -0800
>
[snip]
>So, why IS it that the coolview code requires text=binary mode mounts
>anyways?
Let me remind you that the purpose of the cygnus gnu-win32 project is to
port UNIX code. Most of the UNIX world programs choke on the \r\n
combination. Therefore text=binary is the easiest solution.
>--
>Scott Blachowicz <sab@seanet.com>
- \\||//
---o0O0--Earnie--0O0o----
-earnie_boyd@hotmail.com-
------ooo0O--O0ooo-------
Check out these great gnu-win32 related sites:
ftp://ftp.cygnus.com/pub/gnu-win32/latest/ (ftp site)
http://www.cygnus.com/pubs/gnupro/ (Comercial Page)
http://www.cygnus.com/misc/gnu-win32/ (Project Page)
http://www.cygnus.com/ml/gnu-win32 (Mail Archives)
http://www.itribe.net/virtunix/winhelp-man-pages/ (HTML Man Pages)
http://www.lexa.ru/sos (Sergey Okhapkin)
ftp://www.lexa.ru/pub/domestic/sos/ (Sergey's ftp site)
http://www.fu.is.saga-u.ac.jp/~colin/gcc.html (Colin Peters)
http://www.xraylith.wisc.edu/~khan/software/gnu-win32/ (Mumit Khan)
http://gnu-win32.paranoia.ru (Chuck Bogorad)
ftp://ftp.deninc.com/pub (Den Internet Services)
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: Why text=binary mounts (Re: Gnu-win32 (b18), coolview and NTEmacs)
1998-01-07 5:29 Why text=binary mounts (Re: Gnu-win32 (b18), coolview and NTEmacs) Earnie Boyd
@ 1998-01-07 12:35 ` Scott Blachowicz
1998-01-07 14:50 ` Fergus Henderson
1998-01-07 22:33 ` Jeffrey C. Fried
2 siblings, 0 replies; 222+ messages in thread
From: Scott Blachowicz @ 1998-01-07 12:35 UTC (permalink / raw)
To: Earnie Boyd; +Cc: gnu-win32
"Earnie Boyd" <earnie_boyd@hotmail.com> writes:
> Let me remind you that the purpose of the cygnus gnu-win32 project is to
> port UNIX code. Most of the UNIX world programs choke on the \r\n
> combination. Therefore text=binary is the easiest solution.
Yes, I realize that. But it seems like there are some concessions being
made to the folks who claim that the tools ought to interoperate more
easily with the DOS tools (e.g. accepting file paths like "c:/windows").
So, I keep hoping that someone will come up with some clever scheme to do
away with this text=binary mount stuff (which seems to be one of the most
awkward things about trying to use the gnu-win32 stuff).
I keep hoping to be able to find some affordable (read: negligible
monitary cost :-)) alternative to MKS sh (or whatever) to give me a Unix
toolset that can interoperate with the Windows developers and development
tools that I need to.
--
Scott Blachowicz <sab@seanet.com>
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: Why text=binary mounts (Re: Gnu-win32 (b18), coolview and NTEmacs)
1998-01-07 5:29 Why text=binary mounts (Re: Gnu-win32 (b18), coolview and NTEmacs) Earnie Boyd
1998-01-07 12:35 ` Scott Blachowicz
@ 1998-01-07 14:50 ` Fergus Henderson
1998-01-07 22:33 ` Jeffrey C. Fried
2 siblings, 0 replies; 222+ messages in thread
From: Fergus Henderson @ 1998-01-07 14:50 UTC (permalink / raw)
To: Earnie Boyd; +Cc: sab, gnu-win32
On 07-Jan-1998, Earnie Boyd <earnie_boyd@hotmail.com> wrote:
> From: Scott Blachowicz <sab@seanet.com>
> >So, why IS it that the coolview code requires text=binary mode mounts
> >anyways?
>
> Let me remind you that the purpose of the cygnus gnu-win32 project is to
> port UNIX code. Most of the UNIX world programs choke on the \r\n
> combination. Therefore text=binary is the easiest solution.
I think you misspelt "work-around".
--
Fergus Henderson <fjh@cs.mu.oz.au> | "I have always known that the pursuit
WWW: < http://www.cs.mu.oz.au/~fjh > | of excellence is a lethal habit"
PGP: finger fjh@128.250.37.3 | -- the last words of T. S. Garp.
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: Why text=binary mounts (Re: Gnu-win32 (b18), coolview and NTEmacs)
1998-01-07 5:29 Why text=binary mounts (Re: Gnu-win32 (b18), coolview and NTEmacs) Earnie Boyd
1998-01-07 12:35 ` Scott Blachowicz
1998-01-07 14:50 ` Fergus Henderson
@ 1998-01-07 22:33 ` Jeffrey C. Fried
1998-01-08 10:46 ` Scott Blachowicz
2 siblings, 1 reply; 222+ messages in thread
From: Jeffrey C. Fried @ 1998-01-07 22:33 UTC (permalink / raw)
To: Earnie Boyd, sab; +Cc: gnu-win32
Porting code from Unix to the PC should NOT require the same line
termination mode since most Unix code which reads text uses fread/getc
which automatically handle the end-of-line. And from the replies of most
people i would argue that most of us would prefer to work in the native
mode of the operating system in which we are running rather than having to
constantly convert files between the two models simply because we use tools
from both operating systems under NT/95. For examples of this
compatibility look at many of the GNU tools which handle text, the file
handling will work under both operating systems without any change because
they use text mode I/O which is platform independent once all files have
been converted to the form of the native OS.
... jeff
At 05:28 AM 1/7/98 PST, Earnie Boyd wrote:
>>From: Scott Blachowicz <sab@seanet.com>
>>Date: 06 Jan 1998 11:25:43 -0800
>>
>[snip]
>>So, why IS it that the coolview code requires text=binary mode mounts
>>anyways?
>
>Let me remind you that the purpose of the cygnus gnu-win32 project is to
>port UNIX code. Most of the UNIX world programs choke on the \r\n
>combination. Therefore text=binary is the easiest solution.
>
>>--
>>Scott Blachowicz <sab@seanet.com>
>
>
>- \\||//
>---o0O0--Earnie--0O0o----
>-earnie_boyd@hotmail.com-
>------ooo0O--O0ooo-------
>
>Check out these great gnu-win32 related sites:
> ftp://ftp.cygnus.com/pub/gnu-win32/latest/ (ftp site)
> http://www.cygnus.com/pubs/gnupro/ (Comercial Page)
> http://www.cygnus.com/misc/gnu-win32/ (Project Page)
> http://www.cygnus.com/ml/gnu-win32 (Mail Archives)
> http://www.itribe.net/virtunix/winhelp-man-pages/ (HTML Man Pages)
> http://www.lexa.ru/sos (Sergey Okhapkin)
> ftp://www.lexa.ru/pub/domestic/sos/ (Sergey's ftp site)
> http://www.fu.is.saga-u.ac.jp/~colin/gcc.html (Colin Peters)
> http://www.xraylith.wisc.edu/~khan/software/gnu-win32/ (Mumit Khan)
> http://gnu-win32.paranoia.ru (Chuck Bogorad)
> ftp://ftp.deninc.com/pub (Den Internet Services)
>
>
>______________________________________________________
>Get Your Private, Free Email at http://www.hotmail.com
>-
>For help on using this list (especially unsubscribing), send a message to
>"gnu-win32-request@cygnus.com" with one line of text: "help".
>
>
--
Jeffrey C. Fried jcfried@ix.netcom.com
Because a liar tells the truth does not mean the truth is a lie.
NOTICE: I charge $500.00 for each unsolicited advertisement i receive as email
to cover the cost of my time to review and possibly respond to your
advertisement.
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: Why text=binary mounts (Re: Gnu-win32 (b18), coolview and NTEmacs)
1998-01-07 22:33 ` Jeffrey C. Fried
@ 1998-01-08 10:46 ` Scott Blachowicz
1998-01-09 11:09 ` Larry Hall (RFK Partners Inc)
1998-01-10 6:19 ` Why text=binary mounts (Re: Gnu-win32 (b18), coolview and NTE Michael Hirmke
0 siblings, 2 replies; 222+ messages in thread
From: Scott Blachowicz @ 1998-01-08 10:46 UTC (permalink / raw)
To: Jeffrey C. Fried; +Cc: Earnie Boyd, gnu-win32
"Jeffrey C. Fried" <jcfried@ix.netcom.com> writes:
> from both operating systems under NT/95. For examples of this
> compatibility look at many of the GNU tools which handle text, the file
> handling will work under both operating systems without any change because
> they use text mode I/O which is platform independent once all files have
> been converted to the form of the native OS.
A problem is that the open() call in MS-land has a binary/text mode flag,
but Unix open() calls generally don't (since there is typically no
binary/text mode distinction made). So, you always end up having
problems with porting arbitrary Unix code over to MS-land when the Unix
code calls open() without specifying a mode AND the default mode doesn't
match what the Unix code was expecting.
Part of the problem with specifying the default text file type on a
per-mount basis is that it frequently isn't the right basis for specifying
it. I may have mounts where I want both style of line termination - maybe
it's more related to what kind of file I'm writing. Using the mount point
is kind of a best guess heuristic, I guess. What we need is omniscent
software that just knows what I want and does it :-)).
Maybe it'd be nice of the mount mode were irrelevant when reading an
existing file, but just controlled what happens when you write a file to
the file system. Maybe the reading operations could track what kind of
line termination is being used on a file, then succeeding write operations
could use the same style (unless overridden by the open() flags)? That
sounds weird...and probably unworkable...just food for thought.
How do the MS-land programs that understand both line terminations work?
They probably just accept either on input, then do \r\n on output, right?
Oh, Idunno...
--
Scott Blachowicz <sab@seanet.com>
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: Why text=binary mounts (Re: Gnu-win32 (b18), coolview and NTEmacs)
1998-01-08 10:46 ` Scott Blachowicz
@ 1998-01-09 11:09 ` Larry Hall (RFK Partners Inc)
1998-01-12 20:11 ` Scott Blachowicz
1998-01-10 6:19 ` Why text=binary mounts (Re: Gnu-win32 (b18), coolview and NTE Michael Hirmke
1 sibling, 1 reply; 222+ messages in thread
From: Larry Hall (RFK Partners Inc) @ 1998-01-09 11:09 UTC (permalink / raw)
To: sab; +Cc: gnu-win32
At 10:34 AM 1/8/98 -0800, you wrote:
>Maybe the reading operations could track what kind of
>line termination is being used on a file, then succeeding write operations
>could use the same style (unless overridden by the open() flags)? That
>sounds weird...and probably unworkable...just food for thought.
Not necessarily. Various programs do this, including vim and, I think, NTEmacs.
>How do the MS-land programs that understand both line terminations work?
>They probably just accept either on input, then do \r\n on output, right?
Precisely.
Larry Hall lhall@rfk.com
RFK Partners, Inc. (781) 239-1053
8 Grove Street (781) 239-1655 - FAX
Wellesley, MA 02181
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: Why text=binary mounts (Re: Gnu-win32 (b18), coolview and NTEmacs)
1998-01-09 11:09 ` Larry Hall (RFK Partners Inc)
@ 1998-01-12 20:11 ` Scott Blachowicz
1998-01-16 2:56 ` Benjamin Riefenstahl
0 siblings, 1 reply; 222+ messages in thread
From: Scott Blachowicz @ 1998-01-12 20:11 UTC (permalink / raw)
To: Larry Hall (RFK Partners Inc); +Cc: gnu-win32
> >Maybe the reading operations could track what kind of
> >line termination is being used on a file, then succeeding write operations
> >could use the same style (unless overridden by the open() flags)? That
> >sounds weird...and probably unworkable...just food for thought.
>
> Not necessarily. Various programs do this, including vim and, I think, NTEmacs.
Yes, NTEmacs does, but I was trying to think of the difficulties involved
in doing a filter program. It'd be nice if the line termination for the
output file could somehow match its input file....so either the filter
program would have to use the right fopen() flags to designate the right
kind of text output file or the fopen() could intuit the right value by
looking at recent open()/read()'s...that's what I meant by
"weird"/"unworkable".
--
Scott Blachowicz <sab@seanet.com>
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: Why text=binary mounts (Re: Gnu-win32 (b18), coolview and NTEmacs)
1998-01-12 20:11 ` Scott Blachowicz
@ 1998-01-16 2:56 ` Benjamin Riefenstahl
0 siblings, 0 replies; 222+ messages in thread
From: Benjamin Riefenstahl @ 1998-01-16 2:56 UTC (permalink / raw)
To: gnu-win32
Scott Blachowicz wrote:
> > >Maybe the reading operations could track what kind of
> > >line termination is being used on a file, then succeeding write operations
> > >could use the same style (unless overridden by the open() flags)? That
> > >sounds weird...and probably unworkable...just food for thought.
That would be nice, but not necessary for my purposes. I would be
content if all tools that do text would understand all ASCII text file
input. If that was garanteed for all tools than their output format
could be an arbitrary choice (any one of Unix, DOS, Mac).
OTOH given that I do not have source for some of my tools (esp the OS
supplied), I prefer the output in the native format i.e. DOS. Actually,
thinking about it, I'd say that I would even prefer output in DOS format
over preserving the old format.
======================================
Benjamin Riefenstahl (benny@crocodial.de)
Crocodial Communications EntwicklungsGmbH
Ophagen 16a, D-20257 Hamburg, Germany
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: Why text=binary mounts (Re: Gnu-win32 (b18), coolview and NTE
1998-01-08 10:46 ` Scott Blachowicz
1998-01-09 11:09 ` Larry Hall (RFK Partners Inc)
@ 1998-01-10 6:19 ` Michael Hirmke
1998-01-11 15:55 ` Larry Hall
1 sibling, 1 reply; 222+ messages in thread
From: Michael Hirmke @ 1998-01-10 6:19 UTC (permalink / raw)
To: gnu-win32
Larry Hall (RFK Partners Inc) [lhall@rfk.com] wrote:
[...]
>Not necessarily. Various programs do this, including vim and, I think,
>NTEmacs.
>
>>How do the MS-land programs that understand both line terminations work?
>>They probably just accept either on input, then do \r\n on output, right?
>
>Precisely.
Nope, vim for example reads files in "textmode" or "notextmode" and
also writes them in the same manner. This is true for the Cygnus
compiled vim and for the VC++ compiled one under Windows.
Otherwise you would destroy all your Unix style line breaks, when
reading and writing a file with it.
>
>
>Larry Hall lhall@rfk.com
Bye.
Michael.
--
Michael Hirmke | Telefon +49 (911) 557999
Georg-Strobel-Strasse 81 | FAX +49 (911) 557664
90489 Nuernberg | E-Mail mailto:mh@mike.franken.de
| WWW http://minimike.franken.de/
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 222+ messages in thread
* Re: Why text=binary mounts (Re: Gnu-win32 (b18), coolview and NTE
1998-01-10 6:19 ` Why text=binary mounts (Re: Gnu-win32 (b18), coolview and NTE Michael Hirmke
@ 1998-01-11 15:55 ` Larry Hall
0 siblings, 0 replies; 222+ messages in thread
From: Larry Hall @ 1998-01-11 15:55 UTC (permalink / raw)
To: Michael Hirmke; +Cc: gnu-win32
Michael Hirmke wrote:
>
> Larry Hall (RFK Partners Inc) [lhall@rfk.com] wrote:
>
> [...]
> >Not necessarily. Various programs do this, including vim and, I think,
> >NTEmacs.
> >
> >>How do the MS-land programs that understand both line terminations work?
> >>They probably just accept either on input, then do \r\n on output, right?
> >
> >Precisely.
>
> Nope, vim for example reads files in "textmode" or "notextmode" and
> also writes them in the same manner. This is true for the Cygnus
> compiled vim and for the VC++ compiled one under Windows.
> Otherwise you would destroy all your Unix style line breaks, when
> reading and writing a file with it.
>
> >
> >
> >Larry Hall lhall@rfk.com
>
> Bye.
> Michael.
> --
> Michael Hirmke | Telefon +49 (911) 557999
> Georg-Strobel-Strasse 81 | FAX +49 (911) 557664
> 90489 Nuernberg | E-Mail mailto:mh@mike.franken.de
> | WWW http://minimike.franken.de/
> -
> For help on using this list (especially unsubscribing), send a message to
> "gnu-win32-request@cygnus.com" with one line of text: "help".
Michael,
This is taken out of context. vim works as you describe however I
was not insinuating that vim worked as "MS-land" programs. I was
considering the original poster's definition of "MS-land" programs
as native Win32 programs and not ports of software to this platform
or others. If anyone else got the impression I meant otherwise,
please accept my apologies.
--
Larry
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 222+ messages in thread
[parent not found: <23>]
[parent not found: <Bob>]
[parent not found: <Sebastien>]
[parent not found: <Mumit>]
[parent not found: <Benjamin>]
[parent not found: <Markus>]
[parent not found: <Michael>]
[parent not found: <john>]
[parent not found: <Earnie>]
[parent not found: <Corinna>]
[parent not found: <Larry>]
[parent not found: <Suhaib>]
end of thread, other threads:[~2001-11-25 18:01 UTC | newest]
Thread overview: 222+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <Jeffrey>
[not found] ` <C.>
[not found] ` <Fried"'s>
[not found] ` <message>
[not found] ` <of>
[not found] ` <"Thu,>
[not found] ` <"Fri,>
[not found] ` <11>
[not found] ` <"Mon,>
[not found] ` <"Tue,>
[not found] ` <"Wed,>
[not found] ` <22>
[not found] ` <07>
[not found] ` <Jan>
[not found] ` <2001>
[not found] ` <16:18:12>
[not found] ` <1998>
[not found] ` <11:08:42>
[not found] ` <-0400>
[not found] ` <16:34:34>
[not found] ` <-0500>
[not found] ` <DJ>
[not found] ` <Daniel>
1998-12-11 14:39 ` help on compiling perl/ nt with cygwin. gnu c lib missing john z
1998-12-12 9:41 ` Michael Hirmke
1998-12-13 5:55 ` Peter Moulder
[not found] ` <3.0.5.32.19981213122803.00863b20@pciii>
1998-12-18 20:36 ` Peter Moulder
1999-02-02 5:27 ` OpenGL and glut with B20.1 Suhaib M. Siddiqi
1999-02-02 5:44 ` Levon Saldamli
[not found] ` < 7wsocoudi1.fsf@sandra.lysator.liu.se >
1999-02-02 6:18 ` Theodore Jump
1999-02-28 23:02 ` Theodore Jump
1999-02-03 5:02 ` unsubscribe john z
1999-02-28 23:02 ` unsubscribe john z
1999-02-28 23:02 ` OpenGL and glut with B20.1 Levon Saldamli
1999-02-28 23:02 ` Suhaib M. Siddiqi
2001-01-04 13:09 ` First Cygwin Installation Hough, Louis F
2001-01-04 13:12 ` DJ Delorie
2001-01-04 13:21 ` David M. Karr
2001-01-04 13:39 ` Larry Hall (RFK Partners, Inc)
2001-01-04 13:55 ` David M. Karr
2001-01-04 14:14 ` Larry Hall (RFK Partners, Inc)
2001-01-04 14:41 ` Earnie Boyd
2001-01-04 14:55 ` David M. Karr
2001-01-04 15:10 ` Christopher Faylor
2001-01-05 12:52 ` Drive with cygwin moved from "E:" to "D:", how to fix? David M. Karr
2001-01-05 13:00 ` DJ Delorie
2001-01-05 13:40 ` David M. Karr
2001-01-05 13:46 ` Larry Hall (RFK Partners, Inc)
2001-01-05 14:04 ` David M. Karr
2001-01-05 13:50 ` Gerrit P. Haase
2001-01-06 11:30 ` Quick setup script "taxidermy.pl" Soren Andersen
2001-01-11 14:23 ` NTEmacs shell/CygWin: should control-C work? Daniel Barclay
2001-01-11 15:00 ` David M. Karr
2001-01-12 11:48 ` Daniel Barclay
2001-01-12 11:54 ` David M. Karr
2001-01-12 12:30 ` Larry Hall (RFK Partners, Inc)
2001-01-12 12:43 ` David M. Karr
2001-01-12 13:12 ` Daniel Barclay
2001-01-12 13:13 ` Larry Hall (RFK Partners, Inc)
2001-01-12 13:06 ` Daniel Barclay
2001-01-12 13:26 ` Ehud Karni
2001-01-12 13:57 ` Larry Hall (RFK Partners, Inc)
2001-01-16 11:14 ` Daniel Barclay
2001-01-16 11:27 ` Larry Hall (RFK Partners, Inc)
2001-01-18 8:21 ` Daniel Barclay
2001-01-18 8:27 ` Larry Hall (RFK Partners, Inc)
2001-01-18 16:47 ` Dr. Volker Zell
[not found] ` <14:02:23>
[not found] ` <+0200>
1998-10-23 12:54 ` Which of cygwin32's design goals does ascii file conversion fulfil? David Fox
1998-10-24 10:29 ` Larry Hall
1998-10-26 5:47 ` Olle Olsson
1998-10-28 0:40 ` Geoffrey Noer
1998-10-25 1:41 ` Darren Cook
2000-03-13 15:34 ` [ANN] PW32 the (alternative) Posix-over-Win32 layer 0.3.0 released Michael Hirmke
2000-03-13 15:52 ` Chris Faylor
2000-03-14 13:06 ` Michael Hirmke
[not found] ` <21:45:26>
[not found] ` <-0700>
[not found] ` <(PDT)>
2000-04-26 6:56 ` problems with less Michael Hirmke
2000-05-09 7:42 ` John S Cooper
2000-05-09 9:08 ` Chris Faylor
2000-05-09 10:25 ` Bob McGowan
[not found] ` <1999>
[not found] ` <21:28:12>
[not found] ` <-0600>
[not found] ` <(CST)>
[not found] ` <Pine.SO4.4.05.9902222125010.25431-100000@scooby.simple.dallas.tx.us>
[not found] ` <d9btilixqo.fsf@han.cs.umn.edu>
1999-02-22 22:41 ` [PB] "no acceptable ld" : cywin32 pb, way to handle win path ? Sebastien Barre
1999-02-23 3:06 ` Gary V. Vaughan
1999-02-28 23:02 ` Gary V. Vaughan
1999-02-28 23:02 ` Sebastien Barre
[not found] ` <19:42:30>
[not found] ` <+0100>
1999-02-23 17:15 ` strange mount behaviour Sebastien Barre
1999-02-24 0:08 ` Levon Saldamli
[not found] ` < 7wsobw8gql.fsf@sandra.lysator.liu.se >
1999-02-24 0:59 ` Sebastien Barre
1999-02-28 23:02 ` Sebastien Barre
1999-02-28 23:02 ` Levon Saldamli
1999-03-03 13:25 ` Michael Hirmke
1999-03-31 19:45 ` Michael Hirmke
1999-02-28 23:02 ` Sebastien Barre
2001-01-16 0:08 ` Cygwin commands crashes after ssh login Christer.H.Jansson
2001-01-16 4:41 ` Erdely, Michael
2001-01-16 5:32 ` Corinna Vinschen
2001-01-16 5:49 ` Erdely, Michael
2001-01-16 6:08 ` Henry S. Thompson
2001-01-16 7:38 ` Larry Hall (RFK Partners, Inc)
2001-01-16 7:56 ` Wei Ku
2001-01-16 8:02 ` Christopher Faylor
2001-01-17 4:04 ` Corinna Vinschen
2001-01-16 9:11 ` Egor Duda
2001-01-16 9:28 ` Christopher Faylor
2001-01-17 5:20 ` Egor Duda
2001-01-17 5:29 ` Christopher Faylor
2001-01-17 3:57 ` Corinna Vinschen
2001-01-17 5:20 ` Egor Duda
2001-03-15 13:33 ` tcsh Win2000: command line editing does not work Brad Barber
2001-03-15 14:15 ` Corinna Vinschen
2001-03-22 8:01 ` Kazuhiro Fujieda
2001-03-22 10:08 ` Brad Barber
2001-03-22 10:27 ` Kazuhiro Fujieda
2001-03-22 18:49 ` Christopher Faylor
[not found] ` <m3elvyr90a.fsf@master.athome>
2001-03-16 6:59 ` Brad Barber
[not found] <;>
[not found] ` <from>
[not found] ` <"Michael>
[not found] ` <Hirmke">
[not found] ` <dialup-62.215.274.4.dial1.stamford>
[not found] ` <([62.215.274.4]>
2001-11-25 18:01 ` >>>ADVERTISE TO 11,759,000 PEOPLE FREE! FreeEmailSoftware1
2001-05-03 6:27 Problem with Windows .lnk files treated as Symlinks Martin Oberhuber
2001-05-03 7:49 ` Larry Hall (RFK Partners, Inc)
2001-05-03 10:46 ` Christopher Faylor
-- strict thread matches above, loose matches on Subject: below --
2001-01-24 13:36 KSH is pdksh Galen Boyer
2001-01-24 14:35 ` Larry Hall (RFK Partners, Inc)
2001-01-24 15:33 ` David Feustel
2001-01-24 15:30 ` Corinna Vinschen
2001-01-24 15:39 ` David M. Karr
2001-01-24 17:25 ` Earnie Boyd
2001-01-24 19:07 ` Mumit Khan
2001-01-25 8:25 ` David M. Karr
2001-01-25 8:34 ` Larry Hall (RFK Partners, Inc)
2001-01-25 12:52 ` Matthew Smith
2001-01-25 13:32 ` Earnie Boyd
2001-01-25 14:31 ` Newlib's non-posix'ness [Re: KSH is pdksh] Mumit Khan
2001-01-25 16:17 ` Earnie Boyd
2001-01-25 21:23 ` Christopher Faylor
2001-01-25 7:51 ` KSH is pdksh Galen Boyer
2001-01-25 13:01 ` Galen Boyer
2001-01-18 7:23 Cygwin commands crashes after ssh login Yadin Goldschmidt
2001-01-18 8:18 ` Corinna Vinschen
2001-01-17 13:43 frank.palazzolo
2001-01-17 13:54 ` Larry Hall (RFK Partners, Inc)
2001-01-17 13:12 frank.palazzolo
2001-01-18 6:07 ` Corinna Vinschen
2001-01-25 10:37 ` Erdely, Michael
2001-01-25 12:25 ` Ross Smith
2001-01-25 12:34 ` Larry Hall (RFK Partners, Inc)
2001-01-25 13:57 ` Ross Smith
2001-01-25 15:00 ` Larry Hall (RFK Partners, Inc)
2001-01-25 13:36 ` Erdely, Michael
2001-01-25 14:30 ` Earnie Boyd
2001-01-25 14:52 ` Erdely, Michael
2001-01-25 16:30 ` Earnie Boyd
2001-01-17 7:08 Yadin Goldschmidt
2001-01-18 6:10 ` Corinna Vinschen
2000-03-13 5:16 [ANN] PW32 the (alternative) Posix-over-Win32 layer 0.3.0 released Paul Sokolovsky
2000-03-13 8:05 ` Chris Faylor
2000-03-13 9:03 ` Dr. Volker Zell
2000-03-13 10:05 ` Re[2]: " Paul Sokolovsky
2000-03-13 15:01 ` Michael Hirmke
2000-03-13 15:05 ` Chris Faylor
1999-01-31 23:52 uudecode? John Cooper
1999-01-31 23:52 ` uudecode? Michael Hirmke
1999-01-31 23:52 ` uudecode? John Cooper
1999-01-31 23:52 ` uudecode? root
1999-01-31 23:52 ` uudecode? John Cooper
1999-01-31 23:52 ` uudecode? Pierre A. Humblet
1999-01-31 23:52 ` uudecode? John Cooper
1999-01-31 23:52 ` uudecode? John Cooper
1999-01-31 23:52 ` uudecode? Glenn Spell
1999-01-31 23:52 ` uudecode? Corinna Vinschen
1998-07-21 1:55 long long vs long Graham Murray
1998-07-22 6:17 ` Harry Broomhall
1998-07-22 13:57 ` Nicholas R LeRoy
1998-07-22 13:57 ` Michael H. Warfield
1998-07-23 6:15 ` Harry Broomhall
1998-07-23 13:02 ` Matthew Donadio
1998-07-23 15:30 ` Timothy Writer
1998-07-24 12:58 ` Matthew Donadio
1998-07-25 0:08 ` Larry Hall
1998-07-25 1:22 ` Timothy Writer
1998-07-24 12:58 ` Benjamin Riefenstahl
1998-07-22 16:50 ` Michael Weiser
1998-07-23 8:33 ` Harry Broomhall
1998-07-23 19:01 ` Michael Weiser
1998-07-24 5:20 ` Harry Broomhall
1998-07-25 0:08 ` Mumit Khan
1998-07-26 9:27 ` sjm
[not found] ` <9807261625.AA18550.cygnus.gnu-win32@frodo>
1998-07-28 0:57 ` Christopher G. Faylor
1998-07-27 14:23 ` Michael Weiser
1998-07-25 1:22 ` Timothy Writer
1998-07-28 0:57 ` Michael Weiser
1998-07-24 0:25 ` massimo morara
1998-07-23 8:33 ` Brian Osman
1998-07-27 14:23 ` Michael Weiser
1998-07-22 17:12 ` Andrew Sharp
1998-01-07 5:29 Why text=binary mounts (Re: Gnu-win32 (b18), coolview and NTEmacs) Earnie Boyd
1998-01-07 12:35 ` Scott Blachowicz
1998-01-07 14:50 ` Fergus Henderson
1998-01-07 22:33 ` Jeffrey C. Fried
1998-01-08 10:46 ` Scott Blachowicz
1998-01-09 11:09 ` Larry Hall (RFK Partners Inc)
1998-01-12 20:11 ` Scott Blachowicz
1998-01-16 2:56 ` Benjamin Riefenstahl
1998-01-10 6:19 ` Why text=binary mounts (Re: Gnu-win32 (b18), coolview and NTE Michael Hirmke
1998-01-11 15:55 ` Larry Hall
[not found] <23>
[not found] ` <Feb>
[not found] ` <97>
[not found] ` <18:00:22>
[not found] ` <PST_2@ccm.hf.intel.com>
1997-03-19 18:13 ` Understanding program startup DG Ellis
[not found] ` <19>
[not found] ` <Mar>
[not found] ` <05,>
[not found] ` <2000>
[not found] ` <at>
[not found] ` <12:47PM>
2000-03-05 10:05 ` What is a "forward slash" Michael Hirmke
[not found] ` <08:00:42AM>
[not found] ` <-0800>
2000-03-12 16:21 ` various packages Michael Hirmke
[not found] ` <(PST)>
2000-12-20 16:39 ` new install of cygwin with pdksh doesn't work Earnie Boyd
2000-12-20 17:36 ` David M. Karr
2000-12-20 18:18 ` Chris Abbey
2000-12-21 6:27 ` Earnie Boyd
2000-12-21 8:33 ` David M. Karr
2000-12-21 12:17 ` David M. Karr
2000-12-21 12:48 ` Larry Hall (RFK Partners, Inc)
2000-12-21 13:06 ` Earnie Boyd
2001-01-03 9:56 ` David M. Karr
2001-01-03 14:03 ` Larry Hall (RFK Partners, Inc)
[not found] ` <14:50:18>
[not found] ` <+0000>
[not found] ` <(CT0)>
2000-12-20 19:38 ` Earnie Boyd
2000-12-20 22:54 ` David M. Karr
2000-12-21 6:40 ` Markus Hoenicka
2000-12-21 8:48 ` David M. Karr
2000-12-21 10:46 ` Larry Hall (RFK Partners, Inc)
2000-12-21 16:10 ` Jari Aalto+mail.emacs
2000-12-21 16:22 ` Corinna Vinschen
2000-12-21 16:32 ` Christopher Faylor
2000-12-21 16:31 ` Christopher Faylor
2000-12-22 6:29 ` Markus Hoenicka
2000-12-23 7:03 ` Jari Aalto+mail.linux
[not found] ` <(GMT)>
2001-02-11 8:18 ` QT chris
2001-02-11 15:48 ` QT Dr. Volker Zell
2001-02-12 7:02 ` QT Jonathan Fosburgh
2001-02-12 9:36 ` QT Dr. Volker Zell
2001-02-14 17:05 ` QT - request for bind cygwin patch file Kevin Wright
1997-03-19 23:02 ` Understanding program startup Jim Balter
[not found] ` <10:42:13>
1997-03-26 17:32 ` Re[2]: Linking with .LIB files David W Palmer
1997-03-25 12:55 ` David W Palmer
[not found] ` <01>
1997-03-26 9:44 ` Nick Ing-Simmons
1997-03-27 0:57 ` Jim Balter
[not found] ` <12:12:26>
1997-03-31 12:13 ` Re[2]: " David W Palmer
1997-03-27 15:33 ` Jim Balter
1997-03-27 20:59 ` Re[2]: " David W Palmer
[not found] ` <17>
[not found] ` <10:05:43>
1997-04-01 10:31 ` DLL to lib*.a? David W Palmer
1997-02-23 10:38 ` Re[2]: globbing feature in 17.1 when not under bash issue (b DG Ellis
1997-03-21 10:46 ` Re[2]: Understanding program startup DG Ellis
1997-03-24 10:32 ` Windows API calls that don't work? (Was RE: Stupid stupi David W Palmer
1997-04-02 7:11 ` DLL to lib*.a? kunglao
[not found] ` <13:07:28>
1997-04-08 18:15 ` Re[2]: env command does not work correctly DG Ellis
[not found] ` <14:20:27>
1997-07-17 14:20 ` Installing b18 usertools Brett A Carter
[not found] <Bob>
[not found] <Sebastien>
[not found] <Mumit>
[not found] <Benjamin>
[not found] <Markus>
[not found] <Michael>
[not found] ` <H.>
[not found] <john>
[not found] <Earnie>
[not found] <Corinna>
[not found] <Larry>
[not found] <Suhaib>
[not found] ` <M.>
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).