VERY IMPORTANT MESSAGE

2005-02-22 Thread Vladimir Balakov
Dear  Sir/ Madam,

I am Vladimir Balakov and I represent Mr. Mikhail
Khordokovsky the former C.E.O of Yukos Oil Company in
Russia. I have a very sensitive and confidential brief from
this top (oligarch) to ask for your partnership in
re-profiling funds over US$450 million. I will give
the details, but in summary, the funds are coming via
Security Company. This is a legitimate transaction. You
will be paid 4% for your "management fees".
 
If you are interested, please write back by email  and
provide me with your confidential telephone number, fax
number and email address and I will provide further details
and instructions. Please keep this confidential; we
can't afford more political problems. Finally, please
note
that this must be concluded within two weeks. Please
write back promptly.I will also suggest you visit these
news sites on the internet to be better informed about this
project.
 
http://newsfromrussia.com/main/2003/11/13/51215.html 
 
http://www.supportmbk.com/mbk/mbk_bio.cfm 
 
http://www.disinfopedia.org/wiki.phtml?title=Mikhail_B._Khodorkovsky

http://www.pbs.org/frontlineworld/stories/moscow/khodorkovskyinterview.html

http://www.forbes.com/finance/lists/!75/2004/LIR.jhtml?passListId=75&passYear=2004&passListType=Person&uniqueId=M1IF&datatype=Person

http://mikhail_khodorkovsky_society.blogspot.com/ 
 
Write me back. I look forward to it.

Regards
 
V. Balakov.




___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash


resizing drops information: bash 3.0 and xterm 200

2005-02-22 Thread Sven . Hartrumpf
Hi all.

If I make an xterm window running bash smaller and then larger again,
the information in the window doesn't get restored (only
the information visible in the smaller size is visible after
making the xterm larger).

I could use the screen command for this, but is there an easier solution?

Greetings
Sven


___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash


Travel directory - Travel Site Links Exchange

2005-02-22 Thread China Travel Guide
Dear Colleagues,

Greetings from http://www.landingchina.com/ 
If you have travel and tourism related website, we would like to exchange 
links! Welcome to our selection of travel related sites! We exchange list only 
with sites travel related all over the world. We exchange links on reciprocal 
basis only!

We will not trade with you if your site: 
* Your site directly competes with ours
* Non related links 
* Gambling or adult sites 
* Links page is not accessible from home page 
* You must follow google guidelines 
* Keep the links on a given page to a reasonable number (fewer than 100). 

Get Listed In Our Directory and Get More Traffic! We'll get your link up within 
1 week!

List your travel site links in our free Directory - Add your site now!
http://www.landingchina.com/travellinks/index.htm

Our Link Description
Landing China offers detailed China travel service and tourist information, 
including group and individual China tour packages.
URL: http://www.landingchina.com/

Looking forward for your favorable reply and hoping to be at your service in 
the nearest future. Thanks for your time!

Sincerely yours

LandingChina.com
The Professional Travel Guide To China
*
Beijing Office:
Tel: +86-10-51668586, 51668587
Fax +86-10-89547689
email: [EMAIL PROTECTED]
MSN: [EMAIL PROTECTED]
SKYPE: chinaguide
http://www.landingchina.com 

Xi'an Office:
Tel: +86-29-88372378, 88372380
Fax +86-29-88372380
email: [EMAIL PROTECTED]
SKYPE: consultant-wang
Add: 3/F, A Tower, Huajing Commercial Building, No.20 South Fenghui Rd, 
High-tech Development Zone, Xi;an, China.
Postcode: 710075

Office Hours (GMT+0800): Mon-Fri 08:30-17:30 Sat 09:00-14:00
*


___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash


"cd .." when WD unlinked gives wrong behaviour

