Re: OSTYPE

2002-01-06 Thread Jerome BENOIT
I am very sorry for my big mistake. Jerome "Larry Hall (RFK Partners, Inc)" wrote: > > I'm sorry Jerome but this issue has been discussed to death in the email > archives. If you want to find out why OSTYPE and various other environment > variables are no longer set

Re: OSTYPE

2002-01-06 Thread Larry Hall (RFK Partners, Inc)
I'm sorry Jerome but this issue has been discussed to death in the email archives. If you want to find out why OSTYPE and various other environment variables are no longer set by default in bash, please check the email archives. The reason and discussion is all there. Let's keep the

RE: OSTYPE

2002-01-06 Thread Stephan Mueller
OMPAT (which documents incompatibilities between the current bash and the previous widely-available version, 1.14), item 15: Bash no longer auto-exports the HOME, PATH, SHELL, TERM, HOSTNAME, HOSTTYPE, MACHTYPE, or OSTYPE variables. I'll bet your Debian box is running a slightly older

Re: OSTYPE

2002-01-06 Thread Jerome BENOIT
Fine, but on my Debian box `printenv OSTYPE' gives something. Is it a cygwin feature ? Thanks, Jerome BENOIT "Gerrit P. Haase" wrote: > > Hallo Jérôme-Georges-Michel, > > Am 2002-01-06 um 18:37 schriebst du: > > > Bonjour, > > > what have happen

Re: OSTYPE

2002-01-06 Thread Gerrit P. Haase
Hallo Jérôme-Georges-Michel, Am 2002-01-06 um 18:37 schriebst du: > Bonjour, > what have happened to OSTYPE ? > `printenv OSTYPE' gives nothing ! $ printenv | grep OSTYPE $ set | grep OSTYPE OSTYPE=cygwin $ echo $OSTYPE c

OSTYPE

2002-01-06 Thread Jérôme-Georges-Michel BENOIT
Bonjour, what have happened to OSTYPE ? `printenv OSTYPE' gives nothing ! Thanks in advance, Jerome BENOIT -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.htm