Another bash problem?

Another bash problem?

[Guansong Zhang]

I used to export CYGWIN=tty in B20.1, I forgot the exact reason.

But with the latest net release, this setting has a problem.

With the above setting under bash prompt type

$ bash
$ exit

then type any command, bash won't echo it back. This also will happen if you
do a "man" and quit.

So is this setting still recommanded? Or this is a problem?

Thanks,

Best regards,

Guansong

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Another bash problem?

[Chris Faylor]

On Thu, Jun 01, 2000 at 12:24:01AM -0700, Guansong Zhang wrote:
>I used to export CYGWIN=tty in B20.1, I forgot the exact reason.
>
>But with the latest net release, this setting has a problem.
>
>With the above setting under bash prompt type
>
>$ bash
>$ exit
>
>then type any command, bash won't echo it back. This also will happen if you
>do a "man" and quit.
>
>So is this setting still recommanded? Or this is a problem?

There are no "recommended" settings for the CYGWIN environment variable.
You can set it to do whatever you think is important.

Unfortunately, I can't duplicate your behavior here.  cygcheck output
might help.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Another bash problem?

[Guansong Zhang]

So this IS a problem. I forget to mention, my system is windows 2000.

Guansong

----- Original Message -----
From: "Chris Faylor" <cgf@cygnus.com>
To: <cygwin@sourceware.cygnus.com>
Sent: Wednesday, May 31, 2000 9:40 PM
Subject: Re: Another bash problem?


> On Thu, Jun 01, 2000 at 12:24:01AM -0700, Guansong Zhang wrote:
> >I used to export CYGWIN=tty in B20.1, I forgot the exact reason.
> >
> >But with the latest net release, this setting has a problem.
> >
> >With the above setting under bash prompt type
> >
> >$ bash
> >$ exit
> >
> >then type any command, bash won't echo it back. This also will happen if
you
> >do a "man" and quit.
> >
> >So is this setting still recommanded? Or this is a problem?
>
> There are no "recommended" settings for the CYGWIN environment variable.
> You can set it to do whatever you think is important.
>
> Unfortunately, I can't duplicate your behavior here.  cygcheck output
> might help.
>
> cgf
>
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
>
>

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Another bash problem?

[Chris Faylor]

On Thu, Jun 01, 2000 at 01:02:59AM -0700, Guansong Zhang wrote:
>So this IS a problem. I forget to mention, my system is windows 2000.

So is mine.  I cannot duplicate this.  cygcheck -r -s -v output might help
debug the problem.

cgf

>----- Original Message -----
>From: "Chris Faylor" <cgf@cygnus.com>
>To: <cygwin@sourceware.cygnus.com>
>Sent: Wednesday, May 31, 2000 9:40 PM
>Subject: Re: Another bash problem?
>
>
>> On Thu, Jun 01, 2000 at 12:24:01AM -0700, Guansong Zhang wrote:
>> >I used to export CYGWIN=tty in B20.1, I forgot the exact reason.
>> >
>> >But with the latest net release, this setting has a problem.
>> >
>> >With the above setting under bash prompt type
>> >
>> >$ bash
>> >$ exit
>> >
>> >then type any command, bash won't echo it back. This also will happen if
>you
>> >do a "man" and quit.
>> >
>> >So is this setting still recommanded? Or this is a problem?
>>
>> There are no "recommended" settings for the CYGWIN environment variable.
>> You can set it to do whatever you think is important.
>>
>> Unfortunately, I can't duplicate your behavior here.  cygcheck output
>> might help.
>>
>> cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Another bash problem?

[Guansong Zhang]

Thanks a lot. attached is the check out put. By the way, does stty work in
your bash?

Thanks again.

Guansong

----- Original Message -----
From: "Chris Faylor" <cgf@cygnus.com>
To: <cygwin@sourceware.cygnus.com>
Sent: Wednesday, May 31, 2000 10:05 PM
Subject: Re: Another bash problem?


