On Thu, Jul 04, 2002 at 09:20:38AM -0500, Richard Seaman, Jr. wrote:
On Tue, Jul 02, 2002 at 06:04:36PM -0700, Joel M. Baldwin wrote:
Something has messed up natd. If I don't have the
punch_fw option in the /etc/natd.conf file it eventuially
core dumps with a bus error. I think
net.inet.ip.forwarding: 1
net.inet.ip.fastforwarding: 0
net.inet6.ip6.forwarding: 0
Everything works fine with pre new-ipfw, and has for years. Same
rules, same configuration, and with new ipfw, core dump.
--
Richard Seaman, Jr.email:[EMAIL PROTECTED]
5182 N. Maple Lane phone
. The problem
still exits. It isn't an instant dump, it runs for a while.
Right. Typically 30secs - 5 mins before it dumped. And when I ran
natd in verbose mode, it showed quite a few packets in and out before
it dumped.
--
Richard Seaman, Jr.email:[EMAIL PROTECTED]
5182 N. Maple Lane
from any to any
Yes, I saw this. However, 'ipfw l' doesn't include a 0 rule, and
the rule list appears correct.
--
Richard Seaman, Jr.email:[EMAIL PROTECTED]
5182 N. Maple Lane phone:262-367-5450
Nashotah WI 53058fax:262-367-5852
To Unsubscribe: send
On Sun, Jul 07, 2002 at 04:45:52PM -0500, Richard Seaman, Jr. wrote:
On Sun, Jul 07, 2002 at 11:35:46PM +0200, Szilveszter Adam wrote:
Hello everybody,
I upgraded to yesterday's -CURRENT and have made a few observations:
2) and much more alarmingly: Although the new ipfw really seems
ip_dummynet.c ip_fw.h
sys/conf files
lib/libalias alias_db.c
Added files:
sbin/ipfwipfw2.c
sys/netinet ip_fw2.c
Log:
The new ipfw code.
--
Richard Seaman, Jr.email:[EMAIL PROTECTED]
5182 N. Maple Lane phone:262-367
- Jordan
On Fri, Jun 09, 2000 at 02:11:29PM -0500, Richard Seaman, Jr. wrote:
If I just cat a .au file into /dev/audio, I get about 1/4 of a second
of plan and then silence, with without the patch.
Your symptoms are different then. Don't know if the cause is the
same.
Thin
please try this patches and try to ping6 to my host's 6to4
address?
The procedure is,
For the benefit of the lists, and confirming private mail I sent,
ping6 works using the second of the patches sent (I didn't try the
first).
--
Richard Seaman, Jr. email: [EMAIL PROTECTED]
5182 N
On Fri, Mar 10, 2000 at 07:35:08AM -0600, Richard Seaman, Jr. wrote:
On Fri, Mar 10, 2000 at 08:09:04PM +0900, Yoshinobu Inoue wrote:
6to4 support seems to be very important for initial IPv6
deployment on FreeBSD4.0, so I tried small additinal patches
to make it available. And It seems
the non 6to4
address as the source?
I can ping6 your non 6to4 address from my 6to4 address, see
attached.
--
Richard Seaman, Jr. email: [EMAIL PROTECTED]
5182 N. Maple Lanephone: 262-367-5450
Chenequa WI 53058 fax: 262-367-5852
PING6(56=40+8+8 bytes) 2002:cc5f:bb02
:5aff:fe86:b65a ping6 statistics ---
7 packets transmitted, 5 packets received, 28% packet loss
round-trip min/avg/max = 341.997/432.005/582.145 ms
--
Richard Seaman, Jr. email: [EMAIL PROTECTED]
5182 N. Maple Lanephone: 262-367-5450
Chenequa WI 53058 fax: 262-367
that freenet6 was OK.
Just to clarify, I had to configure a hole in ipfw for freenet6.net
too. I had just forgotten about it. :)
--
Richard Seaman, Jr. email: [EMAIL PROTECTED]
5182 N. Maple Lanephone: 262-367-5450
Chenequa WI 53058 fax: 262-367-5852
n't really need 6to4 "relay" routers? This is
only for reaching native IPv6 sites without 6to4 addresses?
Thanks.
--
Richard Seaman, Jr. email: [EMAIL PROTECTED]
5182 N. Maple Lanephone: 262-367-5450
Chenequa WI 53058 fax: 262-367-5852
To Unsubscribe:
with bde about them. This was
about 1-2 months ago.
--
Richard Seaman, Jr. email: [EMAIL PROTECTED]
5182 N. Maple Lanephone: 262-367-5450
Chenequa WI 53058 fax: 262-367-5852
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-cu
gs.
As I said, this is purely a wild guess from someone who
understands all this poorly.
--
Richard Seaman, Jr. email: [EMAIL PROTECTED]
5182 N. Maple Lanephone: 262-367-5450
Chenequa WI 53058 fax: 262-367-5852
To Unsubscribe: send mail to [EMAIL PROTEC
secs max for this drive. I'm assuming
that what we're seeing is that the ata driver "lost contact"
because the timeout is less that the time it takes to spinup
from standby to idle (or to spinup from an interrupted switch
from idle to standby)?
--
Richard Seaman, Jr. ema
pinning up. If so, for
just this case, perhaps you can adjust the timeout to a greater
value before retrying the command? Also, perhaps you want to
skip printing the diagnostic if the timeout was due to
standby/spinup, unless it also fails on retry?
--
Richard Seaman, Jr. ema
ecs/int, 1 depth queue, DMA
Dec 11 11:31:02 test /kernel: ad2: Maxtor 91152D8/WAS82739 ATA-4 disk at ata1 as
master
Dec 11 11:31:02 test /kernel: ad2: 10991MB (22510656 sectors), 22332 cyls, 16 heads,
63 S/T, 512 B/S
Dec 11 11:31:02 test /kernel: ad2: 16 secs/int, 1 depth queue, UDMA33
--
Richard
sturbed by a command, it is retried 12 hours
later. For timeout concern, refer to 13.0, "Timeout Values" on page 185.
--
Richard Seaman, Jr. email: [EMAIL PROTECTED]
5182 N. Maple Lanephone: 262-367-5450
Chenequa WI 53058 fax: 262-367-5852
To Unsubscribe:
On Thu, Dec 09, 1999 at 11:28:20AM +0100, Soren Schmidt wrote:
It seems Soren Schmidt wrote:
It seems Richard Seaman, Jr. wrote:
On Wed, Dec 08, 1999 at 03:02:37PM +0100, Soren Schmidt wrote:
OK, you asked for it, following is a patch to support the
sis 5591 chipset. Remember
gone, I would still vote to retain it for some intermediate
period. You can put my vote in the appropriate column of your
tally.
--
Richard Seaman, Jr. email: [EMAIL PROTECTED]
5182 N. Maple Lanephone: 262-367-5450
Chenequa WI 53058 fax: 262-367-5852
was changed from the original submission, when it was committed.
See the attached message:
From [EMAIL PROTECTED] Thu May 6 15:14:56 1999
Date: Thu, 6 May 1999 15:14:56 -0500
From: "Richard Seaman, Jr." [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Buglet in SiS support in ide_pci.c
in the tree for a while, even if its
not the default. Possibly there are others in the same boat?
--
Richard Seaman, Jr. email: [EMAIL PROTECTED]
5182 N. Maple Lanephone: 262-367-5450
Chenequa WI 53058 fax: 262-367-5852
To Unsubscribe: send mail to [EMAIL
heads,
63 S/T, 512 B/S
Dec 8 17:25:02 test /kernel: ad2: 16 secs/int, 1 depth queue, UDMA33
Dec 8 17:25:02 test /kernel: Mounting root from ufs:/dev/ad0s1a
--
Richard Seaman, Jr. email: [EMAIL PROTECTED]
5182 N. Maple Lanephone: 262-367-5450
Chenequa WI 53058
. With wd I get UDMA. This was about 2-3 weeks ago.
--
Richard Seaman, Jr. email: [EMAIL PROTECTED]
5182 N. Maple Lanephone: 262-367-5450
Chenequa WI 53058 fax: 262-367-5852
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-cu
in the
patchkit days, or very early FreeBSD 1.x.
Unless I'm mistaken, the FreeBSD Tutorial "Upgrading FreeBSD from source"
tells you to "make world" before you make and install the kernel. I take
it the tutorial is wrong? :)
--
Richard Seaman, Jr. email: [EMAIL PROTECTED
)
thoughts on what FreeBSD thread related syscalls might be helpful.
--
Richard Seaman, Jr. email: d...@tar.com
5182 N. Maple Lanephone: 414-367-5450
Chenequa WI 53058 fax: 414-367-5852
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd
to
their compile options. (This works now too).
--
Richard Seaman, Jr. email: d...@tar.com
5182 N. Maple Lanephone: 414-367-5450
Chenequa WI 53058 fax: 414-367-5852
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body
worth doing, but not a top priority. The main issue
is to decide what interface would be most convenient. Its not a
top priority since the code already exists for those (rare) cases
where someone really needs it. And, lets not call it clone.
--
Richard Seaman, Jr. email: d...@tar.com
, which includes an example using thr_fork.
No reason I can see that thr_fork and/or clone couldn't be added to
libc.
--
Richard Seaman, Jr. email: d...@tar.com
5182 N. Maple Lanephone: 414-367-5450
Chenequa WI 53058 fax: 414-367-5852
.file rf.S
#include
, thread_self can examine its stack, and derive the address
of the TLS efficiently.
Now, it would be very nice to find a better way to do the thread_self
stuff.
--
Richard Seaman, Jr. email: d...@tar.com
5182 N. Maple Lanephone: 414-367-5450
Chenequa WI 53058 fax: 414
problem is, whether it is a bad
signal handler, or more likely, the real problem is whatever
generated the signal within malloc/free, and the bad signal
handler is a misdirect.
--
Richard Seaman, Jr. email: d...@tar.com
5182 N. Maple Lanephone: 414-367-5450
Chenequa WI 53058
in emulation mode you don't have to worry about this.
--
Richard Seaman, Jr. email: d...@tar.com
5182 N. Maple Lanephone: 414-367-5450
Chenequa WI 53058 fax: 414-367-5852
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body
as the old code, but via a different path. Case d)
will now continue executing in a manner equivalent to the new case c).
The question is whether there is a way to do the autogrow function if
the map lock is already held.
--
Richard Seaman, Jr. email: d...@tar.com
5182 N. Maple Lane
in /etc/rc.conf ? It appears to here.
--
Richard Seaman, Jr. email: d...@tar.com
5182 N. Maple Lanephone: 414-367-5450
Chenequa WI 53058 fax: 414-367-5852
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body
. its a kernel thread of the same process) and if
so, raise the priority of pid to that of the calling process for one
time slice so pid has a chance to execute and free the lock.
--
Richard Seaman, Jr. email: d...@tar.com
5182 N. Maple Lanephone: 414-367-5450
Chenequa WI
-DCOMPAT_LINUX_THREADS to
CFLAGS and COPTFLAGS in /etc/make.conf and make world and
remake and install your kernel.
Also, you need to add the posix priority extensions to your
kernel (see LINT).
Or, there is also more information at http://lt.tar.com
--
Richard Seaman, Jr. email: d
implementation. It
wouldn't be all that much more work than getting the user thread
code in first rate shape. But, either way I think its a fairly
big project.
--
Richard Seaman, Jr. email: d...@tar.com
5182 N. Maple Lanephone: 414-367-5450
Chenequa WI 53058 fax
On Wed, Jan 27, 1999 at 10:20:14AM -0500, Brian Feldman wrote:
On Wed, 27 Jan 1999, Sheldon Hearn wrote:
I still don't think we're getting any closer to the question Why is
Netscape unstable on CURRENT when it worked fine for me on STABLE? The
problem seems to be that those who know
On Wed, Jan 27, 1999 at 10:02:31AM -0600, Richard Seaman, Jr. wrote:
If you have Netscape problems, it would be worthwhile to try removing
-DVM_STACK from src/sys/compile/BLAH/Makefile and doing a make clean all
install. I am pretty certain this is the cause of Netscape crashing, at
least
On Wed, Jan 27, 1999 at 11:04:22AM -0800, Parag Patel wrote:
Just another data point. I just updated my 2xPII/300 system to
4.0-CURRENT last night (Tues Jan 26), and I'm running Netscape 4.5 just
fine - no crashes od any odd behavior at all. VM_STACK is defined, I
have 256Mb RAM, and
On Wed, Jan 27, 1999 at 02:20:32PM -0500, Luke wrote:
I tried that one but it wants linux_lib installed on /compat and
theres
no room. Do you know if its ok to make /compat a link to somewhere else for
the
linux_lib port. [why does it install into / anyways]
I have /compat
On Wed, Jan 27, 1999 at 12:35:09PM -0500, Luke wrote:
what is this VM_STACK option?
Its some new code to manage autogrow stacks. The existing (old) code
made a process stack autogrow. But, its useful to be able to create
additional autogrow memory regions to use as thread stacks in
On Mon, Jan 25, 1999 at 07:09:37PM -0800, Manfred Antar wrote:
At 06:41 PM 1/25/99 -0800, Julian Elischer wrote:
The Linuxthreads changes in the system that have been optioned out for a
while have been enabled after testing by many people.
this will require a recompile of at least PS and
On Tue, Jan 26, 1999 at 02:38:12PM -0500, Kenneth Wayne Culver wrote:
when my computer starts up (just finished make world 5 minutes ago) I get
the following error:
link_elf: symbol grow undefined.
does this mean that the linux emu is broken right now?
I think it means there is a goof in
On Mon, Jan 25, 1999 at 05:08:19PM +1100, Bruce Evans wrote:
Can you find out what chipset is in this guy? There's support for anything
Intel or VIA, Promise UDMA cards, Cyrix MediaGX, and Acer Aladdin IV/V
right
now.
See kern/9550. The driver *used* to support my SiS chipset, but it
On Thu, Jan 21, 1999 at 07:39:28PM -0700, Russell L. Carter wrote:
d...@tar.com said:
%libc_r could be modified so that is doesn't replace libc, but rather
%is an addon, comparable to the kernel threaded libc case. But, it
%would involve a bit of work.
I thought so at first, but then I
On Thu, Jan 21, 1999 at 12:38:14PM -0600, Richard Seaman, Jr. wrote:
On Thu, Jan 21, 1999 at 06:12:29PM +0200, Jeremy Lea wrote:
On Tue, Jan 19, 1999 at 09:11:51AM -0600, Richard Seaman, Jr. wrote:
Actually, the new version, in FreeBSD ports form, doesn't require
-DLINUXTHREADS anymore
On Thu, Jan 21, 1999 at 02:00:53PM -0800, Kurt D. Zeilenga wrote:
For kernel threading you just use libc. Whether or not libc generates
thread safe (re-entrant) calls depends on whether its also linked with
a library that 1) sets __isthreaded to a non-zero value, 2) has a
_spinlock()
On Fri, Jan 22, 1999 at 09:49:23AM -0800, Kurt D. Zeilenga wrote:
Richard Seaman, Jr. wrote:
_THREAD_SAFE is only used in stdio.h. Looking at what's there, it could
be rewritten to eliminate _THREAD_SAFE entirely, at a (very slight)
performance penalty. You'd have to check __isthreaded
On Fri, Jan 22, 1999 at 02:47:53PM -0500, Alfred Perlstein wrote:
*confused look*
somehow even though i've been trying to follow this thread i got lost.
questions:
1) are 'linuxthreads' enabled by defualt now?
The terminology is a little confusing. There's linuxthreads for those
running
On Thu, Jan 21, 1999 at 06:12:29PM +0200, Jeremy Lea wrote:
On Tue, Jan 19, 1999 at 09:11:51AM -0600, Richard Seaman, Jr. wrote:
Actually, the new version, in FreeBSD ports form, doesn't require
-DLINUXTHREADS anymore, but it does require -I/usr/local/include to
pick up the right header
On Thu, Jan 21, 1999 at 11:04:38AM -0800, Julian Elischer wrote:
On Thu, 21 Jan 1999, Richard Seaman, Jr. wrote:
And when are COMPAT_LINUX_THREADS and VM_STACK going away?
I have no idea. I was hoping that at least COMPAT_LINUX_THREADS
would go away before the branch. I don't
On Thu, Jan 21, 1999 at 11:42:14AM -0800, Kurt D. Zeilenga wrote:
This is nagging at me. Having two headers of the same name, but importantly
different content is asking for touble. There needs to be a way to ensure
that only one or the other is picked up. The best way I can think of is to
On Mon, Jan 18, 1999 at 06:27:18PM -0800, br...@worldcontrol.com wrote:
I running gimp -unstable (CVS 1/17/1998) and FreeBSD -current
(1/17/1998) with
CFLAGS= -O2 -m486 -pipe -DCOMPAT_LINUX_THREADS -DVM_STACK
COPTFLAGS= -O -pipe -DCOMPAT_LINUX_THREADS -DVM_STACK
and linuxthreads port
On Tue, Jan 19, 1999 at 02:06:13PM +0200, Jeremy Lea wrote:
On Tue, Jan 19, 1999 at 02:45:39AM -0800, br...@worldcontrol.com wrote:
Gimp (CVS) compiled with
CFLAGS=-g -D_THREAD_SAFE -I/usr/local/include -L/usr/local/lib -O2 -m486
-pipe -lpthread
Hmm, if you're using the libpthread from
56 matches
Mail list logo
