Re: Patch for non-netgraph bridge code worthy of attention forpeople experimenting with bridging setups (including ng_bridge)
At 00:48 3-2-01 -0800, Julian Elischer wrote:
"Rogier R. Mulhuijzen" wrote:
I found this while experimenting with both "legacy" bridge and ng_bridge.
The bridging code doesn't check its activation everywhere so when I started
using an ng_bridge node I started getting weird errors.
Patch is rather simple, can someone submit this?
I'm a litle confused when I look at this patch.
I think this is the wrong fix.
I see that you are accounting for packets coming in on two interfaces,
but the aim of the netgraph bridging is to make it look as if the
packets are all coming in off one interface. Theoretically the
bridging code should be attached to only one 'upper' part of a driver
and all packets should arrive at higher levels, looking as if they have
all come in through that one interface. The other interfaces in the bridge
will never receive anything because their input has been diverted. To the
system it should look as if the entire bridged network is on that one
interface.
If this is not the case then we need to fix the bridging code so that
it is true, rather than clutter up higher level code trying to
account for a bug in the lower code.
I found out this bug while using ng_bridge with BRIDGE in the kernel but
turned off with the sysctl.
Like I say in the problem report, this could easily be true if you take 2
NICs and wire them both up to the same switch, each using a different IP.
(Something we do at QuakeCon for instance. We run a lot of servers per box,
so we spread them out over 3 IPs, each with it's own NIC. Worked very
well). Netgraph has nothing to do with this. I'm just warning people who
are experimenting with the netgraph bridge because they will probably still
have BRIDGE in their kernel.
Let's run through this example of 2 NICs. Let's say I have BRIDGE in the
kernel. I would not want to enable bridging in this case, because I would
get a packet storm because of the loop between the machine and the switch.
So I turn it off. But the checks for incoming interface are still switched
off in the ethernet code. Checks that ARE executed when compiling without
BRIDGE. NIC1 has 10.1.1.2 and NIC2 10.1.1.3. An ARP request is sent for
10.1.1.2, and since it's a broadcast it will arrive on both NIC1 and NIC2.
Without the checks for what interface a packet came in on, the kernel will
send 2 ARP replies, one saying 10.1.1.3 is on NIC1, the other that 10.1.1.3
is on NIC2. The last ARP reply to be sent will be used by the other
machines on the network. Now with switches, they will probably handle
broadcast packets the same way each time, so the same NIC on our machine
will always get the ARP after the other got it. So the same NIC will always
win the battle over an IP, resulting in ALL traffic for the machine, no
matter what IP it was sent to, to go over a single NIC. That's a BAD(tm) thing.
Now if you compare the code that my patch effects from before and after the
patch you will see the following changes:
original code:
blabla();
#ifndef BRIDGE
doCheck();
#endif
dumDeDum();
my code
blabla();
#ifdef BRIDGE
if (do_bridge) {/* signifies whether bridging is switched on
or off by the sysctl */
#else
{
#endif
doCheck();
}
dumDeDum();
This will make the ethernet code behave EXACTLY the same when bridging is
switched off with the sysctl and when BRIDGE is NOT compiled into the kernel.
Now, on the netgraph stuff.
So how can an incoming packet look like it is not coming from that single
interface?
1/ ifnet pointer. The function ng_ether_rcv_upper() adjust this, so that's
not the problem.
2/ rcv interface MAC address. This is stripped off before arp gets it
(also in ng_ether_rcv_upper()).
3/ the tha[] or sha[] fields may contain a MAC address for
some other interface. (depending on how the remote mechine fills out
those fields), but our outgoing packets should have the MAC address
of the interface we have selected as out main interface, independent of
which interface it actually goes out of, (unless the hardware
over-writes it). so even that should point to the single interface.
The other interfaces should (maybe) beb ifconfigged 'UP' but they should
not have IP addresses assigned tp them, as they are being slaved from
the main interface by the ng_bridging code so everything comes and
goes via that one.
so I'm slightly confused as to what problem this solves.
(I'm not saying there isn't one, just that I con't figure out what it is).
Everything should act as if there is just one interface when netgraph
bridging is turned on.
Exactly if there's just one interface when netgraph bridging is on. Why?
Why just one interface? Now that my kernel is patched to behave like BRIDGE
wasn't compiled in when I switch it off I can include the upper's of
multiple interfaces in a single netgraph bridge.
If you think about it, this should not even be a problem.
Look
Re: Patch for non-netgraph bridge code worthy of attentionforpeople experimenting with bridging setups (including ng_bridge)
ok I understand now... I thought you were saying that the netgraph code was acting differently to how I belive it should act. Nope that was the legacy bridge. Exactly if there's just one interface when netgraph bridging is on. Why? Why just one interface? Now that my kernel is patched to behave like BRIDGE wasn't compiled in when I switch it off I can include the upper's of multiple interfaces in a single netgraph bridge. sure you can. that isn't a problem. It would be a 'brouter' bridging non IP protocols and routing IP. If you think about it, this should not even be a problem. Look at this diagram http://www.bsdchicks.com/bridge-examples.gif (my apologies to everyone who can't look at graphical stuff) ok I understan.. my question is: Do you know the girl on http://www.bsdchicks.com/ and is she single? :-) Hahahaha, I don't have a clue who she is, and I'd love to know too =) It should be valid.. and I start to see your point. by adding the checks back in (or compiling without BRIDGE) you can have both interfaces Exactly What is the difference between figures 1 and 2? Except that one uses a switch, and the other uses just a FreeBSD box. yep The way packets travel is almost identical. Why wouldn't it be a valid setup? Another possibility would be to make a change to the netgraph bridge code so that it only delivers a broadcast packet to ONE local 'upper' hook. I wouldn't do that. You'd be adding behaviour that people wouldn't expect, and make it a messy unlogical thing. If people want it delivered on one upper hook, they should include just that one hook. Why make "user friendly" logic that makes it complicated and bothersome for people who want to do more than just the standard things. You say that interfaces included in the ng_bridge should not have their upper's included as well, except for one. I didn't mean that they COULDN'T but only that they didn't NEED it Eek. Misunderstood, my apologies. Right now my FreeBSD box is routing between 3 networks and sometimes even bridging between all 3 and it works perfectly. Using netgraph or the other bridging? I presume Netgraph. You are correct. Because I also have my uplink to the internet and I don't want packets "leaking" out to there. My provider might want to start wondering what all these subnets are etc. 2 of the three networks are even on the other side of tunnels built with vtun to Linux and other FreeBSD boxes. Those other networks are also linked to more. Among other things we can now play IPX games over the internet without any hassle =) But like I said, my patch has nothing to do with netgraph. When net.link.ether.bridge == 0 the kernel should behave like a kernel that doesn't have BRIDGE compiled in it. That's currently not the case and my patch fixes that. OK I will commit it. Thanks. DocWilco To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Patch for non-netgraph bridge code worthy of attention for people experimenting with bridging setups (including ng_bridge)
I found this while experimenting with both "legacy" bridge and ng_bridge. The bridging code doesn't check its activation everywhere so when I started using an ng_bridge node I started getting weird errors. Patch is rather simple, can someone submit this? DocWilco Date: Mon, 29 Jan 2001 08:20:01 -0800 (PST) To: [EMAIL PROTECTED] From: [EMAIL PROTECTED] Subject: Re: kern/24720: Bridging code does not always check activation (w/patch) Reply-To: [EMAIL PROTECTED], [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] Thank you very much for your problem report. It has the internal identification `kern/24720'. The individual assigned to look at your report is: freebsd-bugs. You can access the state of your problem report at any time via this link: http://www.freebsd.org/cgi/query-pr.cgi?pr=24720 Category: kern Responsible:freebsd-bugs Synopsis: Bridging code does not always check activation (w/patch) Arrival-Date: Mon Jan 29 08:20:01 PST 2001 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: stange console problem
If I copy GENERIC to DEBUG and recompile the kernel it will not boot properly copy the file back to GENERIC and everything seems fine? I have searched the archives and read UPDATING, but nothing jumps out at me. Does anybody have any idea where I could look next? Chad On Sun, Jan 28, 2001 at 10:16:02PM -0700, Chad David wrote: On a current from last Sunday I recompiled a new kernel with just makeoptions DEBUG=-g and options DDB added to GENERIC and when I boot I see the first few spins of the loader booting the kernel and then all video output stops. After the boot finishs I get a login prompt but no keyboard response or video after that. Have you tried removing the 'makeoptions' line and using 'config -g KERNCONF' instead? That's how I build my debug kernels, and that worked fine last time I did it (last week or so). Also, when you copy the GENERIC file to another name, do you update the ident line? This should normally not matter but you never know with debugging kernels. In both cases you would need to examine the config utility. DocWilco To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: stange console problem
None of this has any bearing on the problem, which was caused by a bug in gensetdefs.pl. Please update your source tree and rebuild your kernel. Eek. I had the gensetdefs.pl problem too, but my machine just seemed to lock. He says his machine does go on running. I have been pretty tied up lately, so maybe I read his post a bit too quickly. DocWilco To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sh can't be exec'd
For the last week, each kernel built with fresh source code cannot exec sh. I've seen a lot of emails about this, but most were about the "correct" way to rebuild a system. Is this a problem affecting only me? I haven't had any trouble. How do you rebuild your system? What is the exact error you get? And (at the risk of sounding stupid) what's the output of ls -l /bin/sh? DocWilco To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Hanging on boot (Was: Interesting man error. Current today.)
I also have a problem with my laptop that built world at the same time. Because of the above, I decided to restart it to put the kernel and programs in sync to see if that was causing the error. Murphy caught me in the act and my laptop now hangs on boot:-( I haven't tried rebooting any of the other machines, yet.) Yup same here, boot hangs. Module preloading gives garbage for module names. I was able to boot with /boot/kernel.old/kernel though... Trying to find more clues. DocWilco To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: status of bridge code
There's a Spanning Tree Protocol (STP) defined by IEEE 802.1D. I'd prefer to have that, but I don't have the 1K US$ to shell out for that. Does BSDi have IEEE subscriptions for FreeBSD developers to use? Please also consider implementing 802.1G, which is for bridging over PPP (BCP I think?). I think a lot of us remember the times when remote bridging was more common than routing ;-) I'd be happy to (I like a challenge) but I still require access to the standards for that. So my question still stands, does BSDi have IEEE subscriptions for FreeBSD developers to use, or are there any other ways for me to aquire (legally of course) the standards I need without having to shell out the 1K US$ myself. This results in the blocking of redundant ports so that loops are eliminated. See http://www.knowcisco.com/content/1578700949/pt02ch06.shtml for a good overview that's pretty in depth. Any Cisco documentation will go into depth explaining the tradeoffs in deciding the timing for the various state (STP is, in the end, a state automaton) depending on the exact topology. You should be careful when deciding defaults, and you should implement a way to adjust them. I'd probably go for the Cisco defaults. And there are lots of netgraph nodes with settings you can change. So I'd consider being able to change the values pretty much a given. =) Also, FreeBSD has support for 802.1q VLAN tagging. Having 802.1q trunks in your network means you (usually) have more than 1 instance of STP. Furthermore, this means that even if you don't care about 802.1q, you should be prepared to receive BPDU-like backets which are NOT part of the 802.1d exchange (unless my mind is playing tricks on me, that is). Of course you can choose not to handle all of this but then the implementation would be less useful in the real world. Duly noted. I recall reading that 802.1Q extends the 802.1D standardble to understand VLANs, but that most implementations still use a single STP instance. Cisco of course uses multiple instances (did I read this on a Cisco related site? n =) ). Having said that, while I am not able to help in writing code (no time to learn netgraph, sorry), I will be more than happy to test it, having a home network comprising a -current box with 4 ethernet ports and 3 or 4 differents brands / models of hubs/switches. I'll drop you a line when the time comes. DocWilco To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: status of bridge code
personally I use the netgraph bridging code and I think (though I'm biased) that you should look at using htat rather than the hardwired bridging code that it was derived from. Now that I've read up on it I can tell you you and and Archie have every right to be biased =) I've had a netgraph bridge in place for a while now and it works very well. (On 4.X-STABLE, on 5.X-CURRENT it went kablooie. See panic trace) item on my list. Being an allround good networking OS this is unacceptable IMHO. Have a look at what you can do with netgraph first. Most people don't know what it is but it allows almost arbitrarily complicated network topologies to be set up from the command line. What you might want to tell people is that it allows networking structures to be setup in a simple manner, but is so powerful it can also be used for immensely complex structures. A friend and fellow BSD user of mine's first response was "I like to keep things simple". After I rephrased into the above he was much more interested. But from my list of wishes I'd say the first 3 are gone. All that's left is spanning tree. I'm probably going to need this pretty soon, so once more I'm asking if anyone is working on it. If not I'll start on it. Also, a quick question for you netgraph guys. Why is it that ng_one2many send a packet only out of one hook? I can see use for an algorithm that sends packets from the 'one' hook to all the 'many' hooks (that are up) and keep the normal behaviour for many to one. DocWilco To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: bw limit in netgraph (Was: status of bridge code)
Since I currently have high workload, I dont have time to port it to 4.x or 5-CURRENT... Conclusion: volunteer required for this work... and I can consult him/her. Shouldn't be too hard. I'll gladly volunteer for this project. Quick question for the netgraph guru's. I haven't looked yet, but is there an explanation of the NG_ macros I see used in the netgraph nodes' code? DocWilco To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: status of bridge code
this would be a REALLY easy node to write...maybe your first? (see how 'ng_tee' works and ng_one2many, and write one that does something in between. I was thinking adding an algorithm to one2many. DocWilco To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: status of bridge code
At 09:37 25-1-01 -0800, Archie Cobbs wrote: Rogier R. Mulhuijzen writes: But from my list of wishes I'd say the first 3 are gone. All that's left is spanning tree. I'm probably going to need this pretty soon, so once more I'm asking if anyone is working on it. If not I'll start on it. Do you have references for how to do this? As I understand it, there are special Ethernet addresses that are "for bridges only -- do not forward" that are used to construct the spanning tree, etc. What is the "standard" algorithm used by bridges, etc.? There's a Spanning Tree Protocol (STP) defined by IEEE 802.1D. I'd prefer to have that, but I don't have the 1K US$ to shell out for that. Does BSDi have IEEE subscriptions for FreeBSD developers to use? Anyway, even without the IEEE standard I have been able to piece together how the protocol works. First of all bridges might have their own MACs that fall into a certain range, but STP does not depend on that. The "do not forward" is deducted from the protocol type. There is an ethernet protocol called BPDU (Bridge Protocol Data Unit) that each bridge sends and receives, but is not forwarded by any of them. These BDPUs are used to elect root bridge and determine root ports and designated ports. This results in the blocking of redundant ports so that loops are eliminated. See http://www.knowcisco.com/content/1578700949/pt02ch06.shtml for a good overview that's pretty in depth. About those blocked ports though I have a question. I've been reading ng_bridge.c and blocking a link in there (a tad more finegrained than right now) should not be a problem. But it seems to me that with the bridge.ether example there might be a problem. I'm using my own situation at home as an example to sketch this out. Please correct me if I'm wrong. 1 real NIC connected to LAN with ed0 as interface 1 tap device ran by vtun with tap0 as interface 1 tun device connected to cablemodem with tun0 as interface I have a netgraph bridge node that has ed0 and tap0 as interfaces, and ed0 as local interface (as per the example script) This means that packets from kernel to LAN go through the bridge node (thanks to the link from ed0.upper to the bridge) but packets from the kernel to the tap0 interface don't go through it (no link from tap0.upper to bridge). This means the bridge node has no idea where the MAC of the tap0 device is located (not stored in the MAC table of the bridge). So when packets directed at my tap0 interface enter the bridge (through the link from tap0.lower to the bridge) the bridge doesn't have a clue where to send it, and will thus forward to all links. Thus it will go through ed0.upper and end up in the kernel, no harm done. BUT it will also go out ed0.lower and end up in my LAN where it doesn't belong. Right now I don't mind because the traffic my cablemodem can handle is 8KB/s max. But it is not desired behaviour of a bridge. What I want to know is can I just link tap0.upper to a new bridge hook? It seems to me that is the case. If that's true the example script should be altered because right now it doesn't support more than one interface. Just say the word and I'll take care of it. =) Also, a quick question for you netgraph guys. Why is it that ng_one2many send a packet only out of one hook? I can see use for an algorithm that sends packets from the 'one' hook to all the 'many' hooks (that are up) and keep the normal behaviour for many to one. Hmm.. you could also get that affect using log2(n) ng_tee(4) nodes.. I don't see how though. Lets say I link only to left, right and left2right. Now when data enters left it will go to both right and left2right. When data enters right it goes to left. But when data enters left2right it goes to right, not left, where I want it. DocWilco To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: status of bridge code
What I want to know is can I just link tap0.upper to a new bridge hook? It
seems to me that is the case.
yes I believe so..
you can hook as many interfaces as you want to the bridge node.
(but you probably don't want to BRIDGE to your cable modem, but to ROUTE
to it )
Don't worry =)
I do want to bridge to the tunnel that goes over my cable modem though.
Make a real VPN there. (And yeah encrypted links)
I don't see how though. Lets say I link only to left, right and left2right.
Now when data enters left it will go to both right and left2right. When
data enters right it goes to left. But when data enters left2right it goes
to right, not left, where I want it.
no, data entering left2right goes to left.
(e. At least it did when I wrote it.. if not let me know )
From ng_tee(4)
Packets may also be received on right2left and left2right; if so, they
are forwarded unchanged out hooks left and right, respectively.
packets on left2right are delivered on right
And to be sure I checked ng_tee.c:
} else if (hinfo == sc-left2right) {
dup = NULL;
dest = sc-right;
}
I'll just add the algorithm to ng_tee...
DocWilco
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
status of bridge code
Is anyone working on the bridge code? I've got a couple of things I'd like to fix in it, but I wouldn't want to be doing anything someone else already did. My wishlist: 1) Better interaction with various drivers (like if_tap). For some reason I need to do a wack (undocumented) sysctl to make the bridge code refresh the iface list 2) Spontanious kablooies. After being in operation for a while it refuses to send anything through and doesn't spew any messages 3) Improve documentation. 3) iface clustering/routing 4) spanning tree implementation There's talk of a userland daemon for the last item. Is there such a thing, and if so, where. If there's no such daemon (not even halfway done), what would be the best way for a daemon like that to interact with the kernel source? A device or sysctl's? Is there any bridging part of BSDi maybe that could be merged into our networking code. Being used a lot in key networking positions FreeBSD should really have good bridging. I've heard a few people who tried it complain about the 2nd item on my list. Being an allround good networking OS this is unacceptable IMHO. DocWilco To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
panic in netgraph (caught by WITNESS) in custom UP kernel
FYI:
Full source CVSupped on the 18th or 19th
Panic came about when I did a 'ls' in ngctl(8).
Kernel config attached, gdb of core follows below:
This GDB was configured as "i386-unknown-freebsd"...
IdlePTD 5300224
initial pcb at 31c4e0
panicstr: from debugger
panic messages:
---
panic: mutex_enter: MTX_SPIN on MTX_DEF mutex netgraph node mutex @
../../netgraph/ng_base.c:2205
panic: from debugger
Uptime: 1d4h5m24s
dumping to dev ad0s2b, offset 262144
dump ata0: resetting devices .. done
128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110
109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88
87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63
62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38
37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13
12 11 10 9 8 7 6 5 4 3 2 1
---
#0 dumpsys () at ../../kern/kern_shutdown.c:477
477 if (dumping++) {
(kgdb) trace
trace command requires an argument
(kgdb) where
#0 dumpsys () at ../../kern/kern_shutdown.c:477
#1 0xc0187342 in boot (howto=260) at ../../kern/kern_shutdown.c:320
#2 0xc0187711 in panic (fmt=0xc02a1794 "from debugger")
at ../../kern/kern_shutdown.c:570
#3 0xc0142b51 in db_panic (addr=-1071151608, have_addr=0, count=-1,
modif=0xc7f70bac "") at ../../ddb/db_command.c:433
#4 0xc0142af1 in db_command (last_cmdp=0xc02e20f4, cmd_table=0xc02e1f54,
aux_cmd_tablep=0xc0305e7c) at ../../ddb/db_command.c:333
#5 0xc0142bb6 in db_command_loop () at ../../ddb/db_command.c:455
#6 0xc0144d83 in db_trap (type=3, code=0) at ../../ddb/db_trap.c:71
#7 0xc027839a in kdb_trap (type=3, code=0, regs=0xc7f70cb0)
at ../../i386/i386/db_interface.c:164
#8 0xc028376c in trap (frame={tf_fs = -1070530536, tf_es = 16,
tf_ds = -940113904, tf_edi = -1056367804, tf_esi = 256,
tf_ebp = -940110596, tf_isp = -940110628, tf_ebx = 2,
tf_edx = -1072984320, tf_ecx = 32, tf_eax = 18, tf_trapno = 3,
tf_err = 0, tf_eip = -1071151608, tf_cs = 8, tf_eflags = 70,
tf_esp = -1070788385, tf_ss = -1070936125}) at
../../i386/i386/trap.c:596
#9 0xc0278608 in Debugger (msg=0xc02acfc3 "panic") at machine/cpufunc.h:60
#10 0xc0187708 in panic (
fmt=0xc02ac060 "mutex_enter: MTX_SPIN on MTX_DEF mutex %s @ %s:%d")
at ../../kern/kern_shutdown.c:568
#11 0xc01813aa in witness_enter (m=0xc1091b48, flags=1,
file=0xc02b5c91 "../../netgraph/ng_base.c", line=2205)
---Type return to continue, or q return to quit---
at ../../kern/kern_mutex.c:842
#12 0xc01e25e6 in ng_snd_item (item=0xc132e740, queue=1)
at ../../sys/mutex.h:528
#13 0xc01e4640 in ng_generic_msg (here=0xc1091b00, item=0xc132e740,
lasthook=0x0) at ../../netgraph/ng_base.c:2855
#14 0xc01e2f14 in ng_apply_item (node=0xc1091b00, item=0xc132e740)
at ../../netgraph/ng_base.c:2386
#15 0xc01e2ab0 in ng_snd_item (item=0xc132e740, queue=0)
at ../../netgraph/ng_base.c:2249
#16 0xc139890f in ?? ()
#17 0xc01ae707 in sosend (so=0xc81e2c00, addr=0xc0f5fb30, uio=0xc7f70edc,
top=0xc0b3fa00, control=0x0, flags=0, p=0xc8d83ca0)
at ../../kern/uipc_socket.c:620
#18 0xc01b3668 in sendit (p=0xc8d83ca0, s=3, mp=0xc7f70f1c, flags=0)
at ../../kern/uipc_syscalls.c:577
#19 0xc01b371e in sendto (p=0xc8d83ca0, uap=0xc7f70f80)
at ../../kern/uipc_syscalls.c:630
#20 0xc0284551 in syscall2 (frame={tf_fs = 47, tf_es = 47, tf_ds = 47,
tf_edi = -1077967404, tf_esi = -1077967406, tf_ebp = -1077966892,
tf_isp = -940109868, tf_ebx = 671528168, tf_edx = -1077967408,
tf_ecx = -1077967408, tf_eax = 133, tf_trapno = 12, tf_err = 2,
tf_eip = 671772124, tf_cs = 31, tf_eflags = 518, tf_esp = -1077967496,
tf_ss = 47}) at ../../i386/i386/trap.c:1153
#21 0xc0278d03 in Xint0x80_syscall ()
---Type return to continue, or q return to quit---
#22 0x28069995 in ?? ()
#23 0x8049dc7 in ?? ()
#24 0x8049119 in ?? ()
#25 0x80490ca in ?? ()
#26 0x804904b in ?? ()
#27 0x8048d1f in ?? ()
#28 0x8048acd in ?? ()
(kgdb)
VENUS
Re: sysinstall move and make release on FreeBSD-stable
3) Most of what FreeBSD installs is not required for day-to-day for most users. Since many users use sysinstall to some extent as a system managing tool, sysinstall is actually quite more oftenly used than many. It's currently the best way to install packages IMHO. With the automatic dependancy resolving and downloading from FTP. The latter pkg_add offers, but it's a bother having to find the URLs. DocWilco To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sysinstall move and make release on FreeBSD-stable
What are you talking about? pkg_add -r pkgname, that's all it takes. *hides head in shame* OK so I'm a sucker for the graphical interface =) DocWilco To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Darn Soundblaster Live :(
Every time I make the thing hangs up. I never had this problem b4 and I think its has something to do with my CPU choice in my config file so here is the million dollar question. From when is your current -current install? (no pun intended) I seem to recall people not being able to build anything without hangs not too long ago. Try installing 4.2 from binary distributions over your -current, and then CVSup and build a brand spanking new -current. If I have a Celeron 400 which CPU type should I choose i586 or i686 CPU_I686 586 is Pentium, 686 is Pentium Pro, and Pentium II and up (Celeron started with having a P2 core with less cache IIRC) DocWilco
Re: number of processes forked since boot
I wish to obtain number of processes forked since boot from userland. I think dynamic sysctl is useful for dynamic context. But, here is just static and it seems there is no advantage. Isn't it? That sounds to me like a wholly dynamic thing. I mean the amount of forks since boot can rise in time right? Or am I losing my mind? =) DocWilco To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/i386/i386 trap.c
At 22:14 14-12-00 +0100, you wrote: On Thu, Dec 14, 2000 at 03:47:24PM +0100, Andrea Campi wrote: Of course I could have abandoned logo_saver, but I love the little devil ;-) Which devil? Hmmm, I've never seen any devil where BSD is involved. Lots of daemons though =) DocWilco To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: growfs(8) for FreeBSD
Stripe'd file systems (or concat ones) ... what growfs allows is someone to add an n+1 drive to their RAID/Stripe and increase the size of the file No, vinum can do this alone. But you couldn't grow the _fs_ after that, so there was no use for this vinum feature. Okay, that is what I said ... "add an n+1 drive to ... and increase the size of the file system" ... I still don't see why growfs wouldn't work on a non-vinum volume. It's just a manipulation of the FS, not of the underlying device. But let's leave this for the makers of growfs to answer shall we =) And yes I know about Vinum, and I know what it can do. =) DocWilco To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: growfs(8) for FreeBSD
Is it also capable of shrinking filesystems? I've sometimes wanted to grow my /var or / slice using space freed by shrinking /usr (on a default partitioned disk). Up to now I've solved it through symlinks, but that doesn't really deserve the beauty award. I'd imagine a lot of new users wouldn't mind being able to change partition size on a fully configured machine without having to resort to backup, reslice, restore Anyways, sounds like a very handy tool already! Just my $0,02 DocWilco At 10:34 7-12-00 -0800, you wrote: Hi, Due to vinum it is no problem to add disks and grow your volumes but up to now you couldn't easily make use of that new space for a file system, except using sequence of ufsdump/newfs/ufsrestore or something similar. Thomas ([EMAIL PROTECTED]) and me ([EMAIL PROTECTED]) have written a growfs(8) for FreeBSD. Currently we can only grow unmounted file systems (in a clean state) without any active snapshots inside. It is foreseen to enhance growfs to grow mounted file systems as well, and handle active snapshots correctly. This requires some infrastructure which is then only available in FreeBSD-5, whilst the current design runs also happily on FreeBSD-4 and FreeBSD-3 (tested) and possibly even on FreeBSD-2 (untested). To help us gathering the needed data for fixing bugs in growfs we additionally wrote ffsinfo(8), a (very) extended version of dumpfs. We've sent a couple of snapshots of our code to Kirk McKusick and to Greg Lehey. Greg also volunteered :-) for reviewing the code. We also maintain some sort of (for some contractual reasons unilaterally) contact with Don Coleman who is doing the same thing for BSD/OS. -- Ciao Christoph :-) M$: Where do you want to go today? Linux:Where do you want to go tomorrow? FreeBSD: Are you guys comming, or what? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
make release CVS?
I want to start building releases on a home box since it's not doing much else when I'm at work. But I have a rather low bandwidth, so I was wondering about the CVS checkout of /usr/src that the make release does. With my bandwidth the source may very well be out of synch with what the binaries were built with (and it takes way too long). Or am I missing something. Also is there anything against doing a 'make clean' in /usr/src (or whereever it's based) and then slurping that tree into the release tree? (in a private patch of course, not suggesting this to be put into -CURRENT itself or anything. I know it might not be the preffered way of doing a real release, but for test builds, would it be acceptable to patch the Makefile to do just that? DocWilco To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current scheduler strangeness
(Stuff about sound skippage mouse jerkiness snipped) I'm getting this too, in fact even pcmplay (about as minimalistic as you can get) skips a lot and often throws hwptr went backwards. Oh yeah, I'm using an AWE64 PnP as well. Making the sound buffer 32K instead of 4K (like a related thread on this list suggested) helped me with the sound, listening to MP3's while I work is now bearable, and I don't get the "hwptr moved backwards" crap, but the jerkiness is still there. It's been said it's caused by IRQ latency and that the SMPNG guys are working on it, so I guess it's a question of keeping current till this is solved. DocWilco To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current on ibm tp a20p?
when inserting a pccard, the card is not being recognized, pccardd tends to call it something like "Null, Null". 1) is this a CardBus card maybe? 2) What does 'pccardc dumpcis' return? DocWilco To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
NTFS patch ready to be committed
NTFS is still broken in -CURRENT I've submitted a patch to gnats (and posted about it): http://www.freebsd.org/cgi/query-pr.cgi?pr=22756 I've been running it for a while now, without problems. Can someone commit it? DocWilco To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Current has hosed the i8254 timecounter...
I'm seeing something similar with -current on this laptop here. Magically, if I jiggle the mouse whilst playing an mp3, things start to skip and the clock goes *way* off way (sometimes by a few seconds in a few seconds. :) I've had this for a few weeks now (the skipage). It has been explained as IRQ latency due to SMPNG code. Can someone make a guestimate on when this will be fixed? Also I was dd'ing the install floppies today, and when I was in X with xmms playing I got about 300-600 bytes/s transfer rate to fd0. After a reboot and being on the commandline I got 27K/s. Except when I moved my mouse, then the transfer top floppy would slow down straight away. DocWilco To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
NTFS problem solved (hopefully =) )
For everybody who was having trouble with NTFS (not being able to read any files): I have submitted a patch with send-pr: http://www.freebsd.org/cgi/query-pr.cgi?pr=22756 give it a spin, let me know if there are any problems with it. DocWilco (junior kernel hacker) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Weird errors during kernel build
At 13:37 6-11-00 -0500, drwilco wrote: Yes I do have PERL_THREADED=true. Or rather I did have it until a minute ago =) Building world kernel was succesful without PERL_THREADED. Maybe a warning should be added to /etc/make.conf? DocWilco To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: dfe-650 on -current
it is detected by the kernel and pccardd correctly as an ed0 device, ifconfig configures it correctly, but as soon as the interface is up, the kernel starts spewing ed0: device timeout... This usually means IRQ stuffups. at first i suspected cable/hardware problem, and rebooted in windows98SE to see if the problem is present there also - unfortunately, the card works like a charm under windoze, so it isn't cable/hardware problem. Reboot again, and see which IRQ the driver there uses. Then go into /etc/pccard.conf and replace the ? on the config line with that IRQ. before updating to the latest current (before it it was -current from 30 days) the card worked perfectly... i think it is some change in etc, because i've run mergemaster, but i am stupid and deleted my backup etc directory too soon;-( Ah the pain we all have to have felt once. =) DocWilco To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: NTFS driver broken
I wonder if anyone noticed, but as of today's current NTFS driver is broken. I can mount a volume, list files on it, but when I'm trying to read any file I have famous "Inappropriate ioctl...". Can someone look what is wrong with it? It's been broken for me for about a week (could have been longer). I mentioned it on this list, but wanted to wait for someone to jump up and say "Oh, it's just this this probably" before digging into it. If there's still noone like that, I guess I'll have to make my promise true and dive into the code.I'll get back on this. DocWilco To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: * watchdog timeout (Was: dc0: watchdog timeout)
At 18:24 30-10-00 +0100, you wrote: Probably not related at all, but on -current I am seeing: xe0: watchdog timeout; resetting card It happens just once, at boot time or after I insert the PC Card (Compaq whatever). After that, everything works ok. This is normal. It's bringing up the card when it's still not up. I agree this should be done earlier. I've been in that code before. I'll see if I can whip up a patch. DocWilco To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: /dev/random related mouse jerkiness is again here
At 10:07 27-10-00 -0700, you wrote: I wonder if anyone noticed that mouse jerkiness caused by entropy harvesting routine is here again (both in syscons and X11), although it was expected to be solved by kthreads, at least on my poor old P133 with PS/2 mouse. You say "here again". Was there a time that it went away with kthreads? I had mouse jerkiness at the same time as I had the sound glitches. Those were explained as a result of SMPNG IRQ latency (IIRC). Could this be the same problem? DocWilco To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
A few issues I ran into (and a quick question)
First of all (using -current of 26 October) I was not able to attach pcm to my Yamaha OPL-SAx soundcard in my Toshiba Tecra8000 when using snd_pcm.ko. Using a statically compiled driver though I had no trouble whatsoever. The module was pre-loaded at boot time. 2nd with a working pcm driver I get sound glitches with display activity under X (4.0). This was something I had before with both pcm and OSS's sounddriver so it's not really an issue with the pcm driver but with the X-server I assume. I DO have additional glitches occaisionally, that I didn't have before and they are accompanied by the following kernel message: pcm0: hwptr went backwards nnn - mmm Where nnn and mmm are numbers. nnn is not always bigger than mmm but I have not seen either value above 4096. Any pointers in what to attack in the X-server and/or pcm driver would be appreciated. My 3rd point is that I can't access any files on my NTFS partition. I have 3 partitions, one NTFS, one FAT16 and one BSD. FAT16 works fine, I can read and write to it and all, but NTFS is being a bitch. I can use 'ls' fine, no trouble there, I get all my directory listings and I can change directories etc. etc. But I can't open any files at all. Even 'cat' fails. The error I get is 'Inappropriate ioctl for device' It's been a long day so I'm not going to look into it further right now, but if no one jumps up and says "D'oh I know what that is, let me fix that..here's your patch, commit in 5 minutes" I'll go dig. In looking for heads-up posts I ran across a single cvs-all post on the 1st of Oct about ntfs.h, so I'm guessing that's where I will start. (The last time I tried to access files on my NTFS drive was with a september build of -current). That's it for now. Oh, just out of curiosity, I build both my kernel and world with -mcpu=pentiumpro and -march=pentiumpro. Would there be any reasons not to? DocWilco To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: はじめまして。
Does this look like english to anyone and is my mailer messed, or is this gobbledegook to anyone not using Outlook + japanese character set? DocWilco At 05:12 27-10-00 +0900, you wrote: $B$O$8$a$^$7$F!#(B $BFMA3$N%a!=%k!":NiCW$7$^$9!#(B $B;d$N%a!%k%\%C%/%9$K!"#1#0%v7n0LA0$+$i(B $B!V#4#0#0#01_$r?6$j9~$`$H!"+J,$N8}:B$K!"$*6b$,?6$j9~$^$l$k$h$$K$J$k!W(B $B$H$$$C$?35N,$N%M%C%H%2!%`$NM6$$$,FO$/$h$$K$J$C$FMh$^$7$?!#(B $B$3$N$h$$J%a!%k$K$O6=L#$,L5$+$C$?$N$G!"Ev=i$OL5;k$7$FB(%4%_H"9T$-$K$7$F$$$^$7$?!#(B $B$3$N5=$N$h$$J46$8$b$7$^$7$?$7!#(B $B$7$+$7!"$3$N%2!%`$,#1#0%v7n$bB3$$$F$$$k;v$K!"/$76=L#$r;}$D$h$$K$J$C$F$-$^$7$?!#(B $B!V#1#0%v7n$bB3$$$F$$$k$N$J$i0cK!@-$OL5$5$=$$@$J!A!W$d!V:#!"N.9T$C$F$$$k$N$+$J!A!)!W(B $B$J$I$H;W$$!"FO$$$?%a!%k$r!"$h!$/FI$s$G8+$k$H!"#1HVe$N?M$OH4$1$F9T$/$N$G!"(B $B3N$+$K0cK!@-$OL5$/!"LLGr$=$ W$($^$7$?!#(B $B$=$Ne!"$$^$/=PMh$F$$$k%7%9%F%`$@$H46?4$7$^$7$?!#(B $B!J%a!%k$N:G8e$NJ}$KK!E*$J;v9`$r5-:\$7$F$$$^$9!#!K(B $B$=$3$G!";d$b;22C$9$k$3$H$K7h$a!"/$7A0$+$i3hF0$7$F$$$^$9!#(B $B$9$k$H!"#1=54VDx$G$*6b$,?6$j9~$^$l$F$/$k$h$$K$J$C$?$N$G$9!#(B $B@5D!"6C$-$^$7$?!#(B $B:#$^$G!"KhG/%8%c%s%\Ju$/$8$rGc$C$F$$$F$b!":G9b$G#3#0#0#01_$7$+Ev$?$C$?;v$,L5$$$N$K!*(B $B$3$l$O!"Ju$/$8$h$j3NN)$O@dBP$K9b$$$H;W$$$^$9!#(B $B0J2$K!":#$^$GD:$$$?%a!%k$NCf$+$iJ8LL$r(B3$B$DH4?h$7$F7G:\$5$;$FD:$-$^$9!#(B $B;29M$K$J$k$H;W$$$^$9$N$G!"$h$1$l$P#1EY!"L\$rDL$7$FD:$1$l$P9,$$$G$9!#(B $B$J$*!"$3$N$h$$J%a!%k$,I,MW$GL5$+$C$?l9g$O?=$7Lu$"$j$^$;$s$G$7$?!#(B $B!y!z!y!z!y!z!y!z!y!z!y!z!y!z!y!z!y!z!y!z!y!z!y!z(B ---$B!c;22C$B@dBP3N/;qK\$GG|Bg$JMx1W;O$a$^$;$s$+!*(B $B@hF|!"25-$N$h$$J%a!%k$r$B!o#4!$#0#0#01_$NEj;q$J$i$H;W$$;n$7$K;22C$7$F$_$?$i!"#2F|L\(B $B$G:G=i$NEj;qJ,$r$9$0$K2s}$G$-$?$N$G!"$3$l$OLLGr$$$H;W$$0F(B $BFb$5$;$FD:$-$^$7$?!#(B $B!o#4!$#0#0#01_$N6b3[$J$iC/$G$b$,!XK!N'$K?($l$J$1$l$P$,!Y(B $B$H$$$46$8$N$h$$G$9!#$I$$G$9$+!)!!(B $B5.J}$bM7$S?4$G;22C$7$F$_$F$O!D!JKhF|#1#07o0Je$N?69~$"$j!K(B $BM7$S?4$r8f;}$A$NJ}$@$1!"@'Hs;22C$7$F2$5$$!#(B $B#4?M$N%j%9%H$K!o#1(B,$B#0#0#01_$E$D$rAw$k$@$1$GEj;q3[0Je$NBg6b(B $B!J!o#1#0#0K|1_0Je!K$r$B!X$=$s$J4E$$OC$,$"$k$+$$$J!Y$=$l$,:G=i$N46A[$G$7$?!#EvA3$G$7(B $B$g$!#$^$H$b$J?M4V$J$i(B...$B!#$G$b!"$h!A$/9M$($F$_$k$H!"$J$+$J$+(B $BLLGr$$%^%M!=%2!=%`$@$7!"$O$:$l$F$P$+$j$$$kJu$/$8$KHf$Y$?$i3N(B $BN($Ot#$K9b$$$+$b!"$H;W$($?$N$G;n$7$K;22C$7$F$_$k;v$K$7$^$7$?!#(B $B$7$+$7%O%^$j2a$.$F;E;v$r(B $B-$a$k$N$O$d$a$^$7$g$!JP!K!#(B $B$"$/$^$G%2!%`$H$$$463P$G#(B $B!y!z!y!z!y!z!y!z!y!z!y!z!y!z!y!z!y!z!y!z!y!z!y!z(B ---$B!c;22C$B$[$s$H$$K$*6b$,$[$7$+$C$?$i%*%9%9%a!*(B $B$\$/$NM'?M$b#3=54V$G#2#0K|1_$A$+$/2T$$$G$7$^$$$^$7$?$+$i!*!*(B 4,000$B1_$,Bg6b$K$J$C$?$h!*$3$N!V%j%T!%H!%U%)!$B$KBg%V!%`$r$*$3$7!"8=:_$O?jB`4|$KF~$C$F$$$k$HJ9$-$^$7$?!#!!(B $B%V!%`$O#2!A#3G/B3$/$H$N$3$H$G$9$,!"F|K\$Nl9g$OeN$7$F$^$@?t%v7n!#(B $B$"$H#1G/$A$g$C$H$O2T$2$k%!*(B $B!J(B12.5.26$B!!El5~!!F?L!!(B24$B:P!K(B $B!y!z!y!z!y!z!y!z!y!z!y!z!y!z!y!z!y!z!y!z!y!z!y!z(B ---$B!c;22C$B!X$=$s$J4E$$OC$,$"$k$@$m$$+!*!Y$=$l$,:G=i$N46A[$G$7$?!#(B $B$H$$$s$G$7$g$!*$G$b!"$h!$/FI$s$G$_$k$HG$B$O$:$l$F$P$+$j$$$kJu%/%8$K$/$i$Y$?$i3NN($O$O$k$+$K9b$$$+$b!)(B $B$=$ 22C$7$F$_$k$3$H$K$7$^$7$?!#(B $B$=$7$FH?.H5?$GBT$C$F$$$k$H!"MbF|$K#17o$NF~6b$,$"$j$^$7$?!#(B $B$BB3$-$^$7$?!##2=54V$r2a$.$?$3$m$K$O(B30$B7o0Je$NF~6b$,!"KhF|!"%?%P$K$J$C$F$/$k$h(B $B$$K$J$j$^$7$?!##4!A#5=54V$GF~6b$,$H$.$l$F$-$^$7$?$N$G!"(B $B$U$?$?$S%a!%k$rAw$C$F$$$k$H$3$m$G$9!#!J(B12.6.25$B!!KL3$F;!!9,;R!!(B34$B:P!K(B - $B!!"#;22CJ}K!"#(B $B$^$:!"25-(B4$B?M$N8}:B$K$*6b$r?6$j9~$s$G$/$@$5$$!#!J6d9T$N?6$j9~(B $B$_5!$G?6$j9~$_$^$9!K(B $B$B%Z!%9%H$7$F!"%j%9%H$K$"$k(B4$B$D$N8}:B$N0lHVe$N?M$r:o=|$7$^$9!#(B $B$=$7$F!"%j%9%H$N0lHV2$K$"$J$?$N8}:B$r=q$-$^$9!#(B $B$"$H$O!"(B4$B$D$N8}:B$K!"HV9f$re$+$i=g$K?6$j$J$*$7$^$9!#(B $B$=$l$r!"$G$-$k$@$1$?$/$5$s%$%s%?!%M%C%H$N7G(HD$N%"%I%l%9$KAw(B $B$C$F$/$@$5$$!#$=$$9$l$P!"$"$H$O$=$l$r$B$j$3$s$G$/$l$^$9!#(B $B:G=i$N#1=54V$G#1#07o0Je$N?69~$,L5$$l9g$O$b$$R$H$U$s$P$j$7$^(B $B$9!#(B $B0lHVe$N8}:B$r:o=|$9$k$+$i!"K!N'$K?($l$J$$$G:Q$`$N$G$9!#$=$l$@(B $B$1$O@dBP$K $B$J$*!"6d9T$K9T$/;~!"(B4$B?M$N8}:B$H8}:BHV9f$r%3%T!$7!"%o!%W%m%=(B $B%U%H$K%Z!%9%H$7$?e$G0u:~$7$F$=$N;f$r;}$C$F$$$/$H$$$A$$$A=q$-(B $BJ$1$FJXMx$G$9$h!#(B $B$?$H$($P!"%3%s%S%K$r3+6H$9$k$?$a$K$b3+6H;q6b$HN$,MW$j$^$9(B $B$M!#$9$J$o$AIJ$N$*J[Ev$rGc$C$?$j!"4L%8%e!%9$rGc$C$?$j!#$@$+(B $B$i!"$I$s$J%S%8%M%9$K$b3+6H;q6b$HN$OI,MW$J$N$G$9!#$"$J$?$,(B $B?6$j9~$`(B4$B@i1_$O!"3+6H;q6b$H$*9M$(2$5$$!#(B $B!!#D#M$NJ?6QE*@.2L$O(B0.3$B!A(B0.5$B!s0L$G$9!#!J(B1/200$B!A(B1/300$B!K(B $B!!8e$O!"8=6b!o#1!$#0#0#01_$,?69~$^$l$k$N$rBT$D$@$1!#(B $B!!#1CJL\$N@.2L!)(B $B!J!o#1!$#0#0#01_!_#1#0?M!a!o#1K|1_!)!K(B $B!!#2CJL\$N@.2L!)(B $B!J!o#1!$#0#0#01_!_#1#0?M!_#1#0?M!a!o#1#0K|1_!)!K(B $B!!#3CJL\$N@.2L!)(B $B!J!o#1!$#0#0#01_!_#1#0?M!_#1#0?M!_#1#0?M!a!o#1#0#0K|1_!)!K(B $B#4CJL\$N@.2L!)(B $B!J!o#1!$#0#0#01_!_#1#0?M!_#1#0?M!_#1#0?M!_#1#0?M!a!o#1#0#0#0K|1_!)!K(B $B"($*6b$rAw$i$J$$$G%j%9%H$K+J,$NLA0$r:\$;$k$H!"D$0$K$P$l$^$9(B
Re: ipfw question.
This makes it difficult to configure remotely without getting locked out of the system. Is there a way to cause the ipfw module to default to a different policy upon loading? I'm not sure about influencing modules with options in kernel config, I'll leave that to the pro's but you could as a workaround use: echo kldload ipfw load_ipfw.sh echo ipfw add 65000 allow all from any to any load_ipfw.sh nohup sh load_ipfw.sh I vaguely remember stuffing them both on one commandline fails because the shell dies due to the block before the ipfw command is executed. Hence the nohup. For now it appears that I am locked out, until I can access the console. That's what all the warnings about doing ipfw stuff remotely are for =) Doc "I have shot myself in the foot doing ipfw remotely too" Wilco To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree86 3.3.6_3 build dies on -current
In file included from /usr/include/sys/wait.h:93, from vgaHW.c:44: /usr/include/machine/endian.h:72: syntax error before `__uint16_swap_unit32' /usr/include/machine/endian.h:72: syntax error before `__x' snip I've not seen this reported before, nor a work around. I don't know which is "the right thing" but adding '#include sys/types.h' in front of either the '#include sys/wait.h' in vgaHW.c or in front of the '#include machine/endian.h' in /usr/include/sys/wait.h should fix your blues. I'm guessing one is the fix and the other is a workaround, but don't know which is which =) . I'm not up to speed on include rules... DocWilco To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new rc.network6 and rc.firewall6
/me hands Chris SARCASM and /SARCASM DocWilco At 13:50 24-10-2000 -0400, you wrote: The solution is very simple. Put a statically linked Perl in /sbin, and write the startup system in Perl. For user convenience, it should have a Gnome interface and a PostgreSQL backend, so we should also put X and pgsql in /sbin. -- Christopher Masto Senior Network Monkey NetMonger Communications [EMAIL PROTECTED][EMAIL PROTECTED]http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage on today's -current
We used to, but we were trying to remove `apm0' from GENERIC. I've fixed to just `apm'. Might it be a good idea to make a INSTALL kernel config and a GENERIC config? INSTALL goes on the floppies and has just enough for all the different sorts of installations. GENERIC has almost LINT proportions so newbies don't have to try and make their own kernel. DocWilco To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new rc.network6 and rc.firewall6
So, who wants to do a proof-of-concept implementation for -current which integrates with our existing rc.conf mechanism? In order to obey POLA, we should at least have the separate scripts switch off the same knobs whenever possible. It's something I'd be willing to do, I guess. I have some history with the rc.foo files. :) I'm rather new to -current, but I'd be willing to be junior hacker on this project. I'm rather fond of shell script hacking and other languages come easily to me too. DocWilco To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release breakage - dokern.sh patch 2
Believe me, if we were to put out a serious call to kill NFS from the installation boot images, you'd very quickly hear from all of those people and they would be screaming. We need to exhaust all other possibilities before we even contemplate that option. Are there maybe other large pieces which could use something like NFS_NOSERVER is to NFS? DocWilco To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
m4 not in build tools for make world
Heya, I don't know if m4 should be in the build tools that are made during make world, but it isn't. And because I had the GNU m4 installed as m4 and not gm4 the building of the boot blocks went belly up (bootblocks crashed on boot). Just my $0.02 DocWilco To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
