Re: Problem in bin/sh stripping the * character through ${expansion%}

2009-08-06 Thread Eygene Ryabinkin
Doug, good day. Thu, Aug 06, 2009 at 11:15:12AM -0700, Doug Barton wrote: > I came across this problem during a recent portmaster update. When > trying to strip off the * character using variable expansion in bin/sh > it doesn't work. Other "special" characters do work if they are > properly escap

Re: Problem in bin/sh stripping the * character through ${expansion%}

2009-08-06 Thread Johan van Selst
Johan van Selst wrote: > When I tried it myself, I automatically typed quotes, which does work > var="${var%\*}" Really should learn to read better: this in fact procudes 'foo' rather than 'foo\' in the given example case. Again, not like bash. Johan pgpbI94sMye6i.pgp Description: PGP si

Re: Problem in bin/sh stripping the * character through ${expansion%}

2009-08-06 Thread Johan van Selst
Doug Barton wrote: > I came across this problem during a recent portmaster update. When > trying to strip off the * character using variable expansion in bin/sh > it doesn't work. Other "special" characters do work if they are > properly escaped. Your script does var=${var%\*} When I trie

Problem in bin/sh stripping the * character through ${expansion%}

2009-08-06 Thread Doug Barton
Howdy, I came across this problem during a recent portmaster update. When trying to strip off the * character using variable expansion in bin/sh it doesn't work. Other "special" characters do work if they are properly escaped. The attached mini-script clearly shows the problem: $ sh sh-strip-pro

Re: sosend() and mbuf

2009-08-06 Thread John Baldwin
On Tuesday 04 August 2009 12:57:25 pm Dag-Erling Smørgrav wrote: > Ed Schouten writes: > > Maslan writes: > > > However, when i checked the pid & tid of the new created thread it > > > was not the same as the parent nor as the proc0 & thread0 > > I am not sure, but sharing another process's addre