Re: Loosing spam fight
On Thursday 25 January 2007 04:08, Peter N. M. Hansteen wrote: > For purposes of making the subject less true, setting up greylisting > with an optional tarpit for known baddies can be very effective. See > Dan Langille's recent Onlamp article[1] or for that matter my tutorial[2] > for how this is done using PF and spamd - this way it doesn't matter much > which MTA(s) you use. > > [1] http://www.onlamp.com/pub/a/bsd/2007/01/18/greylisting-with-pf.html > [2] http://home.nuug.no/~peter/pf/en/, with the specifics of spamd and > greylisting starting at http://home.nuug.no/~peter/pf/en/spamd.html all this methods are certainly useless, stay calm ok the only way to block spam really is blocking any incoming tcp:25 ... any firewall based method you may use do block innocents as well, ike some do they block entire IP ranges from countries because most spam comes from them, that is stupid, more brainless since the spam mostly is not generated by any of this servers, it only goes through it, this method might cause *you* not getting this spam but does not stop spam at all ... probably better, if you like firewall blocks, cutting the complete US IP address space from sending to any tcp:25 to stop spam definitly, because I never heard of chinese or african viagra hahahaha spam block list abviously are very usefull so long as they are maintained IMO a good way and probably the best way is to do some inicial checks like connection rate and limit them, then a spam checker like spamassassin for regex and header checks still you get SPAM and you never can block spam 100%, spammers change servers, IPs, patterns faster then we can react, but we all know this right? and even then if you get it all into your box you still get spam by whom sends it out without caring of identity or hiding it, a correct email msg but spam where spam needs to be catched is at the origin, ISPs should take care of this problem by not permitting access to outside servers but only passing through their smtp gateways, an outgoing spam check is what needs to be done but here nobody cares ... -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bge Ierr rate increase from 5.3R -> 6.1R
Quoting Jeremy Chadwick <[EMAIL PROTECTED]>: [...] Set your Cisco configuration to use 100/full, and edit the ifconfig_bge0 line in rc.conf on your FreeBSD box to have "media 100baseTX mediaopt full-duplex", then reboot the FreeBSD box. If the problem continues, there may be faulty cabling, but usually errors on one direction are a sign of duplex mismatch. If after replacing the cabling the issue continues, then there's a chance the bge(4) driver may be obtaining statistics wrong for the particular chip revision being used (this is hearsay on my part; I'm just guessing...) Ok, I have set the Cisco port to 100/full-duplex and update the bge* interfaces on the development server, but the problem still exists. I have also updated the other server, which is connected to another Cisco switch, but the same results. Regards, Robin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Loosing spam fight
Woah you just made my day Saying dspam or greylisting is useless ;) I hope you mean that by ironic - no you cannot block 100% spam but 99.99% effectivly which I already do even productive. But not with sendmail (who is using sendmail these days?) cheers JoaoBR wrote: > On Thursday 25 January 2007 04:08, Peter N. M. Hansteen wrote: >> For purposes of making the subject less true, setting up greylisting >> with an optional tarpit for known baddies can be very effective. See >> Dan Langille's recent Onlamp article[1] or for that matter my tutorial[2] >> for how this is done using PF and spamd - this way it doesn't matter much >> which MTA(s) you use. >> >> [1] http://www.onlamp.com/pub/a/bsd/2007/01/18/greylisting-with-pf.html >> [2] http://home.nuug.no/~peter/pf/en/, with the specifics of spamd and >> greylisting starting at http://home.nuug.no/~peter/pf/en/spamd.html > > > all this methods are certainly useless, stay calm ok > > the only way to block spam really is blocking any incoming tcp:25 ... > > any firewall based method you may use do block innocents as well, ike some do > they block entire IP ranges from countries because most spam comes from them, > that is stupid, more brainless since the spam mostly is not generated by any > of this servers, it only goes through it, this method might cause *you* not > getting this spam but does not stop spam at all ... > > probably better, if you like firewall blocks, cutting the complete US IP > address space from sending to any tcp:25 to stop spam definitly, because I > never heard of chinese or african viagra hahahaha > > spam block list abviously are very usefull so long as they are maintained > > IMO a good way and probably the best way is to do some inicial checks like > connection rate and limit them, then a spam checker like spamassassin for > regex and header checks > > still you get SPAM and you never can block spam 100%, spammers change servers, > IPs, patterns faster then we can react, but we all know this right? > > and even then if you get it all into your box you still get spam by whom sends > it out without caring of identity or hiding it, a correct email msg but spam > > where spam needs to be catched is at the origin, ISPs should take care of this > problem by not permitting access to outside servers but only passing through > their smtp gateways, an outgoing spam check is what needs to be done but > here nobody cares ... > -- Georg 'Therion' Bege http://coruscant.info http://www.ninth-art.de [EMAIL PROTECTED] GnuPG-Key-ID: 0x5717E214 FingerPrint: A8EC B4B2 C9A9 483B CC87 56EE 07A1 C78E 5717 E214 !DSPAM:45b890c4896261974110222! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Loosing spam fight
On Thu, Jan 25, 2007 at 12:11:43PM +0100, Georg Bege wrote: > Woah you just made my day > > Saying dspam or greylisting is useless ;) > I hope you mean that by ironic - > no you cannot block 100% spam but 99.99% effectivly which I already do > even productive. > But not with sendmail (who is using sendmail these days?) I do, and I have a hitquote arounf 99% as well. I'm using spamassassin and greylisting. Works pretty good. Filter/Tagging spam isn't a MTA problem, it's a configuration problem. You can do anything on any MTA. bye Estartu -- Gerhard Schmidt| Nick : estartu IRC : Estartu | Fischbachweg 3 || PGP Public Key 86856 Hiltenfingen | EMail: [EMAIL PROTECTED] | on request Germany|| pgpZRfkvRxtzj.pgp Description: PGP signature
RE: FreeBSD 6.2-STABLE and Flash 7 patch
Torfinn Ingolfsen <> wrote on Wednesday, January 24, 2007 10:51 PM: > On Wed, 24 Jan 2007 13:11:16 -0600 > ejc <[EMAIL PROTECTED]> wrote: > >> rtld.c has changed a bit over time so here's a patch against the new >> file. > > BTW, what is the reason this "hack" isn't included in the base kernel > / code? Because it is probably unnecessary? I run a recent 6-STABLE and use the flash7 plugin *without* this patch. I am using Opera, though, not Firefox... Helge ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Loosing spam fight
JoaoBR <[EMAIL PROTECTED]> writes: > all this methods are certainly useless, stay calm ok I fully sympathize with your need to rant, but in this context most of what you say is really quite beside the point. Please read what the material at the links provided actually says. > any firewall based method you may use do block innocents as well, ike some do > they block entire IP ranges from countries because most spam comes from them, Blocking entire subnets is generally not useful, and unmaintained blacklists are worse than useless. Which exactly is why I advocate using spamd in pure greylisting mode, possibly supplemented with aggressively maintained blacklists such as Bob Beck's traplist and potentially with local greytrapping. -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/ "First, we kill all the spammers" The Usenet Bard, "Twice-forwarded tales" delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bge Ierr rate increase from 5.3R -> 6.1R
On Thu, Jan 25, 2007 at 12:07:22PM +0100, Robin Gruyters wrote: > Quoting Jeremy Chadwick <[EMAIL PROTECTED]>: > [...] > > > >Set your Cisco configuration to use 100/full, and edit the > >ifconfig_bge0 line in rc.conf on your FreeBSD box to have "media > >100baseTX mediaopt full-duplex", then reboot the FreeBSD box. > >If the problem continues, there may be faulty cabling, but > >usually errors on one direction are a sign of duplex mismatch. > >If after replacing the cabling the issue continues, then there's > >a chance the bge(4) driver may be obtaining statistics wrong for > >the particular chip revision being used (this is hearsay on my > >part; I'm just guessing...) > > > Ok, I have set the Cisco port to 100/full-duplex and update the bge* > interfaces on the development server, but the problem still exists. > > I have also updated the other server, which is connected to another > Cisco switch, but the same results. Okay so at least we know it's not specific to your switch, or to auto-neg nor the cabling (two different switches + boxes with the same problem probably isn't your fault. :) ). That's definitely evidence that it's a driver problem, probably specific to the 5704 (since I have two machines using 5750s without this problem). Looks like we'll need someone with the Broadcom data sheet for the 5704 to help out. There's also the Bill Paul <[EMAIL PROTECTED]> and David Christensen <[EMAIL PROTECTED]> (who worked on bce(4), but might know of some details here...) -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networkinghttp://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Bridging problems on IP address conflict
Hello, I have the following bridge setups: bridge0: flags=8043 mtu 1500 ether ac:de:48:df:0d:8c priority 32768 hellotime 2 fwddelay 15 maxage 20 member: fxp0 flags=3 member: em0 flags=3 bridge1: flags=8043 mtu 1500 ether ac:de:48:fe:cd:41 priority 32768 hellotime 2 fwddelay 15 maxage 20 member: xl1 flags=3 member: xl0 flags=3 And my system constantly reports: arp: 00:13:20:1c:33:22 is using my IP address XX.YY.ZZ.KK! several (thoundsands of) times. In fact this ARP is my own fxp0 interface, and this is the only interface that has this IP. What should I do? Ass IP on the bridge0 interface instead of the fxp0 bridge member? Or anything else? -- === Eduardo Meyer pessoal: [EMAIL PROTECTED] profissional: [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bge Ierr rate increase from 5.3R -> 6.1R
Quoting Jeremy Chadwick <[EMAIL PROTECTED]>: On Thu, Jan 25, 2007 at 12:07:22PM +0100, Robin Gruyters wrote: Quoting Jeremy Chadwick <[EMAIL PROTECTED]>: [...] > >Set your Cisco configuration to use 100/full, and edit the >ifconfig_bge0 line in rc.conf on your FreeBSD box to have "media >100baseTX mediaopt full-duplex", then reboot the FreeBSD box. >If the problem continues, there may be faulty cabling, but >usually errors on one direction are a sign of duplex mismatch. >If after replacing the cabling the issue continues, then there's >a chance the bge(4) driver may be obtaining statistics wrong for >the particular chip revision being used (this is hearsay on my >part; I'm just guessing...) > Ok, I have set the Cisco port to 100/full-duplex and update the bge* interfaces on the development server, but the problem still exists. I have also updated the other server, which is connected to another Cisco switch, but the same results. Okay so at least we know it's not specific to your switch, or to auto-neg nor the cabling (two different switches + boxes with the same problem probably isn't your fault. :) ). That's definitely evidence that it's a driver problem, probably specific to the 5704 (since I have two machines using 5750s without this problem). Looks like we'll need someone with the Broadcom data sheet for the 5704 to help out. There's also the Bill Paul <[EMAIL PROTECTED]> and David Christensen <[EMAIL PROTECTED]> (who worked on bce(4), but might know of some details here...) Hmmm, ok. BTW, I found out there another thread going on on the freebsd-net mailinglist about the same issue(s): http://marc.theaimsgroup.com/?l=freebsd-net&w=2&r=1&s=bge+ierr&q=b There are some patches available, but looks like only for the -CURRENT not for 6.x releases. Regards, Robin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bge Ierr rate increase from 5.3R -> 6.1R
On Thu, Jan 25, 2007 at 03:46:01PM +0100, Robin Gruyters wrote: > Hmmm, ok. BTW, I found out there another thread going on on the > freebsd-net mailinglist about the same issue(s): > > http://marc.theaimsgroup.com/?l=freebsd-net&w=2&r=1&s=bge+ierr&q=b > > There are some patches available, but looks like only for the -CURRENT > not for 6.x releases. Definitely related, and probably the cause. I hope someone backports this to RELENG_6 once everything is tested thoroughly. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networkinghttp://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Netgraph at startup - rc.conf ?
I have a machine with two interfaces in it - bge0 and beg1. I now find I need to usse ng_fec to make these into one interface due to the way out networking contractors are installign a new site. Seems like no problem from the command line, but what I can't find anywhere in the documentation is how to make this happen at boot time using rc.conf. I am assuming my line which looks like: ifconfig_em0="inet 172.16.1.6 netmask 255.255.0.0" becomes ifconfig_fec0="inet 172.16.1.6 netmask 255.255.0.0" but obviously I need to do something to create fec0 before that happens. Preseumably something like cloned_interfaces="fce0", but where does it get the parameters from to create the interface ? cheers, -pcf. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 6.2-STABLE and Flash 7 patch
[EMAIL PROTECTED] wrote: > Torfinn Ingolfsen wrote: > > BTW, what is the reason this "hack" isn't included in the base kernel > > / code? > > Because it is probably unnecessary? I run a recent 6-STABLE and use > the flash7 plugin *without* this patch. I am using Opera, though, not > Firefox... Same here. I use Opera with the Flash plugin on 6-STABLE without any problems. I haven't applied a patch to rtld. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, USt-Id: DE204219783 Any opinions expressed in this message are personal to the author and may not necessarily reflect the opinions of secnetix GmbH & Co KG in any way. FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "I made up the term 'object-oriented', and I can tell you I didn't have C++ in mind." -- Alan Kay, OOPSLA '97 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Netgraph at startup - rc.conf ?
On Thu, 25 Jan 2007 15:36:33 + Pete French <[EMAIL PROTECTED]> wrote: > I have a machine with two interfaces in it - bge0 and beg1. I now > find I need to usse ng_fec to make these into one interface due to > the way out networking contractors are installign a new site. > Seems like no problem from the command line, but what I can't > find anywhere in the documentation is how to make this happen > at boot time using rc.conf. I am assuming my line which > looks like: > ifconfig_em0="inet 172.16.1.6 netmask 255.255.0.0" > becomes > ifconfig_fec0="inet 172.16.1.6 netmask 255.255.0.0" > but obviously I need to do something to create fec0 before > that happens. Preseumably something like cloned_interfaces="fce0", > but where does it get the parameters from to create the interface ? SEE ALSO: http://www.freebsd.org/cgi/query-pr.cgi?pr=conf/104884 If you apply this patch, you can use ng_fec like following in your /etc/rc.conf: fec_interfaces="fec0" fecconfig_fec0="bge0 bge1" ifconfig_fec0="inet 172.16.1.6 netmask 255.255.0.0" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Netgraph at startup - rc.conf ?
On 1/25/07, Pete French <[EMAIL PROTECTED]> wrote: I have a machine with two interfaces in it - bge0 and beg1. I now find I need to usse ng_fec to make these into one interface due to the way out networking contractors are installign a new site. Seems like no problem from the command line, but what I can't find anywhere in the documentation is how to make this happen at boot time using rc.conf. I am assuming my line which looks like: ifconfig_em0="inet 172.16.1.6 netmask 255.255.0.0" becomes ifconfig_fec0="inet 172.16.1.6 netmask 255.255.0.0" but obviously I need to do something to create fec0 before that happens. Preseumably something like cloned_interfaces="fce0", but where does it get the parameters from to create the interface ? To run commands before a interface started, you need to create a /etc/start_if.fec0, #!/bin/sh /usr/sbin/ngctl -f- <<-SEQ mkpeer fec dummy fec msg fec0: add_iface "bge0" msg fec0: add_iface "bge1" msg fec0: set_mode_inet SEQ Then add fec0 to the network_interfaces variable in your /etc/rc.conf. Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
does -STABLE support VIA VT6103 NIC?
I'm looking at the release notes for 6.2-RELEASE: http://www.freebsd.org/releases/6.2R/hardware-i386.html#ETHERNET I'm considering the botherboard on this 1U system: http://www.ironsystems.com/Customkititems.asp?kc=SYS%2DS%2DA113%2D01&Cc=ACLASS Which describes a VIA 'VT6103 10/100 Base-T Ethernet PHY' interface. This is not specifically mentioned as supported; does anyone know for sure? -- Brian Reichert <[EMAIL PROTECTED]> 55 Crystal Ave. #286Daytime number: (603) 434-6842 Derry NH 03038-1725 USA BSD admin/developer at large ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: does -STABLE support VIA VT6103 NIC?
Brian Reichert wrote: > I'm looking at the release notes for 6.2-RELEASE: > > http://www.freebsd.org/releases/6.2R/hardware-i386.html#ETHERNET > > I'm considering the botherboard on this 1U system: > > > http://www.ironsystems.com/Customkititems.asp?kc=SYS%2DS%2DA113%2D01&Cc=ACLASS > > Which describes a VIA 'VT6103 10/100 Base-T Ethernet PHY' interface. > > This is not specifically mentioned as supported; does anyone know for sure? > According to http://developer.novell.com/yes/66541.htm, the VT6105 is a Via Rhine III adapter, which is supported by the vr driver. -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: does -STABLE support VIA VT6103 NIC?
Brian Reichert <[EMAIL PROTECTED]> wrote: > I'm looking at the release notes for 6.2-RELEASE: > > http://www.freebsd.org/releases/6.2R/hardware-i386.html#ETHERNET > > I'm considering the botherboard on this 1U system: > > > http://www.ironsystems.com/Customkititems.asp?kc=SYS%2DS%2DA113%2D01&Cc=ACLASS > > Which describes a VIA 'VT6103 10/100 Base-T Ethernet PHY' interface. The actual interface is a VT6105. The 6103 is just the PHY. This chip is called "Rhine III", and it's listed in the FreeBSD release notes. > This is not specifically mentioned as supported; does anyone know for sure? It's supported by the vr(4) driver. I've got two VT610x NICs on my VIA EDEN PD10k board, too. They work perfectly fine. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, USt-Id: DE204219783 Any opinions expressed in this message are personal to the author and may not necessarily reflect the opinions of secnetix GmbH & Co KG in any way. FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "I have stopped reading Stephen King novels. Now I just read C code instead." -- Richard A. O'Keefe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: does -STABLE support VIA VT6103 NIC?
On Thu, Jan 25, 2007 at 07:02:44PM +0100, Oliver Fromme wrote: > Brian Reichert <[EMAIL PROTECTED]> wrote: > > I'm looking at the release notes for 6.2-RELEASE: > > Which describes a VIA 'VT6103 10/100 Base-T Ethernet PHY' interface. > > The actual interface is a VT6105. The 6103 is just the PHY. > This chip is called "Rhine III", and it's listed in the > FreeBSD release notes. > > > This is not specifically mentioned as supported; does anyone know for sure? > > It's supported by the vr(4) driver. I've got two VT610x > NICs on my VIA EDEN PD10k board, too. They work perfectly > fine. Thanks, both of you, for your feedback. Off I go... > Best regards >Oliver -- Brian Reichert <[EMAIL PROTECTED]> 55 Crystal Ave. #286Daytime number: (603) 434-6842 Derry NH 03038-1725 USA BSD admin/developer at large ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Bridging problems on IP address conflict
On Thu, 2007-Jan-25 12:01:46 -0200, Eduardo Meyer wrote: >bridge0: flags=8043 mtu 1500 > ether ac:de:48:df:0d:8c > priority 32768 hellotime 2 fwddelay 15 maxage 20 > member: fxp0 flags=3 > member: em0 flags=3 > >bridge1: flags=8043 mtu 1500 > ether ac:de:48:fe:cd:41 > priority 32768 hellotime 2 fwddelay 15 maxage 20 > member: xl1 flags=3 > member: xl0 flags=3 > >And my system constantly reports: > >arp: 00:13:20:1c:33:22 is using my IP address XX.YY.ZZ.KK! > >several (thoundsands of) times. In fact this ARP is my own fxp0 >interface, and this is the only interface that has this IP. What >should I do? Ass IP on the bridge0 interface instead of the fxp0 >bridge member? Or anything else? You don't say what version of FreeBSD you are running (there were some bridge(4) fixes between 6.1 and 6.2) or what ifconfig shows for the bridge members. This may be indicative of a loop in your switch network - is there any way that packets leaving fxp0 can re-appear on em0, xl0 or xl1? Based on a previous thread, you probably should put the IP address on the bridge device, though that should not be related to your problem. -- Peter Jeremy pgpKa41LjSwfb.pgp Description: PGP signature
second cpu not used on smp platform
Hello! Just cvsup-ed and upgraded to 6.2-STABLE. The box has hyperthreading processor: # more /var/run/dmesg.boot |grep -i cpu CPU: Intel(R) Pentium(R) 4 CPU 3.00GHz (3000.37-MHz 686-class CPU) Logical CPUs per core: 2 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu0: on acpi0 cpu1: on acpi0 SMP: AP CPU #1 Launched! and also sysctl shows that it is: kern.threads.virtual_cpu: 2 kern.smp.cpus: 2 hw.ncpu: 2 machdep.hlt_cpus: 2 machdep.logical_cpus_mask: 2 dev.cpu.0.%desc: ACPI CPU dev.cpu.0.%driver: cpu dev.cpu.0.%location: handle=\_PR_.CPU0 dev.cpu.0.%pnpinfo: _HID=none _UID=0 dev.cpu.0.%parent: acpi0 dev.cpu.0.cx_supported: C1/0 dev.cpu.0.cx_lowest: C1 dev.cpu.0.cx_usage: 100.00% dev.cpu.1.%desc: ACPI CPU dev.cpu.1.%driver: cpu dev.cpu.1.%location: handle=\_PR_.CPU1 dev.cpu.1.%pnpinfo: _HID=none _UID=0 dev.cpu.1.%parent: acpi0 dev.cpu.1.cx_supported: C1/0 dev.cpu.1.cx_lowest: C1 dev.cpu.1.cx_usage: 0% When I run several concurrent processes I do not see that the CPU1 is used at all! The 'top' shows this, and the sysctl shows this: dev.cpu.0.cx_usage: 100.00% dev.cpu.1.cx_usage: 0% last pid: 732; load averages: 7.94, 5.19, 2.52 up 0+00:29:42 23:39:43 38 processes: 9 running, 29 sleeping CPU states: 99.3% user, 0.0% nice, 0.7% system, 0.0% interrupt, 0.0% idle Mem: 34M Active, 15M Inact, 40M Wired, 34M Buf, 145M Free Swap: 469M Total, 469M Free PID USERNAME THR PRI NICE SIZERES STATE C TIME WCPU COMMAND 691 root1 1120 2628K 1984K RUN0 0:45 12.01% perl5.8.8 693 root1 1120 2628K 1984K RUN0 0:41 11.96% perl5.8.8 696 root1 1120 2628K 1984K RUN0 0:40 11.96% perl5.8.8 698 root1 1120 2628K 1984K RUN0 0:37 11.96% perl5.8.8 690 root1 1120 2628K 1984K RUN0 0:44 11.91% perl5.8.8 694 root1 1120 2628K 1984K RUN0 0:42 11.91% perl5.8.8 697 root1 1120 2628K 1984K RUN0 0:38 11.91% perl5.8.8 723 root1 1120 2628K 1984K RUN0 0:22 11.09% perl5.8.8 What it can be -- Oles mailto:[EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: second cpu not used on smp platform
On Jan 25, 2007, at 3:48 PM, Oles Hnatkevych wrote: Hello! Just cvsup-ed and upgraded to 6.2-STABLE. The box has hyperthreading processor: check value of machdep.hyperthreading_allowed sysctl. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: second cpu not used on smp platform
Oles Hnatkevych wrote: > Hello! > > Just cvsup-ed and upgraded to 6.2-STABLE. > > The box has hyperthreading processor: > > # more /var/run/dmesg.boot |grep -i cpu > CPU: Intel(R) Pentium(R) 4 CPU 3.00GHz (3000.37-MHz 686-class CPU) > Logical CPUs per core: 2 > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > cpu0: on acpi0 > cpu1: on acpi0 > SMP: AP CPU #1 Launched! [...] > What it can be This is done intentionally on all -STABLE branches, see http://security.freebsd.org/advisories/FreeBSD-SA-05:09.htt.asc for details. Note that it is possible to re-enable htt if you know what you are doing, by setting machdep.hyperthreading_allowed. Please note that enabling hyperthreading does hurt performance for many cases, so you will want to evaluate if you really want it, or to disable it from BIOS. Cheers, -- Xin LI <[EMAIL PROTECTED]> http://www.delphij.net/ FreeBSD - The Power to Serve! signature.asc Description: OpenPGP digital signature
Re: second cpu not used on smp platform
Hello! I believe that the kernel boot messages should explicitly tell that hyperthreading is disabled by default, so the guys like me won't be confused. ;-) OH> Hello! OH> Just cvsup-ed and upgraded to 6.2-STABLE. OH> The box has hyperthreading processor: OH> # more /var/run/dmesg.boot |grep -i cpu OH> CPU: Intel(R) Pentium(R) 4 CPU 3.00GHz (3000.37-MHz 686-class CPU) OH> Logical CPUs per core: 2 OH> FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs OH> cpu0 (BSP): APIC ID: 0 OH> cpu1 (AP): APIC ID: 1 OH> cpu0: on acpi0 OH> cpu1: on acpi0 OH> SMP: AP CPU #1 Launched! -- freebsd-stable mailto:freebsd-stable@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
SPARC64: Can't upgrade from 6.1 to 6.2 due to binutils
Hi, I was trying to upgrade my Sun Ultra 5 from 6.1R to 6.2R and bumped into this when doing a make buildword: building static binutils library ranlib libbinutils.a ===> gnu/usr.bin/binutils/addr2line (all) cc -O2 -pipe -I. -I/usr/src/gnu/usr.bin/binutils/addr2line -I/usr/src/gnu/usr.bin/binutils/addr2line/../libbfd -I/usr/obj/u cc -O2 -pipe -I. -I/usr/src/gnu/usr.bin/binutils/addr2line -I/usr/src/gnu/usr.bin/binutils/addr2line/../libbfd -I/usr/obj/u ../libbinutils/libbinutils.a(bucomm.o)(.text+0xb28): In function `make_tempname': : warning: warning: mktemp() possibly used unsafely; consider using mkstemp() ../libbfd/libbfd.a(libbfd.o)(.text+0xa2c): In function `_bfd_generic_verify_endian_match': : undefined reference to `libintl_dgettext' ../libbfd/libbfd.a(libbfd.o)(.text+0xa70): In function `_bfd_generic_verify_endian_match': : undefined reference to `libintl_dgettext' ../libbfd/libbfd.a(libbfd.o)(.text+0xaec): In function `warn_deprecated': : undefined reference to `libintl_dgettext' ../libbfd/libbfd.a(libbfd.o)(.text+0xb30): In function `warn_deprecated': : undefined reference to `libintl_dgettext' ../libbfd/libbfd.a(bfd.o)(.text+0x74): In function `bfd_errmsg': : undefined reference to `libintl_dgettext' ../libbfd/libbfd.a(bfd.o)(.text+0x2dc): more undefined references to `libintl_dgettext' follow *** Error code 1 Stop in /usr/src/gnu/usr.bin/binutils/addr2line. *** Error code 1 Stop in /usr/src/gnu/usr.bin/binutils. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. I poked around binutils in the past trying to get firefox running with the info from this PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=89486 Now I tried cvsuping the src, make clean and rebuilding binutils with no luck. Any pointers are most appreciated :) -- Joao Barros ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Netgraph at startup - rc.conf ?
> http://www.freebsd.org/cgi/query-pr.cgi?pr=conf/104884 Now that's an excellent patch - but not yet applied to STABLE I guess, and I don't want to have to re-patch every time I do an install unfortunately. Though if it gets commited in the near future I would definitely do it this way. thanks, -pete. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 6.2-STABLE and Flash 7 patch
On Wednesday 24 January 2007 19:10, Alexandre Vasconcelos wrote: > Hello, > > Working setup: > - FreeBSD 6.2-PRERELEASE, firefox 2 and flash 7 patched with > rtld_dlsym_hack.diff, like suggested on Handbook. > > After 6.2-STABLE upgrade reaplying the rtld_dlsym_hack.diff fails: > > [EMAIL PROTECTED] src]# patch < rtld_dlsym_hack.diff > Hmm... Looks like a unified diff to me... > The text leading up to this was: > -- > > |--- libexec/rtld-elf/rtld.c.orig Fri Sep 24 08:04:52 2004 > |+++ libexec/rtld-elf/rtld.cSun Oct 17 03:37:44 2004 > > -- > Patching file libexec/rtld-elf/rtld.c using Plan A... > Hunk #1 failed at 129. > Hunk #2 succeeded at 187 (offset 9 lines). > Hunk #3 succeeded at 1820 (offset 82 lines). > 1 out of 3 hunks failed--saving rejects to libexec/rtld-elf/rtld.c.rej > done > > And make fails: > > [EMAIL PROTECTED] rtld-elf]# make > cc -O2 -fno-strict-aliasing -pipe -Wall -DFREEBSD_ELF -DIN_RTLD > -I/usr/src/libexec/rtld-elf/i386 -I/usr/src/libexec/rtld-elf -elf -fpic > -DPIC -std=gnu99 -Wformat=2 -Wno-format-extra-args -Werror -c > /usr/src/libexec/rtld-elf/i386/rtld_start.S > cc -O2 -fno-strict-aliasing -pipe -Wall -DFREEBSD_ELF -DIN_RTLD > -I/usr/src/libexec/rtld-elf/i386 -I/usr/src/libexec/rtld-elf -elf -fpic > -DPIC -std=gnu99 -Wformat=2 -Wno-format-extra-args -Werror -c > /usr/src/libexec/rtld-elf/i386/reloc.c > cc -O2 -fno-strict-aliasing -pipe -Wall -DFREEBSD_ELF -DIN_RTLD > -I/usr/src/libexec/rtld-elf/i386 -I/usr/src/libexec/rtld-elf -elf -fpic > -DPIC -std=gnu99 -Wformat=2 -Wno-format-extra-args -Werror -c > /usr/src/libexec/rtld-elf/rtld.c > /usr/src/libexec/rtld-elf/rtld.c:189: error: `_dlsym' undeclared here > (not in a function) > /usr/src/libexec/rtld-elf/rtld.c:189: error: initializer element is not > constant > /usr/src/libexec/rtld-elf/rtld.c:189: error: (near initialization for > `exports[4]') > *** Error code 1 > > Stop in /usr/src/libexec/rtld-elf. > > > How to fix this? > Thanks, > Alex > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" Hello I had the same problem, I've patched the library myself but I don't know how to make a proper "patch file" so if you want, here's my patched one : http://fkraiem.free.fr/rtld.c Copy into /usr/src/libexec/rtld-elf and follow the instructions given in the handbook. -- () ascii ribbon campaign - against HTML e-mail /\ www.asciiribbon.org - against proprietary attachments ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SPARC64: Can't upgrade from 6.1 to 6.2 due to binutils
On 1/26/07, Matthew Herzog <[EMAIL PROTECTED]> wrote: I have never been able to upgrade Sparc64 from source. I suspect it is nearly impossible. Please let me know if you suceed. This particular box has been upgraded everytime from source for every release since 5.something. I can check the sources, but one thing comes to mind: the first install I did I noticed hme wasn't GIANT free and it has been for a while :) -- Joao Barros ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SPARC64: Can't upgrade from 6.1 to 6.2 due to binutils
On Thu, Jan 25, 2007 at 10:51:21PM +, Joao Barros wrote: > Hi, > > I was trying to upgrade my Sun Ultra 5 from 6.1R to 6.2R and bumped > into this when doing a make buildword: > > building static binutils library > ranlib libbinutils.a > ===> gnu/usr.bin/binutils/addr2line (all) > cc -O2 -pipe -I. -I/usr/src/gnu/usr.bin/binutils/addr2line > -I/usr/src/gnu/usr.bin/binutils/addr2line/../libbfd -I/usr/obj/u > cc -O2 -pipe -I. -I/usr/src/gnu/usr.bin/binutils/addr2line > -I/usr/src/gnu/usr.bin/binutils/addr2line/../libbfd -I/usr/obj/u > ../libbinutils/libbinutils.a(bucomm.o)(.text+0xb28): In function > `make_tempname': > : warning: warning: mktemp() possibly used unsafely; consider using > mkstemp() > ../libbfd/libbfd.a(libbfd.o)(.text+0xa2c): In function > `_bfd_generic_verify_endian_match': > : undefined reference to `libintl_dgettext' > ../libbfd/libbfd.a(libbfd.o)(.text+0xa70): In function > `_bfd_generic_verify_endian_match': > : undefined reference to `libintl_dgettext' > ../libbfd/libbfd.a(libbfd.o)(.text+0xaec): In function `warn_deprecated': > : undefined reference to `libintl_dgettext' > ../libbfd/libbfd.a(libbfd.o)(.text+0xb30): In function `warn_deprecated': > : undefined reference to `libintl_dgettext' > ../libbfd/libbfd.a(bfd.o)(.text+0x74): In function `bfd_errmsg': > : undefined reference to `libintl_dgettext' > ../libbfd/libbfd.a(bfd.o)(.text+0x2dc): more undefined references to > `libintl_dgettext' follow > *** Error code 1 > > Stop in /usr/src/gnu/usr.bin/binutils/addr2line. FreeBSD doesn't and never has included libintl, so if your sources are trying to compile against it, then they or your world are probably contaminated somehow. > I poked around binutils in the past trying to get firefox running with > the info from this PR: > http://www.freebsd.org/cgi/query-pr.cgi?pr=89486 Ah yes, that could do it ;) > Now I tried cvsuping the src, make clean and rebuilding binutils with no > luck. > Any pointers are most appreciated :) The easiest way to repair your system might be to just do a binary upgrade from new sysinstall media. Kris pgpc8EkPkfiTj.pgp Description: PGP signature
Re: SPARC64: Can't upgrade from 6.1 to 6.2 due to binutils
On Fri, Jan 26, 2007 at 03:30:18AM +, Joao Barros wrote: > On 1/26/07, Matthew Herzog <[EMAIL PROTECTED]> wrote: > >I have never been able to upgrade Sparc64 from source. I suspect it is > >nearly impossible. > >Please let me know if you suceed. Matthew, We established long ago that you have a trashed FreeBSD install. You can continue to choose not to believe in the existence the dozen or so sparc64 systems I run that successfully build world (let alone the many sparc64 systems run and updated by other freebsd users) if you wish, but that doesn't make your dreams any closer to reality ;-) Kris pgp60Udver2C7.pgp Description: PGP signature
Re: FreeBSD 6.2-STABLE and Flash 7 patch
This is a Firefox specific patch which requires the rtld be patched. Many thanks to those who have provided patch updates because I was at a lost without them. Oliver Fromme wrote: [EMAIL PROTECTED] wrote: > Torfinn Ingolfsen wrote: > > BTW, what is the reason this "hack" isn't included in the base kernel > > / code? > > Because it is probably unnecessary? I run a recent 6-STABLE and use > the flash7 plugin *without* this patch. I am using Opera, though, not > Firefox... Same here. I use Opera with the Flash plugin on 6-STABLE without any problems. I haven't applied a patch to rtld. Best regards Oliver ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
