If I remeber correctly, someone else reported this was caused by
phk's change staticizing something... Sorry, I do not recall this
in details, and I don't have a fresh -CURRENT.
On Tue, Dec 19, 2000 at 02:35:54PM +0700, John Indra wrote:
Dear all...
Has anyone noticed this problem? Or is it
John Indra [EMAIL PROTECTED] writes:
cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual
-fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../dev
-I../../../include
On Tue, Dec 19, 2000 at 10:16:01AM +0200, Ruslan Ermilov wrote:
If I remeber correctly, someone else reported this was caused by
phk's change staticizing something... Sorry, I do not recall this
in details, and I don't have a fresh -CURRENT.
OK then...
Any workaround or fix coming shortly to
On Tue, Dec 19, 2000 at 09:22:57AM +0100, [EMAIL PROTECTED] wrote:
Can you try the appended patch and tell us how it goes?
Yeah... finally, my world is in sync with the kernel, what a joy :)
Until know... the system is pretty stable.
Will this be committed to the tree soon?
Thank you very
Dear hackers,
Why is there the same VGA code in dev/fb/vga.c and libvgl? I think
especially of the set_palette routines.
As a more general rule, what's the philosophy for the future of
libvgl and framebuffer? Should VGL drawing routines be moved to
dev/fb/vga.c?
Also, there are some drawing
Why is there the same VGA code in dev/fb/vga.c and libvgl? I think
especially of the set_palette routines.
The framebuffer code is a newer addition. Libvgl was done quite a while
ago as more or less a proof-of-concept.
As a more general rule, what's the philosophy for the future of
libvgl
On Tue, Dec 19, 2000 at 01:32:47AM -0800, Mike Smith wrote:
Why is there the same VGA code in dev/fb/vga.c and libvgl? I think
especially of the set_palette routines.
The framebuffer code is a newer addition. Libvgl was done quite a while
ago as more or less a proof-of-concept.
As a
John Indra [EMAIL PROTECTED] writes:
Yeah... finally, my world is in sync with the kernel, what a joy :)
Until know... the system is pretty stable.
Will this be committed to the tree soon?
It has been comitted, I just wanted to test building first.
/assar
To Unsubscribe: send mail to
subscribe freebsd-current
subscribe cvs-all
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
ÓÂÀÆÀÅÌÛÅ ÄÀÌÛ È ÃÎÑÏÎÄÀ!
Ñïåøèì ïîçäðàâèòü Âàñ ñ íàñòóïàþùèì Ðîæäåñòâîì è Íîâûì 2001 ãîäîì!
Æåëàåì Âàì óäà÷è è ïðîöâåòàíèÿ, ÷òî ïðàêòè÷åñêè íåâîçìîæíî áåç íàøåãî ó÷àñòèÿ!
Ãîòîâÿñü ê íîâîìó òûñÿ÷åëåòèþ, ìû òùàòåëüíî ïðîðàáîòàëè öåíîâóþ ïîëèòèêó êîìïàíèè
è ïîäãîòîâèëè íîâîå ïðåäëîæåíèå ïî
Matthew Thyer wrote:
Michael Class wrote:
i am seeing a problem with 5.0-current (from 14.12.00) and a 3COM
3CCFE575CT Lancard (pc-cardbus) using the xl-driver.
Why behaves my FreeBSD-machines worse then the other boxes? Any Ideas?
Make sure you are running with the TCP/IP NewReno
Hi,
I think you're the main maintainer of the ACPICA codebase (and yes, I know
that parts of it is imported from Intel). Attached is a trivial patch which
makes for cleaner testing for RB_POWEROFF in acpi_shutdown_final() - I've had
various kernel/userland routines invoke reboot sequences
$B!!$O$8$a$^$7$F!"!V#J#o#u#h#o!]#Y#A!*!W$N@P@n$H?=$7$^$9!#(B
$B!!FMA3$N%a!<%k$NG[?.@?$K<:Ni$$$?$7$^$7$?!#(B
$B!!6=L#$r$*;}$A$G$J$$>l9g$O!"@?$K62$lF~$j$^$9$,:o=|$/$@$5$$!#(B
$B!!@h$K!"$3$N$h$&$J#D#M$r?4$+$iK>$^$J$$J}$K$b$*Aw$j$7$?$3$H$r?<$/$*OM$S?=$7>e$2$^$9!#(B
Hi, I want to commit pecoff module under sys/compat/.
The code is at
http://people.freebsd.org/~takawata/pecoff.tar.gz
This is kernel part of PEACE(http://chiharu.haun.org/peace/),that is
announced as NewFeature of NetBSD1.5.
Currently one more kernel module is needed to use PEACE in FreeBSD.
After my latest update, I am getting LOTS of the following in my logs:
Dec 19 12:21:04 cae88-102-101 /boot/kernel/kernel: Connection attempt to TCP ::0001:25
from ::0001:1286
Dec 19 12:24:08 cae88-102-101 /boot/kernel/kernel: Connection attempt to TCP ::0001:25
from ::0001:1299
Dec 19 12:27:13
On Tue, Dec 19, 2000 at 01:20:57PM -0500, Donald J . Maddox wrote:
After my latest update, I am getting LOTS of the following in my logs:
Dec 19 12:21:04 cae88-102-101 /boot/kernel/kernel: Connection attempt to TCP
::0001:25 from ::0001:1286
Dec 19 12:24:08 cae88-102-101
On Tue, Dec 19, 2000 at 07:33:49PM +0100, Szilveszter Adam wrote:
On Tue, Dec 19, 2000 at 01:20:57PM -0500, Donald J . Maddox wrote:
After my latest update, I am getting LOTS of the following in my logs:
Dec 19 12:21:04 cae88-102-101 /boot/kernel/kernel: Connection attempt to TCP
To answer your first question, a port need not be open in order to receive
connections. To answer your second, these appear to be IPv4 addresses
encapsulated as IPv6 addresses.
Dec 19 12:21:04 cae88-102-101 /boot/kernel/kernel: Connection attempt to TCP
::0001:25 from ::0001:1286
Dec 19
On Tue, 19 Dec 2000, Michael Class wrote:
It seems that NewReno is switched on by default in current.
Unfortunately switching off NewReno does not change the problem. In
times of very high network-traffic I am still unable to use the network.
The system does not even respond to a ping where
You're right that the answer to my question was IPV6 (I didn't have
it compiled into the previous kernel). You're wrong that a port
need not be open to receive connections. You will note in the
log excerpt below that these are connection *attempts*, not actual
connections.
On Tue, Dec 19,
Dear Friend
Help your organization raise money in a painless way
Cash rebates of up to 30% from BenefitsAll become welcome donations to your
organization when your members shop online with Lands End, Disney, Dell, Gap, Esprit
and 300 plus retailers through our web site.
Widely endorsed,
I've had a problem with -current for a couple weeks that appeared to be a
boot hang at first glace. I compiled the kernel with ddb and was able to
break into the debugger when things appeared to hang. After the kernel
starts up /sbin/init the OS will pause for a second and then begin spewing
This patch works for me on a P2B-DS, previously I had to power off by
hand.
Thanks!
Danny
On Tuesday 19 December 2000 10:36, Mitsuru IWASAKI wrote:
Hi,
I think you're the main maintainer of the ACPICA codebase (and yes, I
know that parts of it is imported from Intel). Attached is a
According to Donald J . Maddox:
open. Also, why the odd format in the addresses?
Looks like some kind of IPv6 address...
--
Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED]
FreeBSD keltia.freenix.fr 5.0-CURRENT #80: Sun Jun 4 22:44:19 CEST 2000
To Unsubscribe: send
On Tue, Dec 19, 2000 at 09:56:36PM +0100, Ollivier Robert wrote:
According to Donald J . Maddox:
open. Also, why the odd format in the addresses?
Looks like some kind of IPv6 address...
You're right. I compiled the new kernel with IPV6 enabled. I
didn't have IPV6 in my previous
Sorry to post this to -current, but (as should be obvious from
the below) it's the only way I can get Ollivier to see it :(
Why are you (or your ISP) refusing to accept mail from people
with cable modems? Enquiring minds want to know... ;-)
The original message was received at Tue, 19 Dec
On Tuesday, 19th December 2000, "Donald J . Maddox" wrote:
Why are you (or your ISP) refusing to accept mail from people
with cable modems? Enquiring minds want to know... ;-)
- Transcript of session follows -
... while talking to frmug.org.:
MAIL From:[EMAIL PROTECTED]
550 no
This is offtopic! If you need to discuss it, please take it to
-chat.
OFFTOPIC
Sorry to post this to -current, but (as should be obvious from
the below) it's the only way I can get Ollivier to see it :(
Why are you (or your ISP) refusing to accept mail from people
with cable modems?
I apologized in advance, and I do again, but I have no way of
knowing if Ollivier is subscribed to -chat. Thanks for
understanding. Further discssion has been moved to chat.
On Wed, Dec 20, 2000 at 08:19:34AM +0200, Mark Murray wrote:
This is offtopic! If you need to discuss it, please take
29 matches
Mail list logo
