r FreeBSD's heir. You may not agree with my decision,
and I'm not asking you to. But if bwoods has the same preference that
I do, I'll gladly tell him how to implement them, and would appreciate
not being told I'm stupid in the process.
Cheers,
joelh
--
Joel Ray Holveck
issue by blocking those packets on a rule before
I send them through the NAT. This also has the advantage that after
the NAT line, I know that anything internal is part of an established
connection; that's invaluable for UDP, or was before we added dynamic
rule support.
Best,
joelh
--
Joel
Could you give me a few more details about the brokenness?
Thanks,
joelh
--
Joel Ray Holveck - [EMAIL PROTECTED]
Fourth law of programming:
Anything that can go wrong wi
sendmail: segmentation violation - core dumped
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
QTDIR, and
everything compiled fine. I haven't done much testing on it yet (only
ran kdehelp a couple of times), but nothing obvious.
Cheers,
joelh
--
Joel Ray Holveck - [EMAIL PROTECTED]
Fourth law of programming:
Anything that can go wrong wi
sendmail: segmentation violation -
nk I ended
up using a different installation method than I originally planned,
but I forgot to document it). Anyway, I'll probably bring it to 4.0
after its release, and I'll try to document whatever I do to make it
happen.
Cheers,
joelh
--
Joel Ray Holveck - [EMAIL PROTECTED]
Fou
mp;d=PALL&p=1&u=/netahtml/srchnum.htm&r=1&f=G&l=50&s1='4,405,829'.WKU.&OS=PN/4,405,829&RS=PN/4,405,829
This means that if I'm in the US, I must have permission from RSA Labs
to use the RSA algorithm. Now, there are two main ways to get
permission.
rally, if OpenSSL-based programs *expect* to build against -lrsa
and -lssl, then I have no objections.
joelh
--
Joel Ray Holveck - [EMAIL PROTECTED]
Fourth law of programming:
Anything that can go wrong wi
sendmail: segmentation violation - core dumped
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
> (gdb) run
> Starting program: /tmp/./sieve
> Program received signal SIGBUS, Bus error.
That reminds me. I thought that SIGBUS meant byte-alignment errors.
What does it mean on FreeBSD/x86?
Cheers,
joelh
--
Joel Ray Holveck - [EMAIL PROTECTED]
Fourth law of programming:
> For backup, I bought DVD-RAM drive for $400.
> 5.2GB(double side) media is around $35, you can use them as 2.3GB x 2
> disks.
No reason to buy double-sided media; just buy single-sided and punch a
hole along the edge. :-)
joelh
--
Joel Ray Holveck - [EMAIL PROTECTED]
Four
ot have them keep coming back again and again.
I suppose if you've got the computrons to waste, then it's okay.
joelh
--
Joel Ray Holveck - [EMAIL PROTECTED]
Fourth law of programming:
Anything that can go wrong wi
sendmail: segmentation violation - core dumped
To Unsubscr
closure and supposed to be read by
> DVD-ROM drives.
Although perhaps not by all DVD-ROM drives; the spec sheet for mine
(Pioneer 303S) specifically says that it won't do DVD-RAM.
joelh
--
Joel Ray Holveck - [EMAIL PROTECTED]
Fourth law of programming:
Anything that can go wrong
ot have them keep coming back again and again.
I suppose if you've got the computrons to waste, then it's okay.
joelh
--
Joel Ray Holveck - [EMAIL PROTECTED]
Fourth law of programming:
Anything that can go wrong wi
sendmail: segmentation violation - core dumped
To Unsubscr
> (gdb) run
> Starting program: /tmp/./sieve
> Program received signal SIGBUS, Bus error.
That reminds me. I thought that SIGBUS meant byte-alignment errors.
What does it mean on FreeBSD/x86?
Cheers,
joelh
--
Joel Ray Holveck - [EMAIL PROTECTED]
Fourth law of programming:
> For backup, I bought DVD-RAM drive for $400.
> 5.2GB(double side) media is around $35, you can use them as 2.3GB x 2
> disks.
No reason to buy double-sided media; just buy single-sided and punch a
hole along the edge. :-)
joelh
--
Joel Ray Holveck - [EMAIL PROTECTED]
Four
(EDT) on ttypd from xanthine:0.0
18 days 20 hours idle
Last login Mon Jun 07 19:22 (EDT) on ttypf from zygorthian-space
New mail received Wed Jun 09 00:29 1999 (EDT)
Unread since Wed Jun 09 00:00 1999 (EDT)
No Plan.
--
Joel Ray Holveck - jo...@gnu.org
Fourth law of programming:
In such a case, I would
set $PREFIX to /usr/local/test while I have KDEDIR set to
/usr/local/kde. An app looking for KDE in /usr/local/test would be
sorely disappointed.
Happy hacking,
joelh
--
Joel Ray Holveck - jo...@gnu.org
Fourth law of programming:
Anything that can go wrong w
given a counterexample. We're not looking at
making it impossible-- or even difficult-- to implement other
keepalive timing strategies in the future, if the need arises, so I
would suggest that we not concern ourselves with this discussion until
the need arises.)
Happy hacking,
joelh
--
J
configure script you quoted
(and probably all KDE configure scripts), and if they coincide (as
they usually will), then --prefix will DTRT.
Which configure script did you take this from? I see the same code in
many bits of KDE itself.
Happy hacking,
joelh
--
Joel Ray Holveck - jo...@gnu.org
atest current, it does not work for me.
By 'it', do you mean that locate does not work, that the failure test
does not work (ie, locate is fine for you), or that the workaround
does not work?
Thanks,
joelh
--
Joel Ray Holveck - jo...@gnu.org
Fourth law of programming:
Anything
wever, this app
needs to find some 3rd-party include files, so --prefix is not
appropriate.
FWIW, I've found that using /usr/local/kde instead of /usr/local has,
in my case, been most helpful. I don't advocate it for every tiny
library, but for something as large and complex as KDE, it works
ause a reconfiguration, then the attacker
generally has no different access to your network than before, and no
more means to hijack an open connection than before.
I've got some whiskey in me right now, so I may be unclear on what
you're saying. Am I missing something here?
Happy hacking,
j
anging the
timeout value on a running system wouldn't affect already opened
sockets. Even that may be changable by an external utility if I can
think of a way to handle the locking in userland.
Cheers,
joelh
--
Joel Ray Holveck - jo...@gnu.org
Fourth law of programming:
Anything that c
roblem.
joelh
--
Joel Ray Holveck - jo...@gnu.org
Fourth law of programming:
Anything that can go wrong wi
sendmail: segmentation violation - core dumped
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
that the bug doesn't affect operation.
Nobody I've talked to has ever seen a Windows 95 machine stay up for
over a week or so, let alone a month.
joelh
--
Joel Ray Holveck - jo...@gnu.org
Fourth law of programming:
Anything that can go wrong wi
sendmail: segmentation violation - co
0
I commented it out, and things work fine. Since no dumpdev was
configured yet, I don't have a dump, but can try to produce one now if
somebody would find a backtrace useful.
Happy hacking,
joelh
--
Joel Ray Holveck - jo...@gnu.org
Fourth law of programming:
Anything that
eeBSD__ >=
> 3, and it will work, but this feels a bit like a hack. I've never updated a
> port, so I can either get some instruction from someone to put in a patch,
> or let someone else do it.
I'll make the patch if a committer can get it in.
--
Joel Ray Holveck
ive me more info privately?
rms is looking at releasing a mostly bugfix Emacs, possibly tommorow,
but it may be another month (he's about to leave town). I haven't
been watching the changes; there may be some X-related fixes in there.
Cheers,
joelh
--
Joel Ray Holveck - jo...@gnu.org
Fo
issues an error or warning if
it's found?
--
Joel Ray Holveck - jo...@gnu.org
Fourth law of programming:
Anything that can go wrong wi
sendmail: segmentation violation - core dumped
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
How many times does gcc get built in a make buildworld? I had assumed
only twice, is this wrong?
Cheers,
joelh
--
Joel Ray Holveck - jo...@gnu.org
Fourth law of programming:
Anything that can go wrong wi
sendmail: segmentation violation - core dumped
To Unsubscribe: send mail to majord
> will make "what" on the kernel work again, at the expense of about 100
> duplicated
> bytes.
Check me if I'm wrong, but could we not do the same thing without the
duplication:
char sccs[] = "@(" "#)" "FreeBSD ...";
char *version = sccs +
resigned to the ranks of the NOCLEAN
masses?
Cheers,
joelh
--
Joel Ray Holveck - jo...@gnu.org
Fourth law of programming:
Anything that can go wrong wi
sendmail: segmentation violation - core dumped
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
tice
mode like this. What do you think about adding safeguards against
syslogd logging more than, say, thirty messages per hour saying why
can't log messages?
Cheers,
joelh
--
Joel Ray Holveck - jo...@gnu.org
Fourth law of programming:
Anything that can go wrong wi
sendmail: segmentat
fair bit of cleanup. I would
appreciate any comments anybody has.
-cut here-
#! /usr/bin/perl -w
# Copyright (c) 1999 Joel Ray Holveck. All rights reserved.
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the follo
p functions can have the wchan specified as a string
literal? There being no robust manner to handle calls with a computed
or dereferenced wchan, such as acquire(), I will allow for a notation
of /* WCHAN: foo */ to cause the appropriate information to be added
to the database.
Thanks,
joelh
--
J
erence wmesg strings back
to the code that sets them, a la TAGS? Would this be useful?
Thanks,
joelh
--
Joel Ray Holveck - jo...@gnu.org
Fourth law of programming:
Anything that can go wrong wi
sendmail: segmentation violation - core dumped
To Unsubscribe: send mail to majord...@freebsd
35 matches
Mail list logo
