Re: Openssl patch breaks Tor
On 2009-12-31, J.C. Roberts list-...@designtools.org wrote: The right answer is backup your data, and do a fresh install of the most recent -CURRENT snapshot. Just a standard upgrade to a -current snapshot would also be fine. On 2009-12-30, Tasmanian Devil tasm.de...@googlemail.com wrote: Changes in version 0.2.1.21 - 2009-12-21 o Major bugfixes: - Work around a security feature in OpenSSL 0.9.8l that prevents our handshake from working unless we explicitly tell OpenSSL that we are using SSL renegotiation safely. We are, of course, but OpenSSL 0.9.8l won't work unless we say we are. This is included in the patched 0.2.1.20 in -current ports.
FW: 802.11n cards for AP?
-Original Message- From: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org] On Behalf Of Brad Tilley Sent: Friday, January 01, 2010 7:49 PM To: OpenBSD Misc Subject: Re: 802.11n cards for AP? On Fri, 01 Jan 2010 19:16 -0500, Steven M. Caesare scaes...@caesare.com wrote: So... back in the 3.6ish days, I had a Prism-based 802.11b card that I used in my OpenBSD FW for a wireless access point. Worked like a charm until I relocated my FW, and could no longer get good RF coverage. Went with a consumer-based 802.11g AP configured as a bridge. That unit just died. I've found some cable/antenna assemblies that might allow me to remote an antenna to a good spot in the house for coverage, and I'm thus re-considering going with a FW based AP setup once again. According to the OpenBSD site, the following 802.11n devices are supported: athn iwn ral run As of 4.6-release, 802.11n is not yet implemented. The devices you list work, but not in n. From the run man page: CAVEATS The run driver does not support any of the 802.11n capabilities offered by the RT2800 and RT3000 chipsets. Additional work is required in ieee80211(9) before those features can be supported. Indeed you are right. That answers that. Thanks. -sc
Which laptops do the developers use?
I didn't want to bother all of them with e-mails so hopefully if any of them see this post, they might respond. Or if someone knows which models they are using they can let me know.
Re: Which laptops do the developers use?
A lot of answers eg. here http://marc.info/?l=openbsd-miscw=2r=1s=developer+laptopq=b and info from this page http://www.openbsd.org/want.html : Laptops. These die often enough that our developers need about 2-3 replacements a year. is somewhat descriptive too. On Sat, Jan 2, 2010 at 5:03 PM, James Hozier guitars...@yahoo.com wrote: I didn't want to bother all of them with e-mails so hopefully if any of them see this post, they might respond. Or if someone knows which models they are using they can let me know. -- http://www.openbsd.org/lyrics.html
Further testing a drive with dd running -current
Sorry if this shows up again. I sent this twice yesterday and for some reason it hasn't appeared on the list. David Gwynne wrote: id try this on a sili(4), ahci(4), or mpi(4) controller and see what happens. my guess is you're hitting issues in the ata stack, specifically to do with the block offsets of your io ops. dlg On 01/01/2010, at 12:03 AM, Scott McEachern wrote: Unfortunately, I do not have any of those available to me. I tried Marco's suggestion (use -current) and let the test run overnight, and the results were the same: Using -current dmesg follows. # date; time dd if=/dev/rwd0c of=/dev/null; date Thu Dec 31 23:44:32 EST 2009 dd: /dev/rwd0c: Input/output error 268435455+0 records in 268435455+0 records out 137438952960 bytes transferred in 23954.900 secs (5737404 bytes/sec) 399m14.93s real 2m12.93s user 174m4.64s system Fri Jan 1 06:23:47 EST 2010 Then I tried these just to see what would happen: Here we get the same result (but quicker) by skipping everything: # dd if=/dev/rwd0c of=/dev/null skip=268435454 dd: /dev/rwd0c: Input/output error 1+0 records in 1+0 records out 512 bytes transferred in 3.975 secs (129 bytes/sec) And as I guessed, using a bs != 512, but a multiple, it gives no error: # dd if=/dev/rwd0c of=/dev/null skip=134217726 bs=1024 ^C729161+0 records in 729161+0 records out 746660864 bytes transferred in 69.331 secs (10769439 bytes/sec) The drive is laid out like so: (Yes, it's kinda crazy and there is a bit of unallocated space at the end.) # mount /dev/wd0a on / type ffs (local, softdep) /dev/wd0e on /home type ffs (local, nodev, nosuid, softdep) /dev/wd0d on /tmp type ffs (local, nodev, nosuid, softdep) /dev/wd0f on /usr type ffs (local, nodev, softdep) /dev/wd0l on /usr/chroots type ffs (local, nosuid, softdep) /dev/wd0g on /usr/ftp type ffs (local, nodev, nosuid, softdep) /dev/wd0h on /usr/local type ffs (local, nodev, softdep) /dev/wd0i on /usr/obj type ffs (local, nodev, nosuid, softdep) /dev/wd0j on /var type ffs (local, nodev, nosuid, softdep) /dev/wd0k on /var/mysql type ffs (local, nodev, nosuid, softdep) blackstaff:~ # disklabel /dev/wd0c # /dev/wd0c: type: ESDI disk: ESDI/IDE disk label: ST31500341AS flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 182401 total sectors: 2930277168 rpm: 3600 /* Huh? This is a 7200RPM drive */ interleave: 1 boundstart: 63 boundend: 2930272065 drivedata: 0 16 partitions: #size offset fstype [fsize bsize cpg] a: 20980827 63 4.2BSD 2048 163841 b: 1060290 20980890swap c: 29302771680 unused d: 20980890 22041180 4.2BSD 2048 163841 e:419441085 43022070 4.2BSD 2048 163841 f:419441085462463155 4.2BSD 2048 163841 g:629153595881904240 4.2BSD 2048 163841 h:419441085 1511057835 4.2BSD 2048 163841 i: 8401995 1930498920 4.2BSD 2048 163841 j:419441085 1938900915 4.2BSD 2048 163841 k:104872320 2358342000 4.2BSD 2048 163841 l:209728575 2463214320 4.2BSD 2048 163841 So it would seem the block in question resides in my (grossly oversized) /tmp partition. I figured that might explain my 3 mysterious hangs, so let's try to trigger it by filling up /tmp: # dd if=/dev/zero of=/tmp/test /tmp: write failed, file system is full dd: /tmp/test: No space left on device 20640897+0 records in 20640896+0 records out 10568138752 bytes transferred in 198.879 secs (53138397 bytes/sec) # df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/wd0a 9.8G537M8.8G 6%/ /dev/wd0e 197G2.4G185G 1%/home /dev/wd0d 9.8G9.8G -504M 105%/tmp /dev/wd0f 197G6.9G180G 4%/usr /dev/wd0l 98.4G 34.6M 93.5G 0%/usr/chroots /dev/wd0g 295G 52.0K281G 0%/usr/ftp /dev/wd0h 197G1.3G186G 1%/usr/local /dev/wd0i 3.9G2.0K3.7G 0%/usr/obj /dev/wd0j 197G8.4G179G 4%/var /dev/wd0k 49.2G 67.4M 46.7G 0%/var/mysql Obviously, /tmp filled up with no crash or hang. If there's anything else I can do, just let me know. Here's the dmesg plus some kernel errors as it downgrades UDMA modes. (The snapshot was dated 11/31 on ftp.openbsd.org, all disksets installed and not compiled from source.) OpenBSD 4.6-current (GENERIC.MP) #370: Wed Dec 30 00:20:24 MST 2009 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP cpu0: Intel(R) Pentium(R) 4 CPU 3.20GHz (GenuineIntel 686-class) 3.20 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,EST,CNXT-ID,CX16,xTPR real mem = 1061974016 (1012MB) avail mem = 1020313600
13 000 euros � gagner
BCM4312 is supported by OpenBSD?
Hi everybody. I've been searching a lot about the BCM4312 support under OpenBSD, but sadly, I haven't found any information. The bwi driver is supposed to work with bcm43xx devices, but looking at dmesg output I see that the kernel identifies wich device I'm using but doesn't load the driver. This is the output of lspci (Linux): 02:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g [14e4:4315] (rev 01) In the changelog of the 4.1 version says that BCM4312 was supported by the bcw driver, but due to GPL violations it was removed from the main tree. Since I'm new using OpenBSD I would like a hand here, guys. Thanks in advance.
Re: BCM4312 is supported by OpenBSD?
2010/1/2 Vijay Sankar vsan...@foretell.ca:
Cortex wrote:
Hi everybody.
I've been searching a lot about the BCM4312 support under OpenBSD, but
sadly, I haven't found any information. The bwi driver is supposed to
work with bcm43xx devices, but looking at dmesg output I see that the
kernel identifies wich device I'm using but doesn't load the driver.
This is the output of lspci (Linux):
02:00.0 Network controller [0280]: Broadcom Corporation BCM4312
802.11b/g [14e4:4315] (rev 01)
In the changelog of the 4.1 version says that BCM4312 was supported by
the bcw driver, but due to GPL violations it was removed from the main
tree.
Since I'm new using OpenBSD I would like a hand here, guys.
Thanks in advance.
I am probably wasting your time since I do not know much about this.
Apologize in advance if that is the case.
In /usr/src/sys/dev/pci/if_bwi_pci.c I see the following:
int
bwi_pci_match(struct device *parent, void *match, void *aux)
{
struct pci_attach_args *pa = aux;
/*
* The second revision of the BCM4311/BCM4312
* chips require v4 firmware.
*/
if (PCI_VENDOR(pa-pa_id) == PCI_VENDOR_BROADCOM
(PCI_PRODUCT(pa-pa_id) == PCI_PRODUCT_BROADCOM_BCM4311 ||
PCI_PRODUCT(pa-pa_id) == PCI_PRODUCT_BROADCOM_BCM4312)
PCI_REVISION(pa-pa_class) == 0x02)
return (0);
return (pci_matchbyid((struct pci_attach_args *)aux,
bwi_pci_devices,
sizeof(bwi_pci_devices) / sizeof(bwi_pci_devices[0])));
}
I wonder what would happen if you removed some of this. If you don't get a
response from the knowledgeable people in the list it may be worth a try.
Vijay
--
Vijay Sankar, M.Eng., P.Eng.
ForeTell Technologies Limited
59 Flamingo Avenue, Winnipeg, MB, Canada R3J 0X6
Phone: (204) 885-9535, E-Mail: vsan...@foretell.ca
Vijay, thanks a lot for your answer. Of course you're not wasting my time!
The thing is that I've been using OpenBSD only on a virtual machine,
while I get ready to install it on my laptop. I was just making sure
that everything works fine.
The revision I'm using is the number 1. Maybe the driver works, I just
used a USB to run the installation program and check if the network
interface was detected, but it didn't; that's the reason why I say the
driver probably doesn't work. I also have a wireless usb device
(D-Link DWA-110) and when I plug it in it loads the appropriated
driver and creates the interface (rum0). I was expecting the same
happen with my Broadcom.
Should I do something else to get my BCM4312 working?
Juan Esteban.
Re: BCM4312 is supported by OpenBSD?
I was checking the output of dmesg again and noticed that it says: Broadcom Integrated HP Module rev 2.00/1.00 Now I don't know what to think :E
Re: Further testing a drive with dd running -current
On Sat, 2 Jan 2010, Scott McEachern wrote: # date; time dd if=/dev/rwd0c of=/dev/null; date Thu Dec 31 23:44:32 EST 2009 dd: /dev/rwd0c: Input/output error 268435455+0 records in 268435455+0 records out 137438952960 bytes transferred in 23954.900 secs (5737404 bytes/sec) 399m14.93s real 2m12.93s user 174m4.64s system Fri Jan 1 06:23:47 EST 2010 Out of curiosity, does the same happen if you dd from /dev/rwd0d? As Matthew Szudzik pointed out, dd is failing when it attempts to read (2^28)th sector of the current device you are reading from. Up to, including, 2^28-1 everything is ok. Regards, David
Re: BCM4312 is supported by OpenBSD?
Hi, Cortex wrote: 02:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g [14e4:4315] (rev 01) BCM4312 *rev 1* should work with bwi(4), the output from lspci does indeed confirm that.. but you'll need to post *OpenBSD* dmesg output here so we have a chance of figuring things out. http://marc.info/?l=openbsd-cvsm=121993685718267w=2 Revision 2 of this chipset and many newer devices require a different firmware (..microcode), these devices erronously attached as bwi(4). I was checking the output of dmesg again and noticed that it says: Broadcom Integrated HP Module rev 2.00/1.00 That is a USB device, you omitted a portion of the output, so perhaps it's bluetooth or maybe a dildo*.. quite unrelated. Now I don't know what to think :E OpenBSD's dmesg is quite easy to parse understand, you can read the output line-by-line by using using more(1). Again, please post the full dmesg output here, you can never provide to much information. * http://marc.info/?l=openbsd-miscm=126220867610069w=2 -Bryan.
Java for other than x86/amd64?
We use Hudson to manage builds. It uses Java. It looks like there's nothing viable here for OpenBSD other than x86 and AMD64? I already have OpenBSD/x86 working. I have Linux/ppc, maybe Linux/sparc working. There's a zero assembly project that has eased things, but the web page says it is gcc and Linux specific. I don't yet know why. Kaffe doesn't work. I tried. Anyone working on this? I might poke around a little but I doubt I have sufficient time. Performance doesn't matter here, so even Linux emulation would suffice. e.g. on ppc and sparc64. That doesn't seem to be present, and I realize it not a small thing. Thanks, - Jay
Re: Further testing a drive with dd running -current
David Vasek wrote: Out of curiosity, does the same happen if you dd from /dev/rwd0d? As Matthew Szudzik pointed out, dd is failing when it attempts to read (2^28)th sector of the current device you are reading from. Up to, including, 2^28-1 everything is ok. Regards, David I made an error in my last post. I said the problem sector was in /tmp on wd0d, but it was actually in /home on wd0e. With that in mind, I tried two tests. First, filling up /home. The only result was the expected reaction of apps using /home to find it full, but no I/O error from dd while filling it up. I was thinking that my previous system hangs had to do with a read or a write to that particular sector during normal system use, but I guess not. The second was your suggestion, and interestingly, it produces the error. Partition e starts at 43 022 070, the problem is at 268 435 455, so we'll skip 225 413 380 to start just before that spot: # dd if=/dev/rwd0e of=/dev/null skip=225413380 dd: /dev/rwd0e: Input/output error 5+0 records in 5+0 records out 2560 bytes transferred in 4.084 secs (627 bytes/sec) Doing the same thing with bs=1024: # dd if=/dev/rwd0e of=/dev/null skip=112706690 bs=1024 ^C164347+0 records in 164347+0 records out 168291328 bytes transferred in 15.241 secs (11041848 bytes/sec) (I aborted it) I've managed to figure out: 1) there's nothing wrong with that actual sector on the drive. 2) it's related to _this_ particular make/model. (The 500GB Western Digital was fine.) 3) it's not a problem with dd. 4) there is no difference between -stable and -current for this. 5) using a bs other than 512 in dd has no problem. Of course, there is no proof my previous hangs have anything to do with this. I haven't had the system lock up in the 5 days I've been using this drive, so that doesn't really mean anything vs. no hangs in say, 30 days. -- -RSM http://www.erratic.ca
observed spamd behavior
Hello, I've got spamd working well (it's very cool!)... Sometimes I see in pftop a state entry that shows spamd has a very old connection that is actively still passing traffic (lasts for hours)... I was able to capture one of these as it began (using tcpdump). Here's what the trace shows (in distilled SMTP): send: 220 my recv: EHLO bogon.domain.com\r\n send: host.domain.net ESMTP MTA; Mon Dec 28 07:55:59 2009\r\n send: 250 Hello, spam sender. Pleased to be wasting your time.\r\n recv: HELO bogon.domain.com\r\n send: 500 5.5.1 Command unrecognized\r\n recv: \r\n send: 500 5.5.1 Command unrecognized\r\n recv: \r\n send: 500 5.5.1 Command unrecognized\r\n recv: \r\n ... etc, approximately two 5.5.1 errors per second This client sends it's EHLO before waiting for spamd to complete sending it's 220 opening message. I try to show that above using an indentation on the third line (the second send line). In fact, spamd is doing it's normal trick of stuttering out the 220 opening message one char per packet... I think spamd's state table is correct in not allowing the SMTP session to reset upon receiving the subsequent HELO. My questions are as follows: Should spamd start to reduce bandwidth for a session by extending reply times after some trigger like too many errors sent or too much time spent...? When a client sends it's EHLO (or anything at all) before waiting for the server's 220 opening message to complete, is that not grounds for immediate greytrapping? I do not think spamd enforces that at the moment. This would be similar to sendmail's FEATURE(`greet_pause') in that there would be a penalty for such misbehavior... Thanks for your consideration. - Tor
Re: Openssl patch breaks Tor
If I upgrade to -current, don't I risk stability and security issues; or are the chances of that are very low as far as this OS goes? Long time ago I did try development versions of NetBSD and FreeBSD because I needed support for hardware that -stable didn't have, and they were quite shaky. Or do you guys just want more people to use -current for the project progress reasons? I thought -current was for people who are more into hacking code than running a stable server. Thanks.
IPSEC bringing down networking
Probably a bit premature to be asking this since I won't be able to physically access the machine until Monday, but here goes ... I have a machine that I admin remotely running 4.6 with all the patches. It's a firewall only machine with 6 ethernet interfaces, 4 of which are active, and has been running fine since I upgraded it. It's got a fairly complex pf.conf. Last week I set up a VPN on it to a Sonic Wall appliance. The VPN comes up and works fine, and then somewhere between 4 and 24 hours later the box loses all network connectivity. You can still login via console, and I've been able to get the local people to run some basic commands (ifconfig, netstat, ps, pfctl -s) and everything seems normal (from what I can get from non-technical people over the phone), but none of the interfaces are passing packets. Rebooting solves the problem for the next 4-24 hrs. It's happened several times now. System logs show nothing. Any ideas as to what is going on would be greatly appreciated. And especially, what should I be looking for (i.e. what commands should I run) if I can manage to get on the box when the network is hosed? Thanks for any help. Here's a dmesg for the machine in question: OpenBSD 4.6-stable (GENERIC.MP) #0: Mon Dec 7 17:59:54 PST 2009 *:/usr/src/sys/arch/i386/compile/GENERIC.MP cpu0: Intel(R) Pentium(R) 4 CPU 3.00GHz (GenuineIntel 686-class) 3 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,CNXT-ID,xTPR real mem = 535261184 (510MB) avail mem = 508735488 (485MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 06/12/06, BIOS32 rev. 0 @ 0xfb6d0, SMBIOS rev. 2.3 @ 0xf0800 (41 entries) bios0: vendor Phoenix Technologies, LTD version 6.00 PG date 06/12/2006 bios0: Supermicro P4SC8 acpi0 at bios0: rev 0 acpi0: tables DSDT FACP APIC acpi0: wakeup devices CSAD(S5) HUB0(S5) HRB_(S5) UAR1(S5) UAR2(S5) USB0(S1) USB1(S1) USBE(S1) MODM(S5) PCI0(S5) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: apic clock running at 199MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Pentium(R) 4 CPU 3.00GHz (GenuineIntel 686-class) 3 GHz cpu1: 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,CNXT-ID,xTPR ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 0, remapped to apid 2 ioapic1 at mainbus0: apid 3 pa 0xfec1, version 20, 24 pins acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (CSAB) acpiprt2 at acpi0: bus 4 (HUB0) acpiprt3 at acpi0: bus 2 (HRB_) acpicpu0 at acpi0 acpicpu1 at acpi0 acpitz0 at acpi0acpitz0: THRM: failed to read _TMP : failed to read _TMP acpibtn0 at acpi0: PWRB bios0: ROM list: 0xc/0x8000 0xc8000/0x1000 0xc9000/0x1000 pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 Intel 82875P Host rev 0x02 ppb0 at pci0 dev 3 function 0 Intel 82875P CSA rev 0x02 pci1 at ppb0 bus 1 em0 at pci1 dev 1 function 0 Intel PRO/1000CT (82547GI) rev 0x00: apic 2 int 18 (irq 11), address 00:30:48:8f:b0:0e ppb1 at pci0 dev 28 function 0 Intel 6300ESB PCIX rev 0x02 pci2 at ppb1 bus 2 ppb2 at pci2 dev 1 function 0 Pericom PI7C21P100 PCIX-PCIX rev 0x01 pci3 at ppb2 bus 3 em1 at pci3 dev 4 function 0 Intel PRO/1000MT QP (82546GB) rev 0x03: apic 3 int 0 (irq 9), address 00:0e:0c:c2:33:1c em2 at pci3 dev 4 function 1 Intel PRO/1000MT QP (82546GB) rev 0x03: apic 3 int 1 (irq 9), address 00:0e:0c:c2:33:1d em3 at pci3 dev 6 function 0 Intel PRO/1000MT QP (82546GB) rev 0x03: apic 3 int 2 (irq 9), address 00:0e:0c:c2:33:1e em4 at pci3 dev 6 function 1 Intel PRO/1000MT QP (82546GB) rev 0x03: apic 3 int 3 (irq 9), address 00:0e:0c:c2:33:1f uhci0 at pci0 dev 29 function 0 Intel 6300ESB USB rev 0x02: apic 2 int 16 (irq 10) uhci1 at pci0 dev 29 function 1 Intel 6300ESB USB rev 0x02: apic 2 int 19 (irq 5) Intel 6300ESB WDT rev 0x02 at pci0 dev 29 function 4 not configured Intel 6300ESB APIC rev 0x02 at pci0 dev 29 function 5 not configured ehci0 at pci0 dev 29 function 7 Intel 6300ESB USB rev 0x02: apic 2 int 23 (irq 11) 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 82801BA Hub-to-PCI rev 0x0a pci4 at ppb3 bus 4 vga1 at pci4 dev 9 function 0 ATI Rage XL rev 0x27 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) em5 at pci4 dev 10 function 0 Intel PRO/1000MT (82541GI) rev 0x00: apic 2 int 19 (irq 5), address 00:30:48:8f:b0:0f ichpcib0 at pci0 dev 31 function 0 Intel 6300ESB LPC rev 0x02 pciide0 at pci0 dev 31 function 1 Intel 6300ESB IDE rev 0x02: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility wd0 at pciide0 channel 0 drive 0:
USB Ethernet
I am trying to use a USB 2.0 Gigabit Ethernet adapter axe0 at uhub1 port 1 configuration 1 interface 0 ASIX Electronics AX88178 rev 2.00/0.01 addr 2 axe0: AX88178, address 00:80:c8:ff:ff:a1 ukphy0 at axe0 phy 0: Generic IEEE 802.3u media interface, rev. 9: OUI 0x1e525e, model 0x0014 $ ifconfig axe0 axe0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 lladdr 00:80:c8:ff:ff:a1 priority: 0 media: Ethernet autoselect (none loopback) status: no carrier inet6 fe80::280:c8ff:feff:ffa1%axe0 prefixlen 64 scopeid 0x5 inet 10.0.0.212 netmask 0xff00 broadcast 10.0.0.255 I can see packets on the interface if I use tcpdump but the status shows No Carrier. However the lights on the adapter are on and I can do a tcpdump and see packets arriving at the interface. I tried this on different systems -- a netbook, a laptop, and two desktops and in each case got the same result (4.5 -stable, 4.6 release, and 4.6 -stable, all i386 and a 4.5 -stable amd64). I also tried changing the media and mediaopt settings to 100BaseTX, 10BaseT, and 1000BaseT in addition to the default autoselect. Will this device work on OpenBSD or if this was a dumb purchase on my part can someone suggest a USB ethernet adapter that will work properly? Thanks very much. Here is the full dmesg and please let me know if any additional information will be useful. $ dmesg OpenBSD 4.6-stable (GENERIC.MP) #0: Sun Dec 27 11:48:54 CST 2009 r...@server8.sankars.local:/usr/src/sys/arch/i386/compile/GENERIC.MP cpu0: Intel(R) Core(TM)2 Duo CPU T8100 @ 2.10GHz (GenuineIntel 686-class) 2.10 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,EST,TM2,CX16,xTPR real mem = 3219075072 (3069MB) avail mem = 3118567424 (2974MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 01/21/08, BIOS32 rev. 0 @ 0xfdc34, SMBIOS rev. 2.4 @ 0xbfecc000 (40 entries) bios0: vendor Phoenix Technologies LTD version COLSSF15 date 01/21/2008 bios0: LG Electronics R500-C.CP03A9 acpi0 at bios0: rev 2 acpi0: tables DSDT FACP HPET MCFG TCPA TMOR SLIC APIC BOOT SSDT SSDT SSDT SSDT SSDT acpi0: wakeup devices LANC(S4) HDEF(S0) PXSX(S4) PXSX(S4) PXSX(S4) PXSX(S4) PXSX(S4) PXSX(S4) USB1(S3) USB2(S4) USB3(S3) USB4(S3) USB5(S0) EHC1(S3) EHC2(S3) PS2K(S3) LID0(S3) PWRB(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 14318179 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: apic clock running at 199MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM)2 Duo CPU T8100 @ 2.10GHz (GenuineIntel 686-class) 2.10 GHz cpu1: 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,EST,TM2,CX16,xTPR ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (PEGP) acpiprt2 at acpi0: bus 2 (RP01) acpiprt3 at acpi0: bus 4 (RP02) acpiprt4 at acpi0: bus 6 (RP03) acpiprt5 at acpi0: bus -1 (RP04) acpiprt6 at acpi0: bus -1 (RP05) acpiprt7 at acpi0: bus -1 (RP06) acpiprt8 at acpi0: bus 8 (PCIB) acpiec0 at acpi0 acpicpu0 at acpi0: C2, C1, PSS acpicpu1 at acpi0: C2, C1, PSS acpipwrres0 at acpi0: CTHT acpitz0 at acpi0: critical temperature 99 degC acpitz1 at acpi0: critical temperature 85 degC acpitz2 at acpi0: critical temperature 85 degC acpiac0 at acpi0: AC unit online acpibat0 at acpi0: CMB0 model BAT1 serial 1234 type LION oem LG acpibtn0 at acpi0: LID0 acpibtn1 at acpi0: PWRB acpibtn2 at acpi0: SLPB acpivideo0 at acpi0: EGFX acpivout0 at acpivideo0: CRT0 acpivout1 at acpivideo0: LCD0 acpivout2 at acpivideo0: LCD1 acpivout3 at acpivideo0: TV0_ acpivout4 at acpivideo0: DVI0 bios0: ROM list: 0xc/0xd200 0xcd800/0x3000! 0xe/0x1800! cpu0: Enhanced SpeedStep 2095 MHz: speeds: 2101, 2100, 1600, 1200, 800 MHz pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 Intel GM965 Host rev 0x03 ppb0 at pci0 dev 1 function 0 Intel GM965 PCIE rev 0x03: apic 2 int 16 (irq 5) pci1 at ppb0 bus 1 vga1 at pci1 dev 0 function 0 vendor NVIDIA, unknown product 0x0425 rev 0xa1 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) em0 at pci0 dev 25 function 0 Intel ICH8 IGP M rev 0x03: apic 2 int 20 (irq 11), address 00:e0:91:36:cc:62 uhci0 at pci0 dev 26 function 0 Intel 82801H USB rev 0x03: apic 2 int 16 (irq 5) uhci1 at pci0 dev 26 function 1 Intel 82801H USB rev 0x03: apic 2 int 21 (irq 11) ehci0 at pci0 dev 26 function 7 Intel 82801H USB rev 0x03: apic 2 int 18 (irq 7) 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 82801H HD Audio rev 0x03: apic 2 int 22 (irq 10) azalia0: codecs: Realtek ALC883 audio0 at azalia0 ppb1 at pci0
What does your environment look like?
Hi, I know not everyone uses OpenBSD for a desktop OS, but I have been for nearly 5 years and I'm quite curious about some of your opinions? do you embrace minimalism or pure aesthetics? are the two mutually exclusive? When I started using OpenBSD (..around 3.7) I was frequently switching between window managers, tweaking.. but for 2 years now I've been using fluxbox and I believe I'm comfortable with it. * Do you use one of the bundled window managers like cwm(1)/twm(1)/fvwm(1) or something else? * What other utilities do you find useful, any dockapps or similar applets? personal customizations? * Do you try to keep things uniform across other desktops? * What does your environment look like? anyone willing to post screenshots or actual workspace photos? I realize none of this may be relevant or even useful, but I figured it was worth asking here anyway. Anyone feel like humouring me? :-) Thanks. -Bryan.
OT - problem with pcc OpenBSD 4.6
As anounced in undeadly.org i've started trying pcc for little things
and personal sources and in case of find bugs, report them. But this
issue seems more like i'm missing something.
My box it's a fresh OpenBSD 4.6 relase install (i've tested this issue
in other machine with a fresh install)
The way I installed pcc was doing make install on /usr/src/usr.bin/pcc .
I made a simple helloworld to test it but it didn't compiled. (error
returned at end of the mail). The source is:
#include stdio.h
int main () {
printf(Hello world\n);
return 0;
}
gcc -Wall compiled without problems but in pcc it doesn't works.
this is the output of pcc -v -o helloworld helloworld.c and
I have no clue about what causes it:
--
/usr/local/libexec//cpp -v -D__PCC__=0 -D__PCC_MINOR__=9
-D__PCC_MINORMINOR__=9 -D__OpenBSD__ -D__unix__ -D__i386__ -D__i386
-D__ELF__ -S /usr/include/ -I
/usr/lib/pcc/TARGMACH-OpenBSD/0.9.9/include helloworld.c /tmp/ctm.1TiiMk
/usr/local/libexec//ccom_i386 -v /tmp/ctm.1TiiMk /tmp/ctm.0IDb4j
/usr/include//time.h, line 112: syntax error
/usr/include//time.h, line 112: syntax error
/usr/include//time.h, line 116: syntax error
/usr/include//time.h, line 116: syntax error
/usr/include//time.h, line 118: syntax error
/usr/include//time.h, line 118: syntax error
/usr/include//stdio.h, line 219: syntax error
/usr/include//stdio.h, line 219: syntax error
/usr/include//stdio.h, line 225: syntax error
/usr/include//stdio.h, line 225: syntax error
/usr/include//stdio.h, line 234: syntax error
/usr/include//stdio.h, line 234: syntax error
/usr/include//stdio.h, line 266: syntax error
/usr/include//stdio.h, line 266: syntax error
/usr/include//stdio.h, line 267: syntax error
/usr/include//stdio.h, line 268: syntax error
/usr/include//stdio.h, line 270: syntax error
/usr/include//stdio.h, line 270: syntax error
/usr/include//stdio.h, line 271: syntax error
/usr/include//stdio.h, line 273: syntax error
/usr/include//stdio.h, line 273: syntax error
/usr/include//stdio.h, line 274: syntax error
/usr/include//stdio.h, line 276: syntax error
/usr/include//stdio.h, line 276: syntax error
/usr/include//stdio.h, line 277: syntax error
/usr/include//stdio.h, line 278: syntax error
/usr/include//stdio.h, line 280: syntax error
/usr/include//stdio.h, line 280: syntax error
/usr/include//stdio.h, line 281: syntax error
/usr/include//stdio.h, line 339: syntax error
/usr/include//stdio.h, line 339: syntax error
/usr/include//stdio.h, line 339: compiler error: too many errors
Re: What does your environment look like?
OpenBSD-STABLE with fluxbox on my work desktop. I have a laptop with a busted LCD and keyboard, so I use it as a WinXP slave via rdesktop for running IE (checking websites, as I work in IT for a hosting company). The XP box runs in seamless mode, so fluxbox looks a bit weird with a Windows task bar across the top...but it works haha. At home I have OpenBSD-CURRENT running on my desktop...fluxbox there as well. Both have conky running as my monitor, with three instances: Left one is RSS feeds (undeadly, milw0rm, etc...), middle is CPU/RAM/etc, right is network-related stuff. I sometimes run GeoXPlanet as my wallpaper setter, but it takes some tweaks to get it running on OpenBSD and I haven't uploaded the fixed version to sourceforge for that (not trying to advertise, but if anyone is interested I'll upload the fixed code). That's pretty much it.
Re: USB Ethernet
On Sat, January 2, 2010 23:03, Vijay Sankar wrote: I am trying to use a USB 2.0 Gigabit Ethernet adapter axe0 at uhub1 port 1 configuration 1 interface 0 ASIX Electronics AX88178 rev 2.00/0.01 addr 2 axe0: AX88178, address 00:80:c8:ff:ff:a1 ukphy0 at axe0 phy 0: Generic IEEE 802.3u media interface, rev. 9: OUI 0x1e525e, model 0x0014 $ ifconfig axe0 axe0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 lladdr 00:80:c8:ff:ff:a1 priority: 0 media: Ethernet autoselect (none loopback) status: no carrier inet6 fe80::280:c8ff:feff:ffa1%axe0 prefixlen 64 scopeid 0x5 inet 10.0.0.212 netmask 0xff00 broadcast 10.0.0.255 I can see packets on the interface if I use tcpdump but the status shows No Carrier. However the lights on the adapter are on and I can do a tcpdump and see packets arriving at the interface. I tried this on different systems -- a netbook, a laptop, and two desktops and in each case got the same result (4.5 -stable, 4.6 release, and 4.6 -stable, all i386 and a 4.5 -stable amd64). I also tried changing the media and mediaopt settings to 100BaseTX, 10BaseT, and 1000BaseT in addition to the default autoselect. Will this device work on OpenBSD or if this was a dumb purchase on my part can someone suggest a USB ethernet adapter that will work properly? I never used this axe based, but can say some about fast ethernet adapters. I have admtek (aue based) and realtek (url based) ethernet nic's, and the realtek was the one to solve my problem. the aue based was only able to see what was happening on the wire, but never got to send a packet. the url based did the job ok, had altq support (what I was looking for) but not good throughput though ( 5Mbps for a 100Mbps nic ... I guess it's usb 1.1 based despite all docs says it's 2.0). My next step someday was to try gigabit nic's, as this one you're talking :) so I guess I not so in a hurry now :) matheus -- We will call you cygnus, The God of balance you shall be A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? http://en.wikipedia.org/wiki/Posting_style
Re: What does your environment look like?
Forgot to send to list. Josh - Forwarded message from Josh Rickmar joshua_rick...@eumx.net - Date: Sat, 2 Jan 2010 21:29:50 + From: Josh Rickmar joshua_rick...@eumx.net To: Brynet bry...@gmail.com Subject: Re: What does your environment look like? User-Agent: Mutt/1.5.20 (2009-06-14) On Sat, Jan 02, 2010 at 09:08:38PM -0500, Brynet wrote: Hi, I know not everyone uses OpenBSD for a desktop OS, but I have been for nearly 5 years and I'm quite curious about some of your opinions? do you embrace minimalism or pure aesthetics? are the two mutually exclusive? When I started using OpenBSD (..around 3.7) I was frequently switching between window managers, tweaking.. but for 2 years now I've been using fluxbox and I believe I'm comfortable with it. * Do you use one of the bundled window managers like cwm(1)/twm(1)/fvwm(1) or something else? dwm (with patches) * What other utilities do you find useful, any dockapps or similar applets? personal customizations? dmenu * Do you try to keep things uniform across other desktops? I'm on a laptop, not so much of an issue. Otherwise I would. * What does your environment look like? anyone willing to post screenshots or actual workspace photos? http://imagebin.ca/view/3JllgShA.png I realize none of this may be relevant or even useful, but I figured it was worth asking here anyway. Anyone feel like humouring me? :-) Thanks. -Bryan. Josh - End forwarded message -
Re: What does your environment look like?
On Sat, Jan 2, 2010 at 16:04, Josh Rickmar joshua_rick...@eumx.net wrote: dmenu * Do you try to keep things uniform across other desktops? I'm on a laptop, not so much of an issue. Otherwise I would. * What does your environment look like? anyone willing to post screenshots or actual workspace photos? http://imagebin.ca/view/3JllgShA.png I will kill to learn how to use mutt... It looks great...
Re: What does your environment look like?
Brynet bry...@gmail.com wrote: Hi, I know not everyone uses OpenBSD for a desktop OS, but I have been for nearly 5 years and I'm quite curious about some of your opinions? do you embrace minimalism or pure aesthetics? are the two mutually exclusive? When I started using OpenBSD (..around 3.7) I was frequently switching between window managers, tweaking.. but for 2 years now I've been using fluxbox and I believe I'm comfortable with it. * Do you use one of the bundled window managers like cwm(1)/twm(1)/fvwm(1) or something else? * What other utilities do you find useful, any dockapps or similar applets? personal customizations? * Do you try to keep things uniform across other desktops? * What does your environment look like? anyone willing to post screenshots or actual workspace photos? I realize none of this may be relevant or even useful, but I figured it was worth asking here anyway. Anyone feel like humouring me? :-) Thanks. -Bryan. awesome, lots of xterm with 'xterm -fa efont:size=9', irssi + bitlbee (local), nail (heirloom mailx) and midori. Saludos. -- DISCLAIMER: http://goldmark.org/jeff/stupid-disclaimers/ This message will self-destruct in 3 seconds.
Re: OT - problem with pcc OpenBSD 4.6 SOLVED
El 03/01/2010 3:41, Jesus Sanchez escribis:
As anounced in undeadly.org i've started trying pcc for little things
and personal sources and in case of find bugs, report them. But this
issue seems more like i'm missing something.
My box it's a fresh OpenBSD 4.6 relase install (i've tested this issue
in other machine with a fresh install)
The way I installed pcc was doing make install on /usr/src/usr.bin/pcc .
I made a simple helloworld to test it but it didn't compiled. (error
returned at end of the mail). The source is:
#include stdio.h
int main () {
printf(Hello world\n);
return 0;
}
gcc -Wall compiled without problems but in pcc it doesn't works.
this is the output of pcc -v -o helloworld helloworld.c and
I have no clue about what causes it:
--
/usr/local/libexec//cpp -v -D__PCC__=0 -D__PCC_MINOR__=9
-D__PCC_MINORMINOR__=9 -D__OpenBSD__ -D__unix__ -D__i386__ -D__i386
-D__ELF__ -S /usr/include/ -I
/usr/lib/pcc/TARGMACH-OpenBSD/0.9.9/include helloworld.c /tmp/ctm.1TiiMk
/usr/local/libexec//ccom_i386 -v /tmp/ctm.1TiiMk /tmp/ctm.0IDb4j
/usr/include//time.h, line 112: syntax error
/usr/include//time.h, line 112: syntax error
/usr/include//time.h, line 116: syntax error
/usr/include//time.h, line 116: syntax error
/usr/include//time.h, line 118: syntax error
/usr/include//time.h, line 118: syntax error
/usr/include//stdio.h, line 219: syntax error
/usr/include//stdio.h, line 219: syntax error
/usr/include//stdio.h, line 225: syntax error
/usr/include//stdio.h, line 225: syntax error
/usr/include//stdio.h, line 234: syntax error
/usr/include//stdio.h, line 234: syntax error
/usr/include//stdio.h, line 266: syntax error
/usr/include//stdio.h, line 266: syntax error
/usr/include//stdio.h, line 267: syntax error
/usr/include//stdio.h, line 268: syntax error
/usr/include//stdio.h, line 270: syntax error
/usr/include//stdio.h, line 270: syntax error
/usr/include//stdio.h, line 271: syntax error
/usr/include//stdio.h, line 273: syntax error
/usr/include//stdio.h, line 273: syntax error
/usr/include//stdio.h, line 274: syntax error
/usr/include//stdio.h, line 276: syntax error
/usr/include//stdio.h, line 276: syntax error
/usr/include//stdio.h, line 277: syntax error
/usr/include//stdio.h, line 278: syntax error
/usr/include//stdio.h, line 280: syntax error
/usr/include//stdio.h, line 280: syntax error
/usr/include//stdio.h, line 281: syntax error
/usr/include//stdio.h, line 339: syntax error
/usr/include//stdio.h, line 339: syntax error
/usr/include//stdio.h, line 339: compiler error: too many errors
doing a cvs download from the official website solved the
issue. Sorry for the noise.
-J
Re: What does your environment look like?
On Sun, Jan 3, 2010 at 12:08 AM, Brynet bry...@gmail.com wrote:
Hi,
I know not everyone uses OpenBSD for a desktop OS, but I have been for
nearly 5 years and I'm quite curious about some of your opinions? do you
embrace minimalism or pure aesthetics? are the two mutually exclusive?
When I started using OpenBSD (..around 3.7) I was frequently switching
between window managers, tweaking.. but for 2 years now I've been using
fluxbox and I believe I'm comfortable with it.
* Do you use one of the bundled window managers like
cwm(1)/twm(1)/fvwm(1) or something else?
* What other utilities do you find useful, any dockapps or similar
applets? personal customizations?
* Do you try to keep things uniform across other desktops?
* What does your environment look like? anyone willing to post
screenshots or actual workspace photos?
I realize none of this may be relevant or even useful, but I figured it
was worth asking here anyway.
Anyone feel like humouring me? :-)
Thanks.
-Bryan.
$ pkg_info -t | cut -d ' ' -f 1 | sed 's/-[[:digit:]].\{1,\}$//' | xclip
amsn
amule
d-feet
dejavu-fonts
dosbox
dvd+rw-tools
easytag
emesene
epdfview
firefox35
galculator
gcc
gimp
gmake
gnome-games
gqview
gtk-gnutella
gtk2-clearlooks-engine
gucharmap
hydrogen
inkscape
ion
kqemu
leafpad
mercurial
mpc
mpd
mplayer
no-ip
openoffice
php5-core
pidgin
python
qemu
quake
scrot
tango-icon-theme-extras
thewidgetfactory
tightvnc
tightvnc-viewer
transmission-gui
unrar
unzip
valknut
vlc
vorbis-tools
xchat
xclip
zenity
zip
Mozilla Firefox extensions:
CheckPlaces
DOM Inspector
DownThemAll!
DownloadHelper
Firebug
LiveClick
Rotate Image
SortPlaces
GTK+ control theme: Darkilouche
GTK+ icon theme: Tango
I use ion3 as my wm, made my own skin for it. Most of the time I'm
running Mozilla Firefox, Pidgin, XChat.
Screen shot:
http://img189.imageshack.us/img189/1508/201001030239311024x768s.png
There I'm running:
galculator | leafpad | Mozilla Firefox
--
mpdfind | xterm |
--
xchat
Obviously not my usual layout. I have key bindings for much of those apps:
F2, xterm
F3, run
F4, galculator
F5, leafpad
F6 + file name, leafpad file
F7 + file name, mplayer file
Ctrl + Alt + J, mpdfind (let's me select a file to play with mpc,
pretty cool)
Ctrl + Alt + End, mpc stop
Etc.
Greetings.
Re: What does your environment look like?
On Sat, Jan 2, 2010 at 6:51 PM, J Sisson sisso...@gmail.com wrote: OpenBSD-STABLE with fluxbox on my work desktop. I have a laptop with a busted LCD and keyboard, so I use it as a WinXP slave via rdesktop for running IE (checking websites, as I work in IT for a hosting company). The XP box runs in seamless mode, so fluxbox looks a bit weird with a Windows task bar across the top...but it works haha. At home I have OpenBSD-CURRENT running on my desktop...fluxbox there as well. Both have conky running as my monitor, with three instances: Left one is RSS feeds (undeadly, milw0rm, etc...), middle is CPU/RAM/etc, right is OT: FYI milw0rm went TU quite a while ago. Another good tracker is Offensive Security: http://www.exploit-db.com/
Re: What does your environment look like?
On Sat, Jan 02, 2010 at 09:08:38PM -0500, Brynet wrote: Anyone feel like humouring me? :-) ScrotWM on OpenBSD-stable. The mouse is only useful for, y'know, selecting which xterm to type into (though tmux is lovely enough for me to stick to a single term). -- Key ID: 493FB6AE Key fingerprint: 3E96 7892 B56D AE27 02EF BBAA BAA6 6C78 493F B6AE Keyserver:pgp.mit.edu
Re: Openssl patch breaks Tor
I can compare OpenBSD to dev versions of OpenSolaris, DragonflyBSD, NetBSD or some stable Linux distro and I must say that OpenBSD is more stable and useful in its current version then any other OS in its stable version. Read this http://www.openbsd.org/faq/faq5.html#Flavors and especially this part is just plain true - In fact, as our hope is to continually improve OpenBSD, the goal is that -current should be more reliable, more secure, and of course, have greater features than -stable. Put bluntly, the best version of OpenBSD is -current. There is different problem. Which type of server you want? Too much often customers don't want break of service and they don't want to pay for eg. cluster so their systems are running weeks/months/years without updates. It's strange and in my personal opinion very stupid. If you have something what's not connected to Internet then I think no problem as you don't need to care about remote security. But how useful is server without connection to Internet? ;-) In that case you may find upgrade feature of OpenBSD very useful as you can have system updated in about 5 minutes. It's not possible with any other system. On Sun, Jan 3, 2010 at 12:45 AM, nixlists nixmli...@gmail.com wrote: If I upgrade to -current, don't I risk stability and security issues; or are the chances of that are very low as far as this OS goes? Long time ago I did try development versions of NetBSD and FreeBSD because I needed support for hardware that -stable didn't have, and they were quite shaky. Or do you guys just want more people to use -current for the project progress reasons? I thought -current was for people who are more into hacking code than running a stable server. Thanks. -- http://www.openbsd.org/lyrics.html
