Re: Pulled out an old song..

2006-06-16 Thread Michael Coulter
On Fri, Jun 16, 2006 at 12:01:35PM +0900, Jason Stubbs wrote:
 Unless the quality of the CD has deterioated, where does the 
 random element come from?

http://www.stereophile.com/features/827/

If you start reading about the low-level details of C/DVDs and
you don't have a lot of faith in math, you'll be scared to death
you ever put data on an optical disc.



Re: Pulled out an old song..

2006-06-16 Thread vladas

On 16/06/06, Michael Coulter [EMAIL PROTECTED] wrote:

On Fri, Jun 16, 2006 at 12:01:35PM +0900, Jason Stubbs wrote:
 Unless the quality of the CD has deterioated, where does the
 random element come from?

http://www.stereophile.com/features/827/

If you start reading about the low-level details of C/DVDs and
you don't have a lot of faith in math, you'll be scared to death
you ever put data on an optical disc.


Jason,

Thank you for the link!



Re: NFS Slow writes

2006-06-16 Thread Otto Moerbeek
On Thu, 15 Jun 2006, Bob Bostwick (Lists) wrote:

 I've narrowed the problem down.  I'm running an FTP server (vsftpd)
 who's users home dir's are on an nfs share.  If I run vstpd without
 mounting the nfs share (and create a user with a valid home dir) I get
 21MB/s uploads.  If I copy a file from the OBSD box to a dir on the NFS
 mount, I get 8MB/s.  However if I ftp to the nfs share I get 700KB/s
 uploads.  Downloads are fast either way, it's just the writes that seem
 really slow.  Vsftpd is starting through inetd (but I tried standalone
 and it made no difference.)  Is there some sort of incompatibility in
 doing it this way?
 
 Any thoughts would be greatly appreciated 

First: you do not tell which version of OpenBSD you are using. Recent
version DO have better NFS write performance. Look at the release
notes of 3.8. 

Since local copies are much faster than the ftp'ed data, I would
suspect that vsftd is doing writes in such a way that it really
stresses nfs. You could try using another ftp server and see if the
performance gets better. If that's the case, you know for sure where
to look further. 

-Otto



Missing ipmi sensors on current

2006-06-16 Thread Nicholas Young
I have upgraded the kernel but not userland to 3.9-current as of a few
hours ago. I do plan to update userland, I just wanted to check that the
kernel would boot on the machine before I do.

Bob Beck suggested testing current as it has fixes for ami/bge problems
we have been experiencing.
See http://marc.theaimsgroup.com/?l=openbsd-miscm=115024220026846w=2
http://cvs.openbsd.org/cgi-bin/query-pr-wrapper?full=yesnumbers=5144

After rebooting with the new kernel the ipmi card which is a Tyan Taro
M3289 is no longer being configured. This was working on 3.9, dmesg is
available in linked post above, 3.9-current dmesg is below. On the
upside we now have a adt0 device that did not seem to exist before.


Thanks for any suggestions.

-- 
nich

OpenBSD 3.9-current (GENERIC.MP) #1: Fri Jun 16 15:21:33 EST 2006
[EMAIL PROTECTED]:/usr/src/current-20060615/sys/arch/amd64/compile/GENERIC
.MP
real mem = 4227461120 (4128380K)
avail mem = 3632005120 (3546880K)
using 22937 buffers containing 422952960 bytes (413040K) of memory
mainbus0 (root)
bios0 at mainbus0: SMBIOS rev. 2.3 @ 0xf98a0 (64 entries)
bios0: To Be Filled By O.E.M. To Be Filled By O.E.M.
ipmi at mainbus0 not configured
mainbus0: Intel MP Specification (Version 1.1) (TYAN S2882   )
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: AMD Opteron(tm) Processor 246, 1991.42 MHz
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CF
LUSH,MMX,FXSR,SSE,SSE2,NXE,MMXX,LONG,3DNOW2,3DNOW
cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 1MB
64b/line 16-
way L2 cache
cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully
associative
cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully
associative
cpu0: apic clock running at 199MHz
cpu1 at mainbus0: apid 1 (application processor)
cpu1: AMD Opteron(tm) Processor 246, 1991.24 MHz
cpu1:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CF
LUSH,MMX,FXSR,SSE,SSE2,NXE,MMXX,LONG,3DNOW2,3DNOW
cpu1: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 1MB
64b/line 16-
way L2 cache
cpu1: ITLB 32 4KB entries fully associative, 8 4MB entries fully
associative
cpu1: DTLB 32 4KB entries fully associative, 8 4MB entries fully
associative
mpbios: bus 0 is type PCI   
mpbios: bus 1 is type PCI   
mpbios: bus 2 is type PCI   
mpbios: bus 3 is type PCI   
mpbios: bus 4 is type PCI   
mpbios: bus 5 is type ISA   
ioapic0 at mainbus0 apid 2 pa 0xfec0, version 11, 24 pins
ioapic1 at mainbus0 apid 3 pa 0xfebff000, version 11, 4 pins
ioapic2 at mainbus0 apid 4 pa 0xfebfe000, version 11, 4 pins
pci0 at mainbus0 bus 0: configuration mode 1
ppb0 at pci0 dev 6 function 0 AMD 8111 PCI-PCI rev 0x07
pci1 at ppb0 bus 4
ohci0 at pci1 dev 0 function 0 AMD 8111 USB rev 0x0b: apic 2 int 19
(irq 9), v
ersion 1.0, legacy support
usb0 at ohci0: USB revision 1.0
uhub0 at usb0
uhub0: AMD OHCI root hub, rev 1.00/1.00, addr 1
uhub0: 3 ports with 3 removable, self powered
ohci1 at pci1 dev 0 function 1 AMD 8111 USB rev 0x0b: apic 2 int 19
(irq 9), v
ersion 1.0, legacy support
usb1 at ohci1: USB revision 1.0
uhub1 at usb1
uhub1: AMD OHCI root hub, rev 1.00/1.00, addr 1
uhub1: 3 ports with 3 removable, self powered
siop0 at pci1 dev 4 function 0 Symbios Logic 53c895 rev 0x02: apic 2
int 16 (i
rq 10), using 4K of on-board RAM
scsibus0 at siop0: 16 targets
pciide0 at pci1 dev 5 function 0 CMD Technology SiI3114 SATA rev 0x02:
DMA
pciide0: using apic 2 int 19 (irq 9) for native-PCI interrupt
vga1 at pci1 dev 6 function 0 ATI Rage XL rev 0x27
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
fxp0 at pci1 dev 8 function 0 Intel 8255x rev 0x10, i82551: apic 2 int
18 (irq
 11), address 00:e0:81:41:0c:06
inphy0 at fxp0 phy 1: i82555 10/100 PHY, rev. 4
pcib0 at pci0 dev 7 function 0 AMD AMD8111 LPC rev 0x05
pciide1 at pci0 dev 7 function 1 AMD 8111 IDE rev 0x03: DMA, channel 0
configu
red to compatibility, channel 1 configured to compatibility
pciide1: channel 0 disabled (no drives)
atapiscsi0 at pciide1 channel 1 drive 0
scsibus1 at atapiscsi0: 2 targets
cd0 at scsibus1 targ 0 lun 0: HL-DT-ST, DVDRAM GSA-4167B, DL10 SCSI0
5/cdrom r
emovable
cd0(pciide1:1:0): using PIO mode 4, Ultra-DMA mode 2
amdiic0 at pci0 dev 7 function 2 AMD 8111 SMBus rev 0x02: SCI
iic0 at amdiic0
amdpm0 at pci0 dev 7 function 3 AMD 8111 Power rev 0x05: rng active
iic1 at amdpm0
lm1 at iic1 addr 0x28: W83627HF
adt0 at iic1 addr 0x2e: adm1027 rev 0x60
ppb1 at pci0 dev 10 function 0 AMD 8131 PCIX rev 0x12
pci2 at ppb1 bus 3
bge0 at pci2 dev 9 function 0 Broadcom BCM5704C rev 0x03, BCM5704 A3
(0x2003):
 apic 3 int 0 (irq 10), address 00:e0:81:41:0c:70
brgphy0 at bge0 phy 1: BCM5704 10/100/1000baseT PHY, rev. 0
bge1 at pci2 dev 9 function 1 Broadcom BCM5704C rev 0x03, BCM5704 A3
(0x2003):
 apic 3 int 1 (irq 5), address 00:e0:81:41:0c:71
brgphy1 at bge1 phy 1: BCM5704 10/100/1000baseT PHY, rev. 0
aapic0 at pci0 dev 10 function 1 AMD 8131 PCIX 

dmesg warning, ahc0: Illegal cable configuration!!

2006-06-16 Thread Daniel Hammett
Hello All,

I am happy to report an apparently successful install of OpenBSD 3.9 Release on
an HP Kayak XU 6/300 (Intel 440LX chipset, 2x Pentium II).

I am delighted to report that this is the first non-Windows OS I have used that
correctly reports and configures the on-board AD1816A audio subsystem straight
out of the box without any need for me to go digging around and hand-crafting
exoctic configurations.

 This is a great result, so well done to the to the OpenBSD development
team. 

As a consequence, I was very happy to pay up for a CD-ROM (which I received 
from Wim Vandeputte [kd85.com] yesterday) and support the project.

As an aside, I wonder if anyone on this list can offer some insight into the
following dmesg warning:

ahc0: Illegal cable configuration!!. Only two connectors on the adapter may be
used at a time!

[Full dmesg posted below]

This isn't unique to OpenBSD: I've seen similar reports in the dmesg from SuSE
Linux using the 2.4.xx series kernels and also from FreeBSD version 6.

It doesn't appear to affect the machine in anyway that I can tell, e.g. there
are no unexpected hangs, slowdowns, disk problems, etc.

The AIC-7880 wide SCSI is connnected to a single disk but there are multiple
(unused) connectors on the ribbon cable which end in a terminator block.

The AIC-7860 narrow SCSI is connected to a single CD-RW drive. Again, there are
multiple (unused) connectors on the ribbon cable and this, too, ends in a
terminator block.

I have used multiple drives in the system and the same message appears.

It occurs to me that there might be some issue with the disk drive itself
providing SCSI termination, or some other jumper configuration error.

Alternatively, doe this message imply that I can only use either the AIC-7860
or the AIC-7880 but not both? I might try unplugging the CD-RW before booting
this evening.

--- dmesg included ---

