Re: Sensorsd
-Original Message- From: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org] On Behalf Of Alexander Polakov Sent: Wednesday, January 06, 2010 4:11 PM To: misc@openbsd.org Subject: Re: Sensorsd 2010/1/6, Morris, Roy : > Ok, figured that might be what it was! Thanks. Too bad it > would be nice to know if the disk count changed ie. someone > plugged in a USB key. >>You can use hotplugd(8) for that. Yes sir you're absolutely correct! thanks.
Re: Sensorsd
-Original Message- From: Theo de Raadt [mailto:dera...@cvs.openbsd.org] Sent: Wednesday, January 06, 2010 3:45 PM To: Morris, Roy Cc: misc@openbsd.org Subject: Re: Sensorsd > I decided to use sensorsd for the first time and am a little confused as > to why it thinks I only have two (2) sensors when I have asked it to > watch > four (4) items. Any ideas would be great. > > The output from sysctl hw is the following > hw.disknames=sd0,cd0 > hw.diskcount=2 > hw.sensors.cpu0.temp0=34.00 degC > hw.sensors.mpi0.drive0=online (sd0), OK >The first two are not sensors. Note the ".sensors." part. Ok, figured that might be what it was! Thanks. Too bad it would be nice to know if the disk count changed ie. someone plugged in a USB key. Cheers Roy
Sensorsd
I decided to use sensorsd for the first time and am a little confused as to why it thinks I only have two (2) sensors when I have asked it to watch four (4) items. Any ideas would be great. The output from sysctl hw is the following hw.disknames=sd0,cd0 hw.diskcount=2 hw.sensors.cpu0.temp0=34.00 degC hw.sensors.mpi0.drive0=online (sd0), OK I put this in my /etc/sensorsd.conf hw.disknames:command=/etc/sendalert %t %n %2 hw.diskcount:command=/etc/sendalert %t %n %2 hw.sensors.cpu0.temp0:high=60C:command=/etc/sendalert %t %n %2 hw.sensors.mpi0.drive0:command=/etc/sendalert %t %n %2 After firing up sensorsd I check the log file and see it says it only sees two ? Will it only work if the word 'sensors' exists? Jan 6 09:17:22 dc-fw1 sensorsd[12648]: startup, system has 2 sensors Jan 6 09:18:22 dc-fw1 sensorsd[23326]: cpu0.temp0: within limits: 34.00 degC Jan 6 09:18:22 dc-fw1 sensorsd[23326]: mpi0.drive0: online, OK
Nat Logging
G'day, I was trying the log keyword in the NAT rule, expecting to see some type of NAT entry but basically I just see the exact same thing as logging in a rule. Is this the expected outcome or should I be seeing internal -> external entry? I used to work with a commercial "firewall" which showed (if logged) separate NAT entries. I thought they were good for debugging once in a while. Anyway, I suspect log was allowed in the event the nat rule was also a pass rule or something. thanks
Re: OT rack mount monitor/keyboards
I used the Perle cs9000. Worked great! -Original Message- From: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org] On Behalf Of stan Sent: Tuesday, September 01, 2009 4:57 PM To: OpenBSD general usage list Subject: OT rack mount monitor/keyboards I have a few locations where I have installed 1U rack mount KVM/monitor/keyboards, and quite frankly. I'm not happy with any of the ones I have tried. I recognize this is off topic, but the people on this list are pretty hard to please. Given that I was wondering if anyone would like to recomend anything that they have used for these, and been happy with? -- One of the main causes of the fall of the roman empire was that, lacking zero, they had no way to indicate successful termination of their C programs.
Re: SFTP - Max Users
excellent thanks. -Original Message- From: Robert [mailto:rob...@openbsd.pap.st] Sent: Thursday, August 27, 2009 2:53 PM To: Morris, Roy Cc: misc@openbsd.org Subject: Re: SFTP - Max Users On Thu, 27 Aug 2009 13:23:18 -0400 "Morris, Roy" wrote: > G'day, > I searched around but couldn't find a simple answer to this > question. I want to host a sftp server and there could be > thousands of accounts, although not all used at once. I was > wondering if there is a limit to the number of user accounts > I can create on a machine? I had originally thought of using > a database for authentication but I don't see an easy way of doing > that on OpenBSD. > > thanks > Roy Number of local user accounts is liminted by the available user id's. Since that's a 16 bit limit and if you stick to the 'from uid 1000 up' rule, that'd leave you with 64536 possible accounts. - Robert
SFTP - Max Users
G'day, I searched around but couldn't find a simple answer to this question. I want to host a sftp server and there could be thousands of accounts, although not all used at once. I was wondering if there is a limit to the number of user accounts I can create on a machine? I had originally thought of using a database for authentication but I don't see an easy way of doing that on OpenBSD. thanks Roy
Re: IMPORTANT, DO THIS OR YOUR E-MAIL WON'T WORK
lmao! -Original Message- From: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org] On Behalf Of Kevin Wilcox Sent: Tuesday, May 26, 2009 2:02 PM To: misc@openbsd.org Subject: Re: IMPORTANT, DO THIS OR YOUR E-MAIL WON'T WORK 2009/5/26 Sam Fourman Jr. : > Sam Fourman Jr. > sfour...@gmail.com > rlz686 Now that's funny. kmw -- To take from one, because it is thought that his own industry and that of his fathers has acquired too much, in order to spare to others, who, or whose fathers have not exercised equal industry and skill, is to violate arbitrarily the first principle of association, bthe guarantee to every one of a free exercise of his industry, & the fruits acquired by it.'
Re: PF and CLamAV "Integration" - how to do it?
my first search came up with an answer http://www.wains.be/index.php/2006/12/19/centosrhelfedora-web-proxy-antivirus -clamav/ -Original Message- From: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org]on Behalf Of Protocol Six Consulting Sent: Thursday, March 19, 2009 10:28 AM To: misc@openbsd.org Subject: PF and CLamAV "Integration" - how to do it? Hi, I was wondering if anyone here knows how to integrate the PF firewall with ClamAV. I am planning on putting into production an OpenBSD firewall and would like to do virus scanning at the network perimeter. I am definitely interested in scanning email traffic, but also possibly Web and IRC (and any other traffic types that makes sense) for a group of 25 people. Unfortunately I've not seen any real discussion or howtos for this type of integration. I've also looked in the PF FAQ pages and in the archives of Openbsd-misc or Openbsd-PF. Finally, the BookOfPF (which I like a lot!!) doesn't seem to touch on this topic either. I suspect my mental picture of how PF and ClamAV work together may be flawed or incomplete. I guess I'm assuming there is a way to have PF pass information directly to ClamAV, but perhaps some middle-ware glue is necessary. Any pointers and/or info would be greatly appreciated by this newbie. Thanks and best regards, :-) Sarah
PF Executive Summary
I need to create an executive summary of pf rules and I remember once seeing a link for a tool that read the rules and gave you back a 'checkpoint(ish)' output .. Anyone know the tool I am talking about or can recommend one? Otherwise I am stuck making stick drawings :)
Re: Find - Sillyness
This worked! You da man! thanks much. -Original Message- From: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org]on Behalf Of Daniel A. Ramaley Sent: Friday, January 23, 2009 9:56 AM To: misc@openbsd.org Subject: Re: Find - Sillyness On Friday January 23 2009 08:07, you wrote: >I am sure it's got something to do with the way I am quoting but it's >not making a lot of sense at this point. > >Here is the actual command I am trying to run and it's error >output. > >spider:/var/logtransfer/dc-fw1# find . -name pflog.*.gz -exec zcat {} > | tcpdump -entttv -r - \; >find: -exec: no terminating ";" >tcpdump: fread: Invalid argument You're right, the problem is quoting. The shell interprets everything after the pipe character ("|") as a separate command, so find never receives the semi-colon. For something this simple, i'd suggest moving the pipe outside of the find command: find . -name pflog.*.gz -exec zcat {} \; | tcpdump -entttv -r - For more complicated situations, you can use a structure more like this: find . -name pflog.*.gz -print0 | while read -d $'\0' file ; do \ echo "Now processing ${file}" \ zcat $file | tcpdump -entttv -r - \ done For your particular situation, not using a find at all might work: gunzip -c pflog.*.gz | tcpdump -entttv -r - That could fail if "pflog.*.gz" expands to so many files that it overflows the maximum command length, but otherwise should work the same. Dan RamaleyDial Center 118, Drake University Network Programmer/Analyst 2407 Carpenter Ave +1 515 271-4540Des Moines IA 50311 USA
Re: Find - Sillyness
Ok, I tried both and neither worked. Same error doh! -Original Message- From: Nick Bender [mailto:nben...@gmail.com] Sent: Friday, January 23, 2009 9:21 AM To: Morris, Roy Cc: misc@openbsd.org Subject: Re: Find - Sillyness On Fri, Jan 23, 2009 at 9:07 AM, Morris, Roy wrote: > Here is the actual command I am trying to run and it's error > output. > > spider:/var/logtransfer/dc-fw1# find . -name pflog.*.gz -exec zcat {} | > tcpdump -entttv -r - \; > find: -exec: no terminating ";" > tcpdump: fread: Invalid argument > Me thinks you need to quote you're pattern (or set noglob) and terminate your exec (just like find is telling you): find . -name 'pflog.*.gz' -exec zcat {} \; | ... -N
Re: Find - Sillyness
Thanks for the help, however I must still be in stupid mode doh! the original command works but as soon as I add the rest of the command it dies. Basically what I am trying to do is go through three years worth of pflogs in gzip format and grep for a part of an ip address. It works on a command line, on a single file but when used with 'find -exec' it yaks. I am sure it's got something to do with the way I am quoting but it's not making a lot of sense at this point. Here is the actual command I am trying to run and it's error output. spider:/var/logtransfer/dc-fw1# find . -name pflog.*.gz -exec zcat {} | tcpdump -entttv -r - \; find: -exec: no terminating ";" tcpdump: fread: Invalid argument -Original Message- From: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org]on Behalf Of John Jackson Sent: Thursday, January 22, 2009 3:12 PM To: misc@openbsd.org Subject: Re: Find - Sillyness On Thu, Jan 22, 2009 at 02:54:21PM -0500, Morris, Roy wrote: > I know this is more of a general 'huh' kind of thing, but I figured someone > could kick start my brain for me. Anyone know why this doesn't work? It > appears to find the files ok but the -exec part thinks it can't? > > > spider:/var/log# find . -name "daemon.*.gz" -exec "echo {}" \; > find: echo ./daemon.2.gz: No such file or directory > find: echo ./daemon.1.gz: No such file or directory > find: echo ./daemon.5.gz: No such file or directory > find: echo ./daemon.4.gz: No such file or directory > find: echo ./daemon.3.gz: No such file or directory > find: echo ./daemon.0.gz: No such file or directory > Try: find . -name "daemon.*.gz" -exec echo {} \; without the double quotes after exec. John
Find - Sillyness
I know this is more of a general 'huh' kind of thing, but I figured someone could kick start my brain for me. Anyone know why this doesn't work? It appears to find the files ok but the -exec part thinks it can't? spider:/var/log# find . -name "daemon.*.gz" -exec "echo {}" \; find: echo ./daemon.2.gz: No such file or directory find: echo ./daemon.1.gz: No such file or directory find: echo ./daemon.5.gz: No such file or directory find: echo ./daemon.4.gz: No such file or directory find: echo ./daemon.3.gz: No such file or directory find: echo ./daemon.0.gz: No such file or directory
Re: Single Use Port Forwarding Using PF
I would use authpf and assign them each a unique port number. They must authenticate with the gateway for the rule to become active. just a thought .. -Original Message- From: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org]on Behalf Of Jonathan Windle Sent: Tuesday, December 30, 2008 7:15 PM To: misc@openbsd.org Subject: Single Use Port Forwarding Using PF Hello, I wanted to know if it was possible to do the following with PF (and/or a mixture of other OpenBSD services). I would like to have an table of IP addresses with a port redirecting to the table. Instead of a round robin behavior however I want the IP address removed from the table when a session is opened. Once the table is empty the rule should become inactive until the table is populated again. The problem is I have a group of Windows boxes running RDP and I only ever want one user to connect to one Windows box. Thanks, Jonathan
Re: AAC 4.4
It all works now! Thanks! -Original Message- From: Marco Peereboom [mailto:[EMAIL PROTECTED] Sent: Thursday, November 27, 2008 3:13 PM To: Morris, Roy Cc: Morris, Roy; Subject: Re: AAC 4.4 We have diagnosed that issue to a bios bug. You must have missed a step in the make release; it isn't hard to do. On Nov 27, 2008, at 1:11 PM, "Morris, Roy" <[EMAIL PROTECTED]> wrote: > sorry , in answer to my own question, UKC>disable acpi fixes > that problem .. I boot right up > > So I guess the real question becomes why didn't my cd work? I > enabled aac in both GENERIC and RAMDISK_CD and did a release .. > It's fairly obvious the GENERIC worked, based on the pxe boot > working using the kernel. > > Should I start from scratch? delete the release directory and > do it again? > > -Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Behalf Of > Morris, Roy > Sent: Thursday, November 27, 2008 1:49 PM > To: Marco Peereboom > Cc: misc@openbsd.org > Subject: Re: AAC 4.4 > > > neat, I did the pxe boot, it appears to see the 3Di now according > to the boot message, however hangs forever at .. > > "piixpm0 at pci0 dev 15 function 0 "ServerWorks CSB5" rev 0x93: > SMIiic0 at piixpm0 > > I haven't seen that before? ... neat! > > > > -Original Message- > From: Marco Peereboom [mailto:[EMAIL PROTECTED] > Sent: Thursday, November 27, 2008 11:08 AM > To: Morris, Roy > Cc: misc@openbsd.org > Subject: Re: AAC 4.4 > > > You must have done it wrong. Did you make a release cd? > > Try booting a bsd.rd over pxe with aac enabled. This has to work. > > On Thu, Nov 27, 2008 at 10:20:52AM -0500, Morris, Roy wrote: >> -Original Message- >> From: Marco Peereboom [mailto:[EMAIL PROTECTED] >> Sent: Wednesday, November 26, 2008 6:35 PM >> To: Morris, Roy >> Cc: misc@openbsd.org >> Subject: Re: AAC 4.4 >> >> >> Show me a dmesg. >> >> On Wed, Nov 26, 2008 at 03:21:35PM -0500, Morris, Roy wrote: >>> I wanted to update this for the archives. Enabling these lines in >>> the kernel does NOT allow 4.4 to see the Perc 3DI controller. The >>> 3.5-stable release that was on the box (off net) worked fine. >>> >>> I did a complete release of 4.4 with the lines enabled (uncommented) >>> and even tried UKC, but alas it's a no go. Hope this saves someone >>> some time down the road. >>> >>> Cheers >>> Roy >>> >>> >>> >>> On Tue, Nov 25, 2008 at 02:17:12PM -0500, Morris, Roy wrote: >>>> Hi, I have a need to run the adaptec 3Di, it's not really a >>>> choice at > this >>>> point. I have >>>> been doing some research in the archives and I think I need to >>>> complile > my >>> 4.4 >>>> kernel >>>> with the following two lines uncommented. Any chance someone can >>>> comment > if >>>> this >>>> sounds right? >>>> >>>> #aac* at pci? # Adaptec FSA RAID controllers >>>> #scsibus* at aac? >>>> >>>> >>>> Cheers >>>> Roy >>> >> >> Sure, here you go! As I said I have even tried the UKC> enable aac* >> >> OpenBSD 4.4-stable (RAMDISK_CD) #0: Wed Nov 26 09:23:49 EST 2008 >> > [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/ > RAMDISK_CD >> cpu0: Intel(R) Pentium(R) III CPU - S 1133MHz ("GenuineIntel" 686- >> class) > 1.13 GHz >> cpu0: > FPU, > V86, > DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,F > XSR,SSE >> real mem = 2146926592 (2047MB) >> avail mem = 2069417984 (1973MB) >> mainbus0 at root >> bios0 at mainbus0: AT/286+ BIOS, date 10/08/03, BIOS32 rev. 0 @ >> 0xffe90, > SMBIOS rev. 2.3 @ 0xfb1e0 (47 entries) >> bios0: vendor Dell Computer Corporation version "A11" date 10/08/2003 >> bios0: Dell Computer Corporation PowerEdge 1650 >> acpi0 at bios0: rev 0 >> acpi0: tables DSDT FACP APIC SPCR >> acpiprt0 at acpi0: bus 0 (PCI0) >> acpiprt1 at acpi0: bus 1 (PCI1) >> acpiprt2 at acpi0: bus 2 (ZION) >> acpiprt3 at acpi0: bus 3 (PCI2) >> bios0: ROM list: 0xc/0x8000 0xc8000/0x1000 0xc9000/0x4000! > 0xec000/0x4000! >> cpu0 at mainbus0 >> pci0 at mainbus0 bus 0: configuration mode 1 (no bios) >> pchb0 at pci0 dev 0 function 0 "ServerWorks CNB20HE Host" rev 0x23 >> pci1 at pchb0 bus 1 >> em0 at pci1 dev 2 function 0 "Intel PRO/1000XT (82
Re: General RE-Build Question
Hmmm, thanks. I think I'll take the rm -r route. Sounds like I fracked something up for sure. Cheers Roy -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Stuart Henderson Sent: Thursday, November 27, 2008 4:31 PM To: misc@openbsd.org Subject: Re: General RE-Build Question On 2008-11-27, Morris, Roy <[EMAIL PROTECTED]> wrote: > I have made changes to the GENERIC & RAMDISK_CD kernels > (yes I know, there is a reason) on a stable system. I > have already made a release on this machine once, but > I am assuming based on the faq that the release process > uses files made from the -stable build process. The > question is what or how do I clean to get a fresh start > at it, to ensure the new changes are picked up? .. > > I followed the FAQ .. > # rm -rf /usr/obj/* > # cd /usr/src > # make obj > # cd /usr/src/etc && env DESTDIR=/ make distrib-dirs > # cd /usr/src > # make build > > and got the following error. Any help would be great! You have build files in the src/ tree. Maybe you didn't re-run "make obj" after updating source sometime when directories were changed and then attempted a build. (You should "make obj" between updating src and building). Either rm -r src and checkout again, or clean your tree: "cvs -q up -Pd -I -" should identify the offending files.
Re: AAC 4.4
Thanks Marco, I feel I am very close now! I just need to sort out my build process .. even if I need to start from scratch and I should be good to go. cheers Roy -Original Message- From: Marco Peereboom [mailto:[EMAIL PROTECTED] Sent: Thursday, November 27, 2008 3:13 PM To: Morris, Roy Cc: Morris, Roy; Subject: Re: AAC 4.4 We have diagnosed that issue to a bios bug. You must have missed a step in the make release; it isn't hard to do. On Nov 27, 2008, at 1:11 PM, "Morris, Roy" <[EMAIL PROTECTED]> wrote: > sorry , in answer to my own question, UKC>disable acpi fixes > that problem .. I boot right up > > So I guess the real question becomes why didn't my cd work? I > enabled aac in both GENERIC and RAMDISK_CD and did a release .. > It's fairly obvious the GENERIC worked, based on the pxe boot > working using the kernel. > > Should I start from scratch? delete the release directory and > do it again? > > -Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Behalf Of > Morris, Roy > Sent: Thursday, November 27, 2008 1:49 PM > To: Marco Peereboom > Cc: misc@openbsd.org > Subject: Re: AAC 4.4 > > > neat, I did the pxe boot, it appears to see the 3Di now according > to the boot message, however hangs forever at .. > > "piixpm0 at pci0 dev 15 function 0 "ServerWorks CSB5" rev 0x93: > SMIiic0 at piixpm0 > > I haven't seen that before? ... neat! > > > > -Original Message- > From: Marco Peereboom [mailto:[EMAIL PROTECTED] > Sent: Thursday, November 27, 2008 11:08 AM > To: Morris, Roy > Cc: misc@openbsd.org > Subject: Re: AAC 4.4 > > > You must have done it wrong. Did you make a release cd? > > Try booting a bsd.rd over pxe with aac enabled. This has to work. > > On Thu, Nov 27, 2008 at 10:20:52AM -0500, Morris, Roy wrote: >> -Original Message- >> From: Marco Peereboom [mailto:[EMAIL PROTECTED] >> Sent: Wednesday, November 26, 2008 6:35 PM >> To: Morris, Roy >> Cc: misc@openbsd.org >> Subject: Re: AAC 4.4 >> >> >> Show me a dmesg. >> >> On Wed, Nov 26, 2008 at 03:21:35PM -0500, Morris, Roy wrote: >>> I wanted to update this for the archives. Enabling these lines in >>> the kernel does NOT allow 4.4 to see the Perc 3DI controller. The >>> 3.5-stable release that was on the box (off net) worked fine. >>> >>> I did a complete release of 4.4 with the lines enabled (uncommented) >>> and even tried UKC, but alas it's a no go. Hope this saves someone >>> some time down the road. >>> >>> Cheers >>> Roy >>> >>> >>> >>> On Tue, Nov 25, 2008 at 02:17:12PM -0500, Morris, Roy wrote: >>>> Hi, I have a need to run the adaptec 3Di, it's not really a >>>> choice at > this >>>> point. I have >>>> been doing some research in the archives and I think I need to >>>> complile > my >>> 4.4 >>>> kernel >>>> with the following two lines uncommented. Any chance someone can >>>> comment > if >>>> this >>>> sounds right? >>>> >>>> #aac* at pci? # Adaptec FSA RAID controllers >>>> #scsibus* at aac? >>>> >>>> >>>> Cheers >>>> Roy >>> >> >> Sure, here you go! As I said I have even tried the UKC> enable aac* >> >> OpenBSD 4.4-stable (RAMDISK_CD) #0: Wed Nov 26 09:23:49 EST 2008 >> > [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/ > RAMDISK_CD >> cpu0: Intel(R) Pentium(R) III CPU - S 1133MHz ("GenuineIntel" 686- >> class) > 1.13 GHz >> cpu0: > FPU, > V86, > DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,F > XSR,SSE >> real mem = 2146926592 (2047MB) >> avail mem = 2069417984 (1973MB) >> mainbus0 at root >> bios0 at mainbus0: AT/286+ BIOS, date 10/08/03, BIOS32 rev. 0 @ >> 0xffe90, > SMBIOS rev. 2.3 @ 0xfb1e0 (47 entries) >> bios0: vendor Dell Computer Corporation version "A11" date 10/08/2003 >> bios0: Dell Computer Corporation PowerEdge 1650 >> acpi0 at bios0: rev 0 >> acpi0: tables DSDT FACP APIC SPCR >> acpiprt0 at acpi0: bus 0 (PCI0) >> acpiprt1 at acpi0: bus 1 (PCI1) >> acpiprt2 at acpi0: bus 2 (ZION) >> acpiprt3 at acpi0: bus 3 (PCI2) >> bios0: ROM list: 0xc/0x8000 0xc8000/0x1000 0xc9000/0x4000! > 0xec000/0x4000! >> cpu0 at mainbus0 >> pci0 at mainbus0 bus 0: configuration mode 1 (no bios) >> pchb0 at pci0 dev 0 function 0 "Se
General RE-Build Question
I have made changes to the GENERIC & RAMDISK_CD kernels (yes I know, there is a reason) on a stable system. I have already made a release on this machine once, but I am assuming based on the faq that the release process uses files made from the -stable build process. The question is what or how do I clean to get a fresh start at it, to ensure the new changes are picked up? .. I followed the FAQ .. # rm -rf /usr/obj/* # cd /usr/src # make obj # cd /usr/src/etc && env DESTDIR=/ make distrib-dirs # cd /usr/src # make build and got the following error. Any help would be great! Configuring in opcodes creating cache ./config.cache checking for Cygwin environment... no checking for mingw32 environment... no checking host system type... i386-unknown-openbsd4.4 checking target system type... i386-unknown-openbsd4.4 checking build system type... i386-unknown-openbsd4.4 checking for strerror in -lcposix... no checking for a BSD compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking whether make sets ${MAKE}... yes configure: error: source directory already configured; run make distclean there first *** Error code 1 Stop in /usr/src/gnu/usr.bin/binutils/obj (line 17948 of Makefile). *** Error code 1 Stop in /usr/src/gnu/usr.bin/binutils (line 102 of /usr/src/gnu/usr.bin/binutils/Makefile.bsd-wrapper). *** Error code 1 Stop in /usr/src/include (line 82 of Makefile). *** Error code 1 Stop in /usr/src (line 73 of Makefile).
Re: AAC 4.4
sorry , in answer to my own question, UKC>disable acpi fixes that problem .. I boot right up So I guess the real question becomes why didn't my cd work? I enabled aac in both GENERIC and RAMDISK_CD and did a release .. It's fairly obvious the GENERIC worked, based on the pxe boot working using the kernel. Should I start from scratch? delete the release directory and do it again? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Morris, Roy Sent: Thursday, November 27, 2008 1:49 PM To: Marco Peereboom Cc: misc@openbsd.org Subject: Re: AAC 4.4 neat, I did the pxe boot, it appears to see the 3Di now according to the boot message, however hangs forever at .. "piixpm0 at pci0 dev 15 function 0 "ServerWorks CSB5" rev 0x93: SMIiic0 at piixpm0 I haven't seen that before? ... neat! -Original Message- From: Marco Peereboom [mailto:[EMAIL PROTECTED] Sent: Thursday, November 27, 2008 11:08 AM To: Morris, Roy Cc: misc@openbsd.org Subject: Re: AAC 4.4 You must have done it wrong. Did you make a release cd? Try booting a bsd.rd over pxe with aac enabled. This has to work. On Thu, Nov 27, 2008 at 10:20:52AM -0500, Morris, Roy wrote: > -Original Message- > From: Marco Peereboom [mailto:[EMAIL PROTECTED] > Sent: Wednesday, November 26, 2008 6:35 PM > To: Morris, Roy > Cc: misc@openbsd.org > Subject: Re: AAC 4.4 > > > Show me a dmesg. > > On Wed, Nov 26, 2008 at 03:21:35PM -0500, Morris, Roy wrote: > > I wanted to update this for the archives. Enabling these lines in > > the kernel does NOT allow 4.4 to see the Perc 3DI controller. The > > 3.5-stable release that was on the box (off net) worked fine. > > > > I did a complete release of 4.4 with the lines enabled (uncommented) > > and even tried UKC, but alas it's a no go. Hope this saves someone > > some time down the road. > > > > Cheers > > Roy > > > > > > > > On Tue, Nov 25, 2008 at 02:17:12PM -0500, Morris, Roy wrote: > > > Hi, I have a need to run the adaptec 3Di, it's not really a choice at this > > > point. I have > > > been doing some research in the archives and I think I need to complile my > > 4.4 > > > kernel > > > with the following two lines uncommented. Any chance someone can comment if > > > this > > > sounds right? > > > > > > #aac* at pci? # Adaptec FSA RAID controllers > > > #scsibus* at aac? > > > > > > > > > Cheers > > > Roy > > > > Sure, here you go! As I said I have even tried the UKC> enable aac* > > OpenBSD 4.4-stable (RAMDISK_CD) #0: Wed Nov 26 09:23:49 EST 2008 > [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/RAMDISK_CD > cpu0: Intel(R) Pentium(R) III CPU - S 1133MHz ("GenuineIntel" 686-class) 1.13 GHz > cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,F XSR,SSE > real mem = 2146926592 (2047MB) > avail mem = 2069417984 (1973MB) > mainbus0 at root > bios0 at mainbus0: AT/286+ BIOS, date 10/08/03, BIOS32 rev. 0 @ 0xffe90, SMBIOS rev. 2.3 @ 0xfb1e0 (47 entries) > bios0: vendor Dell Computer Corporation version "A11" date 10/08/2003 > bios0: Dell Computer Corporation PowerEdge 1650 > acpi0 at bios0: rev 0 > acpi0: tables DSDT FACP APIC SPCR > acpiprt0 at acpi0: bus 0 (PCI0) > acpiprt1 at acpi0: bus 1 (PCI1) > acpiprt2 at acpi0: bus 2 (ZION) > acpiprt3 at acpi0: bus 3 (PCI2) > bios0: ROM list: 0xc/0x8000 0xc8000/0x1000 0xc9000/0x4000! 0xec000/0x4000! > cpu0 at mainbus0 > pci0 at mainbus0 bus 0: configuration mode 1 (no bios) > pchb0 at pci0 dev 0 function 0 "ServerWorks CNB20HE Host" rev 0x23 > pci1 at pchb0 bus 1 > em0 at pci1 dev 2 function 0 "Intel PRO/1000XT (82544EI)" rev 0x02: irq 7, address 00:0f:1f:69:cc:7e > em1 at pci1 dev 4 function 0 "Intel PRO/1000XT (82544EI)" rev 0x02: irq 5, address 00:0f:1f:69:cc:7f > ppb0 at pci1 dev 8 function 0 "Intel 80303 IOP" rev 0x01 > pci2 at ppb0 bus 2 > "Adaptec AIC-7899F" rev 0x01 at pci2 dev 6 function 0 not configured > "Adaptec AIC-7899F" rev 0x01 at pci2 dev 6 function 1 not configured > "Dell PERC 3/Di" rev 0x01 at pci1 dev 8 function 1 not configured > pchb1 at pci0 dev 0 function 1 "ServerWorks CNB20HE Host" rev 0x01 > pchb2 at pci0 dev 0 function 2 "ServerWorks CNB20HE Host" rev 0x01 > pchb3 at pci0 dev 0 function 3 "ServerWorks CNB20HE Host" rev 0x01 > pci3 at pchb3 bus 3 > vga1 at pci0 dev 12 function 0 "ATI Rage XL" rev 0x27 > wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) > pchb4 at pci0 dev 15 function 0 "ServerWorks
Re: AAC 4.4
neat, I did the pxe boot, it appears to see the 3Di now according to the boot message, however hangs forever at .. "piixpm0 at pci0 dev 15 function 0 "ServerWorks CSB5" rev 0x93: SMIiic0 at piixpm0 I haven't seen that before? ... neat! -Original Message- From: Marco Peereboom [mailto:[EMAIL PROTECTED] Sent: Thursday, November 27, 2008 11:08 AM To: Morris, Roy Cc: misc@openbsd.org Subject: Re: AAC 4.4 You must have done it wrong. Did you make a release cd? Try booting a bsd.rd over pxe with aac enabled. This has to work. On Thu, Nov 27, 2008 at 10:20:52AM -0500, Morris, Roy wrote: > -Original Message- > From: Marco Peereboom [mailto:[EMAIL PROTECTED] > Sent: Wednesday, November 26, 2008 6:35 PM > To: Morris, Roy > Cc: misc@openbsd.org > Subject: Re: AAC 4.4 > > > Show me a dmesg. > > On Wed, Nov 26, 2008 at 03:21:35PM -0500, Morris, Roy wrote: > > I wanted to update this for the archives. Enabling these lines in > > the kernel does NOT allow 4.4 to see the Perc 3DI controller. The > > 3.5-stable release that was on the box (off net) worked fine. > > > > I did a complete release of 4.4 with the lines enabled (uncommented) > > and even tried UKC, but alas it's a no go. Hope this saves someone > > some time down the road. > > > > Cheers > > Roy > > > > > > > > On Tue, Nov 25, 2008 at 02:17:12PM -0500, Morris, Roy wrote: > > > Hi, I have a need to run the adaptec 3Di, it's not really a choice at this > > > point. I have > > > been doing some research in the archives and I think I need to complile my > > 4.4 > > > kernel > > > with the following two lines uncommented. Any chance someone can comment if > > > this > > > sounds right? > > > > > > #aac* at pci? # Adaptec FSA RAID controllers > > > #scsibus* at aac? > > > > > > > > > Cheers > > > Roy > > > > Sure, here you go! As I said I have even tried the UKC> enable aac* > > OpenBSD 4.4-stable (RAMDISK_CD) #0: Wed Nov 26 09:23:49 EST 2008 > [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/RAMDISK_CD > cpu0: Intel(R) Pentium(R) III CPU - S 1133MHz ("GenuineIntel" 686-class) 1.13 GHz > cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,F XSR,SSE > real mem = 2146926592 (2047MB) > avail mem = 2069417984 (1973MB) > mainbus0 at root > bios0 at mainbus0: AT/286+ BIOS, date 10/08/03, BIOS32 rev. 0 @ 0xffe90, SMBIOS rev. 2.3 @ 0xfb1e0 (47 entries) > bios0: vendor Dell Computer Corporation version "A11" date 10/08/2003 > bios0: Dell Computer Corporation PowerEdge 1650 > acpi0 at bios0: rev 0 > acpi0: tables DSDT FACP APIC SPCR > acpiprt0 at acpi0: bus 0 (PCI0) > acpiprt1 at acpi0: bus 1 (PCI1) > acpiprt2 at acpi0: bus 2 (ZION) > acpiprt3 at acpi0: bus 3 (PCI2) > bios0: ROM list: 0xc/0x8000 0xc8000/0x1000 0xc9000/0x4000! 0xec000/0x4000! > cpu0 at mainbus0 > pci0 at mainbus0 bus 0: configuration mode 1 (no bios) > pchb0 at pci0 dev 0 function 0 "ServerWorks CNB20HE Host" rev 0x23 > pci1 at pchb0 bus 1 > em0 at pci1 dev 2 function 0 "Intel PRO/1000XT (82544EI)" rev 0x02: irq 7, address 00:0f:1f:69:cc:7e > em1 at pci1 dev 4 function 0 "Intel PRO/1000XT (82544EI)" rev 0x02: irq 5, address 00:0f:1f:69:cc:7f > ppb0 at pci1 dev 8 function 0 "Intel 80303 IOP" rev 0x01 > pci2 at ppb0 bus 2 > "Adaptec AIC-7899F" rev 0x01 at pci2 dev 6 function 0 not configured > "Adaptec AIC-7899F" rev 0x01 at pci2 dev 6 function 1 not configured > "Dell PERC 3/Di" rev 0x01 at pci1 dev 8 function 1 not configured > pchb1 at pci0 dev 0 function 1 "ServerWorks CNB20HE Host" rev 0x01 > pchb2 at pci0 dev 0 function 2 "ServerWorks CNB20HE Host" rev 0x01 > pchb3 at pci0 dev 0 function 3 "ServerWorks CNB20HE Host" rev 0x01 > pci3 at pchb3 bus 3 > vga1 at pci0 dev 12 function 0 "ATI Rage XL" rev 0x27 > wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) > pchb4 at pci0 dev 15 function 0 "ServerWorks CSB5" rev 0x93 > pciide0 at pci0 dev 15 function 1 "ServerWorks CSB5 IDE" rev 0x93: DMA > atapiscsi0 at pciide0 channel 0 drive 0 > scsibus0 at atapiscsi0: 2 targets, initiator 7 > cd0 at scsibus0 targ 0 lun 0: ATAPI 5/cdrom removable > cd0(pciide0:0:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 2 > ohci0 at pci0 dev 15 function 2 "ServerWorks OSB4/CSB5 USB" rev 0x05: irq 11, version 1.0, legacy support > pcib0 at pci0 dev 15 function 3 "ServerWorks CSB5 LPC" rev 0x00 > usb0 at ohci0: USB revision 1.0 > uhub0 at usb0 "ServerWorks OHCI root hub" rev 1.00/1.00 addr 1 > isa0 at pcib0 > isadma0 at isa0 > com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo > pckbc0 at isa0 port 0x60/5 > pckbd0 at pckbc0 (kbd slot) > pckbc0: using irq 1 for kbd slot > wskbd0 at pckbd0: console keyboard, using wsdisplay0 > npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 > fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 > fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec > biomask ff4d netmask ffed ttymask > rd0: fixed, 3800 blocks > softraid0 at root > root on rd0a swap on rd0b dump on rd0b
Re: AAC 4.4
I will give that a go right now! -Original Message- From: Marco Peereboom [mailto:[EMAIL PROTECTED] Sent: Thursday, November 27, 2008 11:08 AM To: Morris, Roy Cc: misc@openbsd.org Subject: Re: AAC 4.4 You must have done it wrong. Did you make a release cd? Try booting a bsd.rd over pxe with aac enabled. This has to work. On Thu, Nov 27, 2008 at 10:20:52AM -0500, Morris, Roy wrote: > -Original Message- > From: Marco Peereboom [mailto:[EMAIL PROTECTED] > Sent: Wednesday, November 26, 2008 6:35 PM > To: Morris, Roy > Cc: misc@openbsd.org > Subject: Re: AAC 4.4 > > > Show me a dmesg. > > On Wed, Nov 26, 2008 at 03:21:35PM -0500, Morris, Roy wrote: > > I wanted to update this for the archives. Enabling these lines in > > the kernel does NOT allow 4.4 to see the Perc 3DI controller. The > > 3.5-stable release that was on the box (off net) worked fine. > > > > I did a complete release of 4.4 with the lines enabled (uncommented) > > and even tried UKC, but alas it's a no go. Hope this saves someone > > some time down the road. > > > > Cheers > > Roy > > > > > > > > On Tue, Nov 25, 2008 at 02:17:12PM -0500, Morris, Roy wrote: > > > Hi, I have a need to run the adaptec 3Di, it's not really a choice at this > > > point. I have > > > been doing some research in the archives and I think I need to complile my > > 4.4 > > > kernel > > > with the following two lines uncommented. Any chance someone can comment if > > > this > > > sounds right? > > > > > > #aac* at pci? # Adaptec FSA RAID controllers > > > #scsibus* at aac? > > > > > > > > > Cheers > > > Roy > > > > Sure, here you go! As I said I have even tried the UKC> enable aac* > > OpenBSD 4.4-stable (RAMDISK_CD) #0: Wed Nov 26 09:23:49 EST 2008 > [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/RAMDISK_CD > cpu0: Intel(R) Pentium(R) III CPU - S 1133MHz ("GenuineIntel" 686-class) 1.13 GHz > cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,F XSR,SSE > real mem = 2146926592 (2047MB) > avail mem = 2069417984 (1973MB) > mainbus0 at root > bios0 at mainbus0: AT/286+ BIOS, date 10/08/03, BIOS32 rev. 0 @ 0xffe90, SMBIOS rev. 2.3 @ 0xfb1e0 (47 entries) > bios0: vendor Dell Computer Corporation version "A11" date 10/08/2003 > bios0: Dell Computer Corporation PowerEdge 1650 > acpi0 at bios0: rev 0 > acpi0: tables DSDT FACP APIC SPCR > acpiprt0 at acpi0: bus 0 (PCI0) > acpiprt1 at acpi0: bus 1 (PCI1) > acpiprt2 at acpi0: bus 2 (ZION) > acpiprt3 at acpi0: bus 3 (PCI2) > bios0: ROM list: 0xc/0x8000 0xc8000/0x1000 0xc9000/0x4000! 0xec000/0x4000! > cpu0 at mainbus0 > pci0 at mainbus0 bus 0: configuration mode 1 (no bios) > pchb0 at pci0 dev 0 function 0 "ServerWorks CNB20HE Host" rev 0x23 > pci1 at pchb0 bus 1 > em0 at pci1 dev 2 function 0 "Intel PRO/1000XT (82544EI)" rev 0x02: irq 7, address 00:0f:1f:69:cc:7e > em1 at pci1 dev 4 function 0 "Intel PRO/1000XT (82544EI)" rev 0x02: irq 5, address 00:0f:1f:69:cc:7f > ppb0 at pci1 dev 8 function 0 "Intel 80303 IOP" rev 0x01 > pci2 at ppb0 bus 2 > "Adaptec AIC-7899F" rev 0x01 at pci2 dev 6 function 0 not configured > "Adaptec AIC-7899F" rev 0x01 at pci2 dev 6 function 1 not configured > "Dell PERC 3/Di" rev 0x01 at pci1 dev 8 function 1 not configured > pchb1 at pci0 dev 0 function 1 "ServerWorks CNB20HE Host" rev 0x01 > pchb2 at pci0 dev 0 function 2 "ServerWorks CNB20HE Host" rev 0x01 > pchb3 at pci0 dev 0 function 3 "ServerWorks CNB20HE Host" rev 0x01 > pci3 at pchb3 bus 3 > vga1 at pci0 dev 12 function 0 "ATI Rage XL" rev 0x27 > wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) > pchb4 at pci0 dev 15 function 0 "ServerWorks CSB5" rev 0x93 > pciide0 at pci0 dev 15 function 1 "ServerWorks CSB5 IDE" rev 0x93: DMA > atapiscsi0 at pciide0 channel 0 drive 0 > scsibus0 at atapiscsi0: 2 targets, initiator 7 > cd0 at scsibus0 targ 0 lun 0: ATAPI 5/cdrom removable > cd0(pciide0:0:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 2 > ohci0 at pci0 dev 15 function 2 "ServerWorks OSB4/CSB5 USB" rev 0x05: irq 11, version 1.0, legacy support > pcib0 at pci0 dev 15 function 3 "ServerWorks CSB5 LPC" rev 0x00 > usb0 at ohci0: USB revision 1.0 > uhub0 at usb0 "ServerWorks OHCI root hub" rev 1.00/1.00 addr 1 > isa0 at pcib0 > isadma0 at isa0 > com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo > pckbc0 at isa0 port 0x60/5 > pckbd0 at pckbc0 (kbd slot) > pckbc0: using irq 1 for kbd slot > wskbd0 at pckbd0: console keyboard, using wsdisplay0 > npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 > fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 > fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec > biomask ff4d netmask ffed ttymask > rd0: fixed, 3800 blocks > softraid0 at root > root on rd0a swap on rd0b dump on rd0b
Re: AAC 4.4
-Original Message- From: Marco Peereboom [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 26, 2008 6:35 PM To: Morris, Roy Cc: misc@openbsd.org Subject: Re: AAC 4.4 Show me a dmesg. On Wed, Nov 26, 2008 at 03:21:35PM -0500, Morris, Roy wrote: > I wanted to update this for the archives. Enabling these lines in > the kernel does NOT allow 4.4 to see the Perc 3DI controller. The > 3.5-stable release that was on the box (off net) worked fine. > > I did a complete release of 4.4 with the lines enabled (uncommented) > and even tried UKC, but alas it's a no go. Hope this saves someone > some time down the road. > > Cheers > Roy > > > > On Tue, Nov 25, 2008 at 02:17:12PM -0500, Morris, Roy wrote: > > Hi, I have a need to run the adaptec 3Di, it's not really a choice at this > > point. I have > > been doing some research in the archives and I think I need to complile my > 4.4 > > kernel > > with the following two lines uncommented. Any chance someone can comment if > > this > > sounds right? > > > > #aac* at pci? # Adaptec FSA RAID controllers > > #scsibus* at aac? > > > > > > Cheers > > Roy > Sure, here you go! As I said I have even tried the UKC> enable aac* OpenBSD 4.4-stable (RAMDISK_CD) #0: Wed Nov 26 09:23:49 EST 2008 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/RAMDISK_CD cpu0: Intel(R) Pentium(R) III CPU - S 1133MHz ("GenuineIntel" 686-class) 1.13 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,F XSR,SSE real mem = 2146926592 (2047MB) avail mem = 2069417984 (1973MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 10/08/03, BIOS32 rev. 0 @ 0xffe90, SMBIOS rev. 2.3 @ 0xfb1e0 (47 entries) bios0: vendor Dell Computer Corporation version "A11" date 10/08/2003 bios0: Dell Computer Corporation PowerEdge 1650 acpi0 at bios0: rev 0 acpi0: tables DSDT FACP APIC SPCR acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (PCI1) acpiprt2 at acpi0: bus 2 (ZION) acpiprt3 at acpi0: bus 3 (PCI2) bios0: ROM list: 0xc/0x8000 0xc8000/0x1000 0xc9000/0x4000! 0xec000/0x4000! cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 "ServerWorks CNB20HE Host" rev 0x23 pci1 at pchb0 bus 1 em0 at pci1 dev 2 function 0 "Intel PRO/1000XT (82544EI)" rev 0x02: irq 7, address 00:0f:1f:69:cc:7e em1 at pci1 dev 4 function 0 "Intel PRO/1000XT (82544EI)" rev 0x02: irq 5, address 00:0f:1f:69:cc:7f ppb0 at pci1 dev 8 function 0 "Intel 80303 IOP" rev 0x01 pci2 at ppb0 bus 2 "Adaptec AIC-7899F" rev 0x01 at pci2 dev 6 function 0 not configured "Adaptec AIC-7899F" rev 0x01 at pci2 dev 6 function 1 not configured "Dell PERC 3/Di" rev 0x01 at pci1 dev 8 function 1 not configured pchb1 at pci0 dev 0 function 1 "ServerWorks CNB20HE Host" rev 0x01 pchb2 at pci0 dev 0 function 2 "ServerWorks CNB20HE Host" rev 0x01 pchb3 at pci0 dev 0 function 3 "ServerWorks CNB20HE Host" rev 0x01 pci3 at pchb3 bus 3 vga1 at pci0 dev 12 function 0 "ATI Rage XL" rev 0x27 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) pchb4 at pci0 dev 15 function 0 "ServerWorks CSB5" rev 0x93 pciide0 at pci0 dev 15 function 1 "ServerWorks CSB5 IDE" rev 0x93: DMA atapiscsi0 at pciide0 channel 0 drive 0 scsibus0 at atapiscsi0: 2 targets, initiator 7 cd0 at scsibus0 targ 0 lun 0: ATAPI 5/cdrom removable cd0(pciide0:0:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 2 ohci0 at pci0 dev 15 function 2 "ServerWorks OSB4/CSB5 USB" rev 0x05: irq 11, version 1.0, legacy support pcib0 at pci0 dev 15 function 3 "ServerWorks CSB5 LPC" rev 0x00 usb0 at ohci0: USB revision 1.0 uhub0 at usb0 "ServerWorks OHCI root hub" rev 1.00/1.00 addr 1 isa0 at pcib0 isadma0 at isa0 com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec biomask ff4d netmask ffed ttymask rd0: fixed, 3800 blocks softraid0 at root root on rd0a swap on rd0b dump on rd0b
AAC 4.4
I wanted to update this for the archives. Enabling these lines in the kernel does NOT allow 4.4 to see the Perc 3DI controller. The 3.5-stable release that was on the box (off net) worked fine. I did a complete release of 4.4 with the lines enabled (uncommented) and even tried UKC, but alas it's a no go. Hope this saves someone some time down the road. Cheers Roy On Tue, Nov 25, 2008 at 02:17:12PM -0500, Morris, Roy wrote: > Hi, I have a need to run the adaptec 3Di, it's not really a choice at this > point. I have > been doing some research in the archives and I think I need to complile my 4.4 > kernel > with the following two lines uncommented. Any chance someone can comment if > this > sounds right? > > #aac* at pci? # Adaptec FSA RAID controllers > #scsibus* at aac? > > > Cheers > Roy
AAC 4.4
Hi, I have a need to run the adaptec 3Di, it's not really a choice at this point. I have been doing some research in the archives and I think I need to complile my 4.4 kernel with the following two lines uncommented. Any chance someone can comment if this sounds right? #aac* at pci? # Adaptec FSA RAID controllers #scsibus* at aac? Cheers Roy
Re: Missing security announcements
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Janne Johansson Sent: Thursday, November 13, 2008 10:14 AM To: Misc OpenBSD Subject: Re: Missing security announcements why not just get it yourself if you're worried about it? just fire a crontab entry and move on. lynx -dump openbsd.org/errata44.html |mail -s "Daily Security" [EMAIL PROTECTED]
Re: 4.2-stable & Postgres
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Stuart Henderson Sent: Thursday, August 28, 2008 10:58 AM To: misc@openbsd.org Subject: Re: 4.2-stable & Postgres On 2008-08-28, Morris, Roy <[EMAIL PROTECTED]> wrote: > Hi, I am hoping someone here has run into this before, I didn't see anything > worth while > (or that I understood) via a google search. > I guess specs first. I have running OpenBSD 4.2-stable with postgres 8.2.4. >speaking from experience: don't forget to dumpall before you >upgrade this machine. I like to add reminders about things like >that to /etc/motd in case I have a spare half-hour in the future >and think it might be a good idea to upgrade the machine, at which >point I've usually forgotten about these things... Thanks, good idea for sure! > Aug 12 20:46:29 logdb postgres[30182]: [1-1] FATAL: could not create shared > memory segment: Invalid argument > Aug 12 20:46:29 logdb postgres[30182]: [1-2] DETAIL: Failed system call was > shmget(key=4225001, size=74702848, 03600). >>the 72MB requested here doesn't fit in the 32MB you get by default. >>/usr/local/share/doc/postgresql/README.OpenBSD tells you a bit about >>the kern.shminfo.shmmax sysctl... Yep, just read this again and I will try changing the value (now 50) to kern.shminfo.shmmax=83886080 and see how that goes. Thanks again.
4.2-stable & Postgres
Hi, I am hoping someone here has run into this before, I didn't see anything worth while (or that I understood) via a google search. I guess specs first. I have running OpenBSD 4.2-stable with postgres 8.2.4. The database itself runs fine, but when I go to run a 'full vaccum' to reclaim space I get the following error, which appears to require me to rebuild the kernel. I am looking for some input on this before I break something. Thanks, here's the error from the logs below. WARNING: relation "pg_toast.pg_toast_17723" contains more than "max_fsm_pages" pages with useful free space HINT: Consider compacting this relation or increasing the configuration parameter "max_fsm_pages". INFO: free space map contains 181258 pages in 12 relations DETAIL: A total of 179200 page slots are in use (including overhead). 5618000 page slots are required to track all free space. Current limits are: 179200 page slots, 1000 relations, using 1115 kB. NOTICE: number of page slots needed (5618000) exceeds max_fsm_pages (179200) HINT: Consider increasing the configuration parameter "max_fsm_pages" to a value over 5618000. Aug 12 20:46:26 logdb savecore: no core dump Aug 12 20:46:29 logdb postgres[30182]: [1-1] FATAL: could not create shared memory segment: Invalid argument Aug 12 20:46:29 logdb postgres[30182]: [1-2] DETAIL: Failed system call was shmget(key=4225001, size=74702848, 03600). Aug 12 20:46:29 logdb postgres[30182]: [1-3] HINT: This error usually means that PostgreSQL's request for a shared memory segment exceeded your kernel's SHMMAX parameter. Aug 12 20:46:29 logdb postgres[30182]: [1-4] You can either reduce the request size or reconfigure the kernel with larger SHMMAX. To reduce the request size (currently Aug 12 20:46:29 logdb postgres[30182]: [1-5] 74702848 bytes), reduce PostgreSQL's shared_buffers parameter (currently 4096) and/or its max_connections parameter (currently Aug 12 20:46:29 logdb postgres[30182]: [1-6] 200). Aug 12 20:46:29 logdb postgres[30182]: [1-7]If the request size is already small, it's possible that it is less than your kernel's SHMMIN parameter, in which case raising Aug 12 20:46:29 logdb postgres[30182]: [1-8] the request size or reconfiguring SHMMIN is called for. Aug 12 20:46:29 logdb postgres[30182]: [1-9]The PostgreSQL documentation contains more information about shared memory configuration.
Monitor Open Files
I am working with a postgres database on openbsd 4.2 -stable. I was wondering what the most correct method would be to monitor the number of open files? I assume (perhaps incorrectly) that the 'openfiles-cur=768' entry that I created for the postgres login class might be identifiable roughly with the command fstat -u _postgresql |wc -l . Is there any chance anyone can tell me if my assumptions are correct? Thanks Roy
32G SSD - Poor Performance on 4.3
I have been reading around the archives a bit and found a few references to using 4.3 to get the full performance out of a Transcend SSD but my results are showing that the drive is slower on all fronts. I am wondering if anyone has tried these tests and what the results might have been? Anyone know if there is a magic switch I can throw to make the OS use this type of drive at full speed? Thanks Roy Drive: Transcend TS32GSSD25-M (32G) OS - 4.3 snapshot from 04/28/2008 PE 350 - Regular HD (Write Time) roy:/home/rmorris$ dd if=/dev/zero of=testfile.blk bs=65536 count=16384 16384+0 records in 16384+0 records out 1073741824 bytes transferred in 55.392 secs (19384111 bytes/sec) PE 350 - SSD HD (Write Time) # dd if=/dev/zero of=testfile.blk bs=65536 count=16384 16384+0 records in 16384+0 records out 1073741824 bytes transferred in 176.273 secs (6091344 bytes/sec) PE 350 - Regular HD (Read time) roy:/home/rmorris$ dd if=testfile.blk of=/dev/null bs=65536 count=16384 16384+0 records in 16384+0 records out 1073741824 bytes transferred in 40.165 secs (26732730 bytes/sec) PE 350 - SSD HD (Read Time) # dd if=testfile.blk of=/dev/null bs=65536 count=16384 16384+0 records in 16384+0 records out 1073741824 bytes transferred in 50.842 secs (21118975 bytes/sec)
Re: Sendmail OpenBSD performance
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Rich Kulawiec Sent: Thursday, April 24, 2008 6:57 AM To: misc@openbsd.org Subject: Re: Sendmail OpenBSD performance On Wed, Apr 23, 2008 at 11:18:34AM -0400, Morris, Roy wrote: > I know this is not exactly a OpenBSD question but I am wondering if anyone > can give me a sense of the performance/limitations of sendmail? Basically > I have a machine that sends out 20,000 mails a day and once and a while > the application sending emails for delivery complains that it has to > wait for sendmail. I go and check the sendmail machine and it's hardly > even breathing hard. Almost no cpu usage, memory fine blah blah .. > > I am not convinced this is a problem with sendmail, just looking for > some feedback from anyone doing volume email on openbsd. >>Many MTA performance problems of this nature are not the related to >>the MTA per se, but to DNS. So much so, that it's become nearly a >>SOP to thoroughly check DNS function and performance before looking >>at the MTA. Yes, thanks I have stats running on the DNS server and dedicated bind server on each mail machine, which I would have thought plenty of horse power. >>That may or may not be your problem, but it's certainly a good place >>to start looking. Should it turn out to be the case, one simple >>mitigating strategy is to enable BIND on the sendmail machine >>(in recursive, caching mode but answering local queries only) and >>set the resolver on it to use that instance of BIND. If you're >>sending to the domains on a regular basis, the cache will become >>and remain populated with most of the DNS information required, >>which should boost query response. >>---Rsk Thanks for your input, Roy
Sendmail OpenBSD performance
I know this is not exactly a OpenBSD question but I am wondering if anyone can give me a sense of the performance/limitations of sendmail? Basically I have a machine that sends out 20,000 mails a day and once and a while the application sending emails for delivery complains that it has to wait for sendmail. I go and check the sendmail machine and it's hardly even breathing hard. Almost no cpu usage, memory fine blah blah .. I am not convinced this is a problem with sendmail, just looking for some feedback from anyone doing volume email on openbsd. cheers Roy