Re: OT: Plea for HELP on dual boot MAC/OpenBSD disaster with refit that turn really bad! (Fixed)

2009-05-02 Thread Daniel Ouellet

HI,

OK, for the archive of may be for an other unlucky sole that may be 
loosing sleep over this like I did for the last two days.


I know it's not an OpenBSD specific subject, but never the less 
countless google research, tests and some support emails that kept me 
going deserved an archive results for this.


If for no one else then myself, I know I will find it in the future if I 
need this again.


Plus something tells me that Nick most likely would be interested to 
know the outcome! (;>


Many thanks Nick for giving me hope and for a few other guys that send 
me some isolate support emails along the way.


Now 30+ some hours later it's fix.

Real simple solution as usual, but HELL to get there!

What was very helpful as a start what this details here:

http://blog.csdn.net/hotsolaris/archive/2008/12/23/3589039.aspx

This show that the same partition is available in to places and the 
accident messed up the first (master) one.


The issue was to get the backup to restore the main one.

All the refit info didn't help, now the efi, witch I knew nothing about 
two days ago, nor about refit either.


But the trick is to force mac and refit indirectly to see a dummy 
MBR/GPT record at the start of the disk on the first LBA1 and then see 
that it is not according to the backup one, but accept as valid GPT/MBR 
to force the update and creation of a new one for valid backup data.


So, the end solution was as simple as creating a fake dummy MBR record 
for this action, witch obvioulsy needs some specific details in it for 
this to happened. Doesn't matter if the partition is with what ever OS 
you want and as many as you want really, even if the MBR is limited to 4 
only.


You create a HEX file with the following content in it.

  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 
||

*
01c0  01 00 ee fe ff ff 01 00  00 00 af ea 42 25 00 00 
|B%..|
01d0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 
||

*
01f0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 55 aa 
|..U.|

0200

I saved this in a file called dummymbr.

Then I needed to boot the MAC laptop in OpenBSD, well, that's what I am 
more comfortable with, so use what ever you like I guess, but this was good.


First step was to by an identical drive to do the backup to it, so I 
could experiment with.


I did this first thing n the morning when the computer store open here. 
I was in line to get the drive.


I got the exact same model the previously, just in case.

Western Digital 250 GB Sata, model WD2500BEVSRTL

I took the old drive out of the laptop and put it into an external USP 
to Sata enclosure. Why, well, the external unit is self power and I 
figure it would take some time and writing should take more power then 
reading form it, so I figure may as well put the new drive in the laptop 
and the original drive external to save on the USB, just in case.


I also got a USB memory stick, 4GB and pop in my OpenBSD CD into the 
laptop and did an install on the USB stick view as SD0. Didn't do any 
special partition, just one / and called it recover. (;>


After it was installed on the USB, well, the laptop didn't boot from the 
USB stick. (;<


So, I needed to find a way to get that going.

I downloaded the refit ISO image and created myself a CD with it.

Get it from the project here:

http://refit.sourceforge.net/

Then pop it in the MAC laptop and holding the c key to boot from the CD 
with my OpenBSD USB stick in the laptop USB port, it saw it and allow me 
to boot directly in OpenBSD.


I did that and then finally I was in some familiar territory.

I plug the USB/Sata external inclosure's in the Laptop and OpenBSD saw 
it and presented it as SD1. SD0 is by UBS flash.


Then I did the image of the drive from the external broken one to the 
new clean internal one.


dd if=/dev/rsd1c of=/dev/rwd0c bs=1m

And let that go. Took for ever and I had no clue of progress.

Then 11072 seconds later it was done. Men, I am glad that was UBS 2.0 as 
1.1, or 1.0 I would still be there next week!


Then unplug the original drive, put it away just to be safe!

Then started the fun part. Well, not so fun but anyway at the end, it 
was simple. It is always simple when the right step are know damit!


So, with my HEX file as above on my flash drive with my copy of the 
broken drive in the laptop with the first block replace by the original 
install stoped.


I had to simply do:

dd if=/dummymbr of=/dev/rwd0c bs=512 count=1

Then I checked to be sure it was what I wanted:

hexdump -Cn512 /dev/rwd0c

So, it was replaced by what I wanted.

Then just rebooted the laptop and hope for the best after countless 
other tests and try.


Then to normal refit came up with the MAC partition and the OpenBSD have 
no boot, but that's for an other day, however, the data, just like 
before with all data intact and nothing lost at all anywhere!


Then you can once more go back as the original time t

Re: Error while applying 001_openssl.patch on OpenBSD 4.5

2009-05-02 Thread freemp

Ya, right, it's my fault.

However, as usually, I exactly followed the instructions in the patch file:

=
This is version 2 of this patch.

Apply by doing:
cd /usr/src
patch -p0 < 001_openssl.patch

And then rebuild and install the library and statically-linked binaries
that depend upon it:

cd lib/libssl
make obj
make depend
make includes
make
make install
cd ../../sbin
make obj
make depend
make
make install
=

I guess that's the way to go, isn't it?




Theo de Raadt wrote:

Well, you did not build your tree correctly.  It is well documented in
'man release' and in the /usr/src/Makefile

I just tried to patch a virgin OpenBSD 4.5 installation by applying 
001_openssl.patch (Version 2).


After successfully rebuilding and installing the library, as well as 
successfully rebuilding the statically linked binaries, running 'make 
install' in /usr/src/sbin fails as follows:


== snip 
...
===> fsck
install -c -s -o root -g bin  -m 555 fsck /sbin/fsck
install -c -o root -g bin -m 444 fsck.cat8 /usr/share/man/cat8/fsck.0
===> fsck_ext2fs
install -c -s -o root -g bin  -m 555 fsck_ext2fs /sbin/fsck_ext2fs
install -c -o root -g bin -m 444 fsck_ext2fs.cat8 
/usr/share/man/cat8/fsck_ext2fs.0

===> fsck_ffs
install -c -s -o root -g bin  -m 555 fsck_ffs /sbin/fsck_ffs
install -c -o root -g bin -m 444 fsck_ffs.cat8 
/usr/share/man/cat8/fsck_ffs.0

===> fsck_ffs/SMM.doc
install -c -o root -g bin -m 444  Makefile 0.t 1.t 2.t 3.t 4.t 
/usr/share/doc/smm/03.fsck_ffs

install: Target: /usr/share/doc/smm/03.fsck_ffs
*** Error code 71

Stop in /usr/src/sbin/fsck_ffs/SMM.doc (line 47 of 
/usr/share/mk/bsd.doc.mk).

*** Error code 1

Stop in /usr/src/sbin/fsck_ffs (line 48 of /usr/share/mk/bsd.subdir.mk).
*** Error code 1

Stop in /usr/src/sbin (line 48 of /usr/share/mk/bsd.subdir.mk).
#

== snip 

Here's my dmesg output (MAC addresses deleted):

OpenBSD 4.5 (GENERIC) #1749: Sat Feb 28 14:51:18 MST 2009
 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel Pentium II ("GenuineIntel" 686-class, 512KB L2 cache) 267 MHz
cpu0: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR

real mem  = 200830976 (191MB)
avail mem = 185782272 (177MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 12/28/99, BIOS32 rev. 0 @ 0xfcc22
apm0 at bios0: Power Management spec V1.2
apm0: battery life expectancy 100%
apm0: AC on, battery charge high, estimated 2:25 hours
pcibios0 at bios0: rev 2.1 @ 0xf/0x1
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xf0ec0/144 (7 entries)
pcibios0: PCI Interrupt Router at 000:05:0 ("Intel 82371FB ISA" rev 0x00)
pcibios0: PCI bus #21 is the last bus
bios0: ROM list: 0xc/0xc000
cpu0 at mainbus0: (uniprocessor)
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "Intel 82443BX AGP" rev 0x02
intelagp0 at pchb0
agp0 at intelagp0: aperture at 0xe000, size 0x1000
ppb0 at pci0 dev 1 function 0 "Intel 82443BX AGP" rev 0x02
pci1 at ppb0 bus 1
vga1 at pci1 dev 3 function 0 "S3 ViRGE MX" rev 0x06
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
piixpcib0 at pci0 dev 5 function 0 "Intel 82371AB PIIX4 ISA" rev 0x02
pciide0 at pci0 dev 5 function 1 "Intel 82371AB IDE" rev 0x01: DMA, 
channel 0 wired to compatibility, channel 1 wired to compatibility

wd0 at pciide0 channel 0 drive 0: 
wd0: 16-sector PIO, LBA, 4887MB, 10009440 sectors
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2
atapiscsi0 at pciide0 channel 1 drive 0
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0:  ATAPI 
5/cdrom removable

cd0(pciide0:1:0): using PIO mode 4, DMA mode 2
uhci0 at pci0 dev 5 function 2 "Intel 82371AB USB" rev 0x01: irq 11
piixpm0 at pci0 dev 5 function 3 "Intel 82371AB Power" rev 0x02: SMBus 
disabled
"Toshiba Fast Infrared Type O" rev 0x33 at pci0 dev 9 function 0 not 
configured

cbb0 at pci0 dev 11 function 0 "Toshiba ToPIC97 CardBus" rev 0x44: irq 11
cbb1 at pci0 dev 11 function 1 "Toshiba ToPIC97 CardBus" rev 0x44: irq 11
vendor "Toshiba", unknown product 0x0406 (class multimedia subclass 
video, rev 0x04) at pci0 dev 12 function 0 not configured
vendor "Toshiba", unknown product 0x0407 (class multimedia subclass 
miscellaneous, rev 0x02) at pci0 dev 13 function 0 not configured

isa0 at piixpcib0
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, using wsdisplay0
pms0 at pckbc0 (aux slot)
pckbc0: using irq 12 for aux slot
wsmouse0 at pms0 mux 0
pcppi0 at isa0 port 0x61
midi0 at pcppi0: 
spkr0 at pcppi0
npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 1

Re: How do I enable bsd.mp kernel in 4.4/i386?

2009-05-02 Thread Theo de Raadt
> Another way would be through creating/editing /etc/boot.conf and  
> having an entry for the mp kernel
> ex:  boot wd0a:/bsd.mp
> 
> where wd0a is your root partition.

I recommend against that.

Firstly, one developer has already been fried on an upgrade using the
-current bsd.rd

Secondly, it is not portable to all our architectures, so why do it?



Re: How do I enable bsd.mp kernel in 4.4/i386?

2009-05-02 Thread Nick Holland
Parvinder Bhasin wrote:
> Another way would be through creating/editing /etc/boot.conf and  
> having an entry for the mp kernel
> ex:  boot wd0a:/bsd.mp
> 
> where wd0a is your root partition.
> 
> -Parvinder Bhasin

but don't do it this way.
not only did it not improve things in the past, it will
make things less fun in the future.

it's also quite i386/amd64-centric.

Nick.



Olha cuidado viu fique de olho aberto!

2009-05-02 Thread Carla Gemaque
Ola, Desculpe-me pela minha fraqueza! Sinto muito em nco poder te falar
pessoalmente, fico ati meia constrangida em te falar por e-mail, mais me
sinto na obrigagco de te avisar, abra os olhos, estco traindo vocj. Eu
sei que i difmcil de acreditar mais como as imagens valem mais do que as
palavras, estou te enviando essas fotos para que vocj veja com seus
prsprios olhos. Se cuida... um grande abrago. --> De um amiga que te quer
bem!.

Ver Aqui as fotos !!!



Re: How do I enable bsd.mp kernel in 4.4/i386?

2009-05-02 Thread Parvinder Bhasin
Another way would be through creating/editing /etc/boot.conf and  
having an entry for the mp kernel

ex:  boot wd0a:/bsd.mp

where wd0a is your root partition.

-Parvinder Bhasin

On May 2, 2009, at 5:03 PM, Anon Y. Mous wrote:


I am running OBSD 4.4/i386 on a Dell Inspiron 6400 (E1505) w/ 2GB RAM
and a 2.0 GHz Intel Core 2 Duo CPU ("Merom").

I am running the GENERIC OBSD 4.4/i386 'bsd' kernel and would like
to set up the bsd.mp kernel instead.

How do I go about this?

Attached is my dmesg as a text file.

-minsai
OpenBSD 4.4 (GENERIC) #1021: Tue Aug 12 17:16:55 MDT 2008
   dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz ("GenuineIntel" 686- 
class) 2 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,TM,SBF,SSE3,MWAIT,DS- 
CPL,VMX,EST,TM2,CX16,xTPR

real mem  = 2145820672 (2046MB)
avail mem = 2066497536 (1970MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 06/13/07, BIOS32 rev. 0 @  
0xffa10, SMBIOS rev. 2.4 @ 0xf7980 (44 entries)

bios0: vendor Dell Inc. version "A17" date 06/13/2007
bios0: Dell Inc. MM061
acpi0 at bios0: rev 0
acpi0: tables DSDT FACP HPET APIC MCFG SLIC BOOT SSDT SSDT
acpi0: wakeup devices LID_(S3) PBTN(S4) MBTN(S5) PCI0(S3) USB0(S0)  
USB1(S0) USB2(S0) USB3(S0) EHCI(S0) AZAL(S3) PCIE(S4) RP01(S4)  
RP02(S3) RP03(S3) RP04(S3) RP05(S3) RP06(S3)

acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (AGP_)
acpiprt2 at acpi0: bus 3 (PCIE)
acpiprt3 at acpi0: bus 11 (RP01)
acpiprt4 at acpi0: bus -1 (RP02)
acpiprt5 at acpi0: bus -1 (RP03)
acpiprt6 at acpi0: bus 12 (RP04)
acpiprt7 at acpi0: bus -1 (RP05)
acpiprt8 at acpi0: bus -1 (RP06)
acpicpu0 at acpi0: C3, C2, C1
acpitz0 at acpi0: critical temperature 126 degC
acpiac0 at acpi0: AC unit offline
acpibat0 at acpi0: BAT0 model " DELLPD9458" serial 987 type LION oem  
"Sanyo"

acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: PBTN
acpibtn2 at acpi0: SBTN
acpivideo at acpi0 not configured
acpivideo at acpi0 not configured
acpivideo at acpi0 not configured
bios0: ROM list: 0xc/0x1
cpu0 at mainbus0
cpu0: Enhanced SpeedStep disabled by BIOS
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "Intel 82945GM Host" rev 0x03
ppb0 at pci0 dev 1 function 0 "Intel 82945GM PCIE" rev 0x03: irq 4
pci1 at ppb0 bus 1
vga1 at pci1 dev 0 function 0 "NVIDIA GeForce 7300 Go" rev 0xa1
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
agp0 at vga1: no integrated graphics
drm at vga1 unsupported
azalia0 at pci0 dev 27 function 0 "Intel 82801GB HD Audio" rev 0x01:  
irq 11
azalia0: codec[s]: Sigmatel STAC9200, Conexant/0x2bfa, using  
Sigmatel STAC9200

audio0 at azalia0
ppb1 at pci0 dev 28 function 0 "Intel 82801GB PCIE" rev 0x01: irq 4
pci2 at ppb1 bus 11
wpi0 at pci2 dev 0 function 0 "Intel PRO/Wireless 3945ABG" rev 0x02:  
irq 4, MoW1, address 00:19:d2:bc:92:76

ppb2 at pci0 dev 28 function 3 "Intel 82801GB PCIE" rev 0x01: irq 3
pci3 at ppb2 bus 12
uhci0 at pci0 dev 29 function 0 "Intel 82801GB USB" rev 0x01: irq 10
uhci1 at pci0 dev 29 function 1 "Intel 82801GB USB" rev 0x01: irq 11
uhci2 at pci0 dev 29 function 2 "Intel 82801GB USB" rev 0x01: irq 9
uhci3 at pci0 dev 29 function 3 "Intel 82801GB USB" rev 0x01: irq 7
ehci0 at pci0 dev 29 function 7 "Intel 82801GB USB" rev 0x01: irq 10
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
ppb3 at pci0 dev 30 function 0 "Intel 82801BAM Hub-to-PCI" rev 0xe1
pci4 at ppb3 bus 3
bce0 at pci4 dev 0 function 0 "Broadcom BCM4401B1" rev 0x02: irq 5,  
address 00:19:b9:63:86:a4

bmtphy0 at bce0 phy 1: BCM4401 10/100baseTX PHY, rev. 0
"Ricoh 5C832 Firewire" rev 0x00 at pci4 dev 1 function 0 not  
configured

sdhc0 at pci4 dev 1 function 1 "Ricoh 5C822 SD/MMC" rev 0x19: irq 9
sdmmc0 at sdhc0
"Ricoh 5C843 MMC" rev 0x01 at pci4 dev 1 function 2 not configured
"Ricoh 5C592 Memory Stick" rev 0x0a at pci4 dev 1 function 3 not  
configured

"Ricoh 5C852 xD" rev 0x05 at pci4 dev 1 function 4 not configured
ichpcib0 at pci0 dev 31 function 0 "Intel 82801GBM LPC" rev 0x01: PM  
disabled
pciide0 at pci0 dev 31 function 2 "Intel 82801GBM SATA" rev 0x01:  
DMA, channel 0 wired to compatibility, channel 1 wired to  
compatibility

wd0 at pciide0 channel 0 drive 0: 
wd0: 16-sector PIO, LBA48, 152627MB, 312581808 sectors
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5
atapiscsi0 at pciide0 channel 1 drive 0
scsibus0 at atapiscsi0: 2 targets, initiator 7
cd0 at scsibus0 targ 0 lun 0:   
ATAPI 5/cdrom removable

cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2
ichiic0 at pci0 dev 31 function 3 "Intel 82801GB SMBus" rev 0x01:  
irq 5

iic0 at ichiic0
spdmem0 at iic0 addr 0x50: 1GB DDR2 SDRAM non-parity PC2-5300CL5 SO- 
DIMM
spdmem1 at iic0 addr 0x52: 1GB DD

Re: How do I enable bsd.mp kernel in 4.4/i386?

2009-05-02 Thread Theo de Raadt
> > I am running OBSD 4.4/i386 on a Dell Inspiron 6400 (E1505) w/ 2GB RAM
> > and a 2.0 GHz Intel Core 2 Duo CPU ("Merom").
> > 
> > I am running the GENERIC OBSD 4.4/i386 'bsd' kernel and would like
> > to set up the bsd.mp kernel instead.
> > 
> > How do I go about this?
> 
> cd /
> mv bsd bsd.sp
> mv bsd.mp bsd
> 
> reboot

As an additional note, in the new -current snapshots this is done
automatically.  As is a lot of other stuff



Re: How do I enable bsd.mp kernel in 4.4/i386?

2009-05-02 Thread Theo de Raadt
> I am running OBSD 4.4/i386 on a Dell Inspiron 6400 (E1505) w/ 2GB RAM
> and a 2.0 GHz Intel Core 2 Duo CPU ("Merom").
> 
> I am running the GENERIC OBSD 4.4/i386 'bsd' kernel and would like
> to set up the bsd.mp kernel instead.
> 
> How do I go about this?

cd /
mv bsd bsd.sp
mv bsd.mp bsd

reboot



How do I enable bsd.mp kernel in 4.4/i386?

2009-05-02 Thread Anon Y. Mous
I am running OBSD 4.4/i386 on a Dell Inspiron 6400 (E1505) w/ 2GB RAM
and a 2.0 GHz Intel Core 2 Duo CPU ("Merom").

I am running the GENERIC OBSD 4.4/i386 'bsd' kernel and would like
to set up the bsd.mp kernel instead.

How do I go about this?

Attached is my dmesg as a text file.

-minsai
OpenBSD 4.4 (GENERIC) #1021: Tue Aug 12 17:16:55 MDT 2008
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz ("GenuineIntel" 686-class) 2 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,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16,xTPR
real mem  = 2145820672 (2046MB)
avail mem = 2066497536 (1970MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 06/13/07, BIOS32 rev. 0 @ 0xffa10, SMBIOS 
rev. 2.4 @ 0xf7980 (44 entries)
bios0: vendor Dell Inc. version "A17" date 06/13/2007
bios0: Dell Inc. MM061
acpi0 at bios0: rev 0
acpi0: tables DSDT FACP HPET APIC MCFG SLIC BOOT SSDT SSDT
acpi0: wakeup devices LID_(S3) PBTN(S4) MBTN(S5) PCI0(S3) USB0(S0) USB1(S0) 
USB2(S0) USB3(S0) EHCI(S0) AZAL(S3) PCIE(S4) RP01(S4) RP02(S3) RP03(S3) 
RP04(S3) RP05(S3) RP06(S3)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (AGP_)
acpiprt2 at acpi0: bus 3 (PCIE)
acpiprt3 at acpi0: bus 11 (RP01)
acpiprt4 at acpi0: bus -1 (RP02)
acpiprt5 at acpi0: bus -1 (RP03)
acpiprt6 at acpi0: bus 12 (RP04)
acpiprt7 at acpi0: bus -1 (RP05)
acpiprt8 at acpi0: bus -1 (RP06)
acpicpu0 at acpi0: C3, C2, C1
acpitz0 at acpi0: critical temperature 126 degC
acpiac0 at acpi0: AC unit offline
acpibat0 at acpi0: BAT0 model " DELLPD9458" serial 987 type LION oem "Sanyo"
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: PBTN
acpibtn2 at acpi0: SBTN
acpivideo at acpi0 not configured
acpivideo at acpi0 not configured
acpivideo at acpi0 not configured
bios0: ROM list: 0xc/0x1
cpu0 at mainbus0
cpu0: Enhanced SpeedStep disabled by BIOS
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "Intel 82945GM Host" rev 0x03
ppb0 at pci0 dev 1 function 0 "Intel 82945GM PCIE" rev 0x03: irq 4
pci1 at ppb0 bus 1
vga1 at pci1 dev 0 function 0 "NVIDIA GeForce 7300 Go" rev 0xa1
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
agp0 at vga1: no integrated graphics
drm at vga1 unsupported
azalia0 at pci0 dev 27 function 0 "Intel 82801GB HD Audio" rev 0x01: irq 11
azalia0: codec[s]: Sigmatel STAC9200, Conexant/0x2bfa, using Sigmatel STAC9200
audio0 at azalia0
ppb1 at pci0 dev 28 function 0 "Intel 82801GB PCIE" rev 0x01: irq 4
pci2 at ppb1 bus 11
wpi0 at pci2 dev 0 function 0 "Intel PRO/Wireless 3945ABG" rev 0x02: irq 4, 
MoW1, address 00:19:d2:bc:92:76
ppb2 at pci0 dev 28 function 3 "Intel 82801GB PCIE" rev 0x01: irq 3
pci3 at ppb2 bus 12
uhci0 at pci0 dev 29 function 0 "Intel 82801GB USB" rev 0x01: irq 10
uhci1 at pci0 dev 29 function 1 "Intel 82801GB USB" rev 0x01: irq 11
uhci2 at pci0 dev 29 function 2 "Intel 82801GB USB" rev 0x01: irq 9
uhci3 at pci0 dev 29 function 3 "Intel 82801GB USB" rev 0x01: irq 7
ehci0 at pci0 dev 29 function 7 "Intel 82801GB USB" rev 0x01: irq 10
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
ppb3 at pci0 dev 30 function 0 "Intel 82801BAM Hub-to-PCI" rev 0xe1
pci4 at ppb3 bus 3
bce0 at pci4 dev 0 function 0 "Broadcom BCM4401B1" rev 0x02: irq 5, address 
00:19:b9:63:86:a4
bmtphy0 at bce0 phy 1: BCM4401 10/100baseTX PHY, rev. 0
"Ricoh 5C832 Firewire" rev 0x00 at pci4 dev 1 function 0 not configured
sdhc0 at pci4 dev 1 function 1 "Ricoh 5C822 SD/MMC" rev 0x19: irq 9
sdmmc0 at sdhc0
"Ricoh 5C843 MMC" rev 0x01 at pci4 dev 1 function 2 not configured
"Ricoh 5C592 Memory Stick" rev 0x0a at pci4 dev 1 function 3 not configured
"Ricoh 5C852 xD" rev 0x05 at pci4 dev 1 function 4 not configured
ichpcib0 at pci0 dev 31 function 0 "Intel 82801GBM LPC" rev 0x01: PM disabled
pciide0 at pci0 dev 31 function 2 "Intel 82801GBM SATA" rev 0x01: DMA, channel 
0 wired to compatibility, channel 1 wired to compatibility
wd0 at pciide0 channel 0 drive 0: 
wd0: 16-sector PIO, LBA48, 152627MB, 312581808 sectors
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5
atapiscsi0 at pciide0 channel 1 drive 0
scsibus0 at atapiscsi0: 2 targets, initiator 7
cd0 at scsibus0 targ 0 lun 0:  ATAPI 5/cdrom 
removable
cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2
ichiic0 at pci0 dev 31 function 3 "Intel 82801GB SMBus" rev 0x01: irq 5
iic0 at ichiic0
spdmem0 at iic0 addr 0x50: 1GB DDR2 SDRAM non-parity PC2-5300CL5 SO-DIMM
spdmem1 at iic0 addr 0x52: 1GB DDR2 SDRAM non-parity PC2-5300CL5 SO-DIMM
usb1 at uhci0: USB revision 1.0
uhub1 at usb1 "Intel UHCI root hub" rev 1.00/1.00 addr 1
usb2 at uhci1: USB revision 1.0
uhub2 at usb2 "Intel UHCI root hub" rev 1.00/1.00 addr 1
usb3 at uhci2: USB revision 1.0
uhub3 at usb3 "Intel UHCI root hub" rev 1.00/1.00 ad

Intel DG45ID on-board Ethernet not support

2009-05-02 Thread Matthew Dempsky
I installed the latest OpenBSD snapshot onto my newly assembled
computer and discovered the motherboard's on-board Ethernet controller
is not supported.  Relevant line from dmesg seems to be:

"Intel ICH10 R BM LF" rev 0x00 at pci0 dev 25 function 0 not configured

I tried quickly hacking if_em*.c to just attach to this device too,
but that didn't seem sufficient.  I thought I'd ping the mailing list
about this to see if anyone had suggestions/patches before digging
into it more.

Thanks.


OpenBSD 4.5-current (GENERIC.MP) #90: Fri May  1 11:58:12 MDT 2009
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 3180941312 (3033MB)
avail mem = 3072720896 (2930MB)
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe84b0 (56 entries)
bios0: vendor Intel Corp. version "IDG4510H.86A.0077.2008.0725.1734"
date 07/25/2008
bios0: Intel Corporation DG45ID
acpi0 at bios0: rev 2
acpi0: tables DSDT FACP APIC MCFG ASF! HPET
acpi0: wakeup devices P0P1(S3) UAR1(S3) UAR3(S5) P0P2(S3) USB0(S3)
USB1(S3) USB2(S3) EUSB(S3) USB3(S3) USB4(S3) USBE(S3) PEX0(S4)
PEX1(S4) PEX2(S4) PEX3(S4) PEX4(S4) GBE_(S4) USB5(S3) PWRB(S5)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz, 2999.99 MHz
cpu0: 
FPU,VME,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,SMX,EST,TM2,CX16,xTPR,NXE,LONG
cpu0: 6MB 64b/line 16-way L2 cache
cpu0: apic clock running at 333MHz
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz, 2999.66 MHz
cpu1: 
FPU,VME,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,SMX,EST,TM2,CX16,xTPR,NXE,LONG
cpu1: 6MB 64b/line 16-way L2 cache
ioapic0 at mainbus0 apid 0 pa 0xfec0, version 20, 24 pins
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (P0P2)
acpiprt2 at acpi0: bus -1 (PEX0)
acpiprt3 at acpi0: bus -1 (PEX1)
acpiprt4 at acpi0: bus -1 (PEX2)
acpiprt5 at acpi0: bus -1 (PEX3)
acpiprt6 at acpi0: bus -1 (PEX4)
acpicpu0 at acpi0:, C3, C2, C1
acpicpu1 at acpi0:, C3, C2, C1
acpibtn0 at acpi0: PWRB
cpu0: unknown Enhanced SpeedStep CPU, msr 0x0616092206000922
cpu0: using only highest and lowest power states
cpu0: Enhanced SpeedStep 3000 MHz (1244 mV): speeds: 3000, 2000 MHz
pci0 at mainbus0 bus 0
extent `pciio' (0x0 - 0x), flags=0
 0xf000 - 0xf143
 0xf150 - 0xf157
 0xf160 - 0xf163
 0xf170 - 0xf177
 0xf180 - 0xf183
 0xf190 - 0xf197
 0xf1a0 - 0xf1a3
 0xf1b0 - 0xf1b7
 0xf1c0 - 0xf1c7
 0x1 - 0x
extent `pcimem' (0x0 - 0x), flags=0
 0x0 - 0x9
 0xe - 0xbdcf
 0xd000 - 0xdfff
 0xfed1c000 - 0xfed1
 0xff00 - 0xff62610f
 0xffa8 - 0xffbf
 0xffe8 - 0x
pchb0 at pci0 dev 0 function 0 "Intel G45 Host" rev 0x03
vga1 at pci0 dev 2 function 0 "Intel G45 Video" rev 0x03
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
intagp0 at vga1
agp0 at intagp0: aperture at 0xd000, size 0x1000
inteldrm0 at vga1: apic 0 int 16 (irq 11)
drm0 at inteldrm0
"Intel G45 Video" rev 0x03 at pci0 dev 2 function 1 not configured
vendor "Intel", unknown product 0x2e24 (class communications subclass
miscellaneous, rev 0x03) at pci0 dev 3 function 0 not configured
"Intel ICH10 R BM LF" rev 0x00 at pci0 dev 25 function 0 not configured
uhci0 at pci0 dev 26 function 0 "Intel 82801JI USB" rev 0x00: apic 0
int 16 (irq 11)
uhci1 at pci0 dev 26 function 1 "Intel 82801JI USB" rev 0x00: apic 0
int 21 (irq 3)
uhci2 at pci0 dev 26 function 2 "Intel 82801JI USB" rev 0x00: apic 0
int 18 (irq 11)
ehci0 at pci0 dev 26 function 7 "Intel 82801JI USB" rev 0x00: apic 0
int 18 (irq 11)
ehci0: timed out waiting for BIOS
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
azalia0 at pci0 dev 27 function 0 "Intel 82801JI HD Audio" rev 0x00:
apic 0 int 22 (irq 10)
azalia0: codecs: IDT 92HD73E1, Intel/0x2803, using IDT 92HD73E1
audio0 at azalia0
uhci3 at pci0 dev 29 function 0 "Intel 82801JI USB" rev 0x00: apic 0
int 23 (irq 3)
uhci4 at pci0 dev 29 function 1 "Intel 82801JI USB" rev 0x00: apic 0
int 19 (irq 11)
uhci5 at pci0 dev 29 function 2 "Intel 82801JI USB" rev 0x00: apic 0
int 18 (irq 11)
ehci1 at pci0 dev 29 function 7 "Intel 82801JI USB" rev 0x00: apic 0
int 23 (irq 3)
ehci1: timed out waiting for BIOS
usb1 at ehci1: USB revision 2.0
uhub1 at usb1 "Intel EHCI root hub" rev 2.00/1.00 addr 1
ppb0 at pci0 dev 30 function 0 "Intel 82801BA Hub-to-PCI" rev 0x90
pci1 at ppb0 bus 1
extent `ppb0 pcimem' (0x0 - 0x), flags=0
 0x0 - 0xff5010ff
 0xff60 - 0x
"AT&T/Lucent FW322 1394" rev 0x70 at pci1 dev 1 function 0

Re: soekris 5501, ral(4) and 4.5-current

2009-05-02 Thread Alexander Hall
Tom Murphy wrote:
> Alexander Hall wrote:
> 
>> I'll second this; from a gw of mine:
>>
>> $ sudo crontab -l | grep ral0
>> # Down and up ral0 on failure
>> *   *   *   *   *   ifconfig ral0 | grep -q
>> OACTIVE && { ifconfig \
>> ral0; echo "\n *\n"; ifconfig ral0 down; sleep 1; ifconfig ral0
>> up; ifconfig \
>> ral0; }
>>
>> /Alexander
> 
> Hi Alexander,
> 
>   What does the 'OACTIVE' mean? I put that crontab entry in and about 5
> times already
> it came up with OACTIVE in the ifconfig output and it downed the
> interface and brought it back up.
> So far the machine has stayed up and hasn't locked up solid yet. Is
> downing the interface and bringing
> it back up when it's 'OACTIVE' help prevent the box from locking up?

No idea really. I noticed sometimes that the ral0 interface stopped
working and the down+up dance made it work again. Later I noticed that
the OACTIVE flag was set when the card locked up. For me, the box itself
never locked up, but rather the AP just got inaccesible.

I skimmed through the code but to no avail.

/Alexander



Re: LMTP capable local mailer

2009-05-02 Thread Philip Guenther
2009/5/2  :
...
> Tell me, please, are there any reasons not to use mail.local
> from /usr/src/gnu/usr.sbin/sendmail? Or maybe there is another
> LMTP capable local mailer in OpenBSD...

The OpenBSD mail.local will never return EX_TEMPFAIL, so the "repeated
delivery to a given user" issue that Nick refers to in his book can't
occur.  In all the situations where other versions of mail.local would
return EX_TEMPFAIL, the OpenBSD versions simply returns normal failure
which will be treated as a permanent failure by sendmail and the
message will be bounced instead of being (re)queued.

So what situations does that cover?  Well, other versions return
EX_TEMPFAIL in such cases as out of memory, too many files, too many
processes, reached disk quota limit, out of disk space, etc.  If
you're concerned about bouncing messages in those cases, then you
should consider switching to a different local delivery agent.
Possibilities include the sendmail mail.local (though I have not
personally tested it on OpenBSD) or various programs that are in
ports/packages, such as maildrop and procmail.  The latter two also
offer extended user-level filtering capabilities which you may find
useful.

I know the sendmail mail.local program and procmail both supports
LMTP, but lack of LMTP support shouldn't necessarily rule out a
delivery agent: do you actually have enough messages with multiple
recipients for them to create an issue?  If your machine only sees a
handful of messages each day with multiple recipients, then who cares
that they require a process per user to deliver?  Verify that it's an
issue before making it a deciding factor in your selection of delivery
agent.


Philip Guenther

(Disclaimer: I maintained procmail for several years and wrote the
LMTP support and now work for Sendmail, Inc, though not on the open
source components.)



plus45.html: "to be released" -> "released"

2009-05-02 Thread Thomas Pfaff
--- plus45.html.origSat May  2 22:42:59 2009
+++ plus45.html Sat May  2 22:43:16 2009
@@ -14,7 +14,7 @@
 
 
 
-OpenBSD 4.5 (to be released May 1, 2009)
+OpenBSD 4.5 released (May 1, 2009)
 
 
 



BESPLATNO: 3miliona email adresa kupaca + Biznis Plan - Biznis Ideje - Registracija Preduzeca.

2009-05-02 Thread DIGITAL MEDIA
CD BIZNIS XXXL  Do sada najprodavanije poslovno izdanje u 2009 godini.

Izadjite iz svetske ekonomske krize kao pobednik, koristeci cetiri veoma mocna
alata.

Ne dozvolite strahu od otpustanja da preovlada Vama, uzmite stvari u svoje
ruke: zapocnite ili vodite biznis uspesno - dajemo Vam kupce BESPLATNO.

CD izdanje sadrzi cetiri elektronska izdanja na jednom mediju:

1. Registracija preduzeca  sve o registraciji preduzeca na jednom mestu +
obrasci.
>>>Advokati ovu uslugu naplacuju preko 50 eura.<<<

2. Ideje i primeri za Vas biznis  Pravljenje rakije, ratluka, briketi;
Pletarstvo; Pcelarstvo; Uzgoj glista; Sakupljanje pecuraka i sumskih plodova;
Uzgoj mente, cveca ... Ukrasne svece.
>>>Dobre ideje kostaju puno, ali ne i ovde.<<<

3. Biznis Plan  napisite sami biznis plan, prihvatljiv od svih banaka u nasoj
zemlji.
>>>Strucnjaci iz ekonomije ovu uslugu naplacuju preko 300 eura.<<<

4. Kupci na dlanu  BESPLATNO  Poklonu se ne gleda u zubi ali ovo izdanje ima
oko 3.000.000 email adresa, potencijalnih kupaca u izdanju Email Adresar 1.0.

Ponudite im svoj proizvod/uslugu.

STARA CENA CD-a je: 2.300,oo dinara. NOVA CENA: 1790,oo dinara.
Nova cena vazi za narucivanja do 01.06.2009.
Placanje pouzecem. Postarina placena.

NARUCIVANJE. Vase podatke (ime i prezime, ulica i broj, grad i pf i broj
telefona) dostavite NA email ADRESU: biznis.x...@gmail.com

S postovanjem,

DIGITAL MEDIA



Re: automaticaly mount/umount encrypted $HOME or ...

2009-05-02 Thread Uwe Werler
Hi Maxim,
 
> Choosing bash was a quick solution for executing the job after I'v  
> logged out, e.g. how else do you umount and vnconfig -u?
> I'd like to use default ksh, but quick google-search gave me an
> answer  
> - ksh can not exec after logout.
> Here I hope someone can point me to the right direction. Using bash  
> and shells at all isn't a clean solution, but the only I have found
> at the time.

You can use something like this with ksh (.profile):

if [[ -r ~/.ksh_logout ]]; then
trap '. ~/.ksh_logout' EXIT TERM KILL
fi

Regards Uwe



Re: Error while applying 001_openssl.patch on OpenBSD 4.5

2009-05-02 Thread Gonzalo Lionel Rodriguez
You download the sys.tar.gz and src.tar.gz packages?


2009/5/2 Theo de Raadt :
> Well, you did not build your tree correctly.  It is well documented in
> 'man release' and in the /usr/src/Makefile
>
>> I just tried to patch a virgin OpenBSD 4.5 installation by applying
>> 001_openssl.patch (Version 2).
>>
>> After successfully rebuilding and installing the library, as well as
>> successfully rebuilding the statically linked binaries, running 'make
>> install' in /usr/src/sbin fails as follows:
>>
>> == snip 
>> ...
>> ===> fsck
>> install -c -s -o root -g bin  -m 555 fsck /sbin/fsck
>> install -c -o root -g bin -m 444 fsck.cat8 /usr/share/man/cat8/fsck.0
>> ===> fsck_ext2fs
>> install -c -s -o root -g bin  -m 555 fsck_ext2fs /sbin/fsck_ext2fs
>> install -c -o root -g bin -m 444 fsck_ext2fs.cat8
>> /usr/share/man/cat8/fsck_ext2fs.0
>> ===> fsck_ffs
>> install -c -s -o root -g bin  -m 555 fsck_ffs /sbin/fsck_ffs
>> install -c -o root -g bin -m 444 fsck_ffs.cat8
>> /usr/share/man/cat8/fsck_ffs.0
>> ===> fsck_ffs/SMM.doc
>> install -c -o root -g bin -m 444  Makefile 0.t 1.t 2.t 3.t 4.t
>> /usr/share/doc/smm/03.fsck_ffs
>> install: Target: /usr/share/doc/smm/03.fsck_ffs
>> *** Error code 71
>>
>> Stop in /usr/src/sbin/fsck_ffs/SMM.doc (line 47 of
>> /usr/share/mk/bsd.doc.mk).
>> *** Error code 1
>>
>> Stop in /usr/src/sbin/fsck_ffs (line 48 of /usr/share/mk/bsd.subdir.mk).
>> *** Error code 1
>>
>> Stop in /usr/src/sbin (line 48 of /usr/share/mk/bsd.subdir.mk).
>> #
>>
>> == snip 
>>
>> Here's my dmesg output (MAC addresses deleted):
>> 
>> OpenBSD 4.5 (GENERIC) #1749: Sat Feb 28 14:51:18 MST 2009
>>  dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
>> cpu0: Intel Pentium II ("GenuineIntel" 686-class, 512KB L2 cache) 267 MHz
>> cpu0:
>>
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR
>> real mem  = 200830976 (191MB)
>> avail mem = 185782272 (177MB)
>> mainbus0 at root
>> bios0 at mainbus0: AT/286+ BIOS, date 12/28/99, BIOS32 rev. 0 @ 0xfcc22
>> apm0 at bios0: Power Management spec V1.2
>> apm0: battery life expectancy 100%
>> apm0: AC on, battery charge high, estimated 2:25 hours
>> pcibios0 at bios0: rev 2.1 @ 0xf/0x1
>> pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xf0ec0/144 (7 entries)
>> pcibios0: PCI Interrupt Router at 000:05:0 ("Intel 82371FB ISA" rev 0x00)
>> pcibios0: PCI bus #21 is the last bus
>> bios0: ROM list: 0xc/0xc000
>> cpu0 at mainbus0: (uniprocessor)
>> pci0 at mainbus0 bus 0: configuration mode 1 (bios)
>> pchb0 at pci0 dev 0 function 0 "Intel 82443BX AGP" rev 0x02
>> intelagp0 at pchb0
>> agp0 at intelagp0: aperture at 0xe000, size 0x1000
>> ppb0 at pci0 dev 1 function 0 "Intel 82443BX AGP" rev 0x02
>> pci1 at ppb0 bus 1
>> vga1 at pci1 dev 3 function 0 "S3 ViRGE MX" rev 0x06
>> wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
>> wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
>> piixpcib0 at pci0 dev 5 function 0 "Intel 82371AB PIIX4 ISA" rev 0x02
>> pciide0 at pci0 dev 5 function 1 "Intel 82371AB IDE" rev 0x01: DMA,
>> channel 0 wired to compatibility, channel 1 wired to compatibility
>> wd0 at pciide0 channel 0 drive 0: 
>> wd0: 16-sector PIO, LBA, 4887MB, 10009440 sectors
>> wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2
>> atapiscsi0 at pciide0 channel 1 drive 0
>> scsibus0 at atapiscsi0: 2 targets
>> cd0 at scsibus0 targ 0 lun 0:  ATAPI
>> 5/cdrom removable
>> cd0(pciide0:1:0): using PIO mode 4, DMA mode 2
>> uhci0 at pci0 dev 5 function 2 "Intel 82371AB USB" rev 0x01: irq 11
>> piixpm0 at pci0 dev 5 function 3 "Intel 82371AB Power" rev 0x02: SMBus
>> disabled
>> "Toshiba Fast Infrared Type O" rev 0x33 at pci0 dev 9 function 0 not
>> configured
>> cbb0 at pci0 dev 11 function 0 "Toshiba ToPIC97 CardBus" rev 0x44: irq 11
>> cbb1 at pci0 dev 11 function 1 "Toshiba ToPIC97 CardBus" rev 0x44: irq 11
>> vendor "Toshiba", unknown product 0x0406 (class multimedia subclass
>> video, rev 0x04) at pci0 dev 12 function 0 not configured
>> vendor "Toshiba", unknown product 0x0407 (class multimedia subclass
>> miscellaneous, rev 0x02) at pci0 dev 13 function 0 not configured
>> isa0 at piixpcib0
>> 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, using wsdisplay0
>> pms0 at pckbc0 (aux slot)
>> pckbc0: using irq 12 for aux slot
>> wsmouse0 at pms0 mux 0
>> pcppi0 at isa0 port 0x61
>> midi0 at pcppi0: 
>> spkr0 at pcppi0
>> 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
>> usb0 at uhci0: USB revision 1.0
>> uhub0 at usb0 "Intel UHCI root hub" rev 1.00/1.00 addr 1
>> cardslot0 at cbb0 slot 0 flags 0
>> cardbus0 at cardslot0: bus 20 device 0 cacheline 0x0, lattimer 0x0
>> pcmcia0 at card

Re: Error while applying 001_openssl.patch on OpenBSD 4.5

2009-05-02 Thread Theo de Raadt
Well, you did not build your tree correctly.  It is well documented in
'man release' and in the /usr/src/Makefile

> I just tried to patch a virgin OpenBSD 4.5 installation by applying 
> 001_openssl.patch (Version 2).
> 
> After successfully rebuilding and installing the library, as well as 
> successfully rebuilding the statically linked binaries, running 'make 
> install' in /usr/src/sbin fails as follows:
> 
> == snip 
> ...
> ===> fsck
> install -c -s -o root -g bin  -m 555 fsck /sbin/fsck
> install -c -o root -g bin -m 444 fsck.cat8 /usr/share/man/cat8/fsck.0
> ===> fsck_ext2fs
> install -c -s -o root -g bin  -m 555 fsck_ext2fs /sbin/fsck_ext2fs
> install -c -o root -g bin -m 444 fsck_ext2fs.cat8 
> /usr/share/man/cat8/fsck_ext2fs.0
> ===> fsck_ffs
> install -c -s -o root -g bin  -m 555 fsck_ffs /sbin/fsck_ffs
> install -c -o root -g bin -m 444 fsck_ffs.cat8 
> /usr/share/man/cat8/fsck_ffs.0
> ===> fsck_ffs/SMM.doc
> install -c -o root -g bin -m 444  Makefile 0.t 1.t 2.t 3.t 4.t 
> /usr/share/doc/smm/03.fsck_ffs
> install: Target: /usr/share/doc/smm/03.fsck_ffs
> *** Error code 71
> 
> Stop in /usr/src/sbin/fsck_ffs/SMM.doc (line 47 of 
> /usr/share/mk/bsd.doc.mk).
> *** Error code 1
> 
> Stop in /usr/src/sbin/fsck_ffs (line 48 of /usr/share/mk/bsd.subdir.mk).
> *** Error code 1
> 
> Stop in /usr/src/sbin (line 48 of /usr/share/mk/bsd.subdir.mk).
> #
> 
> == snip 
> 
> Here's my dmesg output (MAC addresses deleted):
> 
> OpenBSD 4.5 (GENERIC) #1749: Sat Feb 28 14:51:18 MST 2009
>  dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
> cpu0: Intel Pentium II ("GenuineIntel" 686-class, 512KB L2 cache) 267 MHz
> cpu0: 
> FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR
> real mem  = 200830976 (191MB)
> avail mem = 185782272 (177MB)
> mainbus0 at root
> bios0 at mainbus0: AT/286+ BIOS, date 12/28/99, BIOS32 rev. 0 @ 0xfcc22
> apm0 at bios0: Power Management spec V1.2
> apm0: battery life expectancy 100%
> apm0: AC on, battery charge high, estimated 2:25 hours
> pcibios0 at bios0: rev 2.1 @ 0xf/0x1
> pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xf0ec0/144 (7 entries)
> pcibios0: PCI Interrupt Router at 000:05:0 ("Intel 82371FB ISA" rev 0x00)
> pcibios0: PCI bus #21 is the last bus
> bios0: ROM list: 0xc/0xc000
> cpu0 at mainbus0: (uniprocessor)
> pci0 at mainbus0 bus 0: configuration mode 1 (bios)
> pchb0 at pci0 dev 0 function 0 "Intel 82443BX AGP" rev 0x02
> intelagp0 at pchb0
> agp0 at intelagp0: aperture at 0xe000, size 0x1000
> ppb0 at pci0 dev 1 function 0 "Intel 82443BX AGP" rev 0x02
> pci1 at ppb0 bus 1
> vga1 at pci1 dev 3 function 0 "S3 ViRGE MX" rev 0x06
> wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
> wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
> piixpcib0 at pci0 dev 5 function 0 "Intel 82371AB PIIX4 ISA" rev 0x02
> pciide0 at pci0 dev 5 function 1 "Intel 82371AB IDE" rev 0x01: DMA, 
> channel 0 wired to compatibility, channel 1 wired to compatibility
> wd0 at pciide0 channel 0 drive 0: 
> wd0: 16-sector PIO, LBA, 4887MB, 10009440 sectors
> wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2
> atapiscsi0 at pciide0 channel 1 drive 0
> scsibus0 at atapiscsi0: 2 targets
> cd0 at scsibus0 targ 0 lun 0:  ATAPI 
> 5/cdrom removable
> cd0(pciide0:1:0): using PIO mode 4, DMA mode 2
> uhci0 at pci0 dev 5 function 2 "Intel 82371AB USB" rev 0x01: irq 11
> piixpm0 at pci0 dev 5 function 3 "Intel 82371AB Power" rev 0x02: SMBus 
> disabled
> "Toshiba Fast Infrared Type O" rev 0x33 at pci0 dev 9 function 0 not 
> configured
> cbb0 at pci0 dev 11 function 0 "Toshiba ToPIC97 CardBus" rev 0x44: irq 11
> cbb1 at pci0 dev 11 function 1 "Toshiba ToPIC97 CardBus" rev 0x44: irq 11
> vendor "Toshiba", unknown product 0x0406 (class multimedia subclass 
> video, rev 0x04) at pci0 dev 12 function 0 not configured
> vendor "Toshiba", unknown product 0x0407 (class multimedia subclass 
> miscellaneous, rev 0x02) at pci0 dev 13 function 0 not configured
> isa0 at piixpcib0
> 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, using wsdisplay0
> pms0 at pckbc0 (aux slot)
> pckbc0: using irq 12 for aux slot
> wsmouse0 at pms0 mux 0
> pcppi0 at isa0 port 0x61
> midi0 at pcppi0: 
> spkr0 at pcppi0
> 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
> usb0 at uhci0: USB revision 1.0
> uhub0 at usb0 "Intel UHCI root hub" rev 1.00/1.00 addr 1
> cardslot0 at cbb0 slot 0 flags 0
> cardbus0 at cardslot0: bus 20 device 0 cacheline 0x0, lattimer 0x0
> pcmcia0 at cardslot0
> cardslot1 at cbb1 slot 1 flags 0
> cardbus1 at cardslot1: bus 21 device 0 cacheline 0x0, lattimer 0x0
> pcmcia1 at cardslot1
> biomask effd netmask effd ttymask 

Error while applying 001_openssl.patch on OpenBSD 4.5

2009-05-02 Thread freemp

Hi,

I just tried to patch a virgin OpenBSD 4.5 installation by applying 
001_openssl.patch (Version 2).


After successfully rebuilding and installing the library, as well as 
successfully rebuilding the statically linked binaries, running 'make 
install' in /usr/src/sbin fails as follows:


== snip 
...
===> fsck
install -c -s -o root -g bin  -m 555 fsck /sbin/fsck
install -c -o root -g bin -m 444 fsck.cat8 /usr/share/man/cat8/fsck.0
===> fsck_ext2fs
install -c -s -o root -g bin  -m 555 fsck_ext2fs /sbin/fsck_ext2fs
install -c -o root -g bin -m 444 fsck_ext2fs.cat8 
/usr/share/man/cat8/fsck_ext2fs.0

===> fsck_ffs
install -c -s -o root -g bin  -m 555 fsck_ffs /sbin/fsck_ffs
install -c -o root -g bin -m 444 fsck_ffs.cat8 
/usr/share/man/cat8/fsck_ffs.0

===> fsck_ffs/SMM.doc
install -c -o root -g bin -m 444  Makefile 0.t 1.t 2.t 3.t 4.t 
/usr/share/doc/smm/03.fsck_ffs

install: Target: /usr/share/doc/smm/03.fsck_ffs
*** Error code 71

Stop in /usr/src/sbin/fsck_ffs/SMM.doc (line 47 of 
/usr/share/mk/bsd.doc.mk).

*** Error code 1

Stop in /usr/src/sbin/fsck_ffs (line 48 of /usr/share/mk/bsd.subdir.mk).
*** Error code 1

Stop in /usr/src/sbin (line 48 of /usr/share/mk/bsd.subdir.mk).
#

== snip 

Here's my dmesg output (MAC addresses deleted):

OpenBSD 4.5 (GENERIC) #1749: Sat Feb 28 14:51:18 MST 2009
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel Pentium II ("GenuineIntel" 686-class, 512KB L2 cache) 267 MHz
cpu0: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR

real mem  = 200830976 (191MB)
avail mem = 185782272 (177MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 12/28/99, BIOS32 rev. 0 @ 0xfcc22
apm0 at bios0: Power Management spec V1.2
apm0: battery life expectancy 100%
apm0: AC on, battery charge high, estimated 2:25 hours
pcibios0 at bios0: rev 2.1 @ 0xf/0x1
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xf0ec0/144 (7 entries)
pcibios0: PCI Interrupt Router at 000:05:0 ("Intel 82371FB ISA" rev 0x00)
pcibios0: PCI bus #21 is the last bus
bios0: ROM list: 0xc/0xc000
cpu0 at mainbus0: (uniprocessor)
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "Intel 82443BX AGP" rev 0x02
intelagp0 at pchb0
agp0 at intelagp0: aperture at 0xe000, size 0x1000
ppb0 at pci0 dev 1 function 0 "Intel 82443BX AGP" rev 0x02
pci1 at ppb0 bus 1
vga1 at pci1 dev 3 function 0 "S3 ViRGE MX" rev 0x06
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
piixpcib0 at pci0 dev 5 function 0 "Intel 82371AB PIIX4 ISA" rev 0x02
pciide0 at pci0 dev 5 function 1 "Intel 82371AB IDE" rev 0x01: DMA, 
channel 0 wired to compatibility, channel 1 wired to compatibility

wd0 at pciide0 channel 0 drive 0: 
wd0: 16-sector PIO, LBA, 4887MB, 10009440 sectors
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2
atapiscsi0 at pciide0 channel 1 drive 0
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0:  ATAPI 
5/cdrom removable

cd0(pciide0:1:0): using PIO mode 4, DMA mode 2
uhci0 at pci0 dev 5 function 2 "Intel 82371AB USB" rev 0x01: irq 11
piixpm0 at pci0 dev 5 function 3 "Intel 82371AB Power" rev 0x02: SMBus 
disabled
"Toshiba Fast Infrared Type O" rev 0x33 at pci0 dev 9 function 0 not 
configured

cbb0 at pci0 dev 11 function 0 "Toshiba ToPIC97 CardBus" rev 0x44: irq 11
cbb1 at pci0 dev 11 function 1 "Toshiba ToPIC97 CardBus" rev 0x44: irq 11
vendor "Toshiba", unknown product 0x0406 (class multimedia subclass 
video, rev 0x04) at pci0 dev 12 function 0 not configured
vendor "Toshiba", unknown product 0x0407 (class multimedia subclass 
miscellaneous, rev 0x02) at pci0 dev 13 function 0 not configured

isa0 at piixpcib0
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, using wsdisplay0
pms0 at pckbc0 (aux slot)
pckbc0: using irq 12 for aux slot
wsmouse0 at pms0 mux 0
pcppi0 at isa0 port 0x61
midi0 at pcppi0: 
spkr0 at pcppi0
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
usb0 at uhci0: USB revision 1.0
uhub0 at usb0 "Intel UHCI root hub" rev 1.00/1.00 addr 1
cardslot0 at cbb0 slot 0 flags 0
cardbus0 at cardslot0: bus 20 device 0 cacheline 0x0, lattimer 0x0
pcmcia0 at cardslot0
cardslot1 at cbb1 slot 1 flags 0
cardbus1 at cardslot1: bus 21 device 0 cacheline 0x0, lattimer 0x0
pcmcia1 at cardslot1
biomask effd netmask effd ttymask 
mtrr: Pentium Pro MTRR support
ne3 at pcmcia0 function 0 "Dual Speed, 10/100 PC Card, 1.0" port 
0xa000/32, address 
ukphy0 at ne3 phy 4: Generic IEEE 802.3u media interface, rev. 2: OUI 
0x0010dd, model 0x0001
xl0 at cardbus1 dev 0 function 0 "3Com 3CCFE575BT" rev 0x01: irq 11, 
address 

tqphy0 at xl0 phy 0: 78Q2120 10/1

Re: MPLS status questions.

2009-05-02 Thread Chris Cappuccio
Joe S [js.li...@gmail.com] wrote:
> 
> What's really frustrating here are the network admins I work with that
> are trying to migrate from ipsec vpns to MPLS because it's "easier"
> and "just as secure".
> 
> Yaargh.
> 

Typical networking idiots.  Some telcos sell an "MPLS IP VPN" service which is 
comparable in implementation to frame relay, but switched by MPLS 
switches/routers instead of frame relay switches.  There is no encryption.  It 
is not a "VPN" in any sense that you use over the internet or any public 
network (such as a commercial telco)

--
"I'm not aware of any specific concerns," Pentagon spokesman Bryan Whitman 
said, according to Reuters. Whitman added he was speaking generally and not 
talking about specific incidents. 



Re: Wireless ral(4) problem

2009-05-02 Thread Giancarlo Razzolini

Tom escreveu:

Hi Giancarlo,

  I have the same problem. On 4.5-release. My wifi card locks up and
often will lock up the machine if there
is heavy traffic (like a BitTorrent).

ral0 at pci0 dev 14 function 0 "Ralink RT2661" rev 0x00: irq 10,
address 00:14:85:xx:xx:xx
ral0: MAC/BBP RT2661D, RF RT2529 (MIMO XR)

  I'm using Linux wireless clients that talk to the OpenBSD router and
as far as I can tell, they all have powersave
turned off.

  Has this been addressed in -current at all I wonder?

  Tom


  
The only difference is that my box never lock up. It remain working. 
Only the wireless communication with the clients stop for some seconds, 
and then get back working as nothing had happened. I saw this on the manual:


Some PCI ral adapters seem to strictly require a system supporting PCI
2.2 or greater and will likely not work in systems based on older revi
sions of the PCI specification.  Check the board's PCI version before
purchasing the card.

So i went check to see if my pci card requires the 2.2 PCI revision or 
not. It is an OvisLink EVO-W54PCI and it is listed on the man page as 
one that should work. On the manual of the card there is nothing saying 
what revision it need. But i came across a PDF file when searching the 
net, and it says that the card need the 2.2 PCI revision. Mine is 2.1:


pcibios0 at bios0: rev 2.1 @ 0xf/0xd42

AFAIK, the card shouldn't even be detected, nor should it be working. I 
can only guess if this isn't my problem. I was already planning on 
replacing my firewall machine, guess i'll have to do it faster than planned.


My regards,

--
Giancarlo Razzolini
http://lock.razzolini.adm.br
Linux User 172199
Red Hat Certified Engineer no:804006389722501
Verify:https://www.redhat.com/certification/rhce/current/
Moleque Sem Conteudo Numero #002
OpenBSD Stable
Ubuntu 8.04 Hardy Heron
4386 2A6F FFD4 4D5F 5842  6EA0 7ABE BBAB 9C0E 6B85



Re: soekris 5501, ral(4) and 4.5-current

2009-05-02 Thread Michiel van Baak
On 13:24, Sat 02 May 09, Tom wrote:
> Michiel van Baak wrote:
> > Maybe a stupid question, or a question already asked (did not read all
> > the messages in this thread) but have you checked the temperature of the
> > soekris?
> > I put the soekris on it's side instead of horizontal, and the temp
> > dropped from lockup temp to 50C and it's running stable now.
> > Must be because the holes are only on the sides of the case and not in
> > the top.
> 
> Hi,
> 
>   All the sensors seem to look like this:
> 
> hw.sensors.nsclpcsio0.temp0=74.00 degC (Remote)
> hw.sensors.nsclpcsio0.temp1=127.00 degC (Remote)
> hw.sensors.nsclpcsio0.temp2=57.00 degC (Local)
> 
>   temp1 is always 127 C (must not be used). temp0 and temp2 never vary
> more than +/- 2 C from what is above.
> 
>   74 C seems rather high, but I recall seeing on a Soekris mailing list that
> this reading is actually normal. Do yours give similar readings?

hw.sensors.nsclpcsio0.temp0=71.00 degC (Remote)
hw.sensors.nsclpcsio0.temp1=127.00 degC (Remote)
hw.sensors.nsclpcsio0.temp2=53.00 degC (Local)

temp2 is the CPU.

57 C is not too hot for the soekris, so that shouldn't be the problem.
-- 

Michiel van Baak
mich...@vanbaak.eu
http://michiel.vanbaak.eu
GnuPG key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x71C946BD

"Why is it drug addicts and computer aficionados are both called users?"



Re: Wireless ral(4) problem

2009-05-02 Thread Daniel Melameth
On Sat, May 2, 2009 at 4:49 AM, Tom  wrote:
> Same here. If I could do a proper test and debugging on this for furthering
> the research to fix this, I would gladly do so. ifconfig ral0 debug seems
to
> give no useful information at time of crash. All I see are handshakes,
auths,
> and deauths.
>
> I would really love to know what is making it lock up solid. I can't even
send
> a
> BREAK on the serial console to  get into ddb when it locks up solid. All I
> can
> do is use my trust paperclip to reset the machine.
>
> I have used rtorrent as a test on the Soekris itself, and it works
> fine using the
> vr(4) driver. If I ifconfig ral0 down, or even disable ral after boot
> -c, the box is
> quite reliable and will stay up just fine with high amounts of traffic.
>
> It definitely seems to be ral(4) and the way that driver interacts with
> OpenBSD
> and everything else.

This is related to hostap mode and not a Soekris issue.  I've had
boxes that work fine as ral wireless clients, but once I turn them
into ral APs, they dont work very well for long.



Re: OT: Plea for HELP on dual boot MAC/OpenBSD disaster with refit that turn really bad!

2009-05-02 Thread Nick Holland
Daniel Ouellet wrote:
> Nick Holland wrote:
>> the "Use entire disk" question changes no more than 512 bytes on your
>> disk.  That's the good news.  The significance of that 512 bytes is the
>> problem.  (and while 512 bytes doesn't sound that bad, that's
>> 2^(512*8) combinations...so we still gotta do somewhat better than
>> random guessing)
> 
> Nick, one question I have reading lots of stuff on google results and 
> that I want to be sure as my understanding is kind of vague here.
> This action replace only the sector for 512 Bytes and would leave the 
> rest of the cylinder intact right? Or not?

correct.  no touchie.  The boot loader install process does not touch
any of the other sectors on the track or cylinder (or disk ...)

> I am asking as I am may making some progress. I found that the GPT, what 
> ever that is that Apple use form the Intel standard have two copy of it.
> 
> One at the start of the disk and one at the end of the disk and that the 
> GPT also include the MBR details. A bit more here:
> 
> http://blog.csdn.net/hotsolaris/archive/2008/12/23/3589039.aspx
> 
> The primary GPT with I understand would have been what this OpenBSD 
> process replace is gone, but then the secondary GPT most likely still 
> intact.
> 
> Not sure how to read it or even if possible. SO, I will continue the 
> research on this, but to be sure, only the first 512 bytes and nothing 
> at all would have been modified right?

correct. :)

> So, if I can find a way to read the secondary GPT, I might be able to 
> see what the primary should be and may be recreate it. No clue how yet, 
> but that appear logical right?

just on my way out the door, but in the refit "myths and facts" page,
I found reference to a gptsync which seems to copy the EFI stuff to the
MBR.  This is good.  The fact that the rest of the boot code was blown
away is bad.  You need to carefully restore the boot code of the first
sector, then restore the partition info, but the GPT stuff looks like it
can save you.  Installing the same version of refit to another disk may
be a starting point.  or maybe not.

Again...good luck.

Nick.



LMTP capable local mailer

2009-05-02 Thread ciscoadmin
Hello.

I tried to use /usr/libexec/mail.local as a LMTP capable local
mailer in sendmail.mc:

FEATURE(`local_lmtp', `/usr/libexec/mail.local')

but found that LMTP was not supported - fragment from syslog:

"mail.local: usage: mail.local [-lL] [-f from] user ..."

Tell me, please, are there any reasons not to use mail.local
from /usr/src/gnu/usr.sbin/sendmail? Or maybe there is another
LMTP capable local mailer in OpenBSD...


PS. If LMTP is not supported by a local mailer then in some
cases the same message can be delivered to some recipients
several times. It's possible to turn off delivery to
multiple recipients for a local mailer:

MODIFY_MAILER_FLAGS(`LOCAL', `-m')

but this significantly increases CPU usage when delivering
the message to each recipient individually ("Sendmail
Performance Tuning" by Nick Christenson).



Re: soekris 5501, ral(4) and 4.5-current

2009-05-02 Thread Tom
Michiel van Baak wrote:
> Maybe a stupid question, or a question already asked (did not read all
> the messages in this thread) but have you checked the temperature of the
> soekris?
> I put the soekris on it's side instead of horizontal, and the temp
> dropped from lockup temp to 50C and it's running stable now.
> Must be because the holes are only on the sides of the case and not in
> the top.

Hi,

  All the sensors seem to look like this:

hw.sensors.nsclpcsio0.temp0=74.00 degC (Remote)
hw.sensors.nsclpcsio0.temp1=127.00 degC (Remote)
hw.sensors.nsclpcsio0.temp2=57.00 degC (Local)

  temp1 is always 127 C (must not be used). temp0 and temp2 never vary
more than +/- 2 C from what is above.

  74 C seems rather high, but I recall seeing on a Soekris mailing list that
this reading is actually normal. Do yours give similar readings?

  Tom



Re: Plea for HELP on dual boot MAC/OpenBSD disaster with refit that turn really bad!

2009-05-02 Thread Fred Crowson
Hi Daniel,

Which Mac is it?

Hopefully you should be able to recover the error - you might need to
boot his Mac OS X disks which should enable you to get OpenProm to
recognise the HFS part of the disk again.

Fred

On 5/2/09, Tony Abernethy  wrote:
> Daniel Ouellet wrote:
>> Tony Abernethy wrote:
>> >> disklabel, of fdisk
>> >> to look only, looks like there is only one partition now.
>> > Dunno if that is looking at MBR in memory or MBR on disk
>> > If MBR on disk is still the same, should be OK after boot.
>>
>> That's not from memory for sure.
>>
>> Power off and on show the same thing.
>>
>> > If MBR on disk has changed, need exact make model of disk drive
>> > and maybe somebody with same can read the critical values.
>> > Dunno about MAC, but I've had a Windows partition refdisked
>> > reformatted, should have been all gone and all the original
>> > contents showed back up.
>>
>> I don't think this will do anything really.
>>
>> As far as I understand trying to learn to may be fix is that
>> you would
>> have 4 partition there.
>>
>> 1. EFI
>> 2. MAC OS X HFS+
>> 3. EFI System (FAT)
>> 4. the OpenBSD one as id A6
>>
>> Now, id for 1, 2 and 3 are 00 and 4 is A6 with type OpenBSD
>> and all the
>> size for that one and all the three others 0.
>>
>> For what I understand so far is that I would need to somehow restore
>> these 4 partition informations with the right id on them and
>> all should
>> be fine as no data was changed on the data part of the drive anyway.
>>
>> I just have no clue yet as to how to do this, or if possible.
>>
>> How to even figure out what side each one should be and what type???
>>
>> I won't do anything until I am sure, but I am disparately
>> searching so
>> far to find any clue as to how to proceed.
>>
>> I believe it should really be possible, but not there yet for
>> sure anyway.
>>
>> Best,
>>
>> Daniel
>>
> This is from an IBM T41 (booting from USB)
> sd0 is the USB drive. wd0 is the hard disk with only NT on it.
> YOURS will be considerable more complicated.
> ALL those numbers in the middle need their correct values.
> # fdisk sd0
> Disk: sd0   geometry: 3949/16/63 [3981312 Sectors]
> Offset: 0   Signature: 0xAA55
> Starting Ending LBA Info:
>  #: id  C   H   S -  C   H   S [   start:size ]
> 
> ---
>  0: 00  0   0   0 -  0   0   0 [   0:   0 ] unused
>  1: 00  0   0   0 -  0   0   0 [   0:   0 ] unused
>  2: 00  0   0   0 -  0   0   0 [   0:   0 ] unused
> *3: A6  0   1   1 -   3936   8  63 [  63: 3967992 ] OpenBSD
> # fdisk wd0
> Disk: wd0   geometry: 4697/240/63 [71029746 Sectors]
> Offset: 0   Signature: 0xAA55
> Starting Ending LBA Info:
>  #: id  C   H   S -  C   H   S [   start:size ]
> 
> ---
> *0: 07  0   1   1 -   4696 239  63 [  63:71018577 ] NTFS
>  1: 00  0   0   0 -  0   0   0 [   0:   0 ] unused
>  2: 00  0   0   0 -  0   0   0 [   0:   0 ] unused
>  3: 00  0   0   0 -  0   0   0 [   0:   0 ] unused
> What you want are all those values relevant to YOUR system.
>
> Maybe somebody has a similar system (Sorry, no MACs here)



Re: soekris 5501, ral(4) and 4.5-current

2009-05-02 Thread Michiel van Baak
On 11:28, Sat 02 May 09, Tom wrote:
> Just a quick update.
> 
> Blew away 4.5-current I had on there (think it was April 27th) and put
> 4.5-release on to see if that makes any difference.
> (Previously, my Feb 28th 4.4-current snapshot had been running just
> fine.) Still get the odd lockup, and also get the Soekris
> locking up if I send it a lot of data (bittorrent, large scp, etc..)
> 
> My power supply is fine. It's a 36W one with 12V, 3A DC output (model
> GFP361SA-1230-1). It's not one of those dodgy Soekris
> power adapters that were known to spontaneously fail (I checked on that.)
> 
> Looking at CVSWeb, there haven't been any commits to RT2661*/ral(4) in
> months, so I'm not sure if upgrading to a snapshot at this
> time will be helpful or not.
> 
> Is it worth doing a sendbug(1) on this one? Does damien@ read this list? :)

Maybe a stupid question, or a question already asked (did not read all
the messages in this thread) but have you checked the temperature of the
soekris?
I put the soekris on it's side instead of horizontal, and the temp
dropped from lockup temp to 50C and it's running stable now.
Must be because the holes are only on the sides of the case and not in
the top.

-- 

Michiel van Baak
mich...@vanbaak.eu
http://michiel.vanbaak.eu
GnuPG key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x71C946BD

"Why is it drug addicts and computer aficionados are both called users?"



Re: Wireless ral(4) problem

2009-05-02 Thread Dorian Büttner

Tom schrieb:

Hi Giancarlo,

  I have the same problem. On 4.5-release. My wifi card locks up and
often will lock up the machine if there
is heavy traffic (like a BitTorrent).

ral0 at pci0 dev 14 function 0 "Ralink RT2661" rev 0x00: irq 10,
address 00:14:85:xx:xx:xx
ral0: MAC/BBP RT2661D, RF RT2529 (MIMO XR)

  I'm using Linux wireless clients that talk to the OpenBSD router and
as far as I can tell, they all have powersave
turned off.

  Has this been addressed in -current at all I wonder?

  Tom
  
What I experience, is, that the traffic leading to the freeze doesn't 
need to come in via the ral card, it can be on an vr interface as well.
I have used several services ftp, http etc for ages now on the vr 
devices without a hitch, and since I inserted the ral into the soekris 
it randomly locks up 'by itself',
and will do nearly immediately if I suck files via wired LAN. So I 
suspect this is something in the driver itself, propably more to do with 
resource allocation or somewhat.
Anyone knows some useful test scenario, I'll gladly do the practical 
work here?




Re: Wireless ral(4) problem

2009-05-02 Thread Tom
2009/5/2 Dorian BC:
> Tom schrieb:
>>
>> Hi Giancarlo,
>>
>> B I have the same problem. On 4.5-release. My wifi card locks up and
>> often will lock up the machine if there
>> is heavy traffic (like a BitTorrent).
>>
>> ral0 at pci0 dev 14 function 0 "Ralink RT2661" rev 0x00: irq 10,
>> address 00:14:85:xx:xx:xx
>> ral0: MAC/BBP RT2661D, RF RT2529 (MIMO XR)
>>
>> B I'm using Linux wireless clients that talk to the OpenBSD router and
>> as far as I can tell, they all have powersave
>> turned off.
>>
>> B Has this been addressed in -current at all I wonder?
>>
>> B Tom
>>
>
> What I experience, is, that the traffic leading to the freeze doesn't need
> to come in via the ral card, it can be on an vr interface as well.
> I have used several services ftp, http etc for ages now on the vr devices
> without a hitch, and since I inserted the ral into the soekris it randomly
> locks up 'by itself',
> and will do nearly immediately if I suck files via wired LAN. So I suspect
> this is something in the driver itself, propably more to do with resource
> allocation or somewhat.
> Anyone knows some useful test scenario, I'll gladly do the practical work
> here?

Same here. If I could do a proper test and debugging on this for furthering
the research to fix this, I would gladly do so. ifconfig ral0 debug seems to
give no useful information at time of crash. All I see are handshakes, auths,
and deauths.

I would really love to know what is making it lock up solid. I can't even send
a
BREAK on the serial console to  get into ddb when it locks up solid. All I
can
do is use my trust paperclip to reset the machine.

I have used rtorrent as a test on the Soekris itself, and it works
fine using the
vr(4) driver. If I ifconfig ral0 down, or even disable ral after boot
-c, the box is
quite reliable and will stay up just fine with high amounts of traffic.

It definitely seems to be ral(4) and the way that driver interacts with
OpenBSD
and everything else.

Tom



Re: soekris 5501, ral(4) and 4.5-current

2009-05-02 Thread Tom
Just a quick update.

Blew away 4.5-current I had on there (think it was April 27th) and put
4.5-release on to see if that makes any difference.
(Previously, my Feb 28th 4.4-current snapshot had been running just
fine.) Still get the odd lockup, and also get the Soekris
locking up if I send it a lot of data (bittorrent, large scp, etc..)

My power supply is fine. It's a 36W one with 12V, 3A DC output (model
GFP361SA-1230-1). It's not one of those dodgy Soekris
power adapters that were known to spontaneously fail (I checked on that.)

Looking at CVSWeb, there haven't been any commits to RT2661*/ral(4) in
months, so I'm not sure if upgrading to a snapshot at this
time will be helpful or not.

Is it worth doing a sendbug(1) on this one? Does damien@ read this list? :)

Tom



Re: OT: Plea for HELP on dual boot MAC/OpenBSD disaster with refit that turn really bad!

2009-05-02 Thread Dirk Mast
Daniel Ouellet wrote:

> Hi,
> 
> Now sure if anyone could give me a hint or pointer, but I very much
> would appreciated ANY help if there is actually something possible to do.
> 



Hi,

this won't recover your partitions and those things, but as you said your
son needs to access his "workfiles" assuming those are pretty 
standard files, as in mp3/doc/txt/jpg/whatever
you should really have a look at the excellent tool photorec
(I think there's even an OpenBSD port for it!)

It will scan the drive sector wise, looking for known file headers and 
will allow you to recover them - nice way if you only need those special
files - it works very nice.



logging smtp connections

2009-05-02 Thread Robson Caetano
Hi

I would like to log From:, To: and Subject: fields of
every SMTP connection to my internal SMTP server
that is passed by the openbsd firewall.

Could I use relayd in the firewall for that?
Has anyone done something similar?

Thanks for any help.

Regards,

Robson Caetano

--
Be Yourself @ mail.com!
Choose From 200+ Email Addresses
Get a Free Account at www.mail.com



[HAR2009] Finall call for papers: submit before may 15th

2009-05-02 Thread Tom Van Looy
 Original Message 
Subject: [HAR2009] Finall call for papers: submit before may 15th
Date: Fri, 1 May 2009 21:09:50 +0200
From: HAR2009 
Reply-To: har-annou...@har2009.org
To: annou...@har2009.org


Finall call for papers: submit before may 15th

   A significant number of interesting talks and workshops have been
   submitted already, but there is still room in the program for more. The
   uniting theme is, of course, technology. Explicitly sollicited are any
   talks, workshops or other activities that are about pure, hard
   technology. But, dont be afraid to submit anything of a less technical
   nature, maybe just skirting the fringes of technology. But, remember,
   _all_ talks and workshops should definetely be interesting and
   knowledgeable, hopefully be groundbreaking, and possibly, fun.

   The call for papers is available as [1]html, [2]pdf and [3]ascii.
   Please circulate widely: email your friends and relevant mailing lists.
   Proposals may be submitted on
   [4]https://pentabarf.har2009.org/submission/HAR2009, but must be in
   before may 15th.

World community grid

   BOINC! Yes, head over to the [5]World Community Grid site now,
   download the BOINC client and help HAR2009 earn an extra buck! We
   invite you to join the World Community Grid HAR2009-Team, and donate
   some of your CPU power to worthy causes. IBM, who have recently become
   one of the event sponsors, will add to their pledged amount if we all
   manage to get 250 new and active WCG accounts up before June 1st.

   So set yourself up to join the HAR2009 team!

   If you are already active in the world community grid, use this link to
   [6]join the HAR2009 team.

   If you are not part of the Grid yet, go to [7]the WCG-website,
   download & install the software (BOINC) and join the team
   automagically!

   Speaking of sponsors, it is because of [8]these generous parties that
   it was possible to extend the early-bird deadline. Since our last
   announcement, the [9]NLnet foundation is also among those friends of
   HAR2009. They have done and are doing a lot to keep the world open!

References

  1. https://har2009.org/post/call-for-papers
  2.
http://har2009.org/wp-content/uploads/2008/12/har2009_call_for_papers.pdf
  3.
http://har2009.org/wp-content/uploads/2008/12/har2009_call_for_papers.txt
  4. https://pentabarf.har2009.org/submission/HAR2009
  5.
http://secure.worldcommunitygrid.org/reg/viewRegister.do?teamID=1SJQMVGGV1
  6.
http://secure.worldcommunitygrid.org/team/viewTeamInfo.do?teamId=1SJQMVGGV1
  7.
http://secure.worldcommunitygrid.org/reg/viewRegister.do?teamID=1SJQMVGGV1
  8. https://har2009.org/sponsors
  9. http://nlnet.nl/

___
Har-announce mailing list
har-annou...@har2009.org
http://mx.har2009.org/mailman/listinfo/har-announce



Re: OT: Plea for HELP on dual boot MAC/OpenBSD disaster with refit that turn really bad!

2009-05-02 Thread Bryan Irvine
If the disk wasn't formatted and you bought Applecare you should have
gotten a copy of techtool (I think they still give that away with
applecare, if not you can buy it seperately).  On this bootable disk
is a disk utility that wil have a feature called "scavenge".  Run it.
It will look over the HD sector by sector to see what it can still
see.  Plug in an external disk and scavenge can copy all complete
files it can find to the new disk.

Good luck.

-Bryan

On Fri, May 1, 2009 at 6:55 PM, Daniel Ouellet  wrote:
> Hi,
>
> Now sure if anyone could give me a hint or pointer, but I very much would
> appreciated ANY help if there is actually something possible to do.
>
> My Son did a mistake on his laptop tonight in trying to upgrade his OpenBSD
> partition to 4.5 and he is pretty devastated at the outcome.
>
> He put the CD 4.5 in his laptop and booted from it. Then started the install
> but at the question "do you want to use all the disk space for OpenBSD" he
> did answer Yes. Right after that even he realize it was wrong and didn't
> proceed to anything else, just did CTL-C and stop there.
>
> However looking back on his drive in shell mode with disklabel, of fdisk to
> look only, looks like there is only one partition now.
>
> As for fdisk, it show 0, 1, 2, 3 with the #3 as OpenBSD for the full drive.
>
> What he had there before as a boot loader was "refit" that allow him to
> select either OpenBSD or MAC.
>
> He is pretty devastated and I am in unfamiliar territory here and before we
> do anything I try to research things, but I sure do not want to do anything
> that could destroy any data on the drive.
>
> For what I could see, the data should still be there, or I hope it is
> anyway, but the partition table may be is gone.
>
> I don't really know if there is a way, but ANY help would be extremely
> welcome right about now!
>
> I am trying to find a way to help, or plan a possible recovery, but I must
> admit that I am in green territory here. Sure not a MAC user and I do not
> know what the possibility are here.
>
> When you answer "YES" to the "Use all drive" at the install step, but do not
> do anything else, is there a way to restore that?
>
> Again, the only step he did was yes to all drive and when he saw the
> disklabel prompt, realize it was wrong, press CTL-C and reboot, but then the
> laptop didn't reboot. Looks like the MBR or what ever it is in MAC was/is
> gone.
>
> So, I guess all the data is there, but how to recover from that.
>
> I have no idea and I hope anyone could help me. I do not know where to start
> to be totally honest here. MAC is not my world and I don't really know where
> to turn.
>
> Sorry for the off topic question, I am hoping someone can land a hand if
> that's even possible to recover.
>
> My Son is 14 in a month from now and he lost all his school work, witch he
> does need to recover.
>
> This is a long email, sorry, I guess I plea for a generous hand if recover
> is possible.
>
> A dad that try to help, but really have no clue where to start other then
> trying to wipe tiers right now from a panic son.
>
> Many thanks in advance.
>
> Best,
>
> Daniel



Re: Wireless ral(4) problem

2009-05-02 Thread Tom
Hi Giancarlo,

  I have the same problem. On 4.5-release. My wifi card locks up and
often will lock up the machine if there
is heavy traffic (like a BitTorrent).

ral0 at pci0 dev 14 function 0 "Ralink RT2661" rev 0x00: irq 10,
address 00:14:85:xx:xx:xx
ral0: MAC/BBP RT2661D, RF RT2529 (MIMO XR)

  I'm using Linux wireless clients that talk to the OpenBSD router and
as far as I can tell, they all have powersave
turned off.

  Has this been addressed in -current at all I wonder?

  Tom



Re: [PF] Strange Blocks

2009-05-02 Thread ropers
2009/5/1 dug :
0>
1> #Allow SMTP, HTTPS
2> pass quick proto tcp from any to { } port 25
3> pass quick proto tcp from any to { } port 443
4> pass quick proto tcp from { } port 25 to any
5> pass quick proto tcp from { } port 25 to any
6> pass quick proto tcp from any port 25 to { }
7> pass quick proto tcp from { }  to any port 25

Line 4 and 5 are identical. Presumably you wanted to write port 443 in line
5?

> On pflog0 interface, I have these logs :
>
> # tcpdump -vvveni pflog0
> tcpdump: listening on pflog0, link-type PFLOG
> block in on em0: mail-server.443 > 149.6.161.125.58350: [|tcp] (ttl 63, id
> 49121, len 40)

That's understandable, given that your line 5 currently says port 25
instead of port 443.

>
> block in on em0: mail-server.59902 > 81.255.99.202.25: [|tcp] (ttl 63, id
> 14511, len 40)
>
> block in on em0: mail-server.59902 > 81.255.99.202.25: [|tcp] (ttl 63, id
> 40161, len 52)
>

Not sure what's going on here; line 7 should match these.

> block in on em0: mail-server.25 > 81.28.185.240.1777: [|tcp] (ttl 63, id
> 4151, len 41)
>

Not sure what's going on there; line 4 (and, currently, 5) should match
these.

regards,
--ropers



Re: OT: Plea for HELP on dual boot MAC/OpenBSD disaster with refit that turn really bad!

2009-05-02 Thread ropers
Here's what I would do:

- physically remove the laptop's HDD; since you upgraded the laptop to
a bigger HDD yourself, this shouldn't be too much of a problem.
- look at the disk very closely. Buy the exact same type of disk
again. This might seem unnecessary, but the rationale behind this is
that whatever it is that the partitioning tools you used on the Mac
did when you originally installed the box, they are only likely to
fairly reliably do the exact same, especially in terms of auto-sizing,
if they encounter the exact same type of disk. If you can't find the
exact same type of disk, try to buy a replacement disk that is the
*exact* same size,  down to the byte; having just the rounded
marketing values match will not do.
- attach the old laptop disk to another computer that has more free
disk space than the old laptop disk's size. Preferably use a write
blocker: http://www.google.ie/search?q=ide+write+blocker Image the old
laptop disk with dd(1), as others have suggested. Don't do anything
else to the disk. And whatever you do, don't write to it.
- physically remove the old laptop disk from the other computer and
put it in a safe place.
- now attach the new identical disk to said other computer and dd the
image to the new disk. Keep the image, so you can have multiple tries
and goes at this without touching the original old laptop HDD again.
That's the entire point of using an image rather than dd'ing directly
from the old laptop HDD to the new one (repeatedly, with the potential
to make mistakes each time).
- Put the new disk into the Mac laptop and go to town. Go crazy. Try
whatever. If it doesn't work, just restore the image back to it and
try again.
- If you are unable to bring the disk back to life any other way, try
blanking it and then going through the exact same steps that you would
have gone through when originally setting up the Mac laptop. This is
where you may use GUI tools that will auto-size and offer default
suggestions. Provided your new disk really is the same type/size as
the old one, the tools should offer you the exact same layout as they
would have done originally.
- Once you have the layout, use dd with seek/skip to copy everything
but the first 512 bytes to the new HDD. If you want to save time, you
can first dd with seek/skip and count to copy only the first megabyte
in default 512 byte blocks and then use dd with seek/skip=1m and bs=1m
to more swiftly restore the rest.
- If you're lucky, you should end up with a correct first 512 bytes
and a restored HDD. At this point, if you still have any lingering
doubts that you *may* want to go back and revisit the issue some day,
just keep the old HDD in its safe place, and maybe even keep the image
on that other computer. If you are entirely happy to lose the contents
of the old HDD, you may wipe it at this point, but IMHO even then it
would be prudent to then just dd the working setup from your new HDD
to the old HDD and put the old HDD back in storage, just n case you
make the same mistake again in the future.

Good luck!

regards,
--ropers