On 21 Jun, Andrey Alekseyev wrote:
Don,
old vnode and its associated file handle. If the file on the server was
renamed and not deleted, the server won't return ESTALE for the handle
I'm all confused and messed up :) Actually, a rename on the server is not
the same as sillyrename on the
I'm trying to link a lang/fpc program, and ld bombs out with
ld: Memory exhausted when it reaches my physical memory limit. Worse,
it bombed when only one third of the .a's were loaded.
I tried to link with the most optimal deadcode elimination, by simply
creating a smartlinkable compilation
On Sat, Jun 21, 2003 at 05:12:20PM +0200, Soeren Straarup wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi how is it normal to treat auto email replies like this one?
Best regards Søren
Hi Søren,
Best thing to do with these messages is ignore them :-) It's just MS
Outlook being
On Sat, 21 Jun 2003, David Schultz wrote:
dds@ has expressed some interest in compiling the FSMs for regexps
into native code, which would make it blazingly fast. See [EMAIL PROTECTED]
As a practical matter, there are only a couple of zealots who care
what kind of license grep is under, so
Propably not quite the right list - but given the number of people working
on wireless code here:
- In the prism/2 and 2.5 firware are so called Firmware Information
records. The types 1 .. 4 are defined (and I can handle those
now). However I occasionally see a type 0x8001
On Sun, 22 Jun 2003, Dirk-Willem van Gulik wrote:
-In the prism/2 and 2.5 firware are so called Firmware Information
records. The types 1 .. 4 are defined (and I can handle those
now). However I occasionally see a type 0x8001 - i.e. the version
info type with the top bit
Sean Farley [EMAIL PROTECTED] writes:
Reasons to consider for switching:
1. GNU's grep -r option is broken according to the following post.
That reason alone is enough for me, as I regularly run into this
problem when grepping the kernel tree (recursive directory loop due
to back-pointing
On Sun, 22 Jun 2003, Dag-Erling Smørgrav wrote:
Unfortunately, FreeGrep has annoying bugs as well. For instance, it
tries to grep the directories themselves (rather than just their
contents) when recursing, while GNU grep only greps directories if
they are explicitly listed on the command
On Sun, 22 Jun 2003, Matthew N. Dodd wrote:
I've got a number of firmware images here I was testing my firmware image
parser against and haven't run into the record type above.
Which firmware are you seeing this in?
Lets dig into this off-list :-)
Dw.
[ no need to cc me ]
Hello,
I'm running -current. There's some Linux code in plex86
(http://plex86.sf.net/) that does something like
fdTunTap = open(/dev/net/tun, O_RDWR);
// IFF_TAP is for Ethernet frames.
// IFF_TUN is for IP.
// IFF_NO_PI is for not receiving extra meta packet
Sean Farley [EMAIL PROTECTED] wrote:
Reasons to consider for switching:
For whatever little it's worth, OpenBSD just switched to freegrep
(a somewhat modified version from NetBSD). They also dumped the
GNU gzip implementation, after extending compress to substitute as
/usr/bin/gzip.
--
your handling of -i at least is incorrect. after patching, i get very
wrong results. results vary depending on length of string.
reuelos:/tmp/grep-0.16 ./grep -i fastgrep *
grep.c:fastgrep_t *fg_pattern;
reuelos:/tmp/grep-0.16 ./grep fastgrep *
grep.c:fastgrep_t *fg_pattern;
12 matches
Mail list logo