OpenBSD 3.9 (GENERIC.MP) #598: Thu Mar  2 02:37:06 MST 2006
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC.MP
cpu0: Intel Pentium II (GenuineIntel 686-class, 512KB L2 cache) 300 MHz
cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,MMX
real mem  = 536453120 (523880K)
avail mem = 482435072 (471128K)
using 4278 buffers containing 26927104 bytes (26296K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(a1) BIOS, date 10/28/98, BIOS32 rev. 0 @ 0xfd77d
apm0 at bios0: Power Management spec V1.2
apm0: AC on, battery charge unknown
apm0: flags 30102 dobusy 0 doidle 1
pcibios0 at bios0: rev 2.1 @ 0xfd710/0x8f0
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdf20/192 (10 entries)
pcibios0: PCI Interrupt Router at 000:07:0 (Intel 82371FB ISA rev 0x00)
pcibios0: PCI bus #1 is the last bus
bios0: ROM list: 0xc/0x8000 0xc8000/0x4800
mainbus0: Intel MP Specification (Version 1.4) (HP   XU/XW   )
cpu0 at mainbus0: apid 1 (boot processor)
cpu0: apic clock running at 66 MHz
cpu1 at mainbus0: apid 0 (application processor)
cpu1: Intel Pentium II (GenuineIntel 686-class, 512KB L2 cache) 300 MHz
cpu1: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,MMX
mainbus0: bus 0 is type PCI   
mainbus0: bus 1 is type PCI   
mainbus0: bus 2 is type ISA   
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 11, 24 pins
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 Intel 82443LX AGP rev 0x03
ppb0 at pci0 dev 1 function 0 Intel 82443LX AGP rev 0x03
pci1 at ppb0 bus 1
vga1 at pci1 dev 0 function 0 Matrox MGA G400/G450 AGP rev 0x04
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
pcib0 at pci0 dev 7 function 0 Intel 82371AB PIIX4 ISA rev 0x01
pciide0 at pci0 dev 7 function 1 Intel 82371AB IDE rev 0x01: DMA, channel 0
wired to compatibility, channel 1 wired to compatibility
atapiscsi0 at pciide0 channel 0 drive 0
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0: MATSHITA, CD-ROM CR-585, ZP18 SCSI0 5/cdrom
removable
cd0(pciide0:0:0): using PIO mode 0, DMA mode 1
pciide0: channel 1 ignored (disabled)
uhci0 at pci0 dev 7 function 2 Intel 82371AB USB rev 0x01: apic 2 int 19 (irq
11)
usb0 at uhci0: USB revision 1.0
uhub0 at usb0
uhub0: Intel UHCI root hub, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
piixpm0 at pci0 dev 7 function 3 Intel 82371AB Power rev 0x01: SMI
iic0 at piixpm0
unknown at iic0 addr 0x2d not configured
lmtemp0 at iic0 addr 0x48: lm75
ahc0 at pci0 dev 8 function 0 Adaptec AIC-7880 rev 0x01: apic 2 int 16 (irq
11)
ahc0: Illegal cable configuration!!. Only two connectors on the adapter may be
used at a time!
scsibus1 at ahc0: 16 targets
sd0 at scsibus1 targ 3 lun 0: SEAGATE, ST318404LW, 0006 SCSI3 0/direct fixed
sd0: 17501MB, 14384 cyl, 6 head, 415 sec, 512 bytes/sec, 35843670 sec total
ahc1 at pci0 dev 9 function 0 Adaptec AIC-7860 rev 0x03: apic 2 int 19 (irq
11)
scsibus2 at ahc1: 8 targets
cd1 at scsibus2 targ 2 lun 0: HP, CD-Writer+ 9200, 1.0e SCSI4 5/cdrom
removable
rl0 at 

Re: Missing ipmi sensors on current

2006-06-16 Thread Stuart Henderson
On 2006/06/16 17:54, Nicholas Young wrote:
 After rebooting with the new kernel the ipmi card which is a Tyan Taro
 M3289 is no longer being configured.

http://marc.theaimsgroup.com/?l=openbsd-cvsm=114912246701017w=2



Re: Missing ipmi sensors on current

2006-06-16 Thread Nicholas Young
On Fri, Jun 16, 2006 at 09:44:08AM +0100, Stuart Henderson wrote:
 On 2006/06/16 17:54, Nicholas Young wrote:
  After rebooting with the new kernel the ipmi card which is a Tyan Taro
  M3289 is no longer being configured.
 
 http://marc.theaimsgroup.com/?l=openbsd-cvsm=114912246701017w=2

Thanks, I had a look at cvs for ipmi.c should have checked harder.

Is ipmi problematic for stable or just with the recent changes?

-- 
Nich



Re: package dependencies

2006-06-16 Thread z0mbix

On 6/16/06, Bihlmaier Andreas [EMAIL PROTECTED] wrote:

On Thu, Jun 15, 2006 at 04:19:26PM -0700, Spruell, Darren-Perot wrote:
 From: [EMAIL PROTECTED]
  p.s. this question comes from the need to know the exact packages to
  download and burn to CD in order to get a reasonably usable desktop
  system running gnome, when said system has no connection to
  the interweb

 See also: 'make print-build-depends' and 'make print-run-depends' from the
 desired port directory.

 These are all covered in ports(7).

I faced the same problem quite some time ago (download snapshop with a
set of packages (including their dependencies).

The problem with all above methods is that you need a current ports
tree version besides the packages as well.

What I did is to extract the information in the packages (foo.tgz) and
download the result from ftp, until no dependencies are left (it takes
care not to download stuff twice).

Here is the part getting the parsable dependencies from a .tgz file
(yes this is as very dirty hack, but resonably fast and it works):

dd if=${pkg}.tgz bs=64k count=1 2/dev/null | \
zgrep -a '[EMAIL PROTECTED] ' | \
awk 'BEGIN{ FS=: } {print $3.tgz}' | \
sed 's/.*\./\*\./'

For pkg = kdebase-3.5.1p4 the output looks like this:
openldap-client-2.3.11p4.tgz
glib2-2.8.4.tgz
libusb-0.1.10ap1.tgz
cyrus-sasl-2.1.21p2.tgz
kdelibs-3.5.1p0.tgz
qt3-mt-3.5p4.tgz
qt3-mt-3.5p4.tgz

Regards,
ahb




Or you could set your $PKG_PATH and run:

# sudo pkg_add -vn gnome-desktop-2.10.2p1



Re: Missing ipmi sensors on current

2006-06-16 Thread Stuart Henderson
On 2006/06/16 19:07, Nicholas Young wrote:
 On Fri, Jun 16, 2006 at 09:44:08AM +0100, Stuart Henderson wrote:
  On 2006/06/16 17:54, Nicholas Young wrote:
   After rebooting with the new kernel the ipmi card which is a Tyan Taro
   M3289 is no longer being configured.
  
  http://marc.theaimsgroup.com/?l=openbsd-cvsm=114912246701017w=2
 
 Thanks, I had a look at cvs for ipmi.c should have checked harder.
 Is ipmi problematic for stable or just with the recent changes?

I don't know myself, the only board I have with an ipmi card (supermicro
aplus H8SSL) has it attached somewhere I can't find so I haven't used ipmi
on OpenBSD yet.

This reminds me, does anyone remember why the initial ASF support got
backed-out from bge(4)?



Re: Pulled out an old song..

2006-06-16 Thread Jason Stubbs

On 16/06/06, Michael Coulter [EMAIL PROTECTED] wrote:

On Fri, Jun 16, 2006 at 12:01:35PM +0900, Jason Stubbs wrote:
 Unless the quality of the CD has deterioated, where does the
 random element come from?

http://www.stereophile.com/features/827/

If you start reading about the low-level details of C/DVDs and
you don't have a lot of faith in math, you'll be scared to death
you ever put data on an optical disc.


Very interesting article. However, I still don't see how ripped audio 
might change on each ripping. The article states that E11 and E12 errors 
are common but that the original data is fully inferrable(sp?) and that 
E22 errors are usually caused by damage. I can see how audibal changes 
could occur if CD players use the amplitude obtained from the CD 
directly without first going fully digital, but otherwise...


Anyway, enough idle conjecture. When I get home I'll give it a try 
myself and then do further research. :)


vladas wrote:

Jason,

Thank you for the link!


Thank Michael. ;)

--
Jason Stubbs



libtool: link: 'format-python.lo'

2006-06-16 Thread Roger Midmore
I just got a new laptop and was installing OpenBSD 3.9 on it and I got a
linking error when I was trying to build clisp from ports. The error is

libtool: link: 'format-python.lo' is not a valid libtool object

I also get the same error when I try to install some other software from
ports like mozilla-firefox and others. They all seem to be related to this
one problem with libtool. I was wondering if anyone has encountered this
problem.

Laptop is a Acer Aspire 3000 with a 1.8 sempron 3100.



Re: Pulled out an old song..

2006-06-16 Thread vladas

On 16/06/06, Jason Stubbs [EMAIL PROTECTED] wrote:

On 16/06/06, Michael Coulter [EMAIL PROTECTED] wrote:
 On Fri, Jun 16, 2006 at 12:01:35PM +0900, Jason Stubbs wrote:
  Unless the quality of the CD has deterioated, where does the
  random element come from?

 http://www.stereophile.com/features/827/

 If you start reading about the low-level details of C/DVDs and
 you don't have a lot of faith in math, you'll be scared to death
 you ever put data on an optical disc.

Very interesting article. However, I still don't see how ripped audio
might change on each ripping. The article states that E11 and E12 errors
are common but that the original data is fully inferrable(sp?) and that
E22 errors are usually caused by damage. I can see how audibal changes
could occur if CD players use the amplitude obtained from the CD
directly without first going fully digital, but otherwise...

Anyway, enough idle conjecture. When I get home I'll give it a try
myself and then do further research. :)

vladas wrote:
 Jason,

 Thank you for the link!

Thank Michael. ;)


Oh. Sorry:

Thank you, Michael.



--
Jason Stubbs



vladas



Re: dmesg warning, ahc0: Illegal cable configuration!!

2006-06-16 Thread Nick Holland

Daniel Hammett wrote:
...

ahc0: Illegal cable configuration!!. Only two connectors on the adapter may be
used at a time!

[Full dmesg posted below]


yay! :)


This isn't unique to OpenBSD: I've seen similar reports in the dmesg from SuSE
Linux using the 2.4.xx series kernels and also from FreeBSD version 6.

It doesn't appear to affect the machine in anyway that I can tell, e.g. there
are no unexpected hangs, slowdowns, disk problems, etc.

The AIC-7880 wide SCSI is connnected to a single disk but there are multiple
(unused) connectors on the ribbon cable which end in a terminator block.

The AIC-7860 narrow SCSI is connected to a single CD-RW drive. Again, there are
multiple (unused) connectors on the ribbon cable and this, too, ends in a
terminator block.


this isn't the issue, as that's ahc1 according to the dmesg.


I have used multiple drives in the system and the same message appears.

It occurs to me that there might be some issue with the disk drive itself
providing SCSI termination, or some other jumper configuration error.

Alternatively, doe this message imply that I can only use either the AIC-7860
or the AIC-7880 but not both? I might try unplugging the CD-RW before booting
this evening.


nope, again, ahc0 and ahc1 are two different devices, if it is whining 
about X, the problem is with X.  Probably. :)


As I recall, there are some variants of the Adaptec cards that use the 
ahc(4) driver that are kinda...curious.  I think it is the 29160 (or 
some variant) which has both LVD U160 and a single-ended U2, plus a 50 
pin connector...and the rule is, you can use two of the three 
connectors, but not all three at the same time.  I may be misremembering 
this...it might involve the external connector on the spine of the card, 
rather than the 50 pin connector.  But the rule was..only two of the 
connectors.  And note: it's the connectors in use, not the number of 
devices attached.


