ot adjust line
| man1/bash.1.gz:1: warning [p 1, 2.5i]: cannot adjust line
| groff: troff: Signal 11
| grotty::163:warning: no final `x stop' command
| BASH_BUILTINS(1) BASH_BUILTINS(1)
| [...]
L8r,
Buzz.
--
) | | ---/ ---/ Yes, this | This message consists of true | I do not
--
-vr for the ``good'' one:
1.5.19(0.138/4/2) 2005-09-03 18:12
Sorry for the mess.
L8r,
Buzz.
--
) | | ---/ ---/ Yes, this | This message consists of true | I do not
-- | | // really is | and false bits entirely.| mail for
) | | //a 72 by 4 +
Op Fri, 2 Dec 2005 02:05:16 +0100 (MET) schreef Buzz
in buzzy-box.bavag>:
: Actually, it was September 9. I forgot to clean up after a test.
Aargh! September 3rd.
: The uname -vr for the ``good'' one:
: 1.5.19(0.138/4/2) 2005-09-03 18:12
Right.
: Sorry for the mess.
Again.
the $windir environment variable seems to
: be required by WinSock on Windows 95 while later versions apparently
: don't need any variable value. All NT versions OTOH need $SYSTEMROOT.
: Go figure.
Great! Thanks for finding, fixing and explaining that.
: Thanks for testing,
You're
the primary prompt string. The default value is
| ``\s-\v\$ ''.
)
: And the arbitrary use of ticks `
Those <`> are called back-ticks... (and there is nothing arbitrary
about my use of them, IMHO.)
I did accidently start my quotes with <''>, not <``>. So
Op Wed, 21 Dec 2005 00:46:48 -0500 schreef Christopher Faylor
in <[EMAIL PROTECTED]>:
: On Wed, Dec 21, 2005 at 05:16:34AM +0100, Bas van Gompel wrote:
[With a freshly built dll from a CVS-checkout on Dec 20. extra consoles
pop up when logging into sshd on w95]
You fixed it. Great.
L8r,
Op Thu, 22 Dec 2005 10:05:05 +0100 schreef Holger Krull
in <43AA6C41.9080508gmx.de>:
[``strange quoting''?]
: But i believe folks will call this OT now.
So do I. Read my slightly more topical response on the talk-list.
L8r,
Buzz.
--
) | | ---/ ---/ Yes, this | This mes
com/ml/cygwin/2005-12/msg00923.html
I saw it. That's what happens when you try to report ASAP, are not on
a fixed line and don't check your mail every minute... Sorry about the
duplication.
L8r,
Buzz [deer otter bee an owl].
--
) | | ---/ ---/ Yes, this | This message consists of tr
xie.casa.cgf.cx>:
: > Testing a self-built dll from a CVS-checkout on December 23rd.
Rebuilt on the 24rd (GMT+1).
: http://cygwin.com/ml/cygwin/2005-12/msg00923.html
And (of course) you fixed it. Great, Many thanks (not just for this
fix).
*Best* *Cygwin* *Ever*.
L8r,
Buzz [not B20].
--
d you set $DISPLAY correctly? If the
: terminal is a remote X terminal, did you allow your Cygwin client to
: connect (xhost)?
Aargh! An X-app. So I /was/ doing something wrong...
Sorry about the noise.
Thanks. L8r,
Buzz. [Note to self: gtk is xy.]
--
) | | ---/ ---/ Yes, this | This message co
ond exec: Done."
Right, my bad. Following shows the same (odd, IMO) behavior.
=== begin testexec2b.sh ===
#!/bin/bash
exec 5<&0
echo 'echo "First exec: Done."
exec 0<&5
echo "Second exec: Done."
exit 0' |exec /bin/bash
end testexec2b.sh
[No need to Cc me.]
Op Wed, 25 Jan 2006 20:28:32 + schreef Eric Blake
in
<012520062028.10525.43D7DF6F0008E6E6291D22007507840A050E040D0C079D0Acomcast.net>:
[Adding attrib to self:]
: Buzz:
: > I (now) understand what's happening. I think it's undesirable, though.
:
:
it isn't AFAICT.
bin_PROGRAMS = chage chfn chsh expiry gpasswd newgrp passwd rpasswd
sbin_PROGRAMS = chpasswd groupadd groupdel groupmod grpconv grpunconv \
pwconv pwunconv rpasswdd useradd userdel usermod vipw \
pwck grpck
L8r,
Buzz.
--
) | | ---/ ---/ Yes
e: Fri Mar 26 06:37:12 2004
Windows 95 Ver 4.0 Build 1212
Path: k:\cygwin\local\users\Buzz\bin
d:\cygwin\bin
c:\WINDOWS
c:\WINDOWS\COMMAND
c:\DOS
c:\UTIL
c:\UTIL\BVG
d:\cygwin\bin
i:\PROGRAMT\AVG6
k:\cygwin\local\USERS\BUZZ\BI
. Let's wait for the response from
the Red Hat legal department. I just mailed this here FYI.
hth, hand.
EOT IIIUTM
Buzz.
--
) | | ---/ ---/ Yes, this | This message consists of true | I do not
-- | | // really is | and false bits entirely.| mail for
) | | /
, not 0
n1 S14 p5 is 0x7f, not 0
n1 S14 p6 is 0x14, not 0
n1 S14 p7 is 0x61, not 0
n1 S14 p12 is 0x81, not 0
This indicates malloc returning non-zeroed memory.
Has anybody got a clue as to what's going on?
L8r,
Buzz.
--
) | | ---/ ---/ Yes, this | This message consists of
Op Tue, 6 Mar 2007 22:23:22 -0800 schreef Gary Johnson
in <20070307062322.GA21235 AT suncomp1.spk.agilent.com>:
: On 2007-03-07, Buzz wrote:
[...]
: > This indicates malloc returning non-zeroed memory.
: >
: > Has anybody got a clue as to what's going on?
:
: Malloc() re
17 matches
Mail list logo