2005-02-22 Thread Tim Waugh
Configuration Information [Automatically generated, do not change]:
Machine: i386
OS: linux-gnu
Compiler: i386-redhat-linux-gcc
Compilation CFLAGS:  -DPROGRAM='bash' -DCONF_HOSTTYPE='i386' 
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i386-redhat-linux-gnu' 
-DCONF_VENDOR='redhat' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash' -DSHELL 
-DHAVE_CONFIG_H  -I.  -I. -I./include -I./lib  -D_GNU_SOURCE 
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -g -pipe -Wp,-D_FORTIFY_SOURCE=2 
-m32 -march=i386 -mtune=pentium4
uname output: Linux gene.surrey.redhat.com 2.6.9-1.667 #1 Tue Nov 2 14:41:25 
EST 2004 i686 i686 i386 GNU/Linux
Machine Type: i386-redhat-linux-gnu

Bash Version: 3.0
Patch Level: 16
Release Status: release

Description:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=149079

When the working directory has been unlinked, "cd .." should
give an error exit status, but instead exits with code 0.
Additionally, "pwd" (the built-in) appends "/.." to the
previous working directory, rather than giving an error as it
previously did.

Repeat-By:
$ mkdir -p /tmp/foo/bar
$ cd /tmp/foo/bar
$ rm -rf /tmp/foo
$ cd ..
cd: error retrieving current directory: getcwd: cannot access
parent directories: No such file or directory
$ echo $?
0
$ pwd
/tmp/foo/bar/..
$ echo $?
0
$ pwd -P
pwd: error retrieving current directory: getcwd: cannot access
parent directories: No such file or directory
$ pwd
pwd: error retrieving current directory: getcwd: cannot access
parent directories: No such file or directory

Tim.
*/


pgpgBnmGpaYdK.pgp
Description: PGP signature
___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash


Your message to Trasno awaits moderator approval

2005-02-22 Thread trasno-bounces
Your mail to 'Trasno' with the subject

Hello

Is being held until the list moderator can review it for approval.

The reason it is being held:

SpamAssassin identified this message as possible spam (score 3.1)

Either the message will get posted to the list, or you will receive
notification of the moderator's decision.  If you would like to cancel
this posting, please visit the following URL:


http://ceu.fi.udc.es/cgi-bin/mailman/confirm/trasno/b4be7fc318d31815582be81f3eefa36f7801840f



___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash


Re: Best Phaarrmacy

2005-02-22 Thread Sera Tyler



 
Hello, Welcome 
to the best ONLINE ST0RE.
 


  
  
Vi

in $178(90p.)

a

a $209(100p.)

ana

al

  
cod
 Vi
gr
 X
x $299(90p.) Ci
is $324(90p.) 
 
With each purchase you get:
 
>Home delivery.
>Secure pay.
>Total confidentiality
>Reputable  
manufacturerrs.
 
Have a nice day!
___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash


Re: resizing drops information: bash 3.0 and xterm 200

2005-02-22 Thread Chet Ramey
[EMAIL PROTECTED] wrote:
Hi all.
If I make an xterm window running bash smaller and then larger again,
the information in the window doesn't get restored (only
the information visible in the smaller size is visible after
making the xterm larger).
I could use the screen command for this, but is there an easier solution?
Please read item E11 in the Bash FAQ.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
( ``Discere est Dolere'' -- chet )
Live...Laugh...Love
Chet Ramey, ITS, CWRU[EMAIL PROTECTED]http://tiswww.tis.cwru.edu/~chet/
___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash


Re: resizing drops information: bash 3.0 and xterm 200

2005-02-22 Thread Sven . Hartrumpf
> > If I make an xterm window running bash smaller and then larger again,
> > the information in the window doesn't get restored (only
> > the information visible in the smaller size is visible after
> > making the xterm larger).
...
On 22 Feb 2005, Chet Ramey wrote:
> Please read item E11 in the Bash FAQ.

Yes, I read and tried "shopt -s checkwinsize" before I asked this question.
Unfortunately, the problem persists.
Just to be sure: I meant that the old information in the xterm window is 
not extended by the characters that should be visible again after increasing
the window size.

Sven


pgphyhUeWTTRL.pgp
Description: PGP signature
___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash


Re: resizing drops information: bash 3.0 and xterm 200

