Re: sio overflows
Georg Funk wrote: I've recompiled my Kernel, and if I connect to the internet, my console is flooded by lots of sio overflows (on sio1), and my connection is very slow. They're probably silo overflows; silo (a word which refers to a tall, cylinder-shaped building for storing grain on a farm) is one name for the input buffer of a serial I/O chip (another name is FIFO, an acronym for First In, First Out). Anyway . . . a few questions about your setup: Are you using a serial cable that is set up to use hardware (CTS/RTS) flow control? Is your modem configured to use hardware flow control? If the answer to either of these questions is no, then you aren't using hardware flow control (even if you thought you were), and you are =very= likely to lose data. Fix the cable and/or modem settings. Is your serial port (sio1) identified as a 16550A (the A suffix is very important here) when FreeBSD starts up? If not, then you're at risk of losing data at high communication rates (especially if your computer is not extremely fast). Get a new serial card with 16550A support. Are you running the X Window System (XFree86) on the same computer while you are connected to the Internet? If so, which version? Does the serial I/O problem go away if you get out of X and work directly with the plain-text console? There is a known problem with serial I/O and version 4 of XFree86 -- though this problem doesn't seem to exist with the XFree86 version (3.3.6) that is included by default in FreeBSD. If you are using XFree86-4 and aren't willing to go back to version 3.3.6, there may be a workaround for the serial I/O problem; go to http://www.FreeBSD.org/cgi/query-pr.cgi and look up PR #26261 for more details. Rich Wales [EMAIL PROTECTED] http://www.webcom.com/richw/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ipfw: several equal rules under same number bug
Andrey A. Chernov wrote: I use equal ipfw add several times from the script, but the rule number was the same all times. I expect that rule is replaced, not added with same number several times. No. There can be multiple rules with the same number. If you run multiple ipfw add commands with the same number, they are stored (and executed) in the order in which they were added. Having multiple =identical= rules with the same number doesn't make too much sense, since -- as you noticed -- the ones after the first will never match (unless the rule has a count action, in which case all of the identical rules will match). Rich Wales [EMAIL PROTECTED] http://www.webcom.com/richw/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
DON'T DO IT! (Urgent Business Proposal)
An e-mail message was sent out via "freebsd-current" over the weekend, allegedly from one Dr. Yahaya Usman, asking for assistance in handling a large sum of money. THIS IS A SCAM. PLEASE DO NOT BE TAKEN IN BY IT!!! For more info on this scam, see the following: http://home.rica.net/alphae/419coal/ Observant readers should note that, although the e-mail claims to be of a personal, individual nature, the recipient is not named (either in the "To:" line or the body of the message), and the "Received:" header lines clearly show the e-mail was sent to "freebsd-current". (Perhaps Dr. Usman's late uncle was a FreeBSD developer? :-}) Rich Wales [EMAIL PROTECTED] http://www.webcom.com/richw/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Please review: PC-Card melody beep code.
It looks like you have the "duration" and "pitch" elements reversed
in your "tone" structure.
Rich Wales [EMAIL PROTECTED] http://www.webcom.com/richw/
. . .
+struct tone {
+int duration;
+int pitch;
+};
. . .
+static struct tone success_melody_beep[] = {
+ {1200,7}, {1000,7}, { 800, 15}, {NULL, NULL}
+};
. . .
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