> On Thu, Jun 01, 2000 at 01:02:59AM -0700, Guansong Zhang wrote:
> >So this IS a problem. I forget to mention, my system is windows 2000.
>
> So is mine.  I cannot duplicate this.  cygcheck -r -s -v output might help
> debug the problem.
>
> cgf
>
> >----- Original Message -----
> >From: "Chris Faylor" <cgf@cygnus.com>
> >To: <cygwin@sourceware.cygnus.com>
> >Sent: Wednesday, May 31, 2000 9:40 PM
> >Subject: Re: Another bash problem?
> >
> >
> >> On Thu, Jun 01, 2000 at 12:24:01AM -0700, Guansong Zhang wrote:
> >> >I used to export CYGWIN=tty in B20.1, I forgot the exact reason.
> >> >
> >> >But with the latest net release, this setting has a problem.
> >> >
> >> >With the above setting under bash prompt type
> >> >
> >> >$ bash
> >> >$ exit
> >> >
> >> >then type any command, bash won't echo it back. This also will happen
if
> >you
> >> >do a "man" and quit.
> >> >
> >> >So is this setting still recommanded? Or this is a problem?
> >>
> >> There are no "recommended" settings for the CYGWIN environment
variable.
> >> You can set it to do whatever you think is important.
> >>
> >> Unfortunately, I can't duplicate your behavior here.  cygcheck output
> >> might help.
> >>
> >> cgf
>
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
>
>

Re: Another bash problem?

[Kazuhiro Fujieda]

>>> On Thu, 1 Jun 2000 00:24:01 -0700
>>> "Guansong Zhang" <guansong@hotmail.com> said:

> I used to export CYGWIN=tty in B20.1, I forgot the exact reason.
> But with the latest net release, this setting has a problem.
> With the above setting under bash prompt type
> 
> $ bash
> $ exit
> 
> then type any command, bash won't echo it back. This also will happen if you
> do a "man" and quit.

You probably set the CYGWIN variable in .bashrc. This setting
certainly causes such problem. You should set this variable in
the system environment.

There is a more detailed explanation about setting this variable
in the message
< 1DB8BA4BAC88D3118B2300508B5A552CD92546@mail.fitlinxx.com >
from David Bolen.
____
  | AIST      Kazuhiro Fujieda <fujieda@jaist.ac.jp>
  | HOKURIKU  School of Information Science
o_/ 1990      Japan Advanced Institute of Science and Technology

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Another bash problem?

[Earnie Boyd]

--- Guansong Zhang <guansong@hotmail.com> wrote:
> I happen to use this mount to have a /bin/sh. So I should to create a
> symbolic link instead.
> 

No.  /bin/sh already exists with the new format.

Regards,

=====
---
   Earnie Boyd: < mailto:earnie_boyd@yahoo.com >
            __Cygwin: POSIX on Windows__
Cygwin Newbies: < http://www.freeyellow.com/members5/gw32/index.html >
           __Minimalist GNU for Windows__
  Mingw32 List: < http://www.egroups.com/group/mingw32/ >
    Mingw Home: < http://www.mingw.org/ >

__________________________________________________
Do You Yahoo!?
Send instant messages & get email alerts with Yahoo! Messenger.
http://im.yahoo.com/

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Another bash problem?

[Earnie Boyd]

--- Guansong Zhang <guansong@hotmail.com> wrote:
-8<-
> 
> HKEY_CURRENT_USER\Software\Cygnus Solutions
> HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin
> HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2
>   (default) = `/cygdrive'
>   cygdrive flags = 0x00000020
> HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2\/
>   (default) = `e:\cygwin'
>   flags = 0x00000002
> HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2\/packages
>   (default) = `e:\packages'
>   flags = 0x00000002
> HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2\/usr/bin
>   (default) = `e:\cygwin\bin'
>   flags = 0x00000002
> HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2\/usr/lib
>   (default) = `e:\cygwin\lib'
>   flags = 0x00000002

*****************************
* > HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2\bin
* >   (default) = `/usr/bin'
* >   flags = 0x00000002
*****************************

Use regedit and delete this entry from the registry entries.

-8<-
> 
> e:\cygwin\bin  /usr/bin  user    binmode
> e:\cygwin\lib  /usr/lib  user    binmode
> e:\packages  /packages  user    binmode
> e:\cygwin  /        user    binmode

*****************************
* > \usr\bin  bin      user    binmode
*****************************

It's causing this strange mount point.


You could also try `umount bin' to see if that works but if it doesn't get rid
of this entry the regedit is the only way.

Cheers,

=====
---
   Earnie Boyd: < mailto:earnie_boyd@yahoo.com >
            __Cygwin: POSIX on Windows__
Cygwin Newbies: < http://www.freeyellow.com/members5/gw32/index.html >
           __Minimalist GNU for Windows__
  Mingw32 List: < http://www.egroups.com/group/mingw32/ >
    Mingw Home: < http://www.mingw.org/ >

__________________________________________________
Do You Yahoo!?
Send instant messages & get email alerts with Yahoo! Messenger.
http://im.yahoo.com/

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com