2005-02-22 Thread Chet Ramey
[EMAIL PROTECTED] wrote:
If I make an xterm window running bash smaller and then larger again,
the information in the window doesn't get restored (only
the information visible in the smaller size is visible after
making the xterm larger).
...
On 22 Feb 2005, Chet Ramey wrote:
Please read item E11 in the Bash FAQ.

Yes, I read and tried "shopt -s checkwinsize" before I asked this question.
Unfortunately, the problem persists.
Just to be sure: I meant that the old information in the xterm window is 
not extended by the characters that should be visible again after increasing
the window size.
What do you mean by `the information in the window'?
Bash (really readline) will redraw the current command line using the
new dimensions if you resize while the line is being edited.  Everything
else is out of its hands and up to the terminal emulator.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
( ``Discere est Dolere'' -- chet )
Live...Laugh...Love
Chet Ramey, ITS, CWRU[EMAIL PROTECTED]http://tiswww.tis.cwru.edu/~chet/
___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash


-e test for file exists problem with dangling symlinks

2005-02-22 Thread John R. Vanderpool
this will probably be considered a non-bug (because the same behavior
exists in bash, ksh, pdksh, irix, and gnu coreutils!) but i'ld at least
like to hear an explanation if possible.

-e file exists test fails if file is a dangling symlink, this to me does
not seem like the correct behavior, the test should not follow the symlink
(lstat'ed instead of stat'ed).

if anything there should be a note in the man page at least.

bash-2.05b-38
coreutils-5.2.1-7

rm a b
ln -s a b

if [ -e b ]; then echo yes; fi  # bash built-in
if [ -e b ]; then echo yes; fi  # pdksh built-in
if [ test -e b ]; then echo yes; fi # bash built-in
/usr/bin/test -e b ; echo $?# coreutils


thanx for your time fish



___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash


Re: Developement

2005-02-22 Thread andrew
Norman Virus Control a supprimé le message original qui contenait le virus 
[EMAIL PROTECTED]  


___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash


Re: Mail Delivery (failure coke@cs.cmu.edu)

2005-02-22 Thread MESSAGE AGENT
This is an automatic reply.  Feel free to send additional
mail, as this program shouldn't reply to you more than
once or twice.  The following is a prerecorded message,
sent for coke:


Hi,

This is an automated reply from the account for the CMU CS coke
machine.  No one currently reads mail sent to this account.

If the coke machine has taken your money or is empty, please email 
  Charlie Garrod at [EMAIL PROTECTED] --- he's the current coke
  maintainer.



___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash


Re: -e test for file exists problem with dangling symlinks

2005-02-22 Thread Chet Ramey
John R. Vanderpool wrote:
this will probably be considered a non-bug (because the same behavior
exists in bash, ksh, pdksh, irix, and gnu coreutils!) but i'ld at least
like to hear an explanation if possible.
-e file exists test fails if file is a dangling symlink, this to me does
not seem like the correct behavior, the test should not follow the symlink
(lstat'ed instead of stat'ed).
Unless an operator explicitly acts on the link, it should follow
symlinks.  That is what open(2) does, for instance.
if anything there should be a note in the man page at least.
The current (development) version of the manual page includes:
Unless otherwise specified, primaries that operate on files follow sym-
bolic links and operate on the target of the link, rather than the link
itself.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
( ``Discere est Dolere'' -- chet )
Live...Laugh...Love
Chet Ramey, ITS, CWRU[EMAIL PROTECTED]http://tiswww.tis.cwru.edu/~chet/
___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash


Re: More bash POSIX-compliance bugs

2005-02-22 Thread Chet Ramey
> 1) time is no longer allowed to be a reserved word.  For example:

Not true; the POSIX description of time explicitly allows it to be a reserved
word.  But:

> $ set -o posix
> $ alias !='echo hi;'
> $ alias time='echi hi;'
> $ ! true# ! is reserved word, not alias
> $ echo $?
> 1
> $ time true # BUG: time should be an alias, and echo hi
> 
> real0m0.000s
> user0m0.000s
> sys 0m0.000s
> $ set +o posix
> $ ! true# outside of posix mode, bash documents that
> hi  # aliases take precedence over reserved words
> $ echo $?
> 0
> $ time true # BUG: again, time should be an alias
> 
> real0m0.000s
> user0m0.000s
> sys 0m0.000s

I can't  reproduce this.

caleb.INS.CWRU.Edu(2)$ echo $BASH_VERSION
3.00.16(4)-release
caleb.INS.CWRU.Edu(2)$ set -o posix
caleb.INS.CWRU.Edu(2)$ alias time='echo hi;'
caleb.INS.CWRU.Edu(2)$ alias !='echo hi;'
caleb.INS.CWRU.Edu(2)$ ! true
caleb.INS.CWRU.Edu(2)$ echo $?
1
caleb.INS.CWRU.Edu(2)$ time true

real0m0.001s
user0m0.000s
sys 0m0.000s
caleb.INS.CWRU.Edu(2)$ set +o posix
caleb.INS.CWRU.Edu(2)$ ! true
hi
caleb.INS.CWRU.Edu(2)$ echo $?  
0
caleb.INS.CWRU.Edu(2)$ time true
hi

> (Likewise, source is not documented as a reserved word, but since time is
> a POSIX-required utiltiy while source is not, I am okay with source
> remaining a reserved word.)

Source is not a reserved word.

> 2) The wording of bash-3.0/POSIX is misleading on item 4.  Rather than
> stating "Reserved words may not be aliased", you should state something
> like "An aliased reserved word does not undergo alias expansion if it is
> in the context of a reserved word".

OK, the wording could be clearer.

> 3) Items 18 and 19 of bash-3.0/POSIX are wrong.  Reread the description of
> cd (http://www.opengroup.org/onlinepubs/009695399/utilities/cd.html), the
> interpretation on it
> (http://www.opengroup.org/austin/interps/uploads/40/6230/AI-037.txt), and
> pending corrections to the interpretation
> (https://www.opengroup.org/sophocles/show_mail.tpl?source=L&listname=austin-group-l&id=8042).
>  Item 18 is wrong because there is nothing that states that the use of
> CDPATH turns on -P handling.  And item 19 is wrong because when CDPATH
> without . fails to find a directory in step 5, step 6 reverts to using
> $PWD (the current directory).  The following example is required to behave
> the same in POSIX mode as it currently does for normal bash mode:

I have to look at 18.  That change was made back in 1998, and the standard
does not appear to require that any longer.

I disagree that cd should default to `.' if using CDPATH.  If no directory
is found in $CDPATH, the process should stop and cd should fail.  Existing
implementations work this way.

