I am wondering how to do network bridging on current. The description
in the handbook seems to be out of date as the sysctl IODs are no longer
in evidence. Does loading ng_bridge substitute for building the kernel
with OPTIONS BRIDGE?
Thanks,
Boyd
--
Boyd Faulkner
I am wondering how to do network bridging on current. The description
in the handbook seems to be out of date as the sysctl IODs are no longer
in evidence. Does loading ng_bridge substitute for building the kernel
with OPTIONS BRIDGE?
Excuse my ignorance (and curiousity), but wouldn't it
On Thu, Sep 28, 2000 at 12:11:54AM -0700, Peter S. Housel wrote:
I am wondering how to do network bridging on current. The description
in the handbook seems to be out of date as the sysctl IODs are no longer
in evidence. Does loading ng_bridge substitute for building the kernel
with
h,
netgraph's bridging code is more direct but it can not
do IP filtering on the packets that are en-route. This is because it
is a purely MAC-layer service.
I am not sure about Luigi's bridging code. I know the dummynet stuff
seems to connect with the ipfw code but I don't think that the
I'm presently holding at the "PRE_SMPNG" tag
(It's looking stablish now so I may move on soon)
however if Imove my (touchpad) mouse (ps2 driver) while
the audio system is active, I get a lot of these messages
pcm0: hwptr went backwards 708 - 628
pcm0: hwptr went backwards 1644 - 1428
pcm0:
With the addition of ACPI kernel thread, my system hangs in about
10 miniutes use after boot up. By disabling kernel thread, system
runs just fine.
Do you have any idea where to look at?
I'll try and see what I can do myself.
Please set debug.aml_debug and debug.acpi_debug to 1 and
In message [EMAIL PROTECTED], Munehiro Matsuda wrote:
With the addition of ACPI kernel thread, my system hangs in about
10 miniutes use after boot up. By disabling kernel thread, system
runs just fine.
Do you have any idea where to look at?
I'll try and see what I can do myself.
Alfred Perlstein [EMAIL PROTECTED] wrote:
* Tony Johnson [EMAIL PROTECTED] [000927 18:26] wrote:
OK
Well Here is the issue. If I put in the 2 boot floppies I get a page fault
12 after I press Q for "quit" on the visual kernel config. If I can save a
crash dump before any FS's are
Please set debug.aml_debug and debug.acpi_debug to 1 and
see what will happen.
It wouldn't surprise me if the system wasn't running out of kernel
memory. Right now we just keep mallocing storage to queue ACPI events
(bad idea). The entire event/Notify stuff needs to be somewhat
In the last episode (Sep 28), Julian Elischer said:
On Thu, 28 Sep 2000, Boyd R. Faulkner wrote:
On Thu, Sep 28, 2000 at 12:11:54AM -0700, Peter S. Housel wrote:
On Thu, 28 Sep 2000, Boyd R. Faulkner wrote:
I am wondering how to do network bridging on current. The
description in
On Thu, Sep 28, 2000 at 12:38:40AM -0700, Julian Elischer wrote:
I am not sure about Luigi's bridging code. I know the dummynet stuff
seems to connect with the ipfw code but I don't think that the
bridge code does... (I may be wrong) So I don't know how you plan on
filtering the bridged
On Sun, 24 Sep 2000 10:08:12 -0500,
"Jacques A. Vidrine" [EMAIL PROTECTED] said:
n changing them now. Unless objections come up, I'll commit this change
n or something similar with the next nsswitch commit.
Here is another possible trouble. While libc.so.4 with nsswitch no
longer requires
subscribe freebsd-current
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Thu, 28 Sep 2000 22:50:53 +0900, Seigo Tanimura [EMAIL PROTECTED]
said:
Here is another possible trouble. While libc.so.4 with nsswitch no
longer requires the magic '+' entry, libc.so.3 and earlier still
require '+'.
IMHO, This Is A Bug.
-GAWollman
--
Garrett A. Wollman | O Siem / We
Alas, net.link.ether.bridge(_ipfw) are no longer settable via sysctl. That is
my main problem. I cannot do what the documentation says. Unfortunately,
I cannot even test what I have until tonight as the machine for the other
side of the bridge has no video. I stole it, AGP, to replace the PCI
In the last episode (Sep 28), Garrett Wollman said:
On Thu, 28 Sep 2000 22:50:53 +0900, Seigo Tanimura
[EMAIL PROTECTED] said:
Here is another possible trouble. While libc.so.4 with nsswitch no
longer requires the magic '+' entry, libc.so.3 and earlier still
require '+'.
IMHO, This Is
On Thu, Sep 28, 2000 at 10:50:53PM +0900, Seigo Tanimura wrote:
Here is another possible trouble. While libc.so.4 with nsswitch no
longer requires the magic '+' entry, libc.so.3 and earlier still
require '+'.
If one needs to support applications using libc.so.3, then one needs
to use the
Please set debug.aml_debug and debug.acpi_debug to 1 and
see what will happen.
It wouldn't surprise me if the system wasn't running out of kernel
memory. Right now we just keep mallocing storage to queue ACPI events
(bad idea). The entire event/Notify stuff needs to be
On Thu, Sep 28, 2000 at 10:24:01AM -0500, Dan Nelson wrote:
Depends on what Seigo meant. If he meant that libc.so.4 and no
/etc/nsswitch.conf implicitly adds a "+" to the end of /etc/passwd,
that's definitely a bug.
If you don't have an /etc/nsswitch.conf, then it behaves just like
On Tue, Sep 26, 2000, Bruce Evans wrote:
Well, if you have any suggestions, I'm all for it. :-)
I don't understand the problem. You get the filesystem type name
(fstypename) from fs_vfstype in struct fstab or from f_fstypename in
struct statfs. You attempt to execute
hi, there!
On Thu, 28 Sep 2000, Dan Nelson wrote:
Here is another possible trouble. While libc.so.4 with nsswitch no
longer requires the magic '+' entry, libc.so.3 and earlier still
require '+'.
IMHO, This Is A Bug.
Depends on what Seigo meant. If he meant that libc.so.4 and
Currently kernel thread seems broken, so mallocing storage in
acpi_queue_event() never be freed. I think number of events at a
point of tme is limited and we can have static storage for the events.
The implementaion of sys/i386/apm/apm.c:apm_record_event() (it's for apmd)
would be a
On Fri, Sep 29, 2000 at 12:10:39AM +0700, Max Khon wrote:
"passwd: compat" should require '+' if I understand it correctly
You understand correctly :-) Further, this is the default when there
is no /etc/nsswitch.conf.
--
Jacques Vidrine / [EMAIL PROTECTED] / [EMAIL PROTECTED] / [EMAIL
At Thu, 28 Sep 2000 00:50:10 -0700 (PDT),
Julian Elischer [EMAIL PROTECTED] wrote:
pcm0: hwptr went backwards 708 - 628
I've seen this too on my PC running current as of Sep
20. dmesg says:
pcm0: ESS Solo-1 (unknown vendor) port
Currently kernel thread seems broken, so mallocing storage in
acpi_queue_event() never be freed. I think number of events at a
point of tme is limited and we can have static storage for the events.
The implementaion of sys/i386/apm/apm.c:apm_record_event() (it's for apmd)
would be
Howdy.
I tried booting from a pair of kern/mfsroot floppies downloaded from
current.freebsd.org, and no go. the kbd attach fails with 6. This
also happens with grabbing the most current pair of floppies from
today, as well as the beginning of Aug floppies, so this seems to be
b0rken for quite
Out of da blue Doug Barton aka ([EMAIL PROTECTED]) said:
David Siebörger wrote:
I've experienced the (apparently common) problem of switching from X
to console and back to X and getting an unresponsive mouse pointer in
X. This occurs when I use protocol "Auto", or don't specify a
On 2585 Sep 1993 [EMAIL PROTECTED] wrote:
I tried booting from a pair of kern/mfsroot floppies downloaded from
current.freebsd.org, and no go. the kbd attach fails with 6. This
What is more, now that I've had success on some other hardware, is
that what I thought was a New Feature is
Hi,
In message [EMAIL PROTECTED], Munehiro Matsuda wrote:
With the addition of ACPI kernel thread, my system hangs in about
10 miniutes use after boot up. By disabling kernel thread, system
runs just fine.
Do you have any idea where to look at?
I'll try and see what I can do
I recently cvsup'ped my source to the Current 5.0 version of FreeBSD. I
recompiled the kernel and did all of that jazz and ultimately decided I wanted
to go back to 4.1. So, I used CVSup to download the 4.1 release. I deleted
the usr/obj directory and reissued the "make buildworld" command.
Original Message
On 9/28/00, 10:53:21 PM, [EMAIL PROTECTED] wrote regarding Make
World:
I recently cvsup'ped my source to the Current 5.0 version of FreeBSD.
I
recompiled the kernel and did all of that jazz and ultimately decided
I wanted
to go back to 4.1. So, I used CVSup to
I really did not want to reply to this but since some people believe that I
am just see-ing things, then I will set this straight.
I have a dual PPro-200 systems. aha-3950u2 scsi card. Teflon cables from
scsi-cables.com. Segate cheetah 4.5gig drive that runs FreeBSD5.0-Current
since it came
On Thu, 28 Sep 2000, Julian Elischer wrote:
I would assume that code hasn;t changed, it works with ipfw, man bridge:
options BRIDGE
in the kernel config file, and is controlled by two sysctl variables:
net.link.ether.bridge
Set to 1 to enable bridging, set to 0 to
On Thu, 28 Sep 2000, Siobhan Patricia Lynch wrote:
uhoh, on a related note, I missed something, the sysctl's have been taken
out? I definitely missed something. when did this happen?
-Trish
On Thu, 28 Sep 2000, Julian Elischer wrote:
I would assume that code hasn;t changed, it works with
[Format recovered--see http://www.lemis.com/email/email-format.html]
On Thursday, 28 September 2000 at 19:54:01 -0500, Tony Johnson wrote:
On Thursday, September 28, 2000 5:33 AM, Thomas David Rivers wrote:
Alfred Perlstein [EMAIL PROTECTED] wrote:
* Tony Johnson [EMAIL PROTECTED] [000927
In the past couple of days, I've had a couple of panics out of chgsbsize:
(kgdb) bt
#0 boot (howto=260) at ../../kern/kern_shutdown.c:303
#1 0xc01cbac9 in panic (fmt=0xc0380e6f "page fault") at ../../kern/kern_shutdown.c:553
#2 0xc0316466 in trap_fatal (frame=0xc038a5c4, eva=48) at
When the kernel configuration menu comes up with the three possible
selections, pressing ctrl-alt-del ends up with this message:
panic: spin lock (null) held by 0x0 for 5 seconds
sounds like one that should be an easy fix
--
_ __ ___ ___ ___
I will not provide comments as the below messages are already too messy.
Remove my teflon cables... Hmmm... I'll try it but something tells me that
this is like trying to shoot an arbitrary star in the midnight sky. FreeBSD
doesn't like teflon or is it just my system???
The issue is this. I
In article [EMAIL PROTECTED] you wrote:
I don't think this has much to to with the current situation: based on
the evidence we have seen, it seems that Tony has tried to boot a
release snapshot of -CURRENT. It failed. Coincidentally, he has also
disabled IDE support in the belief that
On Thursday, 28 September 2000 at 21:45:13 -0500, Tony Johnson wrote:
I will not provide comments as the below messages are already too
messy.
It would be nice if you'd adhere to the conventions when you reply,
however. It's much easier to understand in chronological order. I've
now had to
On Thursday, 28 September 2000 at 22:20:52 -0400, Wesley Morgan wrote:
When the kernel configuration menu comes up with the three possible
selections, pressing ctrl-alt-del ends up with this message:
panic: spin lock (null) held by 0x0 for 5 seconds
sounds like one that should be an easy
I will not provide comments as the below messages are already too messy.
Remove my teflon cables... Hmmm... I'll try it but something tells me that
this is like trying to shoot an arbitrary star in the midnight sky. FreeBSD
doesn't like teflon or is it just my system???
I think there have
Never mind. I had not updated the boot blocks and was not running the
right kernel. That was an adventure!
Sorry for the noise and thanks.
Boyd
On Thu, Sep 28, 2000 at 09:41:15PM -0400, Siobhan Patricia Lynch wrote:
On Thu, 28 Sep 2000, Julian Elischer wrote:
I would assume that code
43 matches
Mail list logo
