Oakley GASCAN

Esteemed Mr/Mrs On the behalf of Bientuni Pte Ltd Branches in Singapore.I would like to deal a bussiness arrangement to your company, we sincere would like you to provide us #25 unit of Oakley GASCAN Polished Black/Black Gradient. Where we seriously will order from you. But firs

why doesn't "exec" replace current executable w/new

I'm curious -- I thought "exec" was supposed to replace the currently running executing image with the new image. When I do an "exec" in "bash", it leaves the original bash.exe in memory -- but only if the parent is at the top of its tree. I.e. -- I can exec multiple bash's, but only the initial

RE: why doesn't "exec" replace current executable w/new

On 06 November 2006 11:46, Linda Walsh wrote: > So why the top level bash? Is there anything the parent bash can > do that the child bash cannot? The obvious WAG would be "wait for SIGCHLD, meaningfully" :) cheers, DaveK -- Can't think of a witty .sigline today -- Unsubscri

Re: why doesn't "exec" replace current executable w/new

On Mon, Nov 06, 2006 at 11:51:20AM -, Dave Korn wrote: >On 06 November 2006 11:46, Linda Walsh wrote: >>So why the top level bash? Is there anything the parent bash can do >>that the child bash cannot? > >The obvious WAG would be "wait for SIGCHLD, meaningfully" :) Well, there's that, and the

Re: Mapping of \device\harddisk12 and beyond

On Nov 2 18:29, Loh, Joe wrote: > --- cygwin-1.5.19-4/winsup/cygwin/dtable.cc 2006-01-16 > 11:14:35.0 -0600 > +++ src/winsup/cygwin/dtable.cc 2006-11-02 18:13:13.154011100 -0600 > @@ -378,6 +378,7 @@ > case DEV_FLOPPY_MAJOR: > case DEV_CDROM_MAJOR: > case DEV_SD_MAJOR: >

Midnight Commander problem

Hello, Thank all you Cygwin contributors for MC under Win32, at last I can use the same rules in both Windows and Linux. There's a little problem with running programs from CD: If I'm right MC uses /tmp directory for small sh scripts doing run job, but when you change to /cygdrive/d or whate

Re: Question on Super converter and cygwin1.dll

Clayton, First, . I'm redirecting this to the appropriate Cygwin mailing list, and setting the Reply-To: accordingly. Please make sure your mailer respects it. Thanks. More below. On Mon, 6 Nov 2006, Clayton Poole wrote: > Hi - > > I was recently doing a G

Re: Midnight Commander problem

On Mon, 6 Nov 2006, Ruslan Fedyarov wrote: > Hello, > > Thank all you Cygwin contributors for MC under Win32, at last I can use > the same rules in both Windows and Linux. There's a little problem with > running programs from CD: > > If I'm right MC uses /tmp directory for small sh scripts doing r

Bash 3.1.17(9) $@ Expansion error

Hi, I have just tried a 'make check' on CSSC-1.0.1 and found a number of failures caused by what would appear to be a $@ expansion failure for the case where $@ is an empty string. It expands to '\x7F' !!! Test case: Download and unpack CSSC-1.0.1. Enter the following commands: cd CSSC-1.0.1

Re: Imagamagick build fails with new libfontconfig1 - Was: [ANNOUNCEMENT] Updated: fontconfig-2.4.1-2

"Yaakov S (Cygwin Ports)" <[EMAIL PROTECTED]> writes: > | # Directory that this library needs to be installed in: > | libdir='/home/janneke/vc/gub-dev/target/cygwin/system/usr/lib' > | - snap - > Was this fixed in the -2 releases of of Jan's packages? If not, there > should be a -3 ASAP. I'm wo

setup.exe creates files outside install directory

Good day, I installed cygwin to C:\bens\cygwin, and afterwards I found install.log and install.log.full under C:\cygwin\var\log. Cheers, Ben -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cy

RE: setup.exe creates files outside install directory

On 06 November 2006 16:54, Ben Collver wrote: > Good day, > > I installed cygwin to C:\bens\cygwin, and afterwards I found install.log > and install.log.full under C:\cygwin\var\log. > When setup.exe starts up, it has to open the logfile before it asks you where you want it installed to. If

Re: Bash 3.1.17(9) $@ Expansion error

Mark Fortescue mtfhpc.demon.co.uk> writes: > I have just tried a 'make check' on CSSC-1.0.1 and found a number of > failures caused by what would appear to be a $@ expansion failure for the > case where $@ is an empty string. > It expands to '\x7F' !!! This may be the same bug as was reported up

Command

subscribe -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/

Re: Command

Flarn wrote: subscribe Command failed! Error - insufficient reading comprehension Reread -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508

RE: setup.exe creates files outside install directory

On Mon, 6 Nov 2006, Dave Korn wrote: > On 06 November 2006 16:54, Ben Collver wrote: > > > Good day, > > > > I installed cygwin to C:\bens\cygwin, and afterwards I found install.log > > and install.log.full under C:\cygwin\var\log. > > When setup.exe starts up, it has to open the logfile before

Re: 1.5.19-4: sshd: "child_copy: linked dll data write copy failed" after computer reboot (Windows 2003 Server SP1)

On June 6, 2006, =?iso-8859-1?q?Ren=E9_Krell?= <[EMAIL PROTECTED]> wrote: > Hello René, > > Thanks for your notes, comments below: > > On Sunday 04 June 2006 23:22, René Berber wrote: > > René Krell wrote: > > > Well, following the last recommendations I re-installed Cygwin with > > > opensshd f

Re: Midnight Commander problem

Sending the cygcheck output. May cue to the problem is that I haven't used setup.exe for installation, I got used to just unpacking the necessary package under Linux. Igor Peshansky wrote:: On Mon, 6 Nov 2006, Ruslan Fedyarov wrote: Hello, Thank all you Cygwin contributors for MC under