Re: Recent -CURRENT kernel build problem...
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 just happening to me? > On make buildkernel (with -CURRENT just cvsuped a few minutes ago) and the > generic config KERNEL; make depend; make; cycle, the kernel build failed > with this message: > > -- > > 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 -I../../contrib/dev/acpica/Subsystem/Include -D_KERNEL > -include opt_global.h -elf -mpreferred-stack-boundary=2 vers.c > linking kernel > agp_amd.o: In function `agp_amd_alloc_gatt': > agp_amd.o(.text+0x67): undefined reference to `M_AGP' > agp_amd.o(.text+0x89): undefined reference to `M_AGP' > agp_amd.o(.text+0xd5): undefined reference to `M_AGP' > agp_amd.o(.text+0x105): undefined reference to `M_AGP' > agp_amd.o(.text+0x112): undefined reference to `M_AGP' > agp_amd.o(.text+0x234): more undefined references to `M_AGP' follow > *** Error code 1 > > Stop in /usr/src/sys/compile/DANTE. > > -- > > Please help, my kernel and userland is badly not in sync ;) > Attached is my kernel config file. > > Thank you... > > Regards, > John > > ident DANTE > machine i386 > cpu I686_CPU > maxusers 256 > > options INET > options FFS > options FFS_ROOT > options SOFTUPDATES > options COMPAT_43 > options UCONSOLE > options USERCONFIG > options VISUAL_USERCONFIG > options KTRACE > options SYSVSHM > options SYSVMSG > options SYSVSEM > options SHMMAX=33554432 > options SHMALL=16384 > options P1003_1B > options _KPOSIX_PRIORITY_SCHEDULING > options KBD_INSTALL_CDEV > options ATA_STATIC_ID > options ATA_ENABLE_ATAPI_DMA > options USER_LDT > options IPFILTER > options IPFILTER_LOG > options TCP_DROP_SYNFIN > options TCP_RESTRICT_RST > options VESA > options NMBCLUSTERS=16384 > options SC_DISABLE_REBOOT > options NOBLOCKRANDOM > > deviceisa > devicepci > devicefdc > deviceata > deviceatadisk > deviceatapicd > deviceatkbdc 1 > deviceatkbd > devicepsm > devicevga > devicesplash > devicesc 1 > devicenpx > deviceapm > devicesio > deviceppc > deviceppbus > devicelpt > deviceplip > deviceppi > devicemiibus > devicexl > devicerandom > deviceloop > deviceether > devicetun > devicepty > devicemd > devicebpf > devicevn > devicesnp > devicepcm > deviceagp -- Ruslan Ermilov Oracle Developer/DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Recent -CURRENT kernel build problem...
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 -I../../contrib/dev/acpica/Subsystem/Include -D_KERNEL > -include opt_global.h -elf -mpreferred-stack-boundary=2 vers.c > linking kernel > agp_amd.o: In function `agp_amd_alloc_gatt': > agp_amd.o(.text+0x67): undefined reference to `M_AGP' > agp_amd.o(.text+0x89): undefined reference to `M_AGP' > agp_amd.o(.text+0xd5): undefined reference to `M_AGP' > agp_amd.o(.text+0x105): undefined reference to `M_AGP' > agp_amd.o(.text+0x112): undefined reference to `M_AGP' > agp_amd.o(.text+0x234): more undefined references to `M_AGP' follow > *** Error code 1 Can you try the appended patch and tell us how it goes? /assar Index: agp.c === RCS file: /home/ncvs/src/sys/pci/agp.c,v retrieving revision 1.9 diff -u -w -u -w -r1.9 agp.c --- agp.c 2000/12/12 20:24:36 1.9 +++ agp.c 2000/12/19 08:22:01 @@ -59,7 +59,7 @@ MODULE_VERSION(agp, 1); -static MALLOC_DEFINE(M_AGP, "agp", "AGP data structures"); +MALLOC_DEFINE(M_AGP, "agp", "AGP data structures"); #define CDEV_MAJOR 148 /* agp_drv.c */ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Recent -CURRENT kernel build problem...
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 overcome this guys? BTW... I am very interested to become one of you guys, the FreeBSD committers. I mean it. I am ready to devote my life to FreeBSD (if this phrase is not too much :) ). Now I am still trying to finish my Bachelor degree. In the mean time I am working as a Network Administrator for a company in Indonesia. Soon after I finish my school, I will have plenty of time to study C and maybe try to understand piece by piece FreeBSD codes, maybe not in all section, and if I am qualified enough, I'd like to contribute something to FreeBSD. What I need now is a guidance. I think I'm not a very novice programmer. For my bachelor degree, I'm trying to make a Natural Language enabled (at semantic level) search engine. Planning to use Perl to build the beast :) Where can I start to dig more information about OS, efficient programming with C, etc. to help me get what I want? Sorry, I think this is becoming out of topic, but I'm very glad to have said my wish :) Thanks a lot... Regards, John To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Recent -CURRENT kernel build problem...
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 much... Regards, John To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Various VGA, VGL, FB questions
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 routines enclosed with notyet defines. What are there state? bogus? Finally, is someone working on this part of the tree currently? Nicholas -- [EMAIL PROTECTED] Alcôve - Open Source Software Engineer - http://www.alcove.fr To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Various VGA, VGL, FB questions
> 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 and framebuffer? Should VGL drawing routines be moved to > dev/fb/vga.c? The framebuffer should grow a set of drawing primitives, yes. Exactly what these primitives is is probably open to discussion. A good idea might be to look at the GGI project, which is producing BSD-license-compatible kernel-side graphics code. > Finally, is someone working on this part of the tree currently? You would want to check with Soren and Kazu, but I have not seen any activity recently. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Various VGA, VGL, FB questions
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 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? > > The framebuffer should grow a set of drawing primitives, yes. Exactly > what these primitives is is probably open to discussion. A good idea > might be to look at the GGI project, which is producing > BSD-license-compatible kernel-side graphics code. I'm currently porting GGI ;) This is why I'm interested in kernel graphic support. I have already something done which is based on the VGL library (keyboard and display in VGA modes -- the mouse is the standard linux-mouse of GGI on top of /dev/sysmouse). It's already in the GGI library source package. I can't hide much longer that my project is to get KGI ported to FreeBSD. But that's another huge part. First, I'd like to have a clean overview of VGA/VESA/FB support in FreeBSD. I think that with some efforts in the newbus direction, I'd get rapidly this overview, isn't it? Actually I moved to GGI / FreeBSD considerations because we need, in my company, some proof of our capability to integrate low level stuff in open source kernels. The second point is that I personaly think that FreeBSD has some lacks in graphic support and that XFree is something to heavy. I'd really love... a graphic boot. Yes, I know, that's not a priority for FreeBSD headquarters :) For this I'll need graphic very early in the boot stages and I'll certainly ask you more about this soon or later. Nicholas -- [EMAIL PROTECTED] Alcôve - Open Source Software Engineer - http://www.alcove.fr To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Recent -CURRENT kernel build problem...
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 [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
(no subject)
subscribe freebsd-current subscribe cvs-all To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Globex
ÓÂÀÆÀÅÌÛÅ ÄÀÌÛ È ÃÎÑÏÎÄÀ! Ñïåøèì ïîçäðàâèòü Âàñ ñ íàñòóïàþùèì Ðîæäåñòâîì è Íîâûì 2001 ãîäîì! Æåëàåì Âàì óäà÷è è ïðîöâåòàíèÿ, ÷òî ïðàêòè÷åñêè íåâîçìîæíî áåç íàøåãî ó÷àñòèÿ! Ãîòîâÿñü ê íîâîìó òûñÿ÷åëåòèþ, ìû òùàòåëüíî ïðîðàáîòàëè öåíîâóþ ïîëèòèêó êîìïàíèè è ïîäãîòîâèëè íîâîå ïðåäëîæåíèå ïî ïåðåâîçêå íåáîëüøèõ ãðóçîâ èç Åâðîïû àâòîòðàíñïîðòîì ÷åðåç êîíñîëèäàöèþ íà ñêëàäàõ â Ãåðìàíèè è Èòàëèè. Çàíèìàÿñü îðãàíèçàöèåé è êîíòðîëåì äâèæåíèÿ ãðóçîâ èç Ãåðìàíèè è Èòàëèè, ìû äîáèëèñü ñóùåñòâåííîãî ñíèæåíèÿ òðàíñïîðòíûõ çàòðàò íàøèõ êëèåíòîâ è èìååì âîçìîæíîñòü ïðèíèìàòü ê ïåðåâîçêå ãðóçû îò 1 êîðîáêè äî åâðîôóðû. ÎÁÙÀß ÑÒÎÈÌÎÑÒÜ ÎÁÑËÓÆÈÂÀÍÈß ÃÐÓÇΠÏÎ ÃÅÐÌÀÍÈÈ (ÌÞÍÕÅÍ, ÁÅÐËÈÍ) MIN - 250$ 1 - 5 êáì - 240$/êáì 6 - 10 êáì - 230$/êáì 11 - 15 êáì - 220$/êáì 16 - 20 êáì - 210$/êáì 21 - 40 êáì - 200$/êáì 41 - 60 êáì - 195$/êáì ñâûøå 61 êáì - 185$/êáì MIN - 280$ ÏÎ ÈÒÀËÈÈ (ÏÀÄÎÂÀ, ÌÈËÀÍ, ÔÀÍÎ) 1 - 5 êáì - 270$/êáì 6 - 10 êáì - 260$/êáì 11 - 15 êáì - 250$/êáì 16 - 20 êáì - 240$/êáì 21 - 40 êáì - 230$/êáì 41 - 60 êáì - 220$/êáì ñâûøå 61 êáì - 210$/êáì Ñòðàõîâàíèå - 0.55% îò ñòîèìîñòè ãðóçà ïî ôàêòóðàì Îôîðìëåíèå êàæäîé ôàêòóðû - 40$ Äîñòàâêà â ïðåäåëàõ Åâðîïû - îò 80$ äî 600$ (â çàâèñèìîñòè îò îáúåìà ãðóçà è ðàññòîÿíèÿ îò ìåñòà ïîãðóçêè äî ñêëàäà) Äîñòàâêà ïî Ìîñêâå îò 40$ Ñðîêè äîñòàâêè "door to door" ñêëàäûâàþòñÿ èç ñëåäóþùèõ ôàêòîðîâ: Ñ ìîìåíòà ïîëó÷åíèÿ çàÿâêè äî ìîìåíòà ôàêòè÷åñêîãî çàáîðà ãðóçà - 2-4 ðàáî÷èõ äíÿ Ñðîêè äîñòàâêè ãðóçîâ â ïðåäåëàõ Åâðîïû - 2-7 ðàáî÷èõ äíåé Ñðîê õðàíåíèÿ ãðóçà íà ñêëàäå äî áëèæàéøåé ìàøèíû: ! 2-5 ðàáî÷èõ äíåé ïî Èòàëèè ! 3-7 ðàáî÷èõ äíåé ïî Ãåðìàíèè Ñðîê ïåðåâîçêè ãðóçà ïî ìàðøðóòó ñêëàä-Ìîñêâà: ! 7-9 êàëåíäàðíûõ äíåé èç Ãåðìàíèè ! 8-10 êàëåíäàðíûõ äíåé èç Èòàëèè Ìû òàêæå ïðåäëàãàåì ñëåäóþùèå óñëóãè: ! Àâèàïåðåâîçêè ãðóçîâ èç ëþáîé òî÷êè ìèðà â ëþáîé àýðîïîðò. ! Òàìîæåííîå îôîðìëåíèå ãðóçîâ â Øåðåìåòüåâî. ! Ñòðàõîâàíèå ãðóçîâ íà ëþáûõ óñëîâèÿõ. ! Îôîðìëåíèå òîâàðîñîïðîâîäèòåëüíîé äîêóìåíòàöèè ïåðåâîçèìûõ íàìè ãðóçîâ. ! Äîñòàâêà ïåðåâîçèìûõ íàìè ãðóçîâ ïî Ìîñêâå è â ðåãèîíû. ! Îðãàíèçàöèÿ äîñòàâêè ãðóçîâ ïî Ìîñêâå è â ðåãèîíû â ðåæèìå ÂÒÒ. ! Îðãàíèçàöèÿ ïåðåâîçêè ãðóçîâ âíóòðè Åâðîïû. ! Ñîäåéñòâèå â ðåøåíèè ïðîáëåìíûõ âîïðîñîâ â Øåðåìåòüåâñêîé òàìîæíå. ! Ðåãèñòðàöèÿ ïðåäïðèÿòèé â òàìîæåííûõ îðãàíàõ Øåðåìåòüåâî äëÿ âåäåíèÿ ÂÝÄ. ! Ïîìîùü â îðãàíèçàöèè ÂÝÄ. ! Ðàçðàáîòêà îïòèìàëüíûõ ñõåì äîñòàâêè Âàøèõ ãðóçîâ â çàâèñèìîñòè îò âèäà ãðóçà è ìåñòà åãî íàõîæäåíèÿ. ! Êîíñóëüòèðîâàíèå ïî ðàçëè÷íûì âîïðîñàì ÂÝÄ. Òåëåôîíû : 147-6502; 147-6403; 147-4409. Ôàêñ: 147-7016. E-MAIL: [EMAIL PROTECTED] Ñ óâàæåíèåì, Êîëëåêòèâ êîìïàíèè "Globex". To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Network performance-problem
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 optimisation turned > off. There are bugs in the TCP/IP NewReno code that result in bad > packets and hence lots of retransmission with generally reduced network > performance. 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 as all other systems I have (HPUX 10.20, 11.0 and NT4) behave as expected: slow response-times, but still working and ping-able. At home I am using this Laptop in a 100MB-Network and am able to almost saturate the link without any problems. Could it be that this is just happening for multicast-packets (that's what the high network-traffic is)? Anything else I could check? TIA Michael -- ___ Michael ClassE-Mail: [EMAIL PROTECTED] E-Business Solution Division Phone: +49 7031 14-3707 Fax:+49 7031 14-4505 ___ Hewlett-Packard GmbH, PO Box 1430, Mailstop ESD2, 71004 Boeblingen Managing Directors: Rainer Geissel (Chairman),Rainer Erlat, Heribert Schmitz, Hans-Jochen Lueckefett, Fritz Schuller Chairman of the Supervisory Board: Joerg Menno Harms Commercial register: Amtsgericht Boeblingen HRB 4081 ___ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: dev/acpica/acpi.c - minor patch for cleaner poweroff
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 where the howto had
> more bits set than RB_POWEROFF, e.g. RB_NOSYNC. With this patch, shutdown -p
> works for me :)
Thanks, this patch looks good. I'll fix this soon.
I'm sure mike will agree on it :-)
> Thanks for all the work on ACPICA :)
>
> G'luck,
> Peter
>
> PS. Please CC: me in replies as I'm not on -current.
>
> --
> If I had finished this sentence,
>
> Index: acpi.c
> ===
> RCS file: /home/ncvs/src/sys/dev/acpica/acpi.c,v
> retrieving revision 1.7
> diff -u -r1.7 acpi.c
> --- acpi.c2000/12/12 14:20:27 1.7
> +++ acpi.c2000/12/18 14:55:43
> @@ -657,7 +657,7 @@
> {
> ACPI_STATUS status;
>
> -if (howto == RB_POWEROFF) {
> +if (howto & RB_POWEROFF) {
> printf("Power system off using ACPI...\n");
> if ((status = AcpiSetSystemSleepState(ACPI_STATE_S5)) != AE_OK) {
> printf("ACPI power-off failed - %s\n", acpi_strerror(status));
>
>
> 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
$B>pJsHNGd$N$*CN$i$;$G$9(B
$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 $B!!EvJ}!"%M%C%H>e$GN">pJs$NHNGd$r9T$C$F$*$j$^$9!#(B $B!!K\>&IJ$O!"$I$l$b3NpJs$P$+$j$G$9!#6=L#$N$"$kJ}$OI,$:K~B-$7$F$$$?$@$1$k$O$:$G$9!#(B $B!!FbMF$H$7$^$7$F$O!"0J2<$N$H$*$j$G$9!#(B $B"!"!(,(,(,N">pJs(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,"!"!(B $B%A%1%C%H$NEEOCM=Ls!!N">pJs2r@b(B $B(BAAA$B5i$N%9!<%Q!<%3%T!<%V%i%s%I$N8D?M$G;EF~$l$kJ}K!(B $B7HBSEEOC>pJs!*(BDoCoMo F502i$B!!(BDoCoMo P501i$B$NN"5;(B $B56B$%V%i%s%I>&IJ$N8+J,$1J}(B $B&LH5v$N'HV9f2rFIJ}K!(B $B%9!<%Q!<$G#2#0#01_$/$i$$$GGc$($k9gK!%I%i%C%0(B $BITF0;:EP5-NA$rBgI}$K0B$/$9$kN"5;(B $BM9JX6I!&;d@_$N;d=qH"0J30$KL5NA$GM9JXJ*$rC$9N"5;(B $B3$30N99T$NGc$$J*$r%?%@$K$9$k(B $BIwB/>n$HM'C#$K$J$l!"$=$N>eKh7n$*>.;H$$$r$b$i$&J}K!(B $B;D6H$r%+%C%H$5$l$F$b5kNA$N\$7$/2r@b(B $B#3#3%I%k$G309q$N5.B2$K$J$l$kJ}K!(B $B;R6!$N=P;:HqMQ$r%?%@$K$9$kJ}K!(B $B$G%[%s%b%N$NZ$r:n@.$9$kJ}K!(B $BB>?ML>5A$G%[%s%b%N$NZ$r:n@.$9$kJ}K!(B $BL2$C$?$i5/$-$J$$!"$=$N4V$N5-21$,Ht$V%/%9%j:n@.J}K!(B $B%D!<%7%g%C%H9b3[@A5a:>5=$Nh$kJ}K!(B $BBpG[JXBe6b$,%?%@$K$J$k>e!"$*6b$^$GLc$($kJ}K!(B $B%3%s%S%K$GGc$($kJ*$@$1K\3JGzCF$r:n$kJ}K!(B $B85?ML>5A$G%5%i6b$+$i6b$re5-$N>pJs$O!"$^$@$[$s$N0lIt$G$9(B $B!!$"$H!"$*$^$1$H$7$F7]G=?M$N=;=jO?(B92$BL>!"=P?H9;JP:9CM(B130$BL>J,!"(B $B!!%a!<%k%"%I%l%9(B300$BL>J,!!?76==!65$K2CF~$7$F$$$k(B200$BL>(B $B!!$N%j%9%H$b$*IU$1$$$?$7$^$9!#(B $B!!(B $B!!9g7W(B300$BE@$H$*$^$1N">pJs$r(B3000$B1_$GHNGd$$$?$7$^$9!#$3$l$@$1$N>pJs$r$3$N2A3J$G$O!"(B $B!!$[$+$G$O$^$:pJs$H2A3J$K$O!"<+?.$r;}$C$F$$$^$9!#(B $B!!$"$H!"$3$N>pJs$rE>Gd$5$l$k$J$I$9$l$P!"%5%$%I%S%8%M%9$N$*Lr$K$bN)$D$+$H;W$$$^$9!#(B $B!!6=L#$r$b$?$l$?J}$O!"7oL>$r!V>pJs4uK>!W$H$7$F!"$*L>A0!J?69~$_?M3NG'$N$?$a$G$956L>$G$b$+$^$$$^$;$s!K(B $B!!$r=q$+$l$?%a!<%k$r(B [EMAIL PROTECTED]$B!!$K2<$5$l$P(B $B@^$jJV$7?69~$_8}:B!">\:Y$K$D$$$F=q$$$?%a!<%k$r$*Aw$j$7$^$9!#(B $B!!>pJs$NG[?.J}K!$O!"#H#T#M#L7A<0$N%U%!%$%k$r%a!<%k$KE:IU!"$b$7$/$O#U#R#L$+$i$4Mw$K$J$C$F(B $B!!D:$-$^$9!#(B $B!!(B $B!!:G8e$^$G$4Mw$K$J$C$F$$$?$@$-!"$I$&$b$"$j$,$H$&8f:B$$$^$7$?!#(B $B!!"#"""#"""#"""#"""#"""#"""#"""#""(B $B@P@n!!F)!!!J(BIshikawa$B!!(BTohru$B!K(B $B!!([EMAIL PROTECTED] $B"#"""#"""#"""#"""#"""#"""#"""#""(B To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Call for review:PECOFF(Win32 Execution format) module.
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. If there is no objection, I will commit it. Thanks. Takanori Watanabe http://www.planet.sci.kobe-u.ac.jp/~takawata/key.html"> Public Key Key fingerprint = 2C 51 E2 78 2C E1 C5 2D 0F F1 20 A3 11 3A 62 2A To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Interesting new messages in logs
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 cae88-102-101 /boot/kernel/kernel: Connection attempt to TCP ::0001:25 from ::0001:1308 Dec 19 12:39:28 cae88-102-101 /boot/kernel/kernel: Connection attempt to TCP ::0001:25 from ::0001:1336 Obviously, this machine is using log_in_vain, and it appears obvious that these are local smtp transactions. It is _not_ obvious, at least to me, why they are now being logged as if port 25 was not open. Also, why the odd format in the addresses? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Interesting new messages in logs
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 /boot/kernel/kernel: Connection attempt to TCP >::0001:25 from ::0001:1299 > Dec 19 12:27:13 cae88-102-101 /boot/kernel/kernel: Connection attempt to TCP >::0001:25 from ::0001:1308 > Dec 19 12:39:28 cae88-102-101 /boot/kernel/kernel: Connection attempt to TCP >::0001:25 from ::0001:1336 > > Obviously, this machine is using log_in_vain, and it appears obvious > that these are local smtp transactions. It is _not_ obvious, at > least to me, why they are now being logged as if port 25 was not > open. Also, why the odd format in the addresses? Key might be: IPv6.:-) (At least for the addresses.) Check your configuration if you are listening on port 25 for IPv6 or not... That's off the top of my head though so yell at me if I am talking nonsense:-) -- Regards: Szilveszter ADAM Szeged University Szeged Hungary To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Interesting new messages in logs
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 >::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 cae88-102-101 /boot/kernel/kernel: Connection attempt to TCP >::0001:25 from ::0001:1308 > > Dec 19 12:39:28 cae88-102-101 /boot/kernel/kernel: Connection attempt to TCP >::0001:25 from ::0001:1336 > > > > Obviously, this machine is using log_in_vain, and it appears obvious > > that these are local smtp transactions. It is _not_ obvious, at > > least to me, why they are now being logged as if port 25 was not > > open. Also, why the odd format in the addresses? > > Key might be: IPv6.:-) (At least for the addresses.) Check your > configuration if you are listening on port 25 for IPv6 or not... > > That's off the top of my head though so yell at me if I am talking > nonsense:-) Nope, no nonsense, you're right on the money :) In the previous kernel I didn't have IPV6 enabled, and in this one it is enabled. Thanks for helping clear this up for me :) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Interesting new messages in logs
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 12:24:08 cae88-102-101 /boot/kernel/kernel: Connection attempt to TCP > ::0001:25 from ::0001:1299 > Dec 19 12:27:13 cae88-102-101 /boot/kernel/kernel: Connection attempt to TCP > ::0001:25 from ::0001:1308 > Dec 19 12:39:28 cae88-102-101 /boot/kernel/kernel: Connection attempt to TCP > ::0001:25 from ::0001:1336 > Obviously, this machine is using log_in_vain, and it appears obvious > that these are local smtp transactions. It is _not_ obvious, at > least to me, why they are now being logged as if port 25 was not > open. Also, why the odd format in the addresses? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Network performance-problem
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 as all other systems I > have (HPUX 10.20, 11.0 and NT4) behave as expected: slow response-times, > but still working and ping-able. What is your NMBCLUSTERS set to? And in cases of "high traffic," what does `netstat -m' show for number of clusters and mbufs "in use?" How much of mb_map (%) is in use? If any of these are relatively close to exhaustion, try increasing NMBCLUSTERS in your kernel configuration and rebuilding. > At home I am using this Laptop in a 100MB-Network and am able to almost > saturate the link without any problems. Could it be that this is just > happening for multicast-packets (that's what the high network-traffic > is)? > > Anything else I could check? > > TIA > > Michael > > > -- > ___ > Michael ClassE-Mail: [EMAIL PROTECTED] > E-Business Solution Division Phone: +49 7031 14-3707 > Fax:+49 7031 14-4505 > ___ > Hewlett-Packard GmbH, PO Box 1430, Mailstop ESD2, 71004 Boeblingen > Managing Directors: Rainer Geissel (Chairman),Rainer Erlat, Heribert > Schmitz, Hans-Jochen Lueckefett, Fritz Schuller > Chairman of the Supervisory Board: Joerg Menno Harms > Commercial register: Amtsgericht Boeblingen HRB 4081 > ___ > Cheers, Bosko Milekic [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Interesting new messages in logs
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, 2000 at 01:51:04PM -0500, Hasan Azam Diwan wrote: > 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 12:24:08 cae88-102-101 /boot/kernel/kernel: Connection attempt to TCP > > ::0001:25 from ::0001:1299 > > Dec 19 12:27:13 cae88-102-101 /boot/kernel/kernel: Connection attempt to TCP > > ::0001:25 from ::0001:1308 > > Dec 19 12:39:28 cae88-102-101 /boot/kernel/kernel: Connection attempt to TCP > > ::0001:25 from ::0001:1336 > > Obviously, this machine is using log_in_vain, and it appears obvious > > that these are local smtp transactions. It is _not_ obvious, at > > least to me, why they are now being logged as if port 25 was not > > open. Also, why the odd format in the addresses? > > > 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
Donation to your organization 121900
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, socially responsible site offers no obligation, free rebate program for members. See how easy it is for your charity to earn substantial cash back for every online, shopping purchase made. To find out more information from BenefitsAll click on reply and we will contact you shortly. Please put "MORE INFO" in the subject box. If you prefer call us toll free at 866 961 2468. Ask for customer service extension 1 To remove you from this list type " REMOVE" in the subject box and click reply. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
-current "almost" hanging after boot
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 the microuptime() went backwards stuff. The kernel isn't really hanging it is just being really slow about some things. A few months ago we had a problem with the XL driver where an UNLOCK had been mistakenly coded as a LOCK. The problem feels very simlar to that. Does anyone have any hints for what to look at when I break in to the debugger? Is anyone else seeing this behavior? Later Mark Hittinger Earthlink [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: dev/acpica/acpi.c - minor patch for cleaner poweroff
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 trivial
> > patch which makes for cleaner testing for RB_POWEROFF in
> > acpi_shutdown_final() - I've had various kernel/userland routines invoke
> > reboot sequences where the howto had more bits set than RB_POWEROFF, e.g.
> > RB_NOSYNC. With this patch, shutdown -p works for me :)
>
> Thanks, this patch looks good. I'll fix this soon.
> I'm sure mike will agree on it :-)
>
> > Thanks for all the work on ACPICA :)
> >
> > G'luck,
> > Peter
> >
> > PS. Please CC: me in replies as I'm not on -current.
> >
> > --
> > If I had finished this sentence,
> >
> > Index: acpi.c
> > ===
> > RCS file: /home/ncvs/src/sys/dev/acpica/acpi.c,v
> > retrieving revision 1.7
> > diff -u -r1.7 acpi.c
> > --- acpi.c 2000/12/12 14:20:27 1.7
> > +++ acpi.c 2000/12/18 14:55:43
> > @@ -657,7 +657,7 @@
> > {
> > ACPI_STATUSstatus;
> >
> > -if (howto == RB_POWEROFF) {
> > +if (howto & RB_POWEROFF) {
> > printf("Power system off using ACPI...\n");
> > if ((status = AcpiSetSystemSleepState(ACPI_STATE_S5)) != AE_OK) {
> > printf("ACPI power-off failed - %s\n", acpi_strerror(status));
> >
> >
> > 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
--
--
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Interesting new messages in logs
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 mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Interesting new messages in logs
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 kernel... Thanks :) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No cable modems??
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 2000 18:19:21 -0500 (EST) from dmaddox@localhost - The following addresses had permanent fatal errors - [EMAIL PROTECTED] (reason: 550 no cable modems here) - Transcript of session follows - ... while talking to frmug.org.: >>> MAIL From:<[EMAIL PROTECTED]> <<< 550 no cable modems here 554 5.0.0 [EMAIL PROTECTED] Service unavailable Reporting-MTA: dns; cae88-102-101.sc.rr.com Arrival-Date: Tue, 19 Dec 2000 18:19:21 -0500 (EST) Final-Recipient: RFC822; [EMAIL PROTECTED] Action: failed Status: 5.0.0 Diagnostic-Code: SMTP; 550 no cable modems here Last-Attempt-Date: Tue, 19 Dec 2000 18:19:38 -0500 (EST) 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 kernel... Thanks :)
Re: No cable modems??
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 cable modems here >554 5.0.0 [EMAIL PROTECTED] Service unavailable It's a spam reduction move. I'm surprised hub.freebsd.org accepts your mail! You should funnel your mail through your ISP's central mail hub. Followups to -chat, I think. Stephen. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: No cable modems??
This is offtopic! If you need to discuss it, please take it to -chat. > 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 following addresses had permanent fatal errors - > [EMAIL PROTECTED] > (reason: 550 no cable modems here) Many ISP's consider cable modem pools and DSL pools as the same sort of "animal" as dialup users. Very many ISPs will refuse to receive mail from all three of those user-classes, because of the "direct-to-MX" spam issue. The solution is to use your ISP's SMTP "smarthost" for your mail. See http://mail-abuse.org/dul/ M -- Mark Murray Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: No 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 it to > -chat. > > > > 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 following addresses had permanent fatal errors - > > [EMAIL PROTECTED] > > (reason: 550 no cable modems here) > > Many ISP's consider cable modem pools and DSL pools as the same sort > of "animal" as dialup users. > > Very many ISPs will refuse to receive mail from all three of those > user-classes, because of the "direct-to-MX" spam issue. The solution > is to use your ISP's SMTP "smarthost" for your mail. > > See http://mail-abuse.org/dul/ > > > M > -- > Mark Murray > Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
