Re: FreeBSD bind performance in FreeBSD 7
Ted Mittelstaedt wrote: My beef with the DNS tests was that ISC ran out and bought the hardware FIRST, -then- they started testing. This is directly contrary to every bit of advice ever given in the computer industry for the last 50 years - you select the software FIRST, -then- you buy the hardware that runs it. In short, it said far more about the incompetence of the testers than the shortcomings of the software. This is ridiculous. ISC is one of the most fervent pro-FreeBSD companies out there (basing most of our services on the OS, and contributing to the FreeBSD community including the busiest CVSup FTP servers and have FreeBSD committers on staff) I will not stand back and watch folks on a public mailing list call us incompetent individuals with a anti-FreeBSD bias. First off the final report was published last Friday at: http://www.isc.org/pubs/tn/index.pl?tn=isc-tn-2008-1.html (the server this is served from runs FreeBSD) I was not one of the direct testers (we had a couple PhD's handling that, who I know both use FreeBSD on their personal systems), but as one of the folks who supported them in their work, I can tell you that the stats we gave the FreeBSD folks were from a test sponsored by the US National Science Foundation. We were mandated to use branded HW and we tested several models from HP, Sun, even Iron Systems (whitebox) before deciding on the HP's. The mechanism we used are all documented in the paper We were also asked to test DNS performance on several OS's. The short version was 'take a standard commercial off the shelf' server and see how BIND performs (esp. with DNSSEC) on it. We weren't asked to get hardware that was perfect for Brand X OS; that wasn't part of the remit. (We actually use the exact same HP HW for a secondary service where we host a couple of thousand zones using BIND including 30+ TLD zones. Oh and it runs FreeBSD) Yes we found FreeBSD performed poorly in our initial tests. and I talked to several folks (including rwatson and kris) about the issue. Kris had already been working on improving performance with MySQL and PgSQL and was interested in doing the same with BIND. Kris went off and hacked away and right before EuroBSDcon last September asked us to re-run the tests (on the same HW) using a 7.0-CURRENT snapshot, and the end results are shown with a 33,000 query increase over 6.2-RELEASE, bring FreeBSD just behind the Linux distros we tested. I know rwatson and kris have continually worked on the relevent network stack issues that cover BIND, and additional performance gains have been found since then, and working on this issue has been a true partnership between the FreeBSD developers and ISC. BIND isn't perfect, we admit that, we have been constantly improving it's multi-CPU performance and BIND 9.4 and 9.5 are continuing in that effort. We have several members of our dev team who use FreeBSD as their developent platform, including a FreeBSD committer. So Ted, stop spouting this ISC is spewing anti-FreeBSD bias crap, it flatly isn't true... Oh, and this email is coming to you via several of ISC FreeBSD MX servers which resolve the freebsd.org name via caching DNS servers running FreeBSD, to freebsd.org's MX server over a IPv6 tunnel supplied by ISC to the FreeBSD project to help FreeBSD eat their own IPv6 dog food... Yeah, ISC just hates FreeBSD... rolls eyes Best Wishes - Peter -- [EMAIL PROTECTED] | ISC | OpenPGP 0xE8048D08 | The bits must flow signature.asc Description: OpenPGP digital signature
Driver support for 3ware 8506-12 in i386?
Hi - Many of you saw my messages last month on getting a 3ware 8506-12 SATA RAID controller working under heavy I/O on 5.2.1/amd64, and despite the work of Paul Saab in getting me a version of the -CURRENT twe driver, it still locks up under heavy I/O. So since this box is behind schedule, and I need to get this box stable, I am likely to side-grade this box to 5.2.1/i386, with the understanding that the twe driver as it stands now just isn't 64-bit compatible. When 5.3-RELEASE is out and the twe driver is hopefully 64-bit clean, I can reconsider going back to amd64 on this box. Does anyone have a 8506 series (esp. a 8506-12) controller running under 5.2.1/i386 in production? I'd like to know before hand before I make the jump. Best Wishes - Peter -- [EMAIL PROTECTED] | ISC | OpenPGP Key E8048D08 | The bits must flow pgpq0hP3R8n0f.pgp Description: signature
Customizing a 'make release'...
(If this question is better served on another list, let me know) I am trying to come up with a custom FreeBSD ISO w/ my personal preferences (no integrated OpenSSH, Heimdal, or Sendmail) I have been working off of http://www.gsoft.com.au/~doconnor/FreeBSD-release-2.html, and /usr/bin/time sh -c 'make release CHROOTDIR=/hog0/release NODOC=YES NOPORTS=YES BUILDNAME=5.2-REL-FOO CVSROOT=/hog1/FreeBSD-CVS RELEASETAG=RELENG_5_2_1_RELEASE' | tee /tmp/release.log Now my understanding is that 'make release' honors the variables set in /etc/make.conf, where I have: -=- NO_OPENSSH=true NO_KERBEROS=true NO_SENDMAIL=true -=- After creating the binaries and the ISO image, installing the OS on a new box results in a sendmail-less install, but it still has all the OpenSSH and Heimdal bits included. Do I needed to declare NO_OPENSSH and NO_KERBEROS on the 'make release' command line? Also, is there any way to change the default bits the install process - like the default auto-partition (I prefer to leave the /var partition with the remaining space instead of /usr as it is now), and have it automatically install certain packages instead of asking. Thanks in advance for any advice you can pass along... Best Wishes - Peter -- [ http://www.plosh.net/ ] - Earth Halted: Please reboot to continue ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
'make release' questions.
Hello - I am planning to cut my own internal 5.2-RELEASE cut w/ all the Heimdal OpenSSH bits removed, and I have come across some questions on how to build such a release (.ISO in this case) I have been following: http://www.gsoft.com.au/~doconnor/FreeBSD-release-2.html And I was under the impression that it would honor /etc/make.conf, where I have: -=- NO_OPENSSH=true NO_KERBEROS=true -=- (where in the usual make buildworld sense, it would not build/install Heimdal/SSH bits. But the resulting build and ISO still installs Heimdal OpenSSH. Am I missing something here? (do I need to specify it in the 'make release', etc.) Best Wishes - Peter -- [ http://www.plosh.net/ ] - Earth Halted : Please Reboot ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Edgeport USB - Serial Hub support?
Is anyone using any of the Edgeport USB/Serial converters under FreeBSD? (like the Edgeport 4/ or 8/?) Does plugging them in spawn the neccessary ucom* /dev entrys? Or does it need a specific driver that isn't in FreeBSD yet? (The web site at ionetworks.com says that it is supported under Linux, so there is some small hope) Best Wishes - Peter -- [ http://www.plosh.net/ ] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Rocketport (rp0) mapping failure on 5.1-REL
I am installing a RocketPort PCI card into a Acer Altos system; the box was originally running Linux, slapping on FreeBSD 5.1 on the box, the system throws up this error when trying to attach the RP card: -=- rp0: RocketPort PCI port 0x5400-0x54ff,0x5000-0x507f mem 0xed8ffc00-0xed8ffc7f irq 11 at device 2.0 on pci1 rp0: ioaddr mapping failed for RocketPort(PCI). device_probe_and_attach: rp0 attach returned 6 -=- Has anyone ever seen such an error, and if so, how did you get around it? (I haven't been able to find anything via Google) From what I have been told, the card came up cleanly when the box was running Linux. Best Wishes - Peter -- [ http://www.plosh.net/ ] - Resident Kalifornian ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Rocketport (rp0) mapping failure on 5.1-REL
It looks like what I might have is one of the new Universal PCI RocketPort cards - does anyone know if the current rp driver supports the card? (Comport no longer makes the 32-bit-only PCI cards, just the 32 and 64 bit compatible uPCI cards now) If not, is there a new rp driver I can test out that may be in -CURRENT? Best Wishes - Peter On Monday 10 November 2003 10:02 am, Peter Losher wrote: I am installing a RocketPort PCI card into a Acer Altos system; the box was originally running Linux, slapping on FreeBSD 5.1 on the box, the system throws up this error when trying to attach the RP card: -=- rp0: RocketPort PCI port 0x5400-0x54ff,0x5000-0x507f mem 0xed8ffc00-0xed8ffc7f irq 11 at device 2.0 on pci1 rp0: ioaddr mapping failed for RocketPort(PCI). device_probe_and_attach: rp0 attach returned 6 -=- Has anyone ever seen such an error, and if so, how did you get around it? (I haven't been able to find anything via Google) From what I have been told, the card came up cleanly when the box was running Linux. Best Wishes - Peter -- [ http://www.plosh.net/ ] - Resident Kalifornian ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
XFree zooming funkiness...
So, I finally have X11 running on this Dell Inspiron 5100, and all was running well (well, except getting the webfonts to show up right) for the initial 48 hours until yesterday. Now when I start X up, all keyboard input scrolls the screens thru 4 zoom levels. Has anyone seen this, and if so, how did you fix it. X is basically unusable in this state. Attached is my current XF86Config. Any suggestions would be welcome. Best Wishes - Peter -- [ http://www.plosh.net/ ] - Earth Halted : Please Reboot# File generated by xf86config. # # Copyright (c) 1999 by The XFree86 Project, Inc. # # Permission is hereby granted, free of charge, to any person obtaining a # copy of this software and associated documentation files (the Software), # to deal in the Software without restriction, including without limitation # the rights to use, copy, modify, merge, publish, distribute, sublicense, # and/or sell copies of the Software, and to permit persons to whom the # Software is furnished to do so, subject to the following conditions: # # The above copyright notice and this permission notice shall be included in # all copies or substantial portions of the Software. # # THE SOFTWARE IS PROVIDED AS IS, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR # IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, # FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL # THE XFREE86 PROJECT BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, # WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF # OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE # SOFTWARE. # # Except as contained in this notice, the name of the XFree86 Project shall # not be used in advertising or otherwise to promote the sale, use or other # dealings in this Software without prior written authorization from the # XFree86 Project. # # ** # Refer to the XF86Config(4/5) man page for details about the format of # this file. # ** # ** # Module section -- this section is used to specify # which dynamically loadable modules to load. # ** # Section Module # Load the FreeType font modules Loadfreetype # This loads the DBE extension module. Loaddbe # Double buffer extension # This loads the miscellaneous extensions module, and disables # initialisation of the XFree86-DGA extension within that module. SubSection extmod Optionomit xfree86-dga # don't initialise the DGA extension EndSubSection # This loads the Type1 and FreeType font modules #Loadtype1 #Loadspeedo #Loadfreetype #Loadxtt # This loads the GLX module Load glx # This loads the DRI module Load dri EndSection Section DRI Mode 0666 EndSection # ** # Files section. This allows default font and rgb paths to be set # ** Section Files # The location of the RGB database. Note, this is the name of the # file minus the extension (like .txt or .db). There is normally # no need to change the default. RgbPath /usr/X11R6/lib/X11/rgb # Multiple FontPath entries are allowed (which are concatenated together), # as well as specifying multiple comma-separated entries in one FontPath # command (or a combination of both methods) # # If you don't have a floating point coprocessor and emacs, Mosaic or other # programs take long to start up, try moving the Type1 and Speedo directory # to the end of this list (or comment them out). # FontPath /usr/X11R6/lib/X11/fonts/webfonts FontPath /usr/X11R6/lib/X11/fonts/local/ FontPath /usr/X11R6/lib/X11/fonts/misc/ FontPath /usr/X11R6/lib/X11/fonts/75dpi/:unscaled FontPath /usr/X11R6/lib/X11/fonts/100dpi/:unscaled #FontPath /usr/X11R6/lib/X11/fonts/Speedo/ #FontPath /usr/X11R6/lib/X11/fonts/Type1/ #FontPath /usr/X11R6/lib/X11/fonts/TrueType/ #FontPath /usr/X11R6/lib/X11/fonts/freefont/ FontPath /usr/X11R6/lib/X11/fonts/75dpi/ FontPath /usr/X11R6/lib/X11/fonts/100dpi/ FontPath /usr/X11R6/lib/X11/fonts/webfonts # The module search path. The default path is shown here. #ModulePath /usr/X11R6/lib/modules EndSection # ** # Server flags section. # ** Section ServerFlags # Uncomment this to cause a core dump at the spot where a signal is # received. This may leave the console in an unusable state, but may # provide a better stack trace in the core dump to aid
Re: multi-port serial IO support
On Tuesday 25 March 2003 08:29 am, Douglas K. Rand wrote:
Tom WARNING: driver rp should register devices with make_dev() (dev_t =
Tom #rp/0x10082)
While I haven't tested it, I expect that this message goes away with
FreeBSD 4.7. The rp driver got some work done to it between 4.6 and
4.7.
Still happens on my FreeBSD 4.{6,7} console servers @work, where we use
RocketPorts pretty widely. (We even have some old RP ISA cards floating
around that are still in use)
WARNING: driver rp should register devices with make_dev() (dev_t =
#rp/0x10014)
I did hear that a new rp driver (nrp?) had been written/committed in -CURRENT
sometime late last year, and apparently made it in 5.0-RELEASE, but hadn't
been back-ported to -STABLE yet (but patches have been floating around in
the archives). I haven't had a chance to test it yet, although one of the
things the new driver apparently fixes is you are now able to use more than
one PCI card in a box. (we have some installs where we need a second PCI
card to drive a third/fourth pod, where this would be useful)
We just make our own cables and ends. Using flat satin cable, putting
the RJ45 ends on is trivial, and Comtrol's pin out allows a cross over
cable to be built by putting the RJ45 connector on one end of the
cable on backwards.
That's what we do here... (tangled in a web of cat-5 and silver satin cables
at the moment)
Best Wishes - Peter
--
[EMAIL PROTECTED] - [ http://www.plosh.net/ ]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
df outpout inconsistancy on a large filesystem...
So I have a 440GB partition set up on a server I am building, and I am experiencing a problem where I am getting inconsistent df output for that partition: # du -k /disk1 960552 /disk1 #df -k /disk1 Filesystem1K-blocks Used Avail Capacity Mounted on /dev/twed0s1f 4416943921256 406357592 0%/disk1 As you can see, the numbers don't match. Has anyone else experienced this? (the other partitions on the system are reporting normally) Just for completeness sake, this partition was newfs'ed with a 8k filesize, and a 64k blocksize. Also softupdates is active on this partition. The system/disk/partition looks to be working fine, just the df output is 'disturbing'. :( Best Wishes - Peter -- [EMAIL PROTECTED] - [ http://www.plosh.net/ ] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Compiling nm in a make buildworld.
Hi - I have a freshly intalled 4.6.2-REL box, and I wanted to update the box to 4.6.2-REL-p2. I cvsup'ed the src tree, and make buildworld dies @nm: Any ideas of what the cause could be? -=- === gnu/usr.bin/binutils/nm cc -O -pipe -D_GNU_SOURCE -I- -I. -I/usr/src/gnu/usr.bin/binutils/nm -I/usr/src/gnu/usr.bin/binutils/nm/../libbfd/i386 -I/usr/src/gnu/usr.bin/binutils/nm/../../../../contrib/binutils/include -I/usr/src/gnu/usr.bin/binutils/nm/../libbinutils -I/usr/src/gnu/usr.bin/binutils/nm/../../../../contrib/binutils/binutils -c /usr/src/gnu/usr.bin/binutils/nm/../../../../contrib/binutils/binutils/nm.c /usr/src/gnu/usr.bin/binutils/nm/../../../../contrib/binutils/binutils/nm.c: In function `main': /usr/src/gnu/usr.bin/binutils/nm/../../../../contrib/binutils/binutils/nm.c:467: syntax error at null character *** Error code 1 Stop in /usr/src/gnu/usr.bin/binutils/nm. *** Error code 1 -=- Thanks - -- [EMAIL PROTECTED] - [ http://www.plosh.net ] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