As I recall, all it can do is look for terminators.  If it finds more 
terminators than it expects, it apparently sets a whine flag that the 
driver looks for.  Are there any extra terminators on the system?  You 
indicate the cable has a terminator...could the drive also be 
terminated?  Also make sure any unused SCSI connectors are just left 
unconnected.


Otherwise...if everything is correct, and performance is appropriate, 
don't worry about it...probably a quirk in implementation on this 
machine.  I don't recall ever seeing any ability to see messages like 
this under Windows, so I suspect HP may have been a little sloppy about 
how they implemented things.


Nick.



--- dmesg included ---

OpenBSD 3.9 (GENERIC.MP) #598: Thu Mar  2 02:37:06 MST 2006
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC.MP
cpu0: Intel Pentium II (GenuineIntel 686-class, 512KB L2 cache) 300 MHz
cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,MMX
real mem  = 536453120 (523880K)
avail mem = 482435072 (471128K)
using 4278 buffers containing 26927104 bytes (26296K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(a1) BIOS, date 10/28/98, BIOS32 rev. 0 @ 0xfd77d
apm0 at bios0: Power Management spec V1.2
apm0: AC on, battery charge unknown
apm0: flags 30102 dobusy 0 doidle 1
pcibios0 at bios0: rev 2.1 @ 0xfd710/0x8f0
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdf20/192 (10 entries)
pcibios0: PCI Interrupt Router at 000:07:0 (Intel 82371FB ISA rev 0x00)
pcibios0: PCI bus #1 is the last bus
bios0: ROM list: 0xc/0x8000 0xc8000/0x4800
mainbus0: Intel MP Specification (Version 1.4) (HP   XU/XW   )
cpu0 at mainbus0: apid 1 (boot processor)
cpu0: apic clock running at 66 MHz
cpu1 at mainbus0: apid 0 (application processor)
cpu1: Intel Pentium II (GenuineIntel 686-class, 512KB L2 cache) 300 MHz
cpu1: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,MMX
mainbus0: bus 0 is type PCI   
mainbus0: bus 1 is type PCI   
mainbus0: bus 2 is type ISA   
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 11, 24 pins

pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 Intel 82443LX AGP rev 0x03
ppb0 at pci0 dev 1 function 0 Intel 82443LX AGP rev 0x03
pci1 at ppb0 bus 1
vga1 at pci1 dev 0 function 0 Matrox MGA G400/G450 AGP rev 0x04
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
pcib0 at pci0 dev 7 function 0 Intel 82371AB PIIX4 ISA rev 0x01
pciide0 at pci0 dev 7 function 1 Intel 82371AB IDE rev 0x01: DMA, channel 0
wired to compatibility, channel 1 wired to compatibility
atapiscsi0 at pciide0 channel 0 drive 0
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0: MATSHITA, CD-ROM CR-585, ZP18 SCSI0 5/cdrom
removable
cd0(pciide0:0:0): using PIO mode 0, DMA mode 1
pciide0: channel 1 ignored (disabled)
uhci0 at pci0 dev 7 function 2 Intel 82371AB USB rev 0x01: apic 2 int 19 (irq
11)
usb0 at uhci0: USB revision 1.0
uhub0 at usb0
uhub0: Intel UHCI root hub, rev 1.00/1.00, addr 1
uhub0: 2 

Re: Pulled out an old song..

2006-06-16 Thread Schöberle Dániel
 On Behalf Of Jason Stubbs
 Sent: Friday, June 16, 2006 10:06 AM
 On 16/06/06, Michael Coulter [EMAIL PROTECTED] wrote:
  On Fri, Jun 16, 2006 at 12:01:35PM +0900, Jason Stubbs wrote:
   Unless the quality of the CD has deterioated, where does the
   random element come from?
 
  http://www.stereophile.com/features/827/
 
  If you start reading about the low-level details of C/DVDs and
  you don't have a lot of faith in math, you'll be scared to death
  you ever put data on an optical disc.
 
 Very interesting article. However, I still don't see how ripped audio 
 might change on each ripping. The article states that E11 and 
 E12 errors 
 are common but that the original data is fully 
 inferrable(sp?) and that 
 E22 errors are usually caused by damage. I can see how 
 audibal changes 
 could occur if CD players use the amplitude obtained from the CD 
 directly without first going fully digital, but otherwise...
 
 Anyway, enough idle conjecture. When I get home I'll give it a try 
 myself and then do further research. :)

You can get bit identical rips of audio CDs, meaning you can compare
the track's CRC, hash or anything else. EAC (www.exactaudiocopy.de)
is one solution but it's Windows only. I haven't ripped under OpenBSD so 
I have no recommendation for it. www.hydrogenaudio.org is my source of
authoritative information regarding digital audio. Check it out.

Regards, Daniel.



Re: NFS Slow writes

2006-06-16 Thread Andy Hayward

On 6/15/06, Bob Bostwick (Lists) [EMAIL PROTECTED] wrote:

I'm trying to setup an NFS share, and am getting horrible write
performance.  Reads are fast as can be expected.  I've searched the
archives and found several threads on the subject, but no resolutions.
I've tried all possible fstab options (that I know of) but none really
help with write.  I'm currently using

ip.addr:/nfs /test/dir nfs rw,nodev,nosuid,tcp,intr,-r=32768,-w=32768 0 0


I've found (after various tests) with with an OpenBSD (3.8) server and
Linux client, that I get the best performance with:

 rw,noauto,soft,tcp,rsize=2048,wsize=2048

This gives out 8MB/s for both read and write with my hardware.

YMMV, but one thing I did notice is that large rsize/wsize didn't
necessarily translate to better performance.

-- ach



Re: LostFound with PF-Tables?!?!

2006-06-16 Thread sebastian . rother
On Fri, Jun 16, 2006 at 03:31:01AM +0200, [EMAIL PROTECTED]
wrote:

 table dssh persist
 pass in on $ext_if proto tcp to $web_server \
  port 22 flags S/SA keep state \
  (max-src-conn 10, max-src-conn-rate 3/10, overload dssh flush)

 The problem I have is that pf did not added the table dssh after the
 startup. I noticed that during another dumb ssh-bruteforce today where the
 src. host was not blocked automaticly.

What does pfctl -nf /etc/pf.conf say? Anything?

wizzard $ sudo pfctl -nf /etc/pf.conf
wizzard $


Kind regards,
Sebastian



Re: Privilege bracketing in Solaris 10

2006-06-16 Thread Martin Schröder

2006/6/16, Graham Toal [EMAIL PROTECTED]:

30 years after VMS and 40 years after EMAS.

Ivan Sutherland sure had it right with his observatiion
of the great wheel of reincarnation as it applies to computing...


Ask a typical cs graduate today about VMS. I'll be surprised if she
even knows what it is, and I don't expect her to know about it's
clustering features.