> 4) POSIX requires that times be a special built-in.  For example:

You are correct.  Fixed.

> 5) POSIX requires that newgrp be provided as a regular shell built-in, as
> well as a standalone utility.

I disagree.  Although most of the `regular' builtins have to be
implemented within the shell, there is no POSIX requirement to do so. 
In fact, POSIX requires that every one implemented as a shell builtin
also be implemented as a separate utility.  Would you say that bash is
non-compliant if it failed to implement `true' and `false' as
builtins? 

The only requirement is the change to command search order.

> POSIX states that "A common implementation
> of newgrp is that the current shell uses exec to overlay itself with
> newgrp, which in turn overlays itself with a new shell after changing
> group. On some implementations, however, this may not occur and newgrp may
> be invoked as a subprocess."  It is the action of overlaying the current
> shell with newgrp which was the rationale for providing newgrp as a
> regular built-in, even if you choose to implement the built-in by simply
> deferring to the standalone utility rather than changing groups within
> bash before starting the new shell environment.

Sure, that's true, but there's no requirement to do so.

> On cygwin, where no one
> has yet ported a newgrp utility, bash currently fails to be
> POSIX-compliant because of the missing newgrp builtin:
> $ newgrp
> bash: newgrp: command not found

This means that cygwin is non-compliant, not that bash is not.

