Re: POSIX names for drive letters

> > By the way, any idea why //localhost/C$ doesn't work?

> You need to define it in your 
> $SYSTEMROOT/system32/drivers/etc/hosts file.

It is.  The error is "Given log. name not unique".  I do get

$ nslookup localhost
Server:  mail2.siemens.de
Address:  139.25.208.11

Non-authoritative answer:
Name:    localhost.ww002.siemens.net
Address:  127.0.0.1

$

which is also kind of queer---I would not have expected any positive
result, so the problem may be a misconfiguration of our corporate
network.

Regards,

Konrad

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

Re: POSIX names for drive letters

Quoting "Schwarz, Konrad" <konrad.schwarz@...>:

>> > By the way, any idea why //localhost/C$ doesn't work?
>
>> You need to define it in your
>> $SYSTEMROOT/system32/drivers/etc/hosts file.
>
> It is.  The error is "Given log. name not unique".  I do get
>
> $ nslookup localhost
> Server:  mail2.siemens.de
> Address:  139.25.208.11
>

Is your local DNS operating here?

> Non-authoritative answer:
> Name:    localhost.ww002.siemens.net
> Address:  127.0.0.1
>

So you need to fully qualify localhost or use a define a different 
alias mapped to 127.0.0.1 in the hosts file.

> $
>
> which is also kind of queer---I would not have expected any positive
> result, so the problem may be a misconfiguration of our corporate
> network.
>

Re: POSIX names for drive letters

> > Non-authoritative answer:
> > Name:    localhost.ww002.siemens.net
> > Address:  127.0.0.1

> So you need to fully qualify localhost or use a define a 
> different alias mapped to 127.0.0.1 in the hosts file.

Someone on the Cygwin list had a different explanation: according to
him, server names are looked up via NetBIOS query and don't use the DNS
resolver at all.

Regards,

Konrad Schwarz

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

Re: console2

Adam Doppelt wrote:
> I started running MSYS a few days ago, but I was a bit disappointed
> by rxvt.

Yeah, I find it rather disappointing too, which is why I run MSYS in
`--norxvt' mode.

> Some googling turned up this project:
>
> http://sourceforge.net/projects/console
> screenshot: 
http://sourceforge.net/project/screenshots.php?group_id=43764
>
> Console2 has all the bling a hacker could want - great font support, 
> tabs, transparency, nice cursor animations, etc.

Didn't have time to follow up on this, when Adam posted the tip, and
just got around to it this morning.

Shame that, while they publish under GPL, they don't enter into its
spirit in their choice of development tools; it has a dependency on
MSVCP71.dll, suggesting that they use MSVC-7.1.  I don't have that
on my Win2K box, so this pig doesn't fly.

> It's a young project but seems to work pretty well. Have fun,

It doesn't work at all, for me.  I guess I'll just stick with MSYS,
warts and all, in a native Woe32 console.

Regards,

MSYS_LICENSE and the ESPL

Hi,

We have a question about the MSys license over on the the GRASS GIS*
devel. mailing list. We wish to package & redistribute a binary version
of Msys with the windows version of our software**. While I don't
expect this to be a problem due to the Open Souce nature of both
projects, checking the copyright statements in msys-1.0.10-src.tar.bz2
I see that msys/1.0/10/rt/src/MSYS_LICENSE file states: "MSYS specific
software code added regardless of existing license is covered by the 
ESPL which can be found in a file by the same name."

but there is no ESPL file there. A web search turned up a PDF for the
"EcoSpold Public License v1.0 (ESPL 1.0)", but I'm not sure if that is
what the MSys source is refering to.

???

thanks,
Hamish

[*] GRASS: http://grass.itc.it; GPL software

[**] http://thread.gmane.org/gmane.comp.gis.grass.devel/14901/focus=14961

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

Re: MSYS_LICENSE and the ESPL

Hamish wrote:
> We have a question about the MSys license over on the the GRASS GIS*
> devel. mailing list. We wish to package & redistribute a binary version
> of Msys with the windows version of our software**. While I don't
> expect this to be a problem due to the Open Souce nature of both
> projects, checking the copyright statements in msys-1.0.10-src.tar.bz2
> I see that msys/1.0/10/rt/src/MSYS_LICENSE file states: "MSYS specific
> software code added regardless of existing license is covered by the 
> ESPL which can be found in a file by the same name."

Hmm. Yes I too can see that file in CVS, and it sure is confusing, for
the license file you should be reading is here:
http://mingw.cvs.sourceforge.net/mingw/msys/dvlpr/doc/msys/MSYS_LICENSE.rtf

(You should also find it in the `d:/msys/1.0/doc/msys' directory, after
 an MSYS installation to the default path on drive `d:').

> but there is no ESPL file there. A web search turned up a PDF for the
> "EcoSpold Public License v1.0 (ESPL 1.0)", but I'm not sure if that is
> what the MSys source is refering to.

I've really no idea what license this refers to; perhaps Earnie may
comment.  To avoid confusion, I'd suggest removal of the older license
file from CVS, and future source distributions.

Regards,
Keith.

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?

Re: MSYS_LICENSE and the ESPL

Quoting Hamish <hamish_nospam@...>:

> Hi,
>
> We have a question about the MSys license over on the the GRASS GIS*
> devel. mailing list. We wish to package & redistribute a binary version
> of Msys with the windows version of our software**. While I don't
> expect this to be a problem due to the Open Souce nature of both
> projects, checking the copyright statements in msys-1.0.10-src.tar.bz2
> I see that msys/1.0/10/rt/src/MSYS_LICENSE file states: "MSYS specific
> software code added regardless of existing license is covered by the
> ESPL which can be found in a file by the same name."
>
> but there is no ESPL file there. A web search turned up a PDF for the
> "EcoSpold Public License v1.0 (ESPL 1.0)", but I'm not sure if that is
> what the MSys source is refering to.
>

You may replace the 1.0.10 license with the attached; the attached is 
what is currently in CVS HEAD.  I'm not sure what ESPL is and I wrote 
the document. :)

Earnie Boyd

http://shop.siebunlimited.com

-------------------------------------------------------------------------

Re: console2

Keith MARSHALL wrote:
> Adam Doppelt wrote:
>
>> I started running MSYS a few days ago, but I was a bit disappointed
>> by rxvt.
>>
>
> Yeah, I find it rather disappointing too, which is why I run MSYS in
> `--norxvt' mode.
>
>
>> Some googling turned up this project:
>>
>> http://sourceforge.net/projects/console
>> screenshot:
>>
> http://sourceforge.net/project/screenshots.php?group_id=43764
>
>> Console2 has all the bling a hacker could want - great font support,
>> tabs, transparency, nice cursor animations, etc.
>>
>
> Didn't have time to follow up on this, when Adam posted the tip, and
> just got around to it this morning.
>
> Shame that, while they publish under GPL, they don't enter into its
> spirit in their choice of development tools; it has a dependency on
> MSVCP71.dll, suggesting that they use MSVC-7.1.  I don't have that
> on my Win2K box, so this pig doesn't fly.
>

Missing Man Found

So I regularly notice (and acknowledge with shaking fist) that there
is no man facility that comes with either MingW or MSYS. Yes there are
man pages, but no man program (which is just cruel). I acquired the
GnuWin32 groff package but still no man. However I am not the type of
person to just complain about things, so I just made my own. The
attached shell script is a man stand-in. It requires groff, bash, and
grep but nothing else (abnormal). Also whatis "man -k" works if you have
the makewhatis shell/awk script from the gnu man distro or copy the
whatis files from another system.

What is implemented:
* has the magical incantation groff switches to read a man page
* section matching i.e. -S works so "unlink" and "int unlink( char * )"
   respective pages in section 1 and section 3 are accessable
* reads MANPATH environment var
* allows you to prepend to the MANPATH with -M
* allows whatis lookups via man -k <pattern>

Caveats:
* gz and bz2 handing not coded yet
* caching and cat pages not handled yet
* GnuWin32 C man page package and groff package needed

BTW I have a number of other functions, macros, and tools to make a
mingw+msys+win32 system compatible with a Linux system (except X
intrinsics which is sorely needed [166 functions only half needed]) if
they are wanted.

Aron

Re: Missing Man Found

On Thursday 07 September 2006 4:39 pm, Aron Rubin wrote:
> So I regularly notice (and acknowledge with shaking fist) that there
> is no man facility that comes with either MingW or MSYS. Yes there are
> man pages, but no man program (which is just cruel).

So, you've been asleep for about the past year then   See the 
`Documentation' section of our own FAQ:
http://www.mingw.org/MinGWiki/index.php/FAQ

The `officially' sanctioned, and supported versions of `groff' and `man' 
for MinGW and MSYS are here:
http://prdownloads.sourceforge.net/mingw/groff-1.19.2-mingwPORT-1.tar.bz2?download
http://prdownloads.sourceforge.net/mingw/man-1.6-mingw-beta-1-src.tar.gz?download

The first of these is our own delivery package for official `groff' 
direct from GNU source, prepared and maintained by myself; (I am an 
official GNU developer for `groff', in addition to my role as MinGW 
administrator).  The `man' package is my own port of John Eaton's `man', 
(which is the basis for both variants of `man' currently deployed in 
GNU/Linux, and also the BSDs I believe); this port is specifically for 
MinGW/MSYS.  It provides a fully functional `man' implementation, 
including `apropos', `whatis' and `makewhatis', and comes complete with 
all of the manpages relating to these.  It remains `beta', simply because 
I haven't yet completed the port of the internationalised message 
catalogues for its diagnostic messages; however, it does already support 
installable manpages in a number of languages.

Please note that `man' is *not* a GNU package; there is not, and never 
has been, a GNU implementation of `man'.