You mean there are other operating systems but Linux/Unix and Windows? :-(

Best
   Martin



Re: ftp problems with OpenBSD 3.9

2006-06-16 Thread Hannah Schroeter
Hi!

On Thu, Jun 15, 2006 at 09:29:40PM -0400, Nick Holland wrote:
Smith wrote:
how do I compile it.  I know I can look at previous patches and possible 
figure it out but I wouldn't know if it's the proper way to do it.  I 
have a test machine all setup and ready and my pwd is 
/usr/src/libexec/ftpd.

Just replied privately, but since you asked publicly also, should reply 
for the list, in case anyone else wants to try...

And since replying to you, I've tested it.  It at least seems to work. 
Not sure it fixes your problem, however.

   make obj

make cleandir # to be sure
make depend # can sometimes make a difference in addition to
# dependencies (e.g. run yacc/lex)

   make
   make install

Stop and restart ftpd if you are running it as a daemon (ftpd -D), and 
you should be able to test...

Nick.

Kind regards,

Hannah.



Re: Routing trouble with PPPoE on 3.8

2006-06-16 Thread Martin Schröder

2006/6/16, Srikant Tangirala [EMAIL PROTECTED]:

I am trying to connect my obsd 3.8-stable system to internet
via PPPoE ( ISDN connection-64Kbps). ppp program reports
an established connection, ifconfig shows an IP address
assigned to tun0 interface. But i simply can't use any program
like ping, ftp or firefox to connect to any server. They say
no route to host. I must be doing something stupid. Is the
pf ruleset the problem?


Probably not. ppp(8) is your friend.


default:
set log Phase Chat LCP IPCP CCP tun command
pppoe:
set device !/usr/sbin/pppoe -i rl0
set mtu max 1492
set mru max 1492
set speed sync
disable acfcomp protocomp
deny acfcomp
set authname [EMAIL PROTECTED]
set authkey 

set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0
add! default HISADDR

This should give you a default route(8).

Best
   Martin



OpenHSMM-ap New OBSD Project

2006-06-16 Thread Paul Pescitelli

Folks,

For the last 6 months or so, I have been working on a project to take
OpenBSD 3.8 and create an appliance type interface for a Wireless
Access Point. Before I get into the nitty gritty details, here is  a
little about the name. The name is derived from the combination of
Open Source projects designed to facilitate the ideas that are put
forth by the Amateur Radio Relay League High Speed Multi Media Task
Force. ( http://www.arrl.org/hsmm ). This group plays an integral role
in providing guidelines for creating Emergency Communications networks
using Amateur Radio equipment from HF frequencies up through 5.8GHZ.

The goal of the project was to create a relatively small footprint AP
that could be put on a compact flash, plug it in to a Soekris single
board computer (no moving parts) to be deployed on rooftops and
towers. For those of you that are familiar with m0n0wall this will
look very similar. After speaking with Manuel Kasper it seemed to be
somewhat easy to port the m0n0wall FreeBSD code base for this effort.

Visit the web page ( http://www.openhsmm.org ) for some of the initial
and planned features.

Keep in mind that this is an ALPHA version, not all of the
functionality you see works properly. It does currently function as a
basic AP with WEP. 98% of the testing so far has been with the Winstom
CM-9 miniPCI card. I would appreciate constructive feedback. If you
are interested in contributing to the project let me know. If you see
something that needs to be fixed please send me a diff.

and Yes, there are plans in the very near future for migrating the
kernel to 3.9.

--
CIAO - Paul Pescitelli

/**
Unix Advocate and creator of OpenHSMM
Wire Access Point OpenBSD appliance.
www.openhsmm.org
/*/



Is hwinfo good enought to get hw info from win32 boxes?

2006-06-16 Thread vladas

I want to get hw info from win boxes before performing
dedicated OpenBSD installs. Is http://www.hwinfo.com/ good
enough or I should use some other tool to be more informative?

P.S.
Just to make myself clear - I am asking this, because I think that
it might be appreciated by the devs to get not only dmesg but
also hw info from the native drivers.



Re: ddos mail attack thwarted by spamd greylisting!

2006-06-16 Thread Bob Beck
* Joachim Schipper [EMAIL PROTECTED] [2006-06-15 18:03]:
 On Tue, Jun 13, 2006 at 01:07:46AM -0600, Bob Beck wrote:
   Luckily, spamd greylisting saved the day.  If it wasn't for BASE/snort 
   reporting of the portscan, I wouldn't have even bothered looking in my 
   logs
   tonite, and probably would never have been aware of the thwarted attempt.
   
  
  Good thing they're only portscanning and mailbombing you then,
  and not exploiting one of the bazillions of snort overflows ;)
 
 If it was set up properly, exploiting Snort wouldn't gain anyone
 anything more serious than the ability to mess up Snort logs. Granted,
 that can be useful...
 

It'll get you root. on a machine with the ability to see all
your inbound and outbound traffic, and in 99% of the properly setup
cases I've ever seen still means it can inject traffic as well.

That's a big deal, imnso.

Having said that, many snort runners are also having it actively
poke their firewalls. which is even more fun.

So I'm sorry, I guess the if it is set up properly reads to my like
the people who don't have problems with Windows machines - If they
are set up properly. just like I'm going to lose weight and exercise
till I have an ass of hard manly steel.. it's this mythical state that
hardly ever seems to be attainable in the real world under real
installations. 

-Bob



slow realloc: alternate method?

2006-06-16 Thread Jacob Yocom-Piatt
i've got some C code that is reading from a 800 MB CSV file and allocates memory
for an array to store the data in. the method used is to read the CSV file
line-by-line and realloc additional space with each line read. having timed this
and found the realloc speed to be low when the array is large, i am aiming to
make this faster but am not sure about the best way to proceed.

the current code uses realloc in the manner suggested by the manpage:

newsize = size + 1;
time(t1);  // start timing realloc
if ((newap = (int *)realloc(ap, newsize*sizeof(int))) == NULL) {
free(ap);
ap = NULL;
size = 0;
return (NULL);
}
time(t2);  // stop timing realloc; start timing fscanf

as the size of ap grows, so does the time it takes to realloc the space.

an alternative to this procedure would be to scan through the CSV file to
determine how many array entries i would need, realloc it all at once, then go
back through the CSV file again to read the data into the array. i'm not
confident this is the only way to do this and would appreciate any suggestions
for speeding up this procedure.

cheers,
jake 



Re: slow realloc: alternate method?

2006-06-16 Thread Dimitry Andric
Jacob Yocom-Piatt wrote:
 an alternative to this procedure would be to scan through the CSV file to
 determine how many array entries i would need, realloc it all at once, then go
 back through the CSV file again to read the data into the array.

Try starting with a reasonable number of lines, e.g. the average number
of lines in most of your csv files, and doubling the buffer each time
you fill it up.



Re: error clamav at 3.9

2006-06-16 Thread Michael Erdely

riwanlky wrote:

# make install
===  Checking files for unrar-3.54p0
  unrarsrc-3.5.4.tar.gz doesn't seem to exist on this system.
  Fetch http://www.rarlab.com/rar/unrarsrc-3.5.4.tar.gz.
  Size does not match for /usr/ports/distfiles/unrarsrc-3.5.4.tar.gz
/bin/sh: test: unrarsrc-3.5.4.tar.gz: unexpected operator/operand
*** Error code 2


Try deleting the distfile (rm 
/usr/ports/distfiles/unrarsrc-3.5.4.tar.gz) and starting fresh (make clean).


I just tried building this on my system again.  It downloads, passes 
checksum and builds with no problems.


-ME

--
Support OpenBSD: http://www.openbsd.org/orders.html



Re: ftp problems with OpenBSD 3.9

2006-06-16 Thread Smith

Okay, I followed Nick Holland's suggestion.

First, I had setup an OpenBSD 3.9 test machine.  The only configuration 
I did was to setup the ftpd service as described in a previous post.  I 
tested it, the problem still persisted.  Then I download src.tar.gz from 
the 3.8 directory on a mirror and extracted it into /usr/src.  Then in 
/usr/src/libexec/ftpd, I did make obj, make cleandir, make depend, make, 
make install.  Finally I rebooted.  I did a test and it was successful.  
So it appears something did change.  Does this mean I should read up 
sendbug and figure out how to report a bug or was this change intentional?




Re: useradd - Passwort setzen

2006-06-16 Thread Martin Schröder

2006/6/16, Andre Tann [EMAIL PROTECTED]:

Andreas Winkelmann, Freitag, 16. Juni 2006 18:30:
 $ man chpasswd

Ah, das kannte ich noch gar nicht... Danke!


man apropos
apropos password

Gru_
   Martin



Re: failing to install RRDtool package and MRTGpackage on openBSD 3.9

2006-06-16 Thread Michael Erdely

Ton wrote:

I am using openBSD 3.9 on several machines, i have a seperate machine
for testing purpose.
today i want to try to install the RRDtool and MRTGpackage from your site.

Can't install gd-2.0.33p2: lib not found fontconfig.3.0
Even by looking in the dependency tree:


Install xbase.


most kindly
Ton muller ,aka spatieman..


-ME

--
Support OpenBSD: http://www.openbsd.org/orders.html



Re: Hifn policy on documentation

2006-06-16 Thread Wolfgang S. Rupprecht
Phil Howard [EMAIL PROTECTED] writes:
 Ultimately, I'll personally depend on crypto in software I can access for
 myself.  I think that's your real point.

Thanks for the well thought-out reply.

I too would place a heck of a lot less trust in some crypto chip than
something that is inspectable.

 What interests me among Hifn's chips are not the crypto capabilities, but
 the compression capabilities.

Interesting.  I didn't realize they did that.  It looks like a safe
enough use.

knitti [EMAIL PROTECTED] writes:
 any algorithm the cards claim to implement _is_ fully documented, so
 you can test any output except that of the RNG against a 'known
 good' implementation

Even if the cipherstream out of a chip is the same as the software
implementation in general, what prevents the chip from switching to a
trojan mode when it sees a certain data-pattern in the plaintext input
stream?  Sure the other side might not be able to decrypt the doctored
up cipherstream, but the information would have already been leaked.
Heck, if both sides use the same chip, the receiving chip could even
recognize the data stream and pretend that nothing out of the ordinary
were going on.

Personally I don't see how a hardware chip maker can prove that the
chip doesn't have a trojan without providing masks for inspection and
a way to prove that those masks and only those masks were used to make
the chip.  Open source and all that.

-wolfgang
-- 
Wolfgang S. Rupprechthttp://www.wsrcc.com/wolfgang/



Re: Tracking security advisories

2006-06-16 Thread Chris Zakelj
Spruell, Darren-Perot [EMAIL PROTECTED] wrote:  For sysadmins that want to 
know as soon as possible about issues which
are deemed patch-worthy (security vulnerabilities, critical
reliability issues), what is the best way to stay on top of these
issues as they are resolved?

The canonical source of information seems to be errta.html, which does
tend to be updated quickly as the patch becomes available. To keep
track of this, it requires the user to access the page and look for a
new patch which may apply to him.

One could also monitor commits to CVS and while reliable, it becomes a
bit more difficult to pick the critical from some of the rest of it.

There's also a vuxml setup for OpenBSD at
http://www.vuxml.org/openbsd/index.html, which appears to be
independently maintained and doesn't stay sufficiently updated to be
used as an alerting mechanism.

Then, as outlined in release announcements, Security patch
announcements are sent to the [EMAIL PROTECTED] mailing
list. This method is preferred by a lot of people so they get some
kind of proactive notification of potentially impactive problems.
Patch announcements do make it to the list, some as early as 1 day
after patch announcement, others 14 days after patch. The possible
advantage over errata.html though is you get notified even if you've
lapsed in checking out the web page. On the flip side, this requires a
developer to take time and craft the message and send it, so the onus
is on the project to do the work.

DS

  
What is best for one person may not necessarily be best for another.  That 
said, it shouldn't be too hard to make fetching errata.html part of your daily 
crontab, running a diff on the fetch versus a cached reference, and triggering 
an email when there's a difference.



Kernel Hangs; Supermicro 5015M-MR (Intel E7230)

2006-06-16 Thread Jon Holderith

Supermicro 5015M-MR uses Supermicro PDSMi motherboard (Intel E7230 chipset)

Kernel hangs after pcibios0: PCI bus #6 is the last bus
Changed pcibios flags to 1 with UKC and enabled verbose mode.
Kernel then hangs during ppb probe
Changed pcibios flags to 1 and disabled ppb and Kernel finished loading.

Same result with bsd.mp

Is there anything else I can try that will shed more light on this issue?

- Jon


OpenBSD 3.9-current (GENERIC) #882: Thu Jun 15 12:43:50 MDT 2006
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel(R) Pentium(R) D CPU 2.80GHz (GenuineIntel 686-class) 2.78 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,CNXT-ID,CX16
real mem  = 1072128000 (1047000K)
avail mem = 970346496 (947604K)
using 4256 buffers containing 53710848 bytes (52452K) of memory
User Kernel Config
UKC change pcibios
284 pcibios0 at bios0 flags 0x0
change (y/n) ?
flags [0] ? 1
284 pcibios0 changed
284 pcibios0 at bios0 flags 0x1
UKC disable ppb
 89 ppb* disabled
UKC quit
Continuing...
mainbus0 (root)
bios0 at mainbus0: AT/286+(66) BIOS, date 04/17/06, BIOS32 rev. 0 @ 0xfd470,
SMBIOS rev. 2.51 @ 0x3feea000 (33 entries)
bios0: Supermicro PDSMi
pcibios0 at bios0: rev 2.1 @ 0xfd470/0xb90
pcibios0: PCI BIOS has 20 Interrupt Routing table entries
pcibios0: PCI Interrupt Router at 000:31:0 (Intel 82801GB LPC rev 0x00)
pcibios0: PCI bus #6 is the last bus
bios0: ROM list: 0xc/0x8000
ipmi at mainbus0 not configured
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 Intel E7230 MCH rev 0x81
Intel E7230 PCIE rev 0x81 at pci0 dev 1 function 0 not configured
Intel 82801GB PCIE rev 0x01 at pci0 dev 28 function 0 not configured
Intel 82801G PCIE rev 0x01 at pci0 dev 28 function 4 not configured
Intel 82801G PCIE rev 0x01 at pci0 dev 28 function 5 not configured
uhci0 at pci0 dev 29 function 0 Intel 82801GB USB rev 0x01: irq 5
usb0 at uhci0: USB revision 1.0
uhub0 at usb0
uhub0: Intel UHCI root hub, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1 at pci0 dev 29 function 1 Intel 82801GB USB rev 0x01: irq 10
usb1 at uhci1: USB revision 1.0
uhub1 at usb1
uhub1: Intel UHCI root hub, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
uhci2 at pci0 dev 29 function 2 Intel 82801GB USB rev 0x01: irq 11
usb2 at uhci2: USB revision 1.0
uhub2 at usb2
uhub2: Intel UHCI root hub, rev 1.00/1.00, addr 1
uhub2: 2 ports with 2 removable, self powered
uhci3 at pci0 dev 29 function 3 Intel 82801GB USB rev 0x01: irq 10
usb3 at uhci3: USB revision 1.0
uhub3 at usb3
uhub3: Intel UHCI root hub, rev 1.00/1.00, addr 1
uhub3: 2 ports with 2 removable, self powered
ehci0 at pci0 dev 29 function 7 Intel 82801GB USB rev 0x01: irq 5
usb4 at ehci0: USB revision 2.0
uhub4 at usb4
uhub4: Intel EHCI root hub, rev 2.00/1.00, addr 1
uhub4: 8 ports with 8 removable, self powered
Intel 82801BA AGP rev 0xe1 at pci0 dev 30 function 0 not configured
ichpcib0 at pci0 dev 31 function 0 Intel 82801GB LPC rev 0x01: PM disabled
pciide0 at pci0 dev 31 function 1 Intel 82801GB IDE rev 0x01: DMA, channel 0
configured to compatibility, channel 1 configured to compatibility
atapiscsi0 at pciide0 channel 0 drive 0
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0: TEAC, CD-224E-N, 1.AA SCSI0 5/cdrom removable
cd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2
pciide0: channel 1 ignored (disabled)
pciide1 at pci0 dev 31 function 2 Intel 82801GB SATA rev 0x01: DMA, channel 0
configured to native-PCI, channel 1 configured to native-PCI
pciide1: using irq 10 for native-PCI interrupt
wd0 at pciide1 channel 0 drive 0: ST3250623NS
wd0: 16-sector PIO, LBA48, 238475MB, 488397168 sectors
wd0(pciide1:0:0): using PIO mode 4, Ultra-DMA mode 5
ichiic0 at pci0 dev 31 function 3 Intel 82801GB SMBus rev 0x01: irq 10
iic0 at ichiic0
lm1 at iic0 addr 0x2d: W83627HF
lm2 at iic0 addr 0x2f: W83792D rev D
isa0 at ichpcib0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard
vga0 at isa0 port 0x3b0/48 iomem 0xa/131072
wsdisplay0 at vga0 mux 1: console (80x25, vt100 emulation), using wskbd0
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
pcppi0 at isa0 port 0x61
midi0 at pcppi0: PC speaker
spkr0 at pcppi0
lpt0 at isa0 port 0x378/4 irq 7
lm0 at isa0 port 0x290/8: W83627HF
lm1 detached
npx0 at isa0 port 0xf0/16: using exception 16
pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
biomask ff65 netmask ff65 ttymask ffe7
pctr: user-level cycle counter enabled
dkcsum: wd0 matches BIOS drive 0x80
root on wd0a
rootdev=0x0 rrootdev=0x300 rawdev=0x302



Re: Kernel Hangs; Supermicro 5015M-MR (Intel E7230)

2006-06-16 Thread mickey
On Fri, Jun 16, 2006 at 10:39:44AM -0800, Jon Holderith wrote:
 Supermicro 5015M-MR uses Supermicro PDSMi motherboard (Intel E7230 chipset)
 
 Kernel hangs after pcibios0: PCI bus #6 is the last bus
 Changed pcibios flags to 1 with UKC and enabled verbose mode.
 Kernel then hangs during ppb probe
 Changed pcibios flags to 1 and disabled ppb and Kernel finished loading.
 
 Same result with bsd.mp
 
 Is there anything else I can try that will shed more light on this issue?

yes. flags 2 or otherwise just disable pcibios completely.

 OpenBSD 3.9-current (GENERIC) #882: Thu Jun 15 12:43:50 MDT 2006
 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
 cpu0: Intel(R) Pentium(R) D CPU 2.80GHz (GenuineIntel 686-class) 2.78 GHz
 cpu0:
 FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,CNXT-ID,CX16
 real mem  = 1072128000 (1047000K)
 avail mem = 970346496 (947604K)
 using 4256 buffers containing 53710848 bytes (52452K) of memory
 User Kernel Config
 UKC change pcibios
 284 pcibios0 at bios0 flags 0x0
 change (y/n) ?
 flags [0] ? 1
 284 pcibios0 changed
 284 pcibios0 at bios0 flags 0x1
 UKC disable ppb
  89 ppb* disabled
 UKC quit
 Continuing...
 mainbus0 (root)
 bios0 at mainbus0: AT/286+(66) BIOS, date 04/17/06, BIOS32 rev. 0 @ 0xfd470,
 SMBIOS rev. 2.51 @ 0x3feea000 (33 entries)
 bios0: Supermicro PDSMi
 pcibios0 at bios0: rev 2.1 @ 0xfd470/0xb90
 pcibios0: PCI BIOS has 20 Interrupt Routing table entries
 pcibios0: PCI Interrupt Router at 000:31:0 (Intel 82801GB LPC rev 0x00)
 pcibios0: PCI bus #6 is the last bus
 bios0: ROM list: 0xc/0x8000
 ipmi at mainbus0 not configured
 cpu0 at mainbus0
 pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
 pchb0 at pci0 dev 0 function 0 Intel E7230 MCH rev 0x81
 Intel E7230 PCIE rev 0x81 at pci0 dev 1 function 0 not configured
 Intel 82801GB PCIE rev 0x01 at pci0 dev 28 function 0 not configured
 Intel 82801G PCIE rev 0x01 at pci0 dev 28 function 4 not configured
 Intel 82801G PCIE rev 0x01 at pci0 dev 28 function 5 not configured
 uhci0 at pci0 dev 29 function 0 Intel 82801GB USB rev 0x01: irq 5
 usb0 at uhci0: USB revision 1.0
 uhub0 at usb0
 uhub0: Intel UHCI root hub, rev 1.00/1.00, addr 1
 uhub0: 2 ports with 2 removable, self powered
 uhci1 at pci0 dev 29 function 1 Intel 82801GB USB rev 0x01: irq 10
 usb1 at uhci1: USB revision 1.0
 uhub1 at usb1
 uhub1: Intel UHCI root hub, rev 1.00/1.00, addr 1
 uhub1: 2 ports with 2 removable, self powered
 uhci2 at pci0 dev 29 function 2 Intel 82801GB USB rev 0x01: irq 11
 usb2 at uhci2: USB revision 1.0
 uhub2 at usb2
 uhub2: Intel UHCI root hub, rev 1.00/1.00, addr 1
 uhub2: 2 ports with 2 removable, self powered
 uhci3 at pci0 dev 29 function 3 Intel 82801GB USB rev 0x01: irq 10
 usb3 at uhci3: USB revision 1.0
 uhub3 at usb3
 uhub3: Intel UHCI root hub, rev 1.00/1.00, addr 1
 uhub3: 2 ports with 2 removable, self powered
 ehci0 at pci0 dev 29 function 7 Intel 82801GB USB rev 0x01: irq 5
 usb4 at ehci0: USB revision 2.0
 uhub4 at usb4
 uhub4: Intel EHCI root hub, rev 2.00/1.00, addr 1
 uhub4: 8 ports with 8 removable, self powered
 Intel 82801BA AGP rev 0xe1 at pci0 dev 30 function 0 not configured
 ichpcib0 at pci0 dev 31 function 0 Intel 82801GB LPC rev 0x01: PM disabled
 pciide0 at pci0 dev 31 function 1 Intel 82801GB IDE rev 0x01: DMA, 
 channel 0
 configured to compatibility, channel 1 configured to compatibility
 atapiscsi0 at pciide0 channel 0 drive 0
 scsibus0 at atapiscsi0: 2 targets
 cd0 at scsibus0 targ 0 lun 0: TEAC, CD-224E-N, 1.AA SCSI0 5/cdrom 
 removable
 cd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2
 pciide0: channel 1 ignored (disabled)
 pciide1 at pci0 dev 31 function 2 Intel 82801GB SATA rev 0x01: DMA, 
 channel 0
 configured to native-PCI, channel 1 configured to native-PCI
 pciide1: using irq 10 for native-PCI interrupt
 wd0 at pciide1 channel 0 drive 0: ST3250623NS
 wd0: 16-sector PIO, LBA48, 238475MB, 488397168 sectors
 wd0(pciide1:0:0): using PIO mode 4, Ultra-DMA mode 5
 ichiic0 at pci0 dev 31 function 3 Intel 82801GB SMBus rev 0x01: irq 10
 iic0 at ichiic0
 lm1 at iic0 addr 0x2d: W83627HF
 lm2 at iic0 addr 0x2f: W83792D rev D
 isa0 at ichpcib0
 isadma0 at isa0
 pckbc0 at isa0 port 0x60/5
 pckbd0 at pckbc0 (kbd slot)
 pckbc0: using irq 1 for kbd slot
 wskbd0 at pckbd0: console keyboard
 vga0 at isa0 port 0x3b0/48 iomem 0xa/131072
 wsdisplay0 at vga0 mux 1: console (80x25, vt100 emulation), using wskbd0
 wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
 pcppi0 at isa0 port 0x61
 midi0 at pcppi0: PC speaker
 spkr0 at pcppi0
 lpt0 at isa0 port 0x378/4 irq 7
 lm0 at isa0 port 0x290/8: W83627HF
 lm1 detached
 npx0 at isa0 port 0xf0/16: using exception 16
 pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
 pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
 fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
 biomask ff65 netmask ff65 ttymask ffe7
 pctr: user-level cycle counter 

Re: slow realloc: alternate method?

2006-06-16 Thread Otto Moerbeek
On Fri, 16 Jun 2006, Jacob Yocom-Piatt wrote:

 i've got some C code that is reading from a 800 MB CSV file and allocates 
 memory
 for an array to store the data in. the method used is to read the CSV file
 line-by-line and realloc additional space with each line read. having timed 
 this
 and found the realloc speed to be low when the array is large, i am aiming to
 make this faster but am not sure about the best way to proceed.
 
 the current code uses realloc in the manner suggested by the manpage:
 
 newsize = size + 1;
 time(t1);  // start timing realloc
 if ((newap = (int *)realloc(ap, newsize*sizeof(int))) == NULL) {
 free(ap);
 ap = NULL;
 size = 0;
 return (NULL);
 }
 time(t2);  // stop timing realloc; start timing fscanf
 
 as the size of ap grows, so does the time it takes to realloc the space.
 
 an alternative to this procedure would be to scan through the CSV file to
 determine how many array entries i would need, realloc it all at once, then go
 back through the CSV file again to read the data into the array. i'm not
 confident this is the only way to do this and would appreciate any suggestions
 for speeding up this procedure.

You'll have to think how this works: realloc has to copy the data to
the newly allocated region if it is not able to extend the current
region. 

If you do that for each time you'll increase the allocation size and
your size increment is small, you'll do a lot of work. The way you are
doing it now has quadratic time complexity.

So make your increment larger and start with a larger size. Maybe you
can estimate the initial size based on your file size. If you'll end
up allocating a too large area, just use realloc the decrease the size
after you're done.

Also thing about other data structures: you might be better of with a
linked list or tree here, depending on what you are doing with your
data.

-Otto



Re: mount_msdos error

2006-06-16 Thread Fred Crowson

Stuart Henderson wrote:

On 2006/06/15 16:16, Tony Abernethy wrote:

nike:fred /home/fred fdisk sd1
fdisk: sysctl(machdep.bios.diskinfo): Device not configured
Disk: sd1   geometry: 1980/64/32 [4055040 Sectors]
Offset: 0   Signature: 0xAA55
  Starting   Ending   LBA Info:
  #: idC   H  S -C   H  S [   start:  size   ]

*0: 060   7 32 - 1979  56  1 [ 255: 4054530 ] DOS  32MB

That does not look like ANY DOS disk I've every seen.
The initial sector on the drive has the DOS partition table. (easy to find)
Generally, the first stuff on the drive comes on the track
immediately following that sector.
this is typically after 63 sectors on hard drives,
but a power of 2 (like 32 is more plausible on something electronic)
(64 might work, but I'm sure SOMETHING would find a way to make 64 act like
0)


Who knows what geometry it was formatted with?

FAT boot sector, etc, are quite easy to spot - try 
dd if=/dev/sd1i count=1 | hexdump -C with reference to

another FAT partition that can be mounted successfully
and http://en.wikipedia.org/wiki/File_Allocation_Table
and you'll soon know if the partition table is correct.

I wonder if reformatting the card might get it into
some shape where it can be seen by both camera and
OpenBSD...may be worth dd'ing an image of it as it
currently stands before doing this, so it can be
restored if necessary.


Hi Stuart  Tony,

The output of dd if=/dev/sd1i count=1 | hexdump -C made it quite clear 
that it was a FAT16 partition.


After doing fdisk, disklabel and newfs it is now mounting - thanks for 
the clue sticks :~)


Fred



Re: slow realloc: alternate method?

2006-06-16 Thread veins
On Fri, Jun 16, 2006 at 10:14:07PM +0200, Otto Moerbeek wrote:
 On Fri, 16 Jun 2006, Jacob Yocom-Piatt wrote:
 
  i've got some C code that is reading from a 800 MB CSV file and allocates 
  memory
  for an array to store the data in. the method used is to read the CSV file
  line-by-line and realloc additional space with each line read. having timed 
  this
  and found the realloc speed to be low when the array is large, i am aiming 
  to
  make this faster but am not sure about the best way to proceed.
  
  the current code uses realloc in the manner suggested by the manpage:
  
  newsize = size + 1;
  time(t1);  // start timing realloc
  if ((newap = (int *)realloc(ap, newsize*sizeof(int))) == NULL) {
  free(ap);
  ap = NULL;
  size = 0;
  return (NULL);
  }
  time(t2);  // stop timing realloc; start timing fscanf
  
  as the size of ap grows, so does the time it takes to realloc the space.
  
  an alternative to this procedure would be to scan through the CSV file to
  determine how many array entries i would need, realloc it all at once, then 
  go
  back through the CSV file again to read the data into the array. i'm not
  confident this is the only way to do this and would appreciate any 
  suggestions
  for speeding up this procedure.
 
 You'll have to think how this works: realloc has to copy the data to
 the newly allocated region if it is not able to extend the current
 region. 
 
 If you do that for each time you'll increase the allocation size and
 your size increment is small, you'll do a lot of work. The way you are
 doing it now has quadratic time complexity.
 
 So make your increment larger and start with a larger size. Maybe you
 can estimate the initial size based on your file size. If you'll end
 up allocating a too large area, just use realloc the decrease the size
 after you're done.
 
 Also thing about other data structures: you might be better of with a
 linked list or tree here, depending on what you are doing with your
 data.
 
   -Otto

Also, if the purpose of this is to load the file in memory, why not just
mmap() it in the first place ?



Re: libtool: link: 'format-python.lo'

2006-06-16 Thread Roger Midmore
On Fri, 16 Jun 2006, Roger Midmore wrote:

The port that seems to be broken is gettext since all the other packages
are having problems when they try to install it as a dependency.

 I just got a new laptop and was installing OpenBSD 3.9 on it and I got a
 linking error when I was trying to build clisp from ports. The error is

 libtool: link: 'format-python.lo' is not a valid libtool object

 I also get the same error when I try to install some other software from
 ports like mozilla-firefox and others. They all seem to be related to this
 one problem with libtool. I was wondering if anyone has encountered this
 problem.

 Laptop is a Acer Aspire 3000 with a 1.8 sempron 3100.



Re: slow realloc: alternate method?

2006-06-16 Thread veins
On Fri, Jun 16, 2006 at 10:40:29PM +0200, [EMAIL PROTECTED] wrote:
 On Fri, Jun 16, 2006 at 10:14:07PM +0200, Otto Moerbeek wrote:
  On Fri, 16 Jun 2006, Jacob Yocom-Piatt wrote:
  
   i've got some C code that is reading from a 800 MB CSV file and allocates 
   memory
   for an array to store the data in. the method used is to read the CSV file
   line-by-line and realloc additional space with each line read. having 
   timed this
   and found the realloc speed to be low when the array is large, i am 
   aiming to
   make this faster but am not sure about the best way to proceed.
   
   the current code uses realloc in the manner suggested by the manpage:
   
   newsize = size + 1;
   time(t1);  // start timing realloc
   if ((newap = (int *)realloc(ap, newsize*sizeof(int))) == NULL) {
   free(ap);
   ap = NULL;
   size = 0;
   return (NULL);
   }
   time(t2);  // stop timing realloc; start timing 
   fscanf
   
   as the size of ap grows, so does the time it takes to realloc the space.
   
   an alternative to this procedure would be to scan through the CSV file to
   determine how many array entries i would need, realloc it all at once, 
   then go
   back through the CSV file again to read the data into the array. i'm not
   confident this is the only way to do this and would appreciate any 
   suggestions
   for speeding up this procedure.
  
  You'll have to think how this works: realloc has to copy the data to
  the newly allocated region if it is not able to extend the current
  region. 
  
  If you do that for each time you'll increase the allocation size and
  your size increment is small, you'll do a lot of work. The way you are
  doing it now has quadratic time complexity.
  
  So make your increment larger and start with a larger size. Maybe you
  can estimate the initial size based on your file size. If you'll end
  up allocating a too large area, just use realloc the decrease the size
  after you're done.
  
  Also thing about other data structures: you might be better of with a
  linked list or tree here, depending on what you are doing with your
  data.
  
  -Otto
 
 Also, if the purpose of this is to load the file in memory, why not just
 mmap() it in the first place ?


Ooops ... I was doing two things at the same time and did not finish the
mail before sending it.

So basically, why not mmap() the file, go through the map counting \n
while replacing them by \0 until you reach end of map. allocate an
array the size of the counter and have each array entry point to where
it should in the memory map ?



Fwd: Re: error clamav at 3.9

2006-06-16 Thread riwanlky

Sorry,

I just go to rarlab and get the unrarsrc, put it in the distfiles.
Everything is working now. Clamav up and running.

Thanks,
Riwan



Date: Fri, 16 Jun 2006 08:22:52 +0700
To: Michael Erdely [EMAIL PROTECTED], sonjaya [EMAIL PROTECTED]
From: riwanlky [EMAIL PROTECTED]
Subject: Re: error clamav at 3.9
Cc: misc@openbsd.org

Hi guys,

I am trying to install Clamav on 3.9. Previously I used Clamav on 3.8 and 
without

need to make install the unarj.
Manage to make install unarj. However Clamav require unrar and I got this 
error.

# make install
===  Checking files for unrar-3.54p0
 unrarsrc-3.5.4.tar.gz doesn't seem to exist on this system.
 Fetch http://www.rarlab.com/rar/unrarsrc-3.5.4.tar.gz.
 Size does not match for /usr/ports/distfiles/unrarsrc-3.5.4.tar.gz
/bin/sh: test: unrarsrc-3.5.4.tar.gz: unexpected operator/operand
*** Error code 2

Stop in /usr/ports/archivers/unrar (line 2106 of 
/usr/ports/infrastructure/mk/bsd.port.mk).

*** Error code 1

Stop in /usr/ports/archivers/unrar (line 1561 of 
/usr/ports/infrastructure/mk/bsd.port.mk).

*** Error code 1

Stop in /usr/ports/archivers/unrar (line 1750 of 
/usr/ports/infrastructure/mk/bsd.port.mk).


Thanks and looking forward to get more information.

Brgds,
Riwan

At 12:09 AM 5/5/2006 -0400, Michael Erdely wrote:

sonjaya wrote:

i try using port
# cd /usr/ports/archivers/unarj/
# make install
make: don't know how to make install. Stop in /usr/ports/archivers/unarj.


You've got problems with your ports tree.  rm -Rf /usr/ports and 
re-unpack ports.tar.gz.  I tried on my vanilla 3.9 machine with no problems.


-ME

--
Support OpenBSD: http://www.openbsd.org/orders.html




Re: slow realloc: alternate method?

2006-06-16 Thread Otto Moerbeek
On Fri, 16 Jun 2006, [EMAIL PROTECTED] wrote:

 So basically, why not mmap() the file, go through the map counting \n
 while replacing them by \0 until you reach end of map. allocate an
 array the size of the counter and have each array entry point to where
 it should in the memory map ?

I implemented a similar technique in patch(1), minus the '\n' - '\0'
replacing; patch does not use NUL terminated strings internally.

But it all depends on which data is being stored: just the lines from
the file, or data based on the chars found in the file.

-Otto



Re: slow realloc: alternate method?

2006-06-16 Thread veins
On Fri, Jun 16, 2006 at 11:17:39PM +0200, Otto Moerbeek wrote:
 On Fri, 16 Jun 2006, [EMAIL PROTECTED] wrote:
 
  So basically, why not mmap() the file, go through the map counting \n
  while replacing them by \0 until you reach end of map. allocate an
  array the size of the counter and have each array entry point to where
  it should in the memory map ?
 
 I implemented a similar technique in patch(1), minus the '\n' - '\0'
 replacing; patch does not use NUL terminated strings internally.
 
 But it all depends on which data is being stored: just the lines from
 the file, or data based on the chars found in the file.
 
   -Otto


Yup,
I used this in (function splitfields) where the delimiter was chosen
with getopt:

http://etudiant.epitech.net/~veins/sort/sort.c



Re: slow realloc: alternate method?

2006-06-16 Thread Jacob Yocom-Piatt
 Original message 
Date: Fri, 16 Jun 2006 22:14:07 +0200 (CEST)
From: Otto Moerbeek [EMAIL PROTECTED]  
Subject: Re: slow realloc: alternate method?  
To: Jacob Yocom-Piatt [EMAIL PROTECTED]
Cc: misc@openbsd.org


So make your increment larger and start with a larger size. Maybe you
can estimate the initial size based on your file size. If you'll end
up allocating a too large area, just use realloc the decrease the size
after you're done.

Also thing about other data structures: you might be better of with a
linked list or tree here, depending on what you are doing with your
data.

thx for all the suggestions guys. i like the idea of allocating too much space
and trimming it at the end.

the data is tick price data and once it's read into an array, it is searched for
patterns by accessing elements in sequence. linked lists were mentioned by
someone offlist.



Re: Tracking security advisories

2006-06-16 Thread Adam VanderHook
On Fri, Jun 16, 2006 at 09:47:51AM -0700, Spruell, Darren-Perot wrote:
 For sysadmins that want to know as soon as possible about issues which
 are deemed patch-worthy (security vulnerabilities, critical
 reliability issues), what is the best way to stay on top of these
 issues as they are resolved?

OpenBSD Journal (undeadly.org) has an OpenBSD Errata sidebar which,
from what I can tell, they maintain themselves and is pretty reliable.
It also has an associated RSS feed (http://undeadly.org/cgi?action=errata)
that you can poll too.  I have a Python script that uses the 'feedparser'
library to watch after infrequently updated RSS feeds like this and
send me e-mail notification, and has been working pretty good.

Adam

-- 
Adam VanderHook
[EMAIL PROTECTED]
http://acidos.bandwidth-junkies.net/



Re: Tracking security advisories

2006-06-16 Thread Travers Buda
I'm patched, only because I pay attention to [EMAIL PROTECTED] It would
be nice to have security-announce@ be really used. It would't be much
effort to send some blurb like: new patch, check the ftp. That's all
that is really required. Can anyone post to [EMAIL PROTECTED]
Someone has to step up, and that person ought to be official, lest
misc@ and security-announce@ get flooded with frantic screamings of
armageddon (or posting is denied to unofficial persons. I don't know
the staus on that.)  

In all fairness, it was a simple DOS vulnerability. Not too serious. In
the case that a root shell exploit is possible, you'll probably hear
about it (it will be posted asap.) But speaking of fairness, I would
like all patches to be treated the same.

We have security-announce, and many people _expect_ it to be used for
_every_ patch. Please no cracks about paranoia, I'm running low on tin-
foil so my nerves are going bad.

Security patch
announcements are sent to the [EMAIL PROTECTED] mailing
list.

Travers


On Fri, 16 Jun 2006 09:47:51 -0700
Spruell, Darren-Perot [EMAIL PROTECTED] wrote:

 For sysadmins that want to know as soon as possible about issues which
 are deemed patch-worthy (security vulnerabilities, critical
 reliability issues), what is the best way to stay on top of these
 issues as they are resolved?
 
 The canonical source of information seems to be errta.html, which does
 tend to be updated quickly as the patch becomes available. To keep
 track of this, it requires the user to access the page and look for a
 new patch which may apply to him.
 
 One could also monitor commits to CVS and while reliable, it becomes a
 bit more difficult to pick the critical from some of the rest of it.

 Then, as outlined in release announcements, Security patch
 announcements are sent to the [EMAIL PROTECTED] mailing
 list. This method is preferred by a lot of people so they get some
 kind of proactive notification of potentially impactive problems.
 Patch announcements do make it to the list, some as early as 1 day
 after patch announcement, others 14 days after patch. The possible
 advantage over errata.html though is you get notified even if you've
 lapsed in checking out the web page. On the flip side, this requires a
 developer to take time and craft the message and send it, so the onus
 is on the project to do the work.
 
 DS



Re: Tracking security advisories

2006-06-16 Thread Spruell, Darren-Perot
From: Travers Buda via [EMAIL PROTECTED] 

[snip attitude I intentionally avoided in my original posting,]

 Security patch
 announcements are sent to the [EMAIL PROTECTED] mailing
 list.

And in fairness, announcments *are* sent to the list. Check the archives.
They end up there. Some are quite immediate, others can take some time. I
haven't tried to correlate urgency of a patch relative to urgency of post; I
assume that serious ones make it there and I take due diligence in checking
the errata page frequently.

Not _my_ intention to drag this into a post to the list or else you
bastards, simply wondering what's the best way to keep on top of it.

Incidentally, the RSS feed works good for me. I have a reader that pops
notifications on update. Timely notification via a mailing list would work
equally as well.

DS



Re: Tracking security advisories

2006-06-16 Thread Martin Schröder

2006/6/17, Spruell, Darren-Perot [EMAIL PROTECTED]:

And in fairness, announcments *are* sent to the list. Check the archives.


_Recently_ some have been sent. Please check the archives. Did you get
any mail for fixes 1,2  5 of 3.8? The archives didn't.

Best
   Martin



Re: Kernel Hangs; Supermicro 5015M-MR (Intel E7230)

2006-06-16 Thread Jon Holderith

With flags 2 it hangs at:
pcibios0: PCI Interrupt Router at 000:31:0 (Intel 82801GB LPC rev 0x00)

Disabling pcibios has the same result as flags 1

I've tried setting other flags listed in the pcibios man page.  The only flag 
that gives me anything different is flag 20


I setup a serial console to capture the output when setting flags 20


 OpenBSD/i386 BOOT 2.10
boot -c
booting hd0a:/bsd: 5167328+868176 [52+265088+246821]=0x63e980
entry point at 0x200120
   m
[ using 512336 bytes of bsd ELF symbol table ]
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California.  All rights reserved.
Copyright (c) 1995-2006 OpenBSD. All rights reserved.  http://www.OpenBSD.org

OpenBSD 3.9-current (GENERIC) #882: Thu Jun 15 12:43:50 MDT 2006
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel(R) Pentium(R) D CPU 2.80GHz (GenuineIntel 686-class) 2.77 GHz
cpu0: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,CNXT-ID,CX16

real mem  = 1072128000 (1047000K)
avail mem = 970346496 (947604K)
using 4256 buffers containing 53710848 bytes (52452K) of memory
User Kernel Config
UKC change pcibios
284 pcibios0 at bios0 flags 0x0
change (y/n) ?
flags [0] ? 20
284 pcibios0 changed
284 pcibios0 at bios0 flags 0x14
UKC quit
Continuing...
mainbus0 (root)
bios0 at mainbus0: AT/286+(57) BIOS, date 04/17/06, BIOS32 rev. 0 @ 0xfd470, 
SMBIOS rev. 2.51 @ 0x3feea000 (33 entries)

bios0: Supermicro PDSMi
pcibios0 at bios0: rev 2.1 @ 0xfd470/0xb90
pcibios0: config mechanism [1][x], special cycles [x][x], last bus 10
PCI bridge 0: primary 0, secondary 1, subordinate 1
PCI bridge 1: primary 2, secondary 3, subordinate 3
PCI bridge 2: primary 0, secondary 2, subordinate 3
PCI bridge 3: primary 0, secondary 4, subordinate 4
PCI bridge 4: primary 0, secondary 5, subordinate 5
PCI bridge 5: primary 0, secondary 6, subordinate 6
pcibios0: PCI bus #6 is the last bus
[System BIOS Setting]---
  device vendor product
  register space addresssize

000:00:0 8086:2778
[OK]
000:01:0 8086:2779



mickey wrote:

On Fri, Jun 16, 2006 at 10:39:44AM -0800, Jon Holderith wrote:

Supermicro 5015M-MR uses Supermicro PDSMi motherboard (Intel E7230 chipset)

Kernel hangs after pcibios0: PCI bus #6 is the last bus
Changed pcibios flags to 1 with UKC and enabled verbose mode.
Kernel then hangs during ppb probe
Changed pcibios flags to 1 and disabled ppb and Kernel finished loading.

Same result with bsd.mp

Is there anything else I can try that will shed more light on this issue?


yes. flags 2 or otherwise just disable pcibios completely.


OpenBSD 3.9-current (GENERIC) #882: Thu Jun 15 12:43:50 MDT 2006
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel(R) Pentium(R) D CPU 2.80GHz (GenuineIntel 686-class) 2.78 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,CNXT-ID,CX16
real mem  = 1072128000 (1047000K)
avail mem = 970346496 (947604K)
using 4256 buffers containing 53710848 bytes (52452K) of memory
User Kernel Config
UKC change pcibios
284 pcibios0 at bios0 flags 0x0
change (y/n) ?
flags [0] ? 1
284 pcibios0 changed
284 pcibios0 at bios0 flags 0x1
UKC disable ppb
 89 ppb* disabled
UKC quit
Continuing...
mainbus0 (root)
bios0 at mainbus0: AT/286+(66) BIOS, date 04/17/06, BIOS32 rev. 0 @ 0xfd470,
SMBIOS rev. 2.51 @ 0x3feea000 (33 entries)
bios0: Supermicro PDSMi
pcibios0 at bios0: rev 2.1 @ 0xfd470/0xb90
pcibios0: PCI BIOS has 20 Interrupt Routing table entries
pcibios0: PCI Interrupt Router at 000:31:0 (Intel 82801GB LPC rev 0x00)
pcibios0: PCI bus #6 is the last bus
bios0: ROM list: 0xc/0x8000
ipmi at mainbus0 not configured
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 Intel E7230 MCH rev 0x81
Intel E7230 PCIE rev 0x81 at pci0 dev 1 function 0 not configured
Intel 82801GB PCIE rev 0x01 at pci0 dev 28 function 0 not configured
Intel 82801G PCIE rev 0x01 at pci0 dev 28 function 4 not configured
Intel 82801G PCIE rev 0x01 at pci0 dev 28 function 5 not configured
uhci0 at pci0 dev 29 function 0 Intel 82801GB USB rev 0x01: irq 5
usb0 at uhci0: USB revision 1.0
uhub0 at usb0
uhub0: Intel UHCI root hub, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1 at pci0 dev 29 function 1 Intel 82801GB USB rev 0x01: irq 10
usb1 at uhci1: USB revision 1.0
uhub1 at usb1
uhub1: Intel UHCI root hub, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
uhci2 at pci0 dev 29 function 2 Intel 82801GB USB rev 0x01: irq 11
usb2 at uhci2: USB revision 1.0
uhub2 at usb2
uhub2: Intel UHCI root hub, rev 1.00/1.00, addr 1
uhub2: 2 ports with 2 removable, self powered
uhci3 at pci0 dev 29 function 3 Intel 82801GB USB rev 0x01: 

Re: slow realloc: alternate method?

2006-06-16 Thread Matthew R. Dempsky
On Fri, Jun 16, 2006 at 10:55:05AM -0500, Jacob Yocom-Piatt wrote:
 the current code uses realloc in the manner suggested by the manpage:
 
 newsize = size + 1;
 time(t1);  // start timing realloc
 if ((newap = (int *)realloc(ap, newsize*sizeof(int))) == NULL) {
 free(ap);
 ap = NULL;
 size = 0;
 return (NULL);
 }
 time(t2);  // stop timing realloc; start timing fscanf
 
 as the size of ap grows, so does the time it takes to realloc the space.

Growing your array by only a constant amount each iteration takes 
quadratic time.  By instead doubling the array size each time as 
necessary, you can reduce this to (amortized) linear time.  (I believe 
the man page's intention was to show how to avoid leaking memory, not 
how to write an efficient program.)

Alternatively, just do as others have suggested and mmap() the file and 
make an extra preliminary pass.



3.9 release 1st boot: kernel: stopped at scan_smbios

2006-06-16 Thread Craig Skinner
Hi List,

I've just installed 3.9 RELEASE on an i386 and got a kernel page fault.

Booted the box from the floppy39.fs, sliced the disk, installed some
sets  rebooted, as per normal.

I don't use this box very often and the last release I had on it was
3.6, which worked fine.

Where do I go from here? 3.8?

I piped the boot output from tip into a file:

=07connected=0D
=FC OpenBSD/i386 BOOT 2.10
=0Dbooting hd0a:/bsd: \=08|=08/=08-=08\=084966344|=08/=08-=08\=08|=08/=08-=
=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08=
/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=
=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08=
-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=
=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08=
\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=
=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08=
|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=
=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08=
/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=
=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08=
-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=
=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08=
\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=
=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08=
|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=
=08\=08+867848 [52+255872|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=
=08/=08-=08+237161\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=
=08]=3D0x608d64
entry point at 0x100120

[ using 493460 bytes of bsd ELF symbol table ]
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California.  All rights reserved.
Copyright (c) 1995-2006 OpenBSD. All rights reserved.  http://www.OpenBSD.o=
rg

OpenBSD 3.9 (GENERIC) #617: Thu Mar  2 02:26:48 MST 2006
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel Pentium III (GenuineIntel 686-class, 128KB L2 cache) 635 MHz
cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE=
36,MMX,FXSR,SSE
real mem  =3D 199729152 (195048K)
avail mem =3D 175271936 (171164K)
using 2463 buffers containing 10088448 bytes (9852K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(00) BIOS, date 01/15/99, BIOS32 rev. 0 @ 0xfdb70
apm0 at bios0: Power Management spec V1.2
apm0: AC on, battery charge unknown
apm0: flags 30102 dobusy 0 doidle 1
pcibios0 at bios0: rev 2.1 @ 0xf/0x1
pcibios0: PCI BIOS has 9 Interrupt Routing table entries
pcibios0: PCI Interrupt Router at 000:31:0 (Intel 82801AA LPC rev 0x00)
pcibios0: PCI bus #1 is the last bus
bios0: ROM list: 0xc/0x8000
uvm_fault(0xd05c2f60, 0xdeeb8000, 0, 1) - e
kernel: page fault trap, code=3D0
Stopped at  scan_smbios+0xb9:   cmpb$0,0(%ebx)
ddb=20



Re: Tracking security advisories

2006-06-16 Thread Travers Buda
On Fri, 16 Jun 2006 15:26:16 -0700
Spruell, Darren-Perot [EMAIL PROTECTED] wrote:

 Not _my_ intention to drag this into a post to the list or else you
 bastards, simply wondering what's the best way to keep on top of it.

Hey, I'm in _no_ position to demand anything. 

How about security-announce be opened up for anyone to post to? Then
when there is a patch... you get the idea. Devs won't have to post and
the aggregate bitching on misc will go down. =)

I'm just having a hard time understanding why security-announce is
slipping. It is not inline with the attitude of OpenBSD.

Do these patches even matter? Since no one with coding prowess around
here seems to think so, then I could understand the lack-luster attitude
to security-announce. 

Furthermore, many people are using security-announce as their sole
notification method. These people are not just the paranoid patch-at-
once type either. 

Please (see, I'm not demanding) either open up the list, or just delete
it all togeather. It's giving people a false sense of being up-to-date
or informed. 

Travers


Travers



Re: 3.9 release 1st boot: kernel: stopped at scan_smbios

2006-06-16 Thread Travers Buda
Looks like a crappy bios (pardon the redundancy,) try

boot boot -c

UKC  disable pcibios
UKC  quit

Travers

On Sat, 17 Jun 2006 00:45:29 +0100
Craig Skinner [EMAIL PROTECTED] wrote:

 Hi List,
 
 I've just installed 3.9 RELEASE on an i386 and got a kernel page
 fault.
 
 Booted the box from the floppy39.fs, sliced the disk, installed some
 sets  rebooted, as per normal.
 
 I don't use this box very often and the last release I had on it was
 3.6, which worked fine.
 
 Where do I go from here? 3.8?
 
 I piped the boot output from tip into a file:
 
 =07connected=0D
 =FC OpenBSD/i386 BOOT 2.10
 =0Dbooting hd0a:/bsd: \=08|=08/=08-=08\=084966344|=08/=08-=08\=08|=08/
 =08-= =08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-
 =08\=08|=08= /=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08
 \=08|=08/=08-=08\= =08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08
 \=08|=08/=08-=08\=08|=08/=08= -=08\=08|=08/=08-=08\=08|=08/=08-=08
 \=08|=08/=08-=08\=08|=08/=08-=08\=08|= =08/=08-=08\=08|=08/=08-=08
 \=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08= \=08|=08/=08-=08
 \=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/= =08-=08
 \=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08=
 |=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/
 =08-= =08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-
 =08\=08|=08= /=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08
 \=08|=08/=08-=08\= =08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08
 \=08|=08/=08-=08\=08|=08/=08= -=08\=08|=08/=08-=08\=08|=08/=08-=08
 \=08|=08/=08-=08\=08|=08/=08-=08\=08|= =08/=08-=08\=08|=08/=08-=08
 \=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08= \=08|=08/=08-=08
 \=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/= =08-=08
 \=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08=
 |=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/
 =08-= =08\=08+867848 [52+255872|=08/=08-=08\=08|=08/=08-=08\=08|=08/
 =08-=08\=08|= =08/=08-=08+237161\=08|=08/=08-=08\=08|=08/=08-=08\=08|
 =08/=08-=08\=08|=08/= =08]=3D0x608d64 entry point at 0x100120
 
 [ using 493460 bytes of bsd ELF symbol table ]
 Copyright (c) 1982, 1986, 1989, 1991, 1993
   The Regents of the University of California.  All rights
 reserved. Copyright (c) 1995-2006 OpenBSD. All rights reserved.
 http://www.OpenBSD.o= rg
 
 OpenBSD 3.9 (GENERIC) #617: Thu Mar  2 02:26:48 MST 2006
 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
 cpu0: Intel Pentium III (GenuineIntel 686-class, 128KB L2 cache)
 635 MHz cpu0:
 FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE=
 36,MMX,FXSR,SSE real mem  =3D 199729152 (195048K)
 avail mem =3D 175271936 (171164K)
 using 2463 buffers containing 10088448 bytes (9852K) of memory
 mainbus0 (root)
 bios0 at mainbus0: AT/286+(00) BIOS, date 01/15/99, BIOS32 rev. 0 @
 0xfdb70 apm0 at bios0: Power Management spec V1.2
 apm0: AC on, battery charge unknown
 apm0: flags 30102 dobusy 0 doidle 1
 pcibios0 at bios0: rev 2.1 @ 0xf/0x1
 pcibios0: PCI BIOS has 9 Interrupt Routing table entries
 pcibios0: PCI Interrupt Router at 000:31:0 (Intel 82801AA LPC rev
 0x00) pcibios0: PCI bus #1 is the last bus
 bios0: ROM list: 0xc/0x8000
 uvm_fault(0xd05c2f60, 0xdeeb8000, 0, 1) - e
 kernel: page fault trap, code=3D0
 Stopped at  scan_smbios+0xb9:   cmpb$0,0(%ebx)
 ddb=20



cruxports for OpenBSD

2006-06-16 Thread Han Boetes
Hi,

I've been working for quite some time now on an alternative
package-manager for OpenBSD, and since things start working rather
fine now I think it's time to let you guys know.

Lets dive in deep and take a look at a Pkgfile; the description of
a port:
-
# Description: A tool for transfering files with URL syntax
# Maintainer: Han Boetes [EMAIL PROTECTED]
# URL: http://curl.haxx.se
# Depends:

name=curl
version=7.15.3
release=1
source=http://curl.haxx.se/download/$name-$version.tar.bz2;

build()
{
cd $name-$version
./configure \
--prefix=/usr/local \
--with-random=/dev/arandom
make
make install DESTDIR=$PKG
}
-

As you can see it contains nothing more than the bare minimum
which defines how to build and fake-install a source-code package.

If you can see why this is an advantage to you please read on:


In 2000 Per Liden started CRUX-Linux, a distro based on
simplicity. The idea for the ports system was influenced by BSD
ports, but written in sh and C++, the Pkgfiles which define how a
package should be build are nothing but simple shell-scripts.

Cruxports for OpenBSD is a port/rewrite of the CRUX ports-system
to OpenBSD, and is completely written in sh, except for a simple
parser written in C.

Now I hear you say: What's wrong with the normal ports?
Well... wrong is a big word. It's just a matter of personal
preference I think. But let me give you a list of reasons why I
prefer cruxports.

 * Lightweight.
 * Always the latest versions of software, no matter which
   release you use.
 * CRUX ports are much easier to create and maintain since the
   ports are shell-based.
 * Portable, anyone can read and understand a cruxport.
 * Dependencies are optional.
 * It's not trying to be braindead-proof.
 * No checking of md5sum on uninstall of files.
 * Files in /etc are installed, and maintained with a mergemaster
   like application (rejmerge) in a sane and easy way.
 * You can easily share your own ports with others with httpup.
 * Does not conflict with other package-managers.
 * You can build packages from alternative sources like
   binaries or CVS.

my c4o page can be found at:

  http://www.xs4all.nl/~hanb/software/c4o/



# Han



Re: Hifn policy on documentation

2006-06-16 Thread Siju George

Hi all,

I 've been told by people ( more than one ) off list how *uncivilized*
it is to forward *private* mail publicly *even when it has some bad
content*.

And I have been asked to apologize publicly ( not by Hank Cohen ).

Without trying to Justify my points any more I apologize doing this.
I am wrong. I accept it.

Sorry Hank. I know the damage is done. But I 'll make sure that it is
not repeated anymore.

And thank you so much for all who sent the mails of reproof and correction.
Thank you for taking effort to put me in the right track.
And thank you so much for all who silently put up with this misbehaviour.

Kind Regards

Siju

On 6/14/06, Siju George [EMAIL PROTECTED] wrote:

Hi all,

This is the mail I got from Hifn representative for my response to his
mail and clarifications in misc.

This mail was sent to me privately and I am well aware of the fact
that it is not good manners to make private mails public. In that way
i am just going down a little bit down on that. let people see the
response they get from Hifn.

And Mr. Cohen, If what you sent to the list was indeed not a lie then
I sincerly apologize mentioning that you were lying in my previously
mail. I apologize publicly just as I mentioned it publicly.

Also I would like to let you know very humbly that this may not be a
very good way of treating your potential customers.

Thanks for you complements any way :-)

Good Luck ahead with this policy of your company and you personal behaviour.

Kind regards

--Siju




-- Forwarded message --
From: Hank Cohen [EMAIL PROTECTED]
Date: Jun 14, 2006 10:43 AM
Subject: RE: Hifn policy on documentation
To: Siju George [EMAIL PROTECTED]


Mr. george.
I do not appreciate being accused of lying.
If you choose not to use Hifn products then so be it.
I have announced our policy in good faith and been treated to
a barrage of insult and invective.   If I were speaking on my own
account I would feel free to tell you what I really think of this kind
of bullshit but I cannot do so since I will always be seen as a
representative of my company.

You sir have the manners of a pig.  And I shall surely never
recommend your IT and Media services to anyone either.
Having said that perhaps you can understand how much your
threats are likely to have the result that you desire.

Hank Cohen
On my own account.




--
Siju Oommen George, Network Consultant. HiFX IT  MEDIA SERVICES PVT.
LTD. http://www.hifx.net