Chet

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
( ``Discere est Dolere'' -- chet )
Live...Laugh...Love
Chet Ramey, ITS, CWRU[EMAIL PROTECTED]http://tiswww.tis.cwru.edu/~chet/


___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash


Re: resizing drops information: bash 3.0 and xterm 200

2005-02-22 Thread Sven . Hartrumpf
On 22 Feb 2005, Chet Ramey <[EMAIL PROTECTED]> wrote:
> > Just to be sure: I meant that the old information in the xterm window is 
> > not extended by the characters that should be visible again after increasing
> > the window size.
> 
> What do you mean by `the information in the window'?

All the lines in the window.
 
> Bash (really readline) will redraw the current command line using the
> new dimensions if you resize while the line is being edited.  Everything
> else is out of its hands and up to the terminal emulator.

Thanks for the explanation.
How can I solve the problem from the terminal side (xterm or whatever)?
Or a fairer question: where should I pose the above question?

Greetings
Sven


pgpXGzB5Mre5p.pgp
Description: PGP signature
___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash


Re: resizing drops information: bash 3.0 and xterm 200

2005-02-22 Thread Chet Ramey
> > Bash (really readline) will redraw the current command line using the
> > new dimensions if you resize while the line is being edited.  Everything
> > else is out of its hands and up to the terminal emulator.
> 
> Thanks for the explanation.
> How can I solve the problem from the terminal side (xterm or whatever)?
> Or a fairer question: where should I pose the above question?

Sorry, I don't know.

Chet

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
( ``Discere est Dolere'' -- chet )
Live...Laugh...Love
Chet Ramey, ITS, CWRU[EMAIL PROTECTED]http://tiswww.tis.cwru.edu/~chet/


___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash


Re: "cd .." when WD unlinked gives wrong behaviour

2005-02-22 Thread Chet Ramey
>   https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=149079
> 
>   When the working directory has been unlinked, "cd .." should
>   give an error exit status, but instead exits with code 0.
>   Additionally, "pwd" (the built-in) appends "/.." to the
>   previous working directory, rather than giving an error as it
>   previously did.

Odd.  It only works this way on Linux.  MacOS X, FreeBSD and BSD/OS behave
as you expect.

Solaris doesn't allow the rm to work at all.

I will look into it further.

Chet

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
( ``Discere est Dolere'' -- chet )
Live...Laugh...Love
Chet Ramey, ITS, CWRU[EMAIL PROTECTED]http://tiswww.tis.cwru.edu/~chet/


___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash


[EMAIL PROTECTED]

2005-02-22 Thread hame-king
$B"""#"""#"""#"""#"""#"""#"""#""(B
$B%O%a%-%s%0$+$i=EMW$J$*CN$i$;!*(B
$B"#"""#"""#"""#"""#"""#"""#"""#(B
$B$4EPO?%a!<%k%"%I%l%9([EMAIL PROTECTED](B
$B!#%O%a%-%s%0;vL36I$G$9!#(B
$B$4MxMQNA6bL$G<:G=*DL9p$N$*CN$i$;$G$9!#(B
(B
$B!!:G=*DL9p!ZMW3NG'![(B
$B4{$K$*?69~$_4|F|$,D62a$7$F$*$j$^$9!#(B
$B$3$N$^$^!"$4F~6b$,3NG'$G$-$J$$>l9g!"$4EPO?;~$N8D?M>pJs(B($B%G!<%?(B)$B$r$b$H$K<99TIt$K$h$k?H85D4::3+;O$5$;$FD:$-$^$9!#?H85D4::8e$O$4MxMQNA6b!\0cLsB;326b!\1dBZ52<$5$$!#$J$*!"$*;YJ'$$!"$42rLs$4AjCL$O([EMAIL 
(BPROTECTED];2<$5$$!#K\F|$h$j(B2$BF|0JFb$K$*5RMM$+$i$N$42sEz$,$J$$>l9g!"0-pJs5!4X$X$NEPO?!"4J0W:[H==j$K?=$7=P!"7Y;kD#$X$NHo32FO$1$r9T$$$^$9!#>0!"$=$N>l9g$O5.EB$K8eF|!J(B20$BF|0JFb!K$KEv[EMAIL
(B PROTECTED]"MmCW$7$^$7$?$N$A!"4J0W:[H==j$K$F$4;v>[EMAIL 
(BPROTECTED]@$7$FD:$-$^$9!#$4N;>5$N$&$(!"$4H=CGD:$1$^$9MM!"$46(NO4j$$$^$9!#$J$*!"K\%a!<%k$H$4F~6b$,[EMAIL
(B PROTECTED]"$45R[EMAIL 
(BPROTECTED],$4MxMQD:$-$^$7$?EvH$N>e!"$*;YJ'$$$r$*4j$$$7$^$9!#(B
(B
(Bhttp://1107.ch/pts/?g=_default&pn=fakereg&id=f78fd9d000981ea
(B
$B!1(B[$B$4MxMQNA6b(B]$B!1!1!1!1!1!1!1!1(B
(B
(B43.000$B1_(B
(B
(B
(B
$B!1(B[$B$*;YJ'$$4|F|(B]$B!1!1!1!1!1!1!1!1(B
(B
$BF~2qF|$r4^$_(B4$BF|0JFb(B
(B
$B!1(B[$B$4MxMQ4|4V(B]$B!1!1!1!1!1!1!1!1!1(B
(B
$BF~2qF|$h$j(B90$BF|4V(B
(B
$B!1!1!1!1!1!1!1!1!1!1!1!1!1!1!1!1(B
$B>\:Y$K$D$-$^$7$F$O2<5-%Z!<%8$r!"$4;2>H2<$5$$!#(B
(B
(Bhttp://1107.ch/pts/?g=_default&pn=fakereg&id=f78fd9d000981ea
(B
(B
(B
(B
(B
(B
(B_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
$B%O%a%-%s%0;vL36I(B
(B[EMAIL PROTECTED]
(B_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
(B
(B
(B
(B
(B___
(BBug-bash mailing list
(BBug-bash@gnu.org
(Bhttp://lists.gnu.org/mailman/listinfo/bug-bash

Re: "cd .." when WD unlinked gives wrong behaviour

2005-02-22 Thread Chet Ramey
Chet Ramey wrote:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=149079
When the working directory has been unlinked, "cd .." should
give an error exit status, but instead exits with code 0.
Additionally, "pwd" (the built-in) appends "/.." to the
previous working directory, rather than giving an error as it
previously did.

Odd.  It only works this way on Linux.  MacOS X, FreeBSD and BSD/OS behave
as you expect.
Solaris doesn't allow the rm to work at all.
I will look into it further.
OK, I looked.  Here's what happens.  Bash tries to canonicalize the
directory name in the default logical mode.  Along the way, it tries
to verify the existence of each directory (e.g., to avoid the
/tmp/notthere/.. problem).  This canonicalization fails.
Ordinarily, cd might return failure right there.  Bash tries one more
time with the exact directory argument, passed straight to chdir(2).
In this case, this results in a call to chdir(".."), which, on Linux
(at least the version of Red Hat I have) succeeds (huh?).  This call
fails on the other systems I tried.
Well, once the chdir succeeds, bash has to recanonicalize the pathname
somehow.  Since the chdir succeeds, bash assumes that it can simply
call getcwd and get the right directory name, but that fails (the error
message).  Stuck, bash leaves $PWD set to the uncanonicalized name.
Since the chdir succeeded, cd returns 0.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
( ``Discere est Dolere'' -- chet )
Live...Laugh...Love
Chet Ramey, ITS, CWRU[EMAIL PROTECTED]http://cnswww.cns.cwru.edu/~chet/
___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash


Waist Magnetic Trimmer

2005-02-22 Thread winnie
Sky Products Factory

Product name: Waist Magnetic Trimmer
QTY:1000PCS 
The materials : Neoprene and Magnetic  
USD10.00/PC (with shipping cost)


http://hk.page.auctions.yahoo.com/hk/auction/1109185390?aucview=user


Thanks,

Janet



___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash