Re: nmea/udcf recommendation
On Mon, Aug 02, 2021 at 06:38:32PM +0200, Jan Stary wrote: >Hello, > >playing with ntpd a bit, I am looking for a working >nmea or udcf sensor. Can people please recommend >an easy to use device known to work? I use a Garmin GPS 18x with ntpd. Works fine, just make sure you flash it with the latest firmware (my model had an older firmware from before the 2019 week number rollover, which confused ntpd so it wouldn't accept the time). I also use a Meinberg C51 DCF receiver. Not as accurate as GPS, but also works fine. This model is EOL. I expect that the newer model (C600RS) also works, but I've never used it. Maurice
Re: 6.3 : how to check microcode?
On Tue, Apr 03, 2018 at 11:37:25PM +1000, Jonathan Gray wrote: >On Tue, Apr 03, 2018 at 01:36:57PM +0200, Maurice Janssen wrote: >> Hi, >> >> I just installed 6.3 and it seems to work great. >> I've a question about the microcode. Is there a way to check whether an >> updated microcode was installed??? I have an i5 Ivybridge CPU and the Intel >> microcode is in /etc/firmware/intel, but I don't see anything in dmesg about >> it. > >The messages regarding microcode versions are gated by UCODE_DEBUG. >You have IBRS,IBPB,STIBP in cpuid so you are running the updated microcode. Great, thanks for your quick reply. Maurice
6.3 : how to check microcode?
Hi, I just installed 6.3 and it seems to work great. I've a question about the microcode. Is there a way to check whether an updated microcode was installed? I have an i5 Ivybridge CPU and the Intel microcode is in /etc/firmware/intel, but I don't see anything in dmesg about it. Thanks in advance, Maurice OpenBSD 6.3 (GENERIC.MP) #107: Sat Mar 24 14:21:59 MDT 2018 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 12751667200 (12160MB) avail mem = 12358139904 (11785MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xeb450 (77 entries) bios0: vendor American Megatrends Inc. version "F22" date 11/14/2013 bios0: Gigabyte Technology Co., Ltd. Z77-D3H acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC MCFG HPET SSDT SSDT SSDT DMAR acpi0: wakeup devices P0P1(S4) USB1(S3) USB2(S3) USB3(S3) USB4(S3) USB5(S3) USB6(S3) USB7(S3) PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) [...] 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) i5-3570 CPU @ 3.40GHz, 3403.81 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,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN cpu0: 256KB 64b/line 8-way L2 cache acpitimer0: recalibrated TSC frequency 3403350537 Hz cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 100MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i5-3570 CPU @ 3.40GHz, 3403.35 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,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: Intel(R) Core(TM) i5-3570 CPU @ 3.40GHz, 3403.35 MHz cpu2: 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,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 6 (application processor) cpu3: Intel(R) Core(TM) i5-3570 CPU @ 3.40GHz, 3403.35 MHz cpu3: 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,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 0, core 3, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpihpet0: recalibrated TSC frequency 3403372040 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (P0P1) acpiprt2 at acpi0: bus 1 (RP01) acpiprt3 at acpi0: bus -1 (RP02) acpiprt4 at acpi0: bus -1 (RP03) acpiprt5 at acpi0: bus -1 (RP04) acpiprt6 at acpi0: bus -1 (RP05) acpiprt7 at acpi0: bus 2 (RP06) acpiprt8 at acpi0: bus 4 (RP07) acpiprt9 at acpi0: bus 5 (RP08) acpiprt10 at acpi0: bus -1 (PEG0) acpiprt11 at acpi0: bus -1 (PEG1) acpiprt12 at acpi0: bus -1 (PEG2) acpiprt13 at acpi0: bus -1 (PEG3) acpiec0 at acpi0: not present acpicpu0 at acpi0: C3(350@80 mwait.1@0x20), C1(1000@1 mwait.1), PSS acpicpu1 at acpi0: C3(350@80 mwait.1@0x20), C1(1000@1 mwait.1), PSS acpicpu2 at acpi0: C3(350@80 mwait.1@0x20), C1(1000@1 mwait.1), PSS acpicpu3 at acpi0: C3(350@80 mwait.1@0x20), C1(1000@1 mwait.1), PSS acpipwrres0 at acpi0: FN00, resource for FAN0 acpipwrres1 at acpi0: FN01, resource for FAN1 acpipwrres2 at acpi0: FN02, resource for FAN2 acpipwrres3 at acpi0: FN03, resource for FAN3 acpipwrres4 at acpi0: FN04, resource for FAN4 acpitz0 at acpi0: critical temperature is 106 degC acpitz1 at acpi0: critical temperature is 106 degC "INT3F0D" at acpi0 not configured acpibtn0 at acpi0: PWRB "PNP0C0B" at acpi0 not configured "PNP0C0B" at acpi0 not configured "PNP0C0B" at acpi0 not configured "PNP0C0B" at acpi0 not configured "PNP0C0B" at acpi0 not configured acpivideo0 at acpi0: GFX0 acpivout0 at acpivideo0: DD02
Re: ispec - PSK - issues
No problems with Android 5.0.2. -Original Message- From: Justin Mayes To: Raul Miller , Maurice Janssen Cc: Steve Clement , OpenBSD general usage list Sent: do, 18 aug. 2016 21:59 Subject: Re: ispec - PSK - issues Hello all - I was also recently trying to do a simple ipsec/l2tp vpn. I found that it works fine for everything except my android 5.1.1 device. The odd thing is that when I watch the log and/or isakmpd output I can see it connect fine, authenticate to l2tp and so on then it immediately disconnects and says that the client caused the disconnection. When I google I see all sorts of issues with android but mostly related to 6+. I can even see in the log that npppd successfully authenticates my android and creates a tunnel, android just kills it all after 1 second for some reason. Can anyone confirm that android 5.1.1 works with openbsd ipsec/l2tp before I spend more hours trying to figure out why just this android device is not working? Here is that tail of the log where l2tp is killed right after starting. npppd[860]: ppp id=20 layer=base logtype=TUNNELSTART user="mike" duration=0sec layer2=L2TP layer2from=x.x.x.x:1701 auth=MS-CHAP-V2 ip=10.0.0.103 iface=pppx0 npppd[860]: ppp id=20 layer=base Using pipex=yes npppd[860]: ppp id=20 layer=lcp terminated by peer npppd[860]: l2tpd ctrl=21 RecvStopCCN result=GENERAL/1 error=none/0 tunnel_id=13671 message="" npppd[860]: l2tpd ctrl=21 call=1 SendCDN result=ADMINISTRATIVE_REASON/3 npppd[860]: l2tpd ctrl=21 call=1 logtype=PPPUnbind npppd[860]: ppp id=20 layer=base logtype=TUNNELUSAGE user="mike" duration=0sec layer2=L2TP layer2from=x.x.x.x:1701 auth=MS-CHAP-V2 data_in=213bytes,9packets data_out=219bytes,10packets error_in=0 error_out=0 mppe=no iface=pppx0 npppd[860]: l2tpd ctrl=21 Received CDN in 'cleanup-wait' state npppd[860]: l2tpd ctrl=21 logtype=Finished Justin -Original Message- From: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org] On Behalf Of Raul Miller Sent: Tuesday, July 26, 2016 7:14 AM To: Maurice Janssen Cc: Steve Clement ; OpenBSD general usage list Subject: Re: ispec - PSK - issues On Tue, Jul 26, 2016 at 2:08 AM, Maurice Janssen wrote: >>https://code.google.com/p/android/issues/detail?id=196939 > > Yeah, that's the link I wanted to send. Somehow I managed to copy the > wrong link in my previous email. I have been seeing a lot of copy&paste errors myself, where I performed the keyboard action to trigger a copy but paste gives me something from an older context. I'm sure a lot of people put a lot of time into making things work this way... -- Raul
Re: ispec - PSK - issues
On Mon, Jul 25, 2016 at 11:13:48PM +0200, Steve Clement wrote: >Your link talks more about 6.0 > >But this is probably it: >https://code.google.com/p/android/issues/detail?id=196939 Yeah, that's the link I wanted to send. Somehow I managed to copy the wrong link in my previous email. Maurice
Re: ispec - PSK - issues
On Mon, Jul 25, 2016 at 04:54:09PM +0200, Steve Clement wrote: >I tried to connect my Nexus 5 with Android 6.0.1 but that plainly failed, no >clue what the correct config should be, so I haven???t reproduced it under the >Droid. There seems to be an issue with Android 6.0.1 and L2TP/IPSEC connetions: https://code.google.com/p/android/issues/detail?id=194269 -- Maurice
Re: PPPoE issues
On 05/29/16 21:53, Maurice Janssen wrote: Hi, I'm trying to replace a PC Engines Alix board with an APU 2c4 board, but I'm having some issues to get it up and running. I have a fiber connection and my ISP requires a PPPoE connection over VLAN 6. With the old setup, this works like a charm. With the new setup, I can't get the PPPoE connection to work. When I use tcpdump on the ethernet interface, I can see the PADI packets leave the system on VLAN6, but there is no answer at all. OpenBSD keeps sending a PADI every minute or so, to no avail. I have tried to get it running with 5.9-stable (amd64), with a recent snapshot (amd64), with 5.9-stable (i386, as that works fine on the Alix), but none of them work. When I have a working connection on the old router and then quickly move the cable (the one that is connected to the fiber/copper converter) to the new router, I can see some packets (belonging to the 'old' PPPoE connection) arriving on the new router (with tcpdump). So at the ethernet level the link is OK. Does anyone have a clue what could be causing this? Some VLAN-tagging issue with the I210 NIC on the APU? Does anyone have a similar setup working? Thanks a lot in advance, Maurice Thanks for the help. It appeared to be a subtle issue at the ethernet link layer, so nothing to do with the software configuration. For the record: there was an ethernet link between the fiber/copper converter and the router (with about 15 m of cat 5e cable in between them), but no data was getting through. When I add a switch next to the converter (and the same 15 m of cable between switch and router), it all works again. Sorry to waste your time on something that has nothing to do with OpenBSD. Maurice
PPPoE issues
Hi, I'm trying to replace a PC Engines Alix board with an APU 2c4 board, but I'm having some issues to get it up and running. I have a fiber connection and my ISP requires a PPPoE connection over VLAN 6. With the old setup, this works like a charm. With the new setup, I can't get the PPPoE connection to work. When I use tcpdump on the ethernet interface, I can see the PADI packets leave the system on VLAN6, but there is no answer at all. OpenBSD keeps sending a PADI every minute or so, to no avail. I have tried to get it running with 5.9-stable (amd64), with a recent snapshot (amd64), with 5.9-stable (i386, as that works fine on the Alix), but none of them work. When I have a working connection on the old router and then quickly move the cable (the one that is connected to the fiber/copper converter) to the new router, I can see some packets (belonging to the 'old' PPPoE connection) arriving on the new router (with tcpdump). So at the ethernet level the link is OK. Does anyone have a clue what could be causing this? Some VLAN-tagging issue with the I210 NIC on the APU? Does anyone have a similar setup working? Thanks a lot in advance, Maurice
Re: 8-Port Serial Port Card
On Sat, Dec 12, 2015 at 09:54:39AM +, Craig Skinner wrote: >On 2015-12-07 Mon 21:30 PM |, Jordon wrote: >> I recently picked up a few PCI serial port cards from the junk pile at >> work. My intent is to put one in my soon-to-be-retired Soekris net5501 >> and install OpenBSD on it to turn it into an 8 port terminal switch. >> >> I tried the cards in a different PC just to see if they would work. >> Unfortunately, none of them were supported. >> > >If you want to get going quickly Jordan, Moxa PCI cards work: > >$ fgrep puc0 /var/run/dmesg.boot >puc0 at pci0 dev 18 function 0 "Moxa C168H" rev 0x01: ports: 8 com >com4 at puc0 port 0 irq 9: ns16550a, 16 byte fifo >com5 at puc0 port 1 irq 9: ns16550a, 16 byte fifo >com6 at puc0 port 2 irq 9: ns16550a, 16 byte fifo >com7 at puc0 port 3 irq 9: ns16550a, 16 byte fifo >com8 at puc0 port 4 irq 9: ns16550a, 16 byte fifo >com9 at puc0 port 5 irq 9: ns16550a, 16 byte fifo >com10 at puc0 port 6 irq 9: ns16550a, 16 byte fifo >com11 at puc0 port 7 irq 9: ns16550a, 16 byte fifo > >I found 3 on ebay.co.uk & grabbed them - all with octopus cable. Beware, Soekris boards have a 3.3 V PCI slot while the Moxa C168H is a 5 V PCI card. -- Maurice
Re: USB mouse often not detected
On Tue, Nov 10, 2015 at 10:47:24AM +0100, Stefan Sperling wrote: >We need a dmesg from both of you. OpenBSD 5.8 (GENERIC.MP) #1: Wed Oct 14 19:38:08 CEST 2015 jas...@stable-58-amd64.mtier.org:/binpatchng/work-binpatch58-amd64/src/sys/arch/amd64/compile/GENERIC.MP real mem = 4160245760 (3967MB) avail mem = 4030267392 (3843MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xeb450 (75 entries) bios0: vendor American Megatrends Inc. version "F22" date 11/14/2013 bios0: Gigabyte Technology Co., Ltd. Z77-D3H acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC MCFG HPET SSDT SSDT SSDT DMAR acpi0: wakeup devices PS2K(S3) PS2M(S3) P0P1(S4) USB1(S3) USB2(S3) USB3(S3) USB4(S3) USB5(S3) USB6(S3) USB7(S3) PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) [...] 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) i5-3570 CPU @ 3.40GHz, 3403.85 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,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 100MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i5-3570 CPU @ 3.40GHz, 3403.36 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,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: Intel(R) Core(TM) i5-3570 CPU @ 3.40GHz, 3403.36 MHz cpu2: 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,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 6 (application processor) cpu3: Intel(R) Core(TM) i5-3570 CPU @ 3.40GHz, 3403.36 MHz cpu3: 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,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 0, core 3, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (P0P1) acpiprt2 at acpi0: bus 1 (RP01) acpiprt3 at acpi0: bus -1 (RP02) acpiprt4 at acpi0: bus -1 (RP03) acpiprt5 at acpi0: bus -1 (RP04) acpiprt6 at acpi0: bus -1 (RP05) acpiprt7 at acpi0: bus 2 (RP06) acpiprt8 at acpi0: bus 4 (RP07) acpiprt9 at acpi0: bus 5 (RP08) acpiprt10 at acpi0: bus -1 (PEG0) acpiprt11 at acpi0: bus -1 (PEG1) acpiprt12 at acpi0: bus -1 (PEG2) acpiprt13 at acpi0: bus -1 (PEG3) acpiec0 at acpi0: not present acpicpu0 at acpi0: C3(350@80 mwait.1@0x20), C1(1000@1 mwait.1), PSS acpicpu1 at acpi0: C3(350@80 mwait.1@0x20), C1(1000@1 mwait.1), PSS acpicpu2 at acpi0: C3(350@80 mwait.1@0x20), C1(1000@1 mwait.1), PSS acpicpu3 at acpi0: C3(350@80 mwait.1@0x20), C1(1000@1 mwait.1), PSS acpipwrres0 at acpi0: FN00, resource for FAN0 acpipwrres1 at acpi0: FN01, resource for FAN1 acpipwrres2 at acpi0: FN02, resource for FAN2 acpipwrres3 at acpi0: FN03, resource for FAN3 acpipwrres4 at acpi0: FN04, resource for FAN4 acpitz0 at acpi0: critical temperature is 106 degC acpitz1 at acpi0: critical temperature is 106 degC acpibat0 at acpi0: BAT0 not present acpibat1 at acpi0: BAT1 not present acpibat2 at acpi0: BAT2 not present acpibtn0 at acpi0: PWRB acpibtn1 at acpi0: LID0 acpivideo0 at acpi0: GFX0 acpivout0 at acpivideo0: DD02 cpu0: Enhanced SpeedStep 3403 MHz: speeds: 3801, 3800, 3600, 3500, 3300, 3200, 3000, 2900, 2700, 2500, 2400, 2200, 2100, 1900, 1800, 1600 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel Core 3G Host" rev 0x09 vga1 at pci0 dev 2 function 0 "Intel HD Graphics 2500" rev 0x09 intagp at vga1 not configured inteldrm0 at vga1 drm0 at inteldrm0 inteldrm0: 1280x1024 wsdisplay0 at vga1 mux 1: console (std, vt100 emulation) wsdisplay0: screen 1-5 added (std, vt100 emulation) xhc
Re: USB mouse often not detected
Paco Willers schreef op 2015-11-10 07:53: Hi, When using a PS/2 mouse everything worked fine. I swapped it for a USB mouse, but this mouse isn't always detected while booting my (386-based) OpenBSD 5.8-stable system. Replugging the mouse when the system is running usually solves the problem: the mouse is detected and works fine. Sometimes this replugging needs to be done several times on different USB ports for it to have effect. Before sending this message I checked whether the mouse itself is the problem because it's a cheap one, so I tried other OSes (Debian Linux 8.2, NetBSD 7.0 and FreeBSD 10.2) and the problem was gone, so my mouse looks OK. Possibly the problem is in the combination of my hardware with OpenBSD. However I would like to use OpenBSD. :) Is this a known problem? I saw some people on this mailing list having trouble with USB mouses periodically reconnecting, but that's not my problem: most of the time it isn't detected at all. I have the same issue, but much less frequent. I guess it happens one out of 20 or 30 times I start the machine and replugging it once (in the same port) always makes it work. And once it works, it keeps working without any further issues. I run 5.8-stable/amd64, but this also happened on 5.7-stable (and I think also on older versions). Maurice
Re: SPARC minimum hardware specification
On Thu, Jul 16, 2015 at 08:25:20PM +0200, Francois Pussault wrote: >> What are the minimum requirements for a "decent" SPARC machine? I mean >> by that a machine who is able to run OpenBSD as a desktop. <...> >for cheaper price : >Maybe somme v4xx or v2xx should be a good choice for budget...like v490 I hope you are making a joke. You definately don't want to use such a noisy beast as a desktop. -- Maurice
Re: ntpd.drift values?
On 01/13/15 19:54, Christian Weisgerber wrote: On 2015-01-13, Stuart Henderson wrote: 2x e-08 (esxi) Oooh, interesting. I hadn't considered VMs that actually keep time. 4.560218e-09 (VM at Transip.nl, don't know what kind of host OS they use) Maurice
nsd_flags
Hi, I just upgraded my nameserver to 5.6-stable and noticed the following line in /etc/rc.conf: nsd_flags=NO# for normal use: "-c /var/nsd/etc/nsd.conf" However, /etc/rc.d/nsd contains the following line: daemon_flags="-c /var/nsd/etc/nsd.conf" I suppose the comment in rc.conf should be: for normal use: "" Just like most other services. Is that correct? Thanks, Maurice
Re: 8 port serial card connections
skin...@britvault.co.uk schreef op 2014-06-20 16:08: Works for me, apart from last 2, but the card isn't listed as supported. /etc/remote: # FIXME No. 9 Moxa card port: moxa09:dv=/dev/tty10:common: # FIXME No. 10 Moxa card port: moxa10:dv=/dev/tty11:common: Try /dev/tty0a and /dev/tty0b Maurice
Re: SunFire v210 for developer
On 03/30/14 22:47, Maurice Janssen wrote: Hi, I have two SunFire V210 machines to offer to any developer (preferably in Europe) that can use such a machine for OpenBSD development. Both are dual CPU 1.0 GHz with 2 GB RAM. Just contact me off list please. Maurice I've had a couple replies, so the machines will be on their way soon. Mauraice
SunFire v210 for developer
Hi, I have two SunFire V210 machines to offer to any developer (preferably in Europe) that can use such a machine for OpenBSD development. Both are dual CPU 1.0 GHz with 2 GB RAM. Just contact me off list please. Maurice
Re: spamd in blacklist only modexd
On 12/11/13 21:06, Alexander Hall wrote:
On 12/10/13 21:38, Maurice Janssen wrote:
How about this (and of course remove the spamd-setup bits from /etc/rc):
--- spamd.orig Tue Dec 10 21:24:48 2013
+++ spamd Tue Dec 10 21:24:14 2013
@@ -15,4 +15,12 @@
return 0
}
+rc_start() {
+ ${rcexec} "${daemon} ${daemon_flags} ${_bg}"
+ spamd_setup_flags="-D"
+ [ X"${spamd_black}" != X"NO" ] && \
+ spamd_setup_flags="-b ${spamd_setup_flags}"
+ rc_do rc_wait start && /usr/libexec/spamd-setup
${spamd_setup_flags}
+}
This seems like the wrong order. Currently, we run spamd-setup prior to
starting spamd, which sounds more appropriate to me.
Are you sure? In /etc/rc, spamd-setup is run after spamd and spamlogd.
Seems more appropriate to me, as spamd-setup sends blacklist data to spamd.
Maurice
Re: spamd in blacklist only modexd
On 12/10/13 14:03, Craig R. Skinner wrote:
On 2013-12-10 Tue 09:26 AM |, Alexander Hall wrote:
The OP is referring to this part of /etc/rc, which has nothing to do
with neither crontab nor /etc/rc.d/*.
if [ X"${spamd_flags}" != X"NO" ]; then
/usr/libexec/spamd-setup -D
fi
Indeed, please suggest a diff.
Maybe we should just incorporate that into /etc/rc.d/spamd instead?
This has worked OK for me for a few months:
Index: rc
===
RCS file: /cvs/src/etc/rc,v
retrieving revision 1.407
diff -u -u -p -r1.407 rc
--- rc 9 Aug 2013 16:24:54 - 1.407
+++ rc 10 Dec 2013 12:59:49 -
@@ -499,10 +499,6 @@ start_daemon rbootd mopd popa3d spamd sp
start_daemon ipropd_master ipropd_slave sndiod
echo '.'
-if [ X"${spamd_flags}" != X"NO" ]; then
- /usr/libexec/spamd-setup -D
-fi
-
# If rc.firstime exists, run it just once, and make sure it is deleted
if [ -f /etc/rc.firsttime ]; then
mv /etc/rc.firsttime /etc/rc.firsttime.run
Index: rc.d/spamd
===
RCS file: /cvs/src/etc/rc.d/spamd,v
retrieving revision 1.3
diff -u -u -p -r1.3 spamd
--- rc.d/spamd 13 Sep 2013 14:50:56 - 1.3
+++ rc.d/spamd 10 Dec 2013 12:59:49 -
@@ -1,18 +1,23 @@
#!/bin/sh
#
-# $OpenBSD: spamd,v 1.3 2013/09/13 14:50:56 okan Exp $
+# $OpenBSD: spamd,v 1.4 2013/09/05 19:08:22 skinner Exp $
-daemon="/usr/libexec/spamd"
+daemon='/usr/libexec/spamd'
. /etc/rc.d/rc.subr
pexp="spamd: \[priv\]"
rc_reload=NO
-rc_pre() {
- [ X"${spamd_black}" != X"NO" ] && \
- daemon_flags="-b ${daemon_flags}"
- return 0
+rc_pre()
+{
+ [[ ${spamd_black} == 'NO' ]] || daemon_flags="-b ${daemon_flags}"
+}
+
+rc_start()
+{
+ ${rcexec} "${daemon} ${daemon_flags} ${_bg}"
+ rc_do rc_wait start && ${daemon}-setup -D
}
rc_cmd $1
Cheers,
Nice, but this also fails to add -b to spamd-setup. How about this (and
of course remove the spamd-setup bits from /etc/rc):
--- spamd.orig Tue Dec 10 21:24:48 2013
+++ spamd Tue Dec 10 21:24:14 2013
@@ -15,4 +15,12 @@
return 0
}
+rc_start() {
+ ${rcexec} "${daemon} ${daemon_flags} ${_bg}"
+ spamd_setup_flags="-D"
+ [ X"${spamd_black}" != X"NO" ] && \
+ spamd_setup_flags="-b ${spamd_setup_flags}"
+ rc_do rc_wait start && /usr/libexec/spamd-setup ${spamd_setup_flags}
+}
+
rc_cmd $1
Re: spamd in blacklist only mode
On 12/09/13 08:41, Jason McIntyre wrote: On Sun, Dec 08, 2013 at 07:59:48PM +0100, Maurice Janssen wrote: Hi, If I understand the man pages correctly, you should start both spamd and spamd-setup with the -b option when you want to use spamd in blacklist only mode. In /etc/rc.d/spamd, the -b option is set when you have spamd_black=yes in your rc.conf.local. However, spamd-setup is always started with -D only from /etc/rc. It doesn't check for the spamd_black environment variable and therefore set -b. So it seems that you have to adapt /etc/rc when you want to run spamd in blacklist only mode. This seems a bit odd, doesn't it? Am I missing something, or is this intended? Thanks, Maurice you shouldn;t have to mess about with the rc.d stuff at all. you run spamd with the -b flag on the command line, or set spamd_black in rc.conf.local. then, following through the man page: spamd-setup(8) should be run periodically by cron(8). When run in blacklist-only mode, the -b flag should be specified. Use crontab(1) to uncomment the entry in root's crontab. hope that's clear. jmc Thanks, the cron part is clear. When spamd-setup is run from cron (with -b), spamd-setup downloads the blacklists as configured in spamd.conf and sends the data to the pf table and to the spamd process. So far so good. But when spamd-setup is run during boot from /etc/rc (without -b), it doesn't send the IPs from the blacklists to pf. Therefore, connections from blacklisted IP's are not redirected to spamd and spamd is not operational until spamd-setup is run from crontab (with -b). This can take up to an hour with the default crontab entry. Not a big deal, but annoying. So why not check for spamd_black in /etc/rc and run spamd-setup with -b in case it is set? Maurice
spamd in blacklist only mode
Hi, If I understand the man pages correctly, you should start both spamd and spamd-setup with the -b option when you want to use spamd in blacklist only mode. In /etc/rc.d/spamd, the -b option is set when you have spamd_black=yes in your rc.conf.local. However, spamd-setup is always started with -D only from /etc/rc. It doesn't check for the spamd_black environment variable and therefore set -b. So it seems that you have to adapt /etc/rc when you want to run spamd in blacklist only mode. This seems a bit odd, doesn't it? Am I missing something, or is this intended? Thanks, Maurice
pflow(4) errata in -stable branch
Hi, I noticed a new patch for pflow(4) in 5.3-stable in 5.4-stable. However, these are not yet in the -stable branch in CVS. I hope someone will commit them. Thanks. Maurice
missing hop on traceroute6
Hi, I'm seeing some behaviour with traceroute6 that I can't explain. I have a small home network with a router/firewall running OpenBSD 5.3-stable. I use pppoe(4) on the WAN interface for IPv4 connectivity. For IPv6, I have a gif tunnel from Sixxs. The gif tunnel has the address 2001:610:600:46b::1 (remote endpoint) and 2001:610:600:46b::2 (local endpoint). The block 2001:610:637::/48 is routed towards me. One of the LAN-interfaces of the router is configured with 2001:610:637:4::/64. When I do a traceroute from a local machine to a host somewhere on the internet, I see all the hops that I expect to see. For example: $ traceroute6 -n xs8.xs4all.nl traceroute6 to xs8.xs4all.nl (2001:888:0:1::888) from 2001:610:637:4::14, 64 hops max, 12 byte packets 1 2001:610:637:4::1 0.503 ms 0.445 ms 0.459 ms 2 2001:610:600:46b::1 6.287 ms 5.624 ms 5.59 ms 3 * * * 4 2001:610:1:80bb:192:87:102:97 5.983 ms 5.716 ms 5.747 ms 5 2001:610:f01:9168::169 5.727 ms 5.734 ms 5.75 ms 6 2001:610:e08:80::81 5.972 ms 19.351 ms 5.865 ms 7 2001:610:f16:6056::2 5.871 ms 9.22 ms 5.989 ms 8 2001:888:1:4000::2 6.612 ms 6.236 ms 6.249 ms 9 2001:888:0:1::888 6.353 ms 6.23 ms 6.24 ms Hop 1 is my local router, hop 2 is the remote tunnel endpoint. When doing a traceroute6 in the reverse direction, I get the following result: $ traceroute6 -n gemini.z74.net traceroute to gemini.z74.net (2001:610:637:4::14), 30 hops max, 80 byte packets 1 2001:888:0:1::1 0.366 ms 0.457 ms 0.555 ms 2 2001:888:1:4000::1 0.505 ms 0.490 ms 2.349 ms 3 2001:610:f16:6056::1 0.466 ms 0.427 ms 0.483 ms 4 2001:610:f01:9216::218 0.970 ms 0.993 ms 1.006 ms 5 2001:610:188:994:145:97:20:249 0.883 ms 1.008 ms 0.904 ms 6 2001:610:1:80bb:192:87:102:107 0.853 ms 0.771 ms 0.792 ms 7 2001:610:600:46b::1 0.921 ms 0.973 ms 0.855 ms 8 2001:610:637:4::14 7.014 ms 7.012 ms 6.978 ms Hop 7 is the remote tunnel endpoint, hop 8 is a system on my home network. I would expect to see an additional line between 7 and 8 for my local router. Is this expected for a gif tunnel or is there a bug in the TTL handling? Best regards, Maurice
Re: Network appliance recomendation.
On 08/09/13 17:05, Francisco Valladolid H. wrote: Hi folks. Currently I have a Wireless network serving in my town using a small form factor (mini-itx) PC with OpenBSD for pf,squid, and dns cache. I need recommendations for a network appliance in rack mode with flash storage and five rj45 ports. Can anyone recommended a solution for my needs ? Axiomtek NA-320R might be an alternative. Rack mount, 6 gbit ports, CF-storage and Atom 1.6 GHz CPU. Maurice
5.3-stable
Hi, A few months ago a bug was fixed in src/usr.sbin/tftpd/tftpd.c This was also applied to 5.2-stable, but it looks to me that the bug is still present in 5.3-stable. Also in Perl, CVE-2013-1667 was fixed in -current and 5.2-stable, not in 5.3-stable. Would it be possible to get these into 5.3-stable? Thanks. Maurice
Re: xenocara build failure
On Mon, May 13, 2013 at 09:15:17PM -0700, Marco S Hyman wrote: >This is probably something stupid I'm doing, but I can't see it right this >second. >Trying to build xenocara from sources pulled from >anon...@anoncvs3.usa.openbsd.org:/cvs >as of about 60 minutes before sending this email message gives me > >*** Error 1 in /usr/xenocara (Makefile:35 'build') > >Any hints as to what I'm doing wrong? Are you using make in parallel (-j) mode? If so, please try without -j Maurice
errata for 5.3-stable
Hi, There is an errata for 5.3 on http://www.openbsd.org/errata53.html which is not in the OPENBSD_5_3 branch in CVS. I'd like to build releases for 5.3-stable as soon as possible after 5.3 is released and I'd rather use CVS to keep my source tree up to date than applying patches by hand. There were also some patches back ported to 5.2-stable that seem a good candidate for 5.3-stable (http://ftp.openbsd.org/pub/OpenBSD/patches/5.2/common/003_tftpd.patch and the fix for Perl CVE-2013-1667). I hope these can be commit to the OPENBSD_5_3 branch soon. Thanks, Maurice
Re: sendmail stops remote delivery when PTR for local IP points to domain-part
On Thu, Mar 21, 2013 at 12:23:18PM +0100, Paul de Weerd wrote: >For the sendmail heroes out there... Let's say I have the following >in DNS: > >$ORIGIN example.com. >@ IN MX 10 mx1 >@ IN A 192.0.2.1 >@ IN 2001:db8::1 >mx1IN A 192.0.2.2 >mx1IN 2001:db8::2 >wwwIN A 192.0.2.1 >wwwIN 2001:db8::1 > >$ORIGIN 2.0.192.in-addr.arpa. >1 IN PTR example.com. >2 IN PTR mx1.example.com. > >$ORIGIN 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.b.d.0.1.0.0.2.ip6.arpa. >1 IN PTR example.com. >2 IN PTR mx1.example.com. > >(assume there's SOA and NS records too, they're not relevant to the >question) > >Now on machine 'www.example.com' (this is the hostname set in >/etc/myname) I would like to send e-mail to x...@example.com. However, >sendmail ignores the MX record and attempts local delivery (which >fails, because 'xxx' is not a local user). Are you sure this is becaus of the PTR record (according to the subject of your email)? I think sendmail looks up the A and MX record for example.com and sees that the A record is a local IP. So, do you need the A record for example.com? In case this record is only needed for those who omit www when trying to visit your website, you might try to use a CNAME instead. Maurice
stable tree
The latest patches on the errata-page for 5.2 and 5.3 are not yet in the stable tree. Is this correct? Also the Perl patch from about a week ago is only back ported to 5.2-stable. Shouldn't these be also in 5.1-stable and 5.3-stable? Thanks, Maurice
Re: Hardware hunting
On Fri, Nov 16, 2012 at 11:33:28AM +0100, Pierre-Emmanuel Andr? wrote: >At work, i'm using a bytemine appliance: >http://blog.bytemine.net/2012/08/15/bytemine-appliance-6a16e/ >https://shop.bytemine.net/startseitenprodukte/bytemine-appliance-6a16e.html > >Works very fine. Does anyone know the dimensions of it? Can't find them on the website of Bytemine and I was wondering if it would fit in 1U when placed on a rack shelf. Thanks, Maurice
Re: SSH_CLIENT in recent OpenBSD releases
On Thu, Oct 11, 2012 at 10:38:04AM +0200, Bernd wrote: >Hi, > >I've got to port some shell scripts which rely on env vars. One >amongst those is $SSH_CLIENT. > >On OpenBSD 5.1 machines, I don't get what I'd assume to get: > ># echo $SSH_CLIENT > >It returns just a blank line. > >I re-tested this on an older development machine, running OpenBSD 4.6: > ># echo $SSH_CLIENT >123.45.67.89 34402 22 I do get an answer like the above on a 5.1 machine. So perhaps something in your local environment that clear it? -- Maurice
Re: ftp in both direction through pf
On 08/21/2012 10:15 AM, lilit-aibolit wrote:
On 08/20/2012 09:49 PM, Maurice Janssen wrote:
On 08/20/2012 04:43 PM, lilit-aibolit wrote:
I have internal ftp-server.
To give access for it from Internet I use ftp-proxy:
ftpproxy_flags="-R ftp_server -p 21 -b ext_ip"
and rules:
anchor "ftp-proxy/*"
pass in on $ext_if inet proto tcp from any to (em1) port ftp
pass out on $int_if inet proto tcp from any to port ftp
user proxy
and this work. But I need to give access to external ftp-servers from my
lan.
I use rules:
match out on $ext_if inet proto tcp from to any nat-to (em1)
pass in on $int_if inet proto tcp from to any port { ftp, >49151 }
pass out on $ext_if inet proto tcp from (em1) to any port { ftp,
>49151 }
and it not work from lan:
what is wrong with my config?
thanks.
You need to start ftp-proxy twice. One to redirect the external
clients to the internal server and another one for the internal clients.
And of course you also need to redirect the internal client to the
second instance of ftp-proxy.
Something like this should work:
rc.conf.local (for internal clients):
ftpproxy_flags=""
rc.local (for external clients):
/usr/sbin/ftp-proxy -R -p 21 -b
And make sure you have something like this in your pf.conf:
pass in on $int_if inet proto tcp to port ftp divert-to 127.0.0.1 port
8021
Thanks for reply Maurice.
I just start new instanse of ftp-proxy and modify rules:
# fstat | grep internet | grep ftp
proxy ftp-proxy 24178 3* internet stream tcp 0xd6354198 127.0.0.1:8021
proxy ftp-proxy 29949 3* internet stream tcp 0xd6bea334 ext_ip:21
# ps -ax | grep ftp
29949 ?? Is 0:00.87 ftp-proxy -R 192.168.2.102 -p 21 -b ext_ip
24178 ?? Is 0:00.00 ftp-proxy
That looks good.
match out on $ext_if inet proto tcp from to any nat-to (em1)
pass in on $int_if inet proto tcp to port ftp divert-to 127.0.0.1 port 8021
pass out on $ext_if inet proto tcp from (em1) to any port { ftp, >49151 }
With this ftp connection work in passive mode, but if I delete >49151 it
stop to work.
You mean for internal clients connecting to external ftp servers?
As it should be? Because man-page don't say to open >49151:
http://www.openbsd.org/cgi-bin/man.cgi?query=ftp-proxy&sektion=8&manpath=OpenBSD+5.1#end
The high port should be opened by ftp-proxy, so something is not right.
Difficult to say without seeing the whole pf.conf.
Maurice
Maurice
Re: ftp in both direction through pf
On 08/20/2012 04:43 PM, lilit-aibolit wrote:
I have internal ftp-server.
To give access for it from Internet I use ftp-proxy:
ftpproxy_flags="-R ftp_server -p 21 -b ext_ip"
and rules:
anchor "ftp-proxy/*"
pass in on $ext_if inet proto tcp from any to (em1) port ftp
pass out on $int_if inet proto tcp from any to port ftp
user proxy
and this work. But I need to give access to external ftp-servers from my
lan.
I use rules:
match out on $ext_if inet proto tcp from to any nat-to (em1)
pass in on $int_if inet proto tcp from to any port { ftp, >49151 }
pass out on $ext_if inet proto tcp from (em1) to any port { ftp, >49151 }
and it not work from lan:
what is wrong with my config?
thanks.
You need to start ftp-proxy twice. One to redirect the external clients
to the internal server and another one for the internal clients.
And of course you also need to redirect the internal client to the
second instance of ftp-proxy.
Something like this should work:
rc.conf.local (for internal clients):
ftpproxy_flags=""
rc.local (for external clients):
/usr/sbin/ftp-proxy -R -p 21 -b
And make sure you have something like this in your pf.conf:
pass in on $int_if inet proto tcp to port ftp divert-to 127.0.0.1 port 8021
Maurice
Re: Unbound
On 05/25/2012 09:00 PM, Sebastian Benoit wrote: 1. run nsd on 127.0.0.1 (or some other ip != your unbound ip) 2. tell unbound where to ask for your local domain "example.com": stub-zone: name: "example.com" stub-addr: 127.0.0.1 If you run nsd on localhost, remember to set do-not-query-localhost to no (default=yes). Took me quite a while to figure out why it didn't work. In some cases it might be easier to run nsd on a different port, so you can send queries to it from other hosts for debugging (or notifies in case of a slave). Maurice
Re: xenocara won't build on vax (5.1-stable)
On 05/07/2012 08:45 AM, Matthieu Herrb wrote: On Sun, May 06, 2012 at 09:57:21PM +0200, Maurice Janssen wrote: Hi, I'm having some trouble building xenocara on a Vaxstation running 5.1-stable. The xenocare source directory is mounted over NFS, in case it matters. The sources are a clean anoncvs checkout and also used by some other platforms (without any problems), so I am pretty sure the tree is OK. I followed the exact steps from FAQ 5.5 and after about 6 hours the build fails. Below are the last lines of make build. Anybody got an idea what might be wrong? This is a known issue with OpenBSD's pkg-config(1). Hmm, deja vu... The current version does not produce the list of libraries needed by sxpm in the correct order. The work around is to use the OpenBSD 4.9 version. Thanks, I'm sure this will help (like 6 months ago, when I asked the same question for 5.0-stable...) Maurice
xenocara won't build on vax (5.1-stable)
Hi, I'm having some trouble building xenocara on a Vaxstation running 5.1-stable. The xenocare source directory is mounted over NFS, in case it matters. The sources are a clean anoncvs checkout and also used by some other platforms (without any problems), so I am pretty sure the tree is OK. I followed the exact steps from FAQ 5.5 and after about 6 hours the build fails. Below are the last lines of make build. Anybody got an idea what might be wrong? Thanks, Maurice Making all in sxpm if gcc -DHAVE_CONFIG_H -I. -I/usr/xenocara/lib/libXpm/sxpm -I.. -I/usr/xenocara/lib/libXpm/include -Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -fno-strict-aliasing -Wbad-function-cast -Wformat=2 -I/usr/X11R6/include -O2 -pipe -MT sxpm.o -MD -MP -MF ".deps/sxpm.Tpo" -c -o sxpm.o /usr/xenocara/lib/libXpm/sxpm/sxpm.c; then mv -f ".deps/sxpm.Tpo" ".deps/sxpm.Po"; else rm -f ".deps/sxpm.Tpo"; exit 1; fi /bin/sh ../libtool --tag=CC --mode=link gcc -Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -fno-strict-aliasing -Wbad-function-cast -Wformat=2 -I/usr/X11R6/include -O2 -pipe-o sxpm sxpm.o -L/usr/X11R6/lib -pthread -lXext -lXdmcp -lXau -lpthread-stubs -lxcb -lX11 -lSM -lICE -lXt ../src/libXpm.la mkdir .libs gcc -Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -fno-strict-aliasing -Wbad-function-cast -Wformat=2 -I/usr/X11R6/include -O2 -pipe -o sxpm sxpm.o -pthread -L/usr/X11R6/lib /usr/X11R6/lib/libXext.a /usr/X11R6/lib/libXt.a /usr/X11R6/lib/libSM.a /usr/X11R6/lib/libICE.a ../src/.libs/libXpm.a -pthread /usr/X11R6/lib/libX11.a /usr/X11R6/lib/libXdmcp.a /usr/X11R6/lib/libXau.a -lpthread-stubs -lxcb sxpm.o: warning: sprintf() is often misused, please use snprintf() Error.o: warning: sprintf() is often misused, please use snprintf() Initialize.o: warning: strcat() is almost always misused, please use strlcat() Initialize.o: warning: strcpy() is almost always misused, please use strlcpy() Intrinsic.o: warning: strcpy() is almost always misused, please use strlcpy() NextEvent.o: warning: sprintf() is often misused, please use snprintf() Shell.o: warning: strcpy() is almost always misused, please use strlcpy() TMaction.o: warning: strcat() is almost always misused, please use strlcat() TMprint.o: warning: strcpy() is almost always misused, please use strlcpy() TMprint.o: warning: sprintf() is often misused, please use snprintf() Converters.o: warning: strcpy() is almost always misused, please use strlcpy() ResConfig.o: warning: strcpy() is almost always misused, please use strlcpy() sm_client.o: warning: strcpy() is almost always misused, please use strlcpy() sm_misc.o: warning: strcpy() is almost always misused, please use strlcpy() process.o: warning: sprintf() is often misused, please use snprintf() authutil.o: warning: strcpy() is almost always misused, please use strlcpy() authutil.o: warning: strcat() is almost always misused, please use strlcat() RdFToI.o: warning: strcpy() is almost always misused, please use strlcpy() scan.o: warning: sprintf() is often misused, please use snprintf() Font.o: warning: strcpy() is almost always misused, please use strlcpy() FSWrap.o: warning: strcpy() is almost always misused, please use strlcpy() GetAtomNm.o: warning: strcpy() is almost always misused, please use strlcpy() IntAtom.o: warning: strcpy() is almost always misused, please use strlcpy() KeysymStr.o: warning: sprintf() is often misused, please use snprintf() SetHints.o: warning: strcpy() is almost always misused, please use strlcpy() XlibInt.o: warning: sprintf() is often misused, please use snprintf() XlibInt.o: warning: strcpy() is almost always misused, please use strlcpy() lcWrap.o: warning: strcpy() is almost always misused, please use strlcpy() lcWrap.o: warning: strcat() is almost always misused, please use strlcat() ErrDes.o: warning: sprintf() is often misused, please use snprintf() lcUTF8.o: warning: sprintf() is often misused, please use snprintf() lcGenConv.o: warning: strcpy() is almost always misused, please use strlcpy() lcDB.o: warning: strcpy() is almost always misused, please use strlcpy() lcFile.o: warning: sprintf() is often misused, please use snprintf() lcFile.o: warning: strcpy() is almost always misused, please use strlcpy() lcFile.o: warning: strcat() is almost always misused, please use strlcat() lcGeneric.o: warning: sprintf() is often misused, please use snprintf() lcGeneric.o: warning: strcat() is almost always misused, please use strlcat() lcGeneric.o: warning: strcpy() is almost always misused, please use strlcpy() lcPubWrap.o: warning: strcpy() is almost always misused, please use strlcpy() lcTxtPr.o: warning: strcpy() is almost always misused, please use strlcpy() imInsClbk.o: warning: strcpy() is almost always misused, please use strlcpy() imInsClbk.o: warning: strcat() is almost always misused, plea
Re: xenocara build fails on vax
On 11/10/2011 09:13 PM, Maurice Janssen wrote: On 11/10/2011 10:51 AM, Matthieu Herrb wrote: On Wed, Nov 9, 2011 at 7:02 PM, Maurice Janssen wrote: Hi, I'm having some trouble doing a build of xenocara on a vaxstation under 5.0-stable. I know it's not needed because there are no patches for xenocara yet for 5.0-stable, but it bugs me that the build fails consistently. There is a know problem with OpenBSD's pkg-config implementation, which shuffles the order of computed libraries dependencies differently than it used to. It needs to be fixed. In the mean time you can use the pkg-config from 4.9 for that. Thanks, Matthieu. I will give it a try and report back, probably after the weekend. As expected, with pkg-config from 4.9 it worked fine. Thanks, Maurice
Re: xenocara build fails on vax
On 11/10/2011 10:51 AM, Matthieu Herrb wrote: On Wed, Nov 9, 2011 at 7:02 PM, Maurice Janssen wrote: Hi, I'm having some trouble doing a build of xenocara on a vaxstation under 5.0-stable. I know it's not needed because there are no patches for xenocara yet for 5.0-stable, but it bugs me that the build fails consistently. There is a know problem with OpenBSD's pkg-config implementation, which shuffles the order of computed libraries dependencies differently than it used to. It needs to be fixed. In the mean time you can use the pkg-config from 4.9 for that. Thanks, Matthieu. I will give it a try and report back, probably after the weekend. Maurice
xenocara build fails on vax
Hi, I'm having some trouble doing a build of xenocara on a vaxstation under 5.0-stable. I know it's not needed because there are no patches for xenocara yet for 5.0-stable, but it bugs me that the build fails consistently. My setup: - An OpenBSD NFS server with the src and xenocara source tree - A bunch of machines, with NFS mounts for /usr/src and /usr/xenocara, all of them doing a build of kernel, userland and xenocara just fine, except xenocara on the vax. So the vax survives a make kernel and make build for userland just fine (so the hardware seems stable), and the other machines also can do a xenocara build just fine (so the xenocara source tree seems OK). - FWIW: this machine was running 4.8-stable before 1 November and I never had a problem with building xenocara on it. - I tried a xenocara build with a fresh install of 5.0-release and after an update to 5.0-stable, but xenocara fails on the same spot. Last lines from the console are below. I hope someone can give me a little push in the right direction. Thanks, Maurice gcc -Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -fno-strict-aliasing -Wbad-function-cast -Wformat=2 -I/usr/X11R6/include -O2 -pipe -o sxpm sxpm.o -L/usr/X11R6/lib /usr/X11R6/lib/libXt.a /usr/X11R6/lib/libSM.a /usr/X11R6/lib/libICE.a /usr/X11R6/lib/libXext.a ../src/.libs/libXpm.a /usr/X11R6/lib/libX11.a -lxcb sxpm.o: warning: sprintf() is often misused, please use snprintf() Error.o: warning: sprintf() is often misused, please use snprintf() Initialize.o: warning: sprintf() is often misused, please use snprintf() Initialize.o: warning: strcat() is almost always misused, please use strlcat() Initialize.o: warning: strcpy() is almost always misused, please use strlcpy() Intrinsic.o: warning: strcpy() is almost always misused, please use strlcpy() NextEvent.o: warning: sprintf() is often misused, please use snprintf() Selection.o: warning: sprintf() is often misused, please use snprintf() Shell.o: warning: strcpy() is almost always misused, please use strlcpy() Shell.o: warning: sprintf() is often misused, please use snprintf() TMaction.o: warning: strcat() is almost always misused, please use strlcat() TMprint.o: warning: strcpy() is almost always misused, please use strlcpy() TMprint.o: warning: sprintf() is often misused, please use snprintf() Converters.o: warning: strcpy() is almost always misused, please use strlcpy() ResConfig.o: warning: sprintf() is often misused, please use snprintf() ResConfig.o: warning: strcpy() is almost always misused, please use strlcpy() sm_client.o: warning: strcpy() is almost always misused, please use strlcpy() sm_misc.o: warning: strcpy() is almost always misused, please use strlcpy() process.o: warning: sprintf() is often misused, please use snprintf() authutil.o: warning: strcpy() is almost always misused, please use strlcpy() authutil.o: warning: strcat() is almost always misused, please use strlcat() RdFToI.o: warning: strcpy() is almost always misused, please use strlcpy() scan.o: warning: sprintf() is often misused, please use snprintf() Font.o: warning: strcpy() is almost always misused, please use strlcpy() FSWrap.o: warning: strcpy() is almost always misused, please use strlcpy() GetAtomNm.o: warning: strcpy() is almost always misused, please use strlcpy() InitExt.o: warning: strcpy() is almost always misused, please use strlcpy() IntAtom.o: warning: strcpy() is almost always misused, please use strlcpy() KeysymStr.o: warning: sprintf() is often misused, please use snprintf() SetHints.o: warning: strcpy() is almost always misused, please use strlcpy() XlibInt.o: warning: sprintf() is often misused, please use snprintf() XlibInt.o: warning: strcpy() is almost always misused, please use strlcpy() lcWrap.o: warning: strcpy() is almost always misused, please use strlcpy() lcWrap.o: warning: strcat() is almost always misused, please use strlcat() ErrDes.o: warning: sprintf() is often misused, please use snprintf() lcUTF8.o: warning: sprintf() is often misused, please use snprintf() lcGenConv.o: warning: strcpy() is almost always misused, please use strlcpy() XKBGAlloc.o: warning: strcpy() is almost always misused, please use strlcpy() lcDB.o: warning: strcpy() is almost always misused, please use strlcpy() lcFile.o: warning: strcpy() is almost always misused, please use strlcpy() lcFile.o: warning: sprintf() is often misused, please use snprintf() lcFile.o: warning: strcat() is almost always misused, please use strlcat() lcGeneric.o: warning: strcpy() is almost always misused, please use strlcpy() lcGeneric.o: warning: sprintf() is often misused, please use snprintf() lcGeneric.o: warning: strcat() is almost always misused, please use strlcat() lcPubWrap.o: warning: strcpy() is almost always misused, please use strlcpy() lcPublic.o: warning: strcpy() is almost always misused, please use strlcpy() lcTxtPr.o: warning: strcpy() is almost always misused, please use
Re: Detect APC UPS is on battery
Op Wo, 19 oktober, 2011 11:41, schreef Paul de Weerd: > So .. what is the fundamental difference from a 'real' UPS that can > signal the machine itself that power is going down ? You get to do > the same steps "in case power is restored while we're going down". > The difference is that a smart UPS can be told to kill the power in the rc.shutdown script. If the UPS does what it is supposed to do, it will kill the power to the computer and wait until the power is restored or it will cycle the power to the computer if the power comes back after the 'kill power command' is received but before the power is killed. Maurice
Re: Changing to tty2 on an iBook
On 08/13/2011 06:58 AM, Hugo Osvaldo Barrera wrote: On most PCs I've handled, I change across consoles using alt+ctrl+f2, alt+ctrl+f3, etc. I've now installed OpenBSD on an iBook G4, which doesn't quite have f1-f12 keys. It has a "brightness-up" key, and if I press fn+brightness_up, it works like an f2 key. HOWEVER, if I press ctrl+alt+fn+brightness_up, this will not switch me over to tty2 for some reason. Is there any workaround for this? How have users of similar notebooks handled this? Run tmux or X. Multiple virtual consoles are only supported on i386, amd64, zaurus and some alpha (according to FAQ 7.4). Maurice
Re: awkward usb-to-serial adapter problem -more data!-
On 08/01/2011 01:47 PM, Daniel Gracia wrote: Known facts: * uticom is awful unstable. * uftdi is unstable. New facts: I have got from friday an uplcom quad-port adapter that looks quite stable; as today, I haven't got a single freeze (still testing). FWIW: I've used a uplcom adapter for a couple of years to connect a UPS with a serial port to a Soekris and later an Alix board. It worked fine in general, perhaps one or two hickups during that time. I can't remember if a reboot was needed to get it working again or only unplug & plug in again. Maurice
Re: ISAKMPD
MG wrote: Forgive my ignorance, but does this mean that if I were to install OpenBSD 4.9 via FTP today, there shouldn't be random IPsec disconnects as described in bug PR6601? Thanks. The file sets on ftp.openbsd.org/pub/OpenBSD/4.9/ (and of course on all official mirrors) are 4.9-release (the same as on the CD). If you don't mind getting your files from an non-official source, you can install or update from ftp://ftp.openbsd-stable.org./pub/OpenBSD-stable/4.9-stable/ The patch for isakmpd is included in these file sets. Maurice BTW: openbsd-stable.org is my pet project, so I'm a bit biased.
Re: SMP machine, run a program on a single CPU?
On Sat, Jul 09, 2011 at 07:52:58AM -0400, Nick Holland wrote: >On 07/09/11 03:57, Maurice Janssen wrote: >> Hi, >> >> Is it possible to somehow force a program to run on a single CPU in an >> SMP system? >> The reason I ask that on some SMP-capable architectures, I'm having some >> problems with ntpd. On hppa and sgi, the clock won't sync because ntpd >> sees replies with negative delay: >> >> Jul 9 08:58:19 hppa ntpd[21406]: reply from 192.168.4.12: negative >> delay -0.854615s, next query 3120s >> >> (reported as PR6592) >> >> If I run the bsd.sp kernel, the negative delays are gone and ntpd syncs >> without any problem. I was wondering if the problem would occur if I >> could limit ntpd to a single CPU. Diving into the code is way beyond my >> skills, so I was hoping that there is a utility like nice to achieve this. >> >> Thanks, >> Maurice > >Things aren't that simple. >Time is an illusion. Lunch time, doubly so >(obligatory Hitchhiker's quote) >Time on computers is complicated, doubly so on a multiprocessor system. > >ntpd isn't your problem, it's time on the SMP system. Fiddling with >processor affinity (trying to attach particular tasks to particular >CPUs) wouldn't help if you could (and you can't). OK, thanks for making that clear. >Is time really drifting (consistently increasing error in one direction) >on these systems? Or is it just "jittering" around proper time? The hppa was about 10 seconds behind proper time since boot (the machine is not powered on anymore). The delay was quite stable. The sgi was close to proper time (within one second) and finally synced the clocked after about 4 hours. But the 'negative delay' lines keep appearing in /var/log/daemon: Jul 9 07:10:40 sgi ntpd[25403]: ntp engine ready Jul 9 07:11:47 sgi ntpd[7566]: set local clock to Sat Jul 9 07:11:47 CEST 2011 (offset 66.702436s) Jul 9 07:11:53 sgi ntpd[25403]: reply from 192.168.4.10: negative delay -0.422241s, next query 3298s Jul 9 07:11:55 sgi ntpd[25403]: reply from 192.168.4.12: negative delay -0.420484s, next query 3071s Jul 9 08:03:06 sgi ntpd[25403]: 0 out of 2 peers valid Jul 9 08:03:06 sgi ntpd[25403]: bad peer ntp.z74.net (192.168.4.10) Jul 9 08:03:06 sgi ntpd[25403]: bad peer ntp2.z74.net (192.168.4.12) Jul 9 08:03:06 sgi ntpd[25403]: reply from 192.168.4.12: negative delay -0.419880s, next query 3052s Jul 9 08:07:02 sgi ntpd[25403]: reply from 192.168.4.10: negative delay -0.422318s, next query 3238s Jul 9 08:53:58 sgi ntpd[25403]: reply from 192.168.4.12: negative delay -0.419919s, next query 3083s Jul 9 09:00:59 sgi ntpd[25403]: peer 192.168.4.10 now valid Jul 9 09:01:22 sgi ntpd[25403]: reply from 192.168.4.10: negative delay -0.422266s, next query 3053s Jul 9 09:45:21 sgi ntpd[25403]: reply from 192.168.4.12: negative delay -0.420109s, next query 3036s Jul 9 09:52:46 sgi ntpd[27014]: adjusting local clock by -0.370742s Jul 9 09:53:17 sgi ntpd[25403]: reply from 192.168.4.10: negative delay -0.415123s, next query 3068s Jul 9 10:36:11 sgi ntpd[25403]: peer 192.168.4.12 now valid Jul 9 10:38:47 sgi ntpd[25403]: reply from 192.168.4.12: negative delay -0.420481s, next query 3214s Jul 9 10:44:24 sgi ntpd[25403]: reply from 192.168.4.10: negative delay -0.422004s, next query 3188s Jul 9 11:32:21 sgi ntpd[25403]: reply from 192.168.4.12: negative delay -0.420039s, next query 3204s Jul 9 11:38:39 sgi ntpd[27014]: adjusting local clock by 0.099333s Jul 9 11:38:38 sgi ntpd[25403]: clock is now synced Jul 9 11:39:09 sgi ntpd[25403]: reply from 192.168.4.10: negative delay -0.422172s, next query 3257s Jul 9 12:25:45 sgi ntpd[25403]: reply from 192.168.4.12: negative delay -0.419923s, next query 3077s and this keeps on going. >If it >is really drifting, you should probably put in a problem report on this. I got an email from Joel Sing, he's going to take a closer look. Thanks, Maurice
SMP machine, run a program on a single CPU?
Hi, Is it possible to somehow force a program to run on a single CPU in an SMP system? The reason I ask that on some SMP-capable architectures, I'm having some problems with ntpd. On hppa and sgi, the clock won't sync because ntpd sees replies with negative delay: Jul 9 08:58:19 hppa ntpd[21406]: reply from 192.168.4.12: negative delay -0.854615s, next query 3120s (reported as PR6592) If I run the bsd.sp kernel, the negative delays are gone and ntpd syncs without any problem. I was wondering if the problem would occur if I could limit ntpd to a single CPU. Diving into the code is way beyond my skills, so I was hoping that there is a utility like nice to achieve this. Thanks, Maurice
Re: xenocara doesn't build correctly on 4.9-stable/hppa
Maurice Janssen wrote: Hi, I noticed something strange while building xenocara on 4.9-stable on an hppa-system. One of the files in the xbase49.tgz file set (from 4.9-release) is /usr/X11R6/lib/libfontconfig.so.7.0. After 'make build', there's a libfontconfig.so.5.4 in /usr/X11R6/lib/ that is identical to the 7.0 file from -release. When I do 'make release', only the 5.4 file ends up in /usr/dest/ , resulting in a missing libfontconfig.so file in the xbase49.tgz file set (the maketars script expects that libfontconfig.so.7.0 is there, but it isn't). So for some reason, the libfontconfig.so.x.y file has the wrong name. I tried to find the cause, but I get lost in Makefiles and configure scripts. BTW: I followed the exact steps from the FAQ (section 5.5), with the xenocara source tree on an NFS server. The build / release process works without a hitch on other architectures that use the same NFS server for the source tree. Does anyone know what is going on and, even better, how to fix it? After some more testing, it seems that make -j is causing the problem. I thought xenocara was make -j safe, but apparantly there are some corner cases where things can go wrong. I am now doing a make build again (without -j), and it seems that the problem is gone. Maurice
xenocara doesn't build correctly on 4.9-stable/hppa
Hi, I noticed something strange while building xenocara on 4.9-stable on an hppa-system. One of the files in the xbase49.tgz file set (from 4.9-release) is /usr/X11R6/lib/libfontconfig.so.7.0. After 'make build', there's a libfontconfig.so.5.4 in /usr/X11R6/lib/ that is identical to the 7.0 file from -release. When I do 'make release', only the 5.4 file ends up in /usr/dest/ , resulting in a missing libfontconfig.so file in the xbase49.tgz file set (the maketars script expects that libfontconfig.so.7.0 is there, but it isn't). So for some reason, the libfontconfig.so.x.y file has the wrong name. I tried to find the cause, but I get lost in Makefiles and configure scripts. BTW: I followed the exact steps from the FAQ (section 5.5), with the xenocara source tree on an NFS server. The build / release process works without a hitch on other architectures that use the same NFS server for the source tree. Does anyone know what is going on and, even better, how to fix it? Thanks, Maurice
Re: Updating 'Release' with packaged Security Fixes
mailbox wrote: Are there considerations to push the very few changes marked as 'Security Fixes' into the 'Release' branch between releases? So that a 'Release' user could do a pgk_add -u fixed.tgz to get the fixed version of the package. This would benefit users who like to have the 2 or 3 'Security Fixes' covered without the need to apply patches by hand or working with the Patch branch. Not as simple as pkg_add -u, but there are file sets for -stable releases available (www.openbsd-stable.org). It's not an official part of OpenBSD, so it's up to you to trust those files or not. Maurice BTW: I started it a few years ago, so I'm a bit biased.
Re: Strange pf match
On Wed, Feb 16, 2011 at 04:27:27AM -0800, m wrote: >Hi again, > >could someone please tell me how it's possible for a rule to match wrong dst >address? Under what circumstances woult it match in that way? Do I have to >rewrite all IPRange rules? This is fixed in -current: http://marc.info/?l=openbsd-cvs&m=129768133121806&w=2 I'm not sure if this fix will go into 4.7-stable and 4.8-stable, but I think it will. Maurice
xenocara: make release fails on vax/4.8-stable
Hi, On vax/4.8-stable, make release in /usr/xenocara fails with + install -c -o root -g wheel -m 644 /usr/xenocara/etc/X11.vax/xorg.conf /usr/dest/etc/X11 install: /usr/xenocara/etc/X11.vax/xorg.conf: No such file or directory *** Error code 71 Stop in /usr/xenocara (line 97 of Makefile). This seems to be fixed in revision 1.38 of /usr/xenocara/Makefile (commit comment: make 'make release' work on vax), but this is only in -current, not in 4.8-stable. Shouldn't this be commited to the stable branch as well? Thanks. Maurice
Re: something weird with perl in CVS?
Philip Guenther wrote: On Sat, Oct 30, 2010 at 10:34 AM, Maurice Janssen wrote: A few days ago, I extracted the src.tar.gz from the 4.8 CDROM and synchronized the src tree to -stable through CVS. I expected to see about 5 files being changed, but to my surprise a lot (all?) files in src/gnu/usr.bin/perl/ were also updated. This seems weird, because as far as I know, no commits were done to CVS in the perl directory with a OPENBSD_4_8 tag and certainly not so many. I looked at a few files for the differences and until know I've seen only changes in the comments, for example: (src0/ is a clean copy from src.tar.gz from the CDROM, src/ is synced through CVS to OPENBSD_4_8) ... Does anybody know what has happened? There was a late change in the keyword substitution mode for those files. That's a per-file mode (note that it's *not* per-revision per-mode) and there are no email messages generated for them, just as no messages generated for imports. I assume that my src tree (after syncing with CVS and therefore with all the 'new' files in gnu/usr.bin/perl) is still suitable for building 4.8-stable. Is this assumption correct? Yep, it's good. OK, thanks for your answer. Maurice
something weird with perl in CVS?
Hi, A few days ago, I extracted the src.tar.gz from the 4.8 CDROM and synchronized the src tree to -stable through CVS. I expected to see about 5 files being changed, but to my surprise a lot (all?) files in src/gnu/usr.bin/perl/ were also updated. This seems weird, because as far as I know, no commits were done to CVS in the perl directory with a OPENBSD_4_8 tag and certainly not so many. I looked at a few files for the differences and until know I've seen only changes in the comments, for example: (src0/ is a clean copy from src.tar.gz from the CDROM, src/ is synced through CVS to OPENBSD_4_8) $ diff -u src0/gnu/usr.bin/perl/x2p/Makefile.SH src/gnu/usr.bin/perl/x2p/Makefile.SH --- src0/gnu/usr.bin/perl/x2p/Makefile.SH Sat Oct 24 19:01:02 2009 +++ src/gnu/usr.bin/perl/x2p/Makefile.SHThu Oct 28 20:42:22 2010 @@ -27,12 +27,9 @@ echo "Extracting x2p/Makefile (with variable substitutions)" rm -f Makefile cat >Makefile <
Re: Spanish hardware list is more detailed
On Fri, Sep 17, 2010 at 08:25:00AM -0300, Hugo Osvaldo Barrera wrote: >I wanted to know if the "Adaptec Quartet64 ANA-62044" was supported on >OpenBSD, and started to google around, only to find that the *spanish* list >of supported hardware has a greater level of detail when compared to the >english version. >I found that the entire "ethernet adapters" section is by far more detailed >in it's spanish version: > >http://www.openbsd.org/es/amd64.html >http://www.openbsd.org/amd64.html > >While the english verision just says "Adaptec \"Starfire\" AIC-6915 based >PCI adapters", the spanish version says the same, and a list of four know >supported adapters. The spanish translation is not maintained at the moment and is therefore not up to date. The mentioned page http://www.openbsd.org/es/amd64.html was translated almost 6 years ago... Maurice
Re: Is there anything I can use in place of MATLAB on OpenBSD?
Siju George wrote: Hi, Is there anything I can use in place of MATLAB on OpenBSD? http://www.mathworks.com/products/matlab/ even at least through Linux emulation? Looking for a free Alternative :-) Octave might be an alternative: http://www.gnu.org/software/octave/ Maurice
dependencies for RAMDISK kernel
Hi, I just built a new kernel and a new release for 4.7-stable, because of the patch in the OPENBSD_4_7 tree. I noticed that the release process builds a new bsd and bsd.mp kernel, but the bsd.rd ramdisk kernel is identical to the old ramdisk kernel from when the first release was built on this system. I this supposed to happen like this? I suspected that 'make release' will also build a new ramdisk kernel, with today's patches on sd.c, st.c and cd.c in it, but also with the correct checksums of the new file sets. Any ideas? Thanks. Maurice
Re: 4.6 patch support
On Mon, Mar 22, 2010 at 01:36:45PM +0200, Andreas Gerdd wrote: >Hi, > >I've an OpenBSD 4.6-Stable system. I wanted to ask how long will >OBSD4.6 has patch/update support? >If there is a support time limit like lets say up to 12/24 months, >does it mean after that time, it will not get any update, not even >(possible) critical vulnerabilities? http://www.openbsd.org/faq/faq5.html#Flavors
Re: apachectl restart bug?
On Thu, Mar 11, 2010 at 04:08:10PM +0200, Ozgur Kazancci wrote: >When apachectl issuing a restart, it sends a SIGHUP signal to httpd, >and when httpd receives this signal, it doesn't exit from its chroot. >So, "apachectl restart" becomes unfunctional when you have external >modules via LoadModule in your httpd.conf. That's a documented 'feature' in man apachectl: restart Restart httpd(8) by sending it a SIGHUP. If the daemon is not running, it is started. This command automatically checks the configuration files via configtest before initi- ating the restart to make sure httpd(8) doesn't die. If httpd runs chrooted (default in OpenBSD) and 3rd party mod- ules are loaded, restart may fail due to path inconsisten- cy. Completely stop and start the daemon instead.
Re: allow dhcp in pf
On Tue, Nov 24, 2009 at 05:08:06PM +0400, open...@e-solutions.re wrote:
>Hello
>
>i added theses lines :
>pass in on $int_if inet proto { tcp, udp } from any to $gw_obsd port 67
>pass in on $int_if inet proto { tcp, udp } from any to $gw_obsd port 68
>
>my dhcpd.conf is a standard config...
>my hostname.bge0 :
>inet 192.168.0.1 255.255.255.0 NONE
You have to adapt dhcpd.conf to YOUR network configuration.
Take a look at the log files. You will probably see that dhcpd didn't
start succesfully.
Maurice
Re: Spanish language resources for OpenBSD
On Thu, Nov 19, 2009 at 10:35:35AM -0300, Hugo Osvaldo Barrera wrote: > >I'd very much like to help translate, specially the FAQ and the website. >However, should this be discussed in misc@ or www@ ? Please read http://www.OpenBSD.org/translation.html and contact one of the coordinators. Maurice
Re: Compiling 4.6 i386 GENERIC - error - don't know how to make vers.o. Stop in ...
Lars Nooden wrote: Ingo Schwarze wrote: When not only tracking -current, but even building the system from source, consider following source-changes@, or you will from time to time miss minor flag days. Ok. Taken care of. Is there a message header or string in the body that can be used to sort -current from -stable ? Sure, all commit's to the -stable branch have OPENBSD_4_6 or OPENBSD_4_5 Maurice
Re: kern.bufcachepercent
On Wed, Nov 04, 2009 at 10:26:50AM -0500, Luis Useche wrote: >OK. Sorry for the noise. In any case, this change is in the 4.6 >changelog (twice, http://www.openbsd.org/plus46.html): > >"Added dynamic buffer cache sizing. The sysctl kern.bufcachepercent >will allow you to specify a high-water mark above 10 percent for use >by the cache. If you run low on memory, the page daemon will reclaim >pages from the buffer cache. " > >"Added a kern.bufcachepercent sysctl(8) to allow adjusting the buffer >cache size on a running system." No, three times: "Backed out all the c2k9 buffer cache changes committed during c2k9." Maurice
Re: make release fails on sgi
Miod Vallat wrote: Maurice Janssen wrote: Hi, I'm trying to build the file sets for 4.6-stable on an O2 machine, but it keeps failing with the following error: In file included from mips64/cpu.h:358, from machine/cpu.h:5, from mips64/param.h:44, from machine/param.h:42, from ../../../../sys/param.h:95, from ../../../../altq/altq_subr.c:30: ../../../../sys/sched.h:110: error: bit-field `spc_qs' width not an integer constant *** Error code 1 Stop in /usr/src/sys/arch/sgi/compile/GENERIC-IP27 (line 92 of /usr/share/mk/sys.mk). *** Error code 1 Stop in /usr/src/etc (line 12 of etc.sgi/Makefile.inc). Just had a similar error during building xenocara file sets: In file included from /usr/xenocara/xserver/include/miscstruct.h:53, from /usr/xenocara/xserver/include/regionstr.h:53, from /usr/xenocara/xserver/include/region.h:51, from /usr/xenocara/xserver/include/window.h:52, from /usr/xenocara/xserver/include/input.h:55, from /usr/xenocara/xserver/include/inputstr.h:52, from /usr/xenocara/xserver/Xi/selectev.c:60: /usr/X11R6/include/pixman-1/pixman.h:149: error: bit-field `p1' width not an integer constant *** Error code 1 Stop in /usr/xenocara/kdrive/obj/Xi (line 821 of Makefile). Can this be caused by flaky hardware? Maybe, but then this could be an unexpected compiler configuration change. Do you have an /etc/mk.conf file specifying fancy compiler options? You might want to look at the files causing compilation problems (sys/sched.h, xenocara/lib/pixman/pixman/pixman.h) and compare them to fresh 4.6 files as well. Or it could be that either /usr/include/machine/_types.h or /usr/include/sys/_types.h has been modified or replaced, and definitions of types such as int32_t are missing. The source tree is a clean checkout and there is no /etc/mk.conf. I moved the hard disk to a different machine and both make build and make release finished without a hitch. So it seems the first O2 does have some hardware problem. The machine is building X now, I have good hopes it will finish this as well. Maurice
Re: make release fails on sgi
Maurice Janssen wrote: Hi, I'm trying to build the file sets for 4.6-stable on an O2 machine, but it keeps failing with the following error: In file included from mips64/cpu.h:358, from machine/cpu.h:5, from mips64/param.h:44, from machine/param.h:42, from ../../../../sys/param.h:95, from ../../../../altq/altq_subr.c:30: ../../../../sys/sched.h:110: error: bit-field `spc_qs' width not an integer constant *** Error code 1 Stop in /usr/src/sys/arch/sgi/compile/GENERIC-IP27 (line 92 of /usr/share/mk/sys.mk). *** Error code 1 Stop in /usr/src/etc (line 12 of etc.sgi/Makefile.inc). Just had a similar error during building xenocara file sets: In file included from /usr/xenocara/xserver/include/miscstruct.h:53, from /usr/xenocara/xserver/include/regionstr.h:53, from /usr/xenocara/xserver/include/region.h:51, from /usr/xenocara/xserver/include/window.h:52, from /usr/xenocara/xserver/include/input.h:55, from /usr/xenocara/xserver/include/inputstr.h:52, from /usr/xenocara/xserver/Xi/selectev.c:60: /usr/X11R6/include/pixman-1/pixman.h:149: error: bit-field `p1' width not an integer constant *** Error code 1 Stop in /usr/xenocara/kdrive/obj/Xi (line 821 of Makefile). Can this be caused by flaky hardware? Maurice
Re: make release fails on sgi
Miod Vallat wrote: Hi, I'm trying to build the file sets for 4.6-stable on an O2 machine, but it keeps failing with the following error: That's odd. What is the revision number of sys/sched.h in your source tree? It's 1.22 Maurice
make release fails on sgi
Hi, I'm trying to build the file sets for 4.6-stable on an O2 machine, but it keeps failing with the following error: In file included from mips64/cpu.h:358, from machine/cpu.h:5, from mips64/param.h:44, from machine/param.h:42, from ../../../../sys/param.h:95, from ../../../../altq/altq_subr.c:30: ../../../../sys/sched.h:110: error: bit-field `spc_qs' width not an integer constant *** Error code 1 Stop in /usr/src/sys/arch/sgi/compile/GENERIC-IP27 (line 92 of /usr/share/mk/sys.mk). *** Error code 1 Stop in /usr/src/etc (line 12 of etc.sgi/Makefile.inc). Does anyone know what the problem might be? Thanks, Maurice
Re: ALIX and PC Engines CompactFlash
Jan Stary wrote: would you please share the RELEVANT PORTION OF YOUR DMESG for the card (and your opinions if you'd like)? I'm particularly interested in what's reported for x-sector PIO and related. It might be a bit late, but ... $ dmesg | grep wd wd0 at pciide0 channel 0 drive 0: wd0: 1-sector PIO, LBA, 3823MB, 7831152 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 root on wd0a swap on wd0b dump on wd0b $ This is on 4.5. I use that card in my Alix-based firewall. So far I didn't have any problems with it. Some time ago, it was suggested that the "1-sector PIO" is what's occasionaly "slow" about some of these cards (e.g. when untarring a big tgz during an install). Sadly, I have never seen any multi-sector PIO card. And obviuosly, I will be upgrading soon (ALICes, actually). Can people recommend some quality multi-sector PIO CF cards? wd0 at wdc0 channel 0 drive 0: wd0: 4-sector PIO, LBA, 977MB, 2001888 sectors This is a SanDisk CF card I got some years ago. I think it's an Ultra-II card, but I'm not 100% sure. It works fine in my Soekris box. Maurice
Re: Defending OpenBSD Performance
Bob Beck wrote: Once you have a built release you can run upgrades everywhere from that release tarball. man release to figure out how to do that. Now you may ask, why don't we do that? We simply do not have the resources and time to devote racks of machines, developer time, and internet bandwidth to building stable somewhere for all architectures, and distributing it securely. I started doing this a couple years ago. But not for all architectures and I also must add that these are not 'official'. I'm not an OpenBSD developer, just some nut who thinks this might be useful for others. Sometimes I wonder why I keep doing it ;-) Maurice
Re: shutting down
Mauro Rezzonico wrote: Why don't ask the NSF server to do a 'shutdown +5' and the others to do a 'shutdown now'? (see shutdown(8) http://www.openbsd.org/cgi-bin/man.cgi?query=shutdown) The NFS-server is an embedded device (Netgear NAS). Unfortunately I can't set the +5 on the shutdown command... Sorry I know nothing about this 'nut' software you are talking about... nut = networkupstools from ports. Quite nice set of tools to talk to your ups. Maurice
Re: shutting down
Toni Mueller wrote: Hi, On Fri, 11.09.2009 at 22:28:43 +0200, Maurice Janssen wrote: Will the master shutdown normally, or will it stall while trying to umount the NFS share? The slaves will shutdown first, so when the master goes down, the NFS server won't be responding. man mount_nfs You can mount NFS shares soft. This means that it becomes less reliable for you, but your clients won't hang if you shut down your NFS server first. Another option could be to somehow notify your NFS clients, so they know that they need to unmount the NFS shares. I tried it, but there's still a time-out of several minutes. Not ideal when the UPS might kill the power any minute. I solved it by using upssched from nut. When the battery goes low, I umount the NFS share on the master (this is the only machine that has a share mounted on the NFS-server). The slaves will begin to shutdown a couple of seconds after the battery goes low, so this should be OK. I'll do some tests to see if this really works as I think it does. Maurice
shutting down
Hi, I have a few systems that are powered by the same UPS. All of them are running nut; one system is connected to the UPS over the serial port (the 'master'), the others are talking over the network to the master (the 'slaves'). One of the slaves is acting as an NFS server and the master has a directory from the NFS-server mounted. I'm wondering what will happen if the battery goes low and the NFS server will shutdown first. Will the master shutdown normally, or will it stall while trying to umount the NFS share? The slaves will shutdown first, so when the master goes down, the NFS server won't be responding. The master doesn't have to wait for the NFS server, so umount -at nonfs would be fine. Does this happen automatically or is there some way to configure this? Thanks, Maurice
Re: ksplice
Siju George wrote: Do you have plans to introduce binary updates for OpenBSD so that hours are not spent on compile time?. A few years ago I started to create file sets of the -stable tree. See http://www.z74.net/openbsd.html for more information. It's far from perfect, but perhaps it's useful to you. Maurice
Re: bind 9.x DoS
Robert wrote: Short followup: Theo has commited an identical diff to -current. Looking at the cvs tags for update.c rev 1.7, this patch applies to 4.6, 4.5, 4.4 and 4.3. I noticed that there's a patch for 4.4 , 4.5 and 4.6 on the FTP-servers, but a checkout of the -stable tree still gives me the unpatched revision. Shouldn't this fix be in CVS with a OPENBSD_4_x tag? Maurice
Re: OpenBSD 4.5 pf port forwarding
On Tue, Jul 07, 2009 at 03:16:17PM -0600, Anathae Townsend wrote: >I am currently trying to open up a few ports on my firewall to allow an >internal >windows home server to provide services to the outside world. > >My OpenBSD version is OpenBSD 4.5-current (GENERIC) #6: Sat May 16 21:50:41 >MDT 2009 > >I am trying to use the simple proxy method mentioned in the faq on the >OpenBSD.org to >forward internal requests to the external ip address to the home server. > >However, I can't get there from here. Neither internal nor external >requests to the >external ip address work. A msdos telnet session to the external ip >address, port 25 >returns an SMTP 421 error immediately and exits. The 421 error comes from the SMTP server. So you have a connection and forwarding seems to work fine. You need to look at the server's configuration or log files to sort this out. Maurice
Re: Ultrabasic guide to NAT
On Fri, Jul 03, 2009 at 02:18:40AM -0700, Manuel Ravasio wrote: >I'm still missing a point: how do I map more than 1 IP address on a single >physical interface? > >Is there something like Linux' and Solaris' >ifconfig [interface]:1 blah blah blah >? http://www.OpenBSD.org/faq/faq6.html#Setup.aliases
Re: apc ups daemon
On Wed, Jun 10, 2009 at 12:57:40PM +0300, Thanasis wrote: >I don't know if that matters, but let me add that the connection between >the sparc machine's port and the ups' port consists of two cables and a >gender changer in between, like so: >On the sun's port side the plug is a DB25 and the other end on the same >cable in a DB9. This RS232 DB9 is connected through a "gender changer" >to the UPS' black cable which is DB9 on both ends. >Gender changer is DB9 male/male: >http://www.partsdata.co.uk/Gender_changer_2x_DB9_male_K-100.html >I hope it's clear ... I hope it's not a null-modem cable. Maurice
Re: apc ups daemon
Thanasis wrote: Is there a port of the apcupsd or any other daemon for ups on openbsd? Nut seems to work fine for me. It's in ports and available as package. Maurice
Re: active ftp over IPv6 to OpenBSD's ftpd not working
On Tue, May 26, 2009 at 08:50:32PM +, Stuart Henderson wrote: >On 2009-05-25, Maurice Janssen wrote: >> I have an FTP-server (running OpenBSD 4.5-stable) that is only reachable >> over IPv6. Passive FTP works fine, but active FTP doesn't seem to work. >> I run ftpd from rc.conf.local (-DAS6), not through inetd. > >This fixes it, but I'm not sure whether it's correct. I noticed it's commited to -current, thanks. Any chance this will be commited to 4.4-stable and 4.5-stable? Seems to me it can be applied to those without any problem. Maurice
Re: active ftp over IPv6 to OpenBSD's ftpd not working
On Tue, May 26, 2009 at 08:50:32PM +, Stuart Henderson wrote: >On 2009-05-25, Maurice Janssen wrote: >> I have an FTP-server (running OpenBSD 4.5-stable) that is only reachable >> over IPv6. Passive FTP works fine, but active FTP doesn't seem to work. >> I run ftpd from rc.conf.local (-DAS6), not through inetd. > >This fixes it, but I'm not sure whether it's correct. Thanks for fixing it, Stuart. I hope someone can confirm that it's correct. If so, do you think this can be commited to 4.5-stable as well? Thanks. Maurice
Re: active ftp over IPv6 to OpenBSD's ftpd not working
Stuart Henderson wrote: On 2009-05-25, Maurice Janssen wrote: Hi, I have an FTP-server (running OpenBSD 4.5-stable) that is only reachable over IPv6. Passive FTP works fine, but active FTP doesn't seem to work. I run ftpd from rc.conf.local (-DAS6), not through inetd. The client gets the following error: ftp> ls 229 Entering Extended Passive Mode (|||55566|) 150 Opening ASCII mode data connection for '/bin/ls'. total 4 dr-xr-xr-x 3 0 0 512 May 22 08:52 pub 226 Transfer complete. ftp> passive Passive mode off. ftp> ls 200 EPRT command successful. 421 Service not available, remote server has closed connection. When I temporarily enable IPv4 (kill ftpd and start with -DAS), passive and active FTP work fine over IPv4, but still only passive over IPv6. Is this a bug or feature? I can't seem to find any documentation telling me it is intended behaviour. Thanks, Maurice Works for me. Do you reach it via a firewall that doesn't know how to handle EPRT? It also fails (in exactly the same way) when connecting from an ftp-client on the same subnet. The ftp-server has a 'pass out all' statement in pf.conf and tcpdump on pflog0 doesn't show any filtered packets from port 20. The client doesn't see any packets coming from port 20, only the packets related to the control connection (to/from port 21 on the ftp-server). Even with "pass in all;pass out all" in pf.conf and nothing else, no packets from port 20 arrive on the client. So it looks like it's a problem on the ftp-server, but not pf related. I suppose I'm missing some very simple, but I don't see it. Thanks, Maurice
active ftp over IPv6 to OpenBSD's ftpd not working
Hi, I have an FTP-server (running OpenBSD 4.5-stable) that is only reachable over IPv6. Passive FTP works fine, but active FTP doesn't seem to work. I run ftpd from rc.conf.local (-DAS6), not through inetd. The client gets the following error: ftp> ls 229 Entering Extended Passive Mode (|||55566|) 150 Opening ASCII mode data connection for '/bin/ls'. total 4 dr-xr-xr-x 3 0 0 512 May 22 08:52 pub 226 Transfer complete. ftp> passive Passive mode off. ftp> ls 200 EPRT command successful. 421 Service not available, remote server has closed connection. When I temporarily enable IPv4 (kill ftpd and start with -DAS), passive and active FTP work fine over IPv4, but still only passive over IPv6. Is this a bug or feature? I can't seem to find any documentation telling me it is intended behaviour. Thanks, Maurice
update 4.5 branch to -stable
Shouldn't this go in the OPENBSD_4_5 branch? Index: newvers.sh === RCS file: /cvs/src/sys/conf/newvers.sh,v retrieving revision 1.94 diff -u -r1.94 newvers.sh --- newvers.sh 26 Feb 2009 17:55:17 - 1.94 +++ newvers.sh 1 May 2009 05:24:18 - @@ -67,8 +67,9 @@ osr="4.5" cat >vers.c <
Re: build fails on 4.5
Ted Unangst wrote: On Mon, Apr 27, 2009 at 1:54 PM, Maurice Janssen wrote: ===> libexec/ld.so /bin/sh: cd: /usr/src/libexec/ld.so - No such file or directory *** Error code 1 The mirror is broken because rsync, in its infinite wisdom, doesn't copy directories named *.so. And since the mirror doesn't have that directory, you don't have it either. Get it from somewhere else. Thanks, that's exactly what was wrong, make build runs fine now. Maurice
build fails on 4.5
Hi, I'm trying to build a release (to be able to publish file sets for the stable tree for a number of architectures on May 1st), but I'm having some troubles. Creating the links for the obj directories during 'make obj' fails like this: ===> libexec/login_token /usr/src/libexec/login_token/obj -> /usr/obj/libexec/login_token ===> libexec/login_radius /usr/src/libexec/login_radius/obj -> /usr/obj/libexec/login_radius ===> libexec/login_tis /usr/src/libexec/login_tis/obj -> /usr/obj/libexec/login_tis ===> libexec/rpc.yppasswdd /usr/src/libexec/rpc.yppasswdd/obj -> /usr/obj/libexec/rpc.yppasswdd ===> libexec/ld.so /bin/sh: cd: /usr/src/libexec/ld.so - No such file or directory *** Error code 1 Stop in /usr/src/libexec (line 48 of /usr/share/mk/bsd.subdir.mk). *** Error code 1 Stop in /usr/src (line 48 of /usr/share/mk/bsd.subdir.mk). This happens on amd64, i386, macppc and sparc64. Is there something wrong with the source tree (my tree is in sync with the anoncvs mirror (tag: OPENBSD_4_5) or am I doing something wrong? Maurice
Re: 4.5 soon, but ...
Theo de Raadt wrote: So OpenBSD 4.5 will be available soon, next weekend. I feel that I should urge people to avoid the new snapshots until after they give 4.5 a try, because a few of us have been improving the system installer a little bit. It is night and day. Therefore; don't try to install a -current snapshot or you'll really hate installing 4.5... It certainly works great. The automatic disk lay-out didn't seem to work (with the 25-4 snapshot), but I'll try a new snapshot soon. Some other thing I'm missing (and has been missing for as long as I can remember): there's a question for the default IPv4 gateway, but I never get this question for the dafault IPv6 gateway. I only use manually configured IPv4 and IPv6 addresses. Maurice
Re: Parallel build in ports - make -j4
On Tue, Mar 24, 2009 at 09:51:10AM +0100, Marc Espie wrote: >Yep, does not work with all ports. And I still have stuff I need to fix >in make itself before we even think of fixing the ports that don't work >with make -j: some of them don't work because the makefiles are wrong, and >some of them don't work because make -j does not equate targets which leads >to the same file. E.g., make -j does not know (yet) that a and ./a are >the same file... Is it supported to compile a kernel (or make build) with -j ? Maurice
Re: Release IP-adress OpenBSD 3.8
On Wednesday, January 7, 2009 at 17:52:48 -0600, Andrew Daugherity wrote: >Without the DHCPRELEASE functionality, the only option is to wait >until the old lease expires. There's another option: change the MAC address of the new card to match the old card's MAC address. Somthing like this in your hostname.if: dhcp NONE NONE NONE lladdr aa:bb:cc:dd:ee:ff Maurice
Re: Wondering about openbsd way to update for patches.
On Thursday, November 27, 2008 at 23:56:31 -0600, Javier Vasquez wrote: >I'm sorry about my ignorance, but I was reading the section 5.4 about >releases, and couldn't find out how to upgrade a system from a >release, :(. > >Maybe such upgrade is more like >"http://www.openbsd.org/faq/upgrade44.html";? But the release tree >needs to be downloaded, or maybe synchronized instead, maybe using >rsync? > >Just thinking out loud how to do upgrades to this binary repo once the >installation is OK I usually do it like this: - download bsd.rd and copy it to / - reboot and type 'boot bsd.rd' at the boot> prompt - select upgrade - select ftp as location for the file sets - select the file sets you need - reboot Because you go from 4.4-release to 4.4-stable, there's no need to fiddle with etc44.tgz. After the last reboot, it just works. Maurice
Re: Wondering about openbsd way to update for patches.
On Sunday, November 23, 2008 at 13:56:44 +0100, Maurice Janssen wrote: >On Saturday, November 22, 2008 at 06:52:14 -0600, Javier Vasquez wrote: >>Hi, >> >>I'm just looking at how openbsd works to see if it suits my needs. I >>have a small old box (piii celeron @797 MHz & 32KB $, with 512 MB >>ram), and in my experience compiling just the linux kernel takes ~4 >>hrs, and compiling gcc/g++ takes ~24 hrs... >> >>I read in the documentation that if there are fixes, they come through >>patches, and then to keep things simple, the easiest "fastest" way is >>to keep the whole stable source tree up to date with patches, which >>imply initial compilation + recompiling any time a patch arise... >> >>I'm wondering whether this would mean lots of compilation time, which >>in this small machine might take too much... >> >>So it's true there's no binary way to keep the system patched, right? > >I've been making releases of the -stable tree since 4.0. Forgot to mention where you can download the filesets: ftp://ftp.z74.net/pub/OpenBSD/ A list of mirrors and a bit more info can be found at: http://www.z74.net/openbsd.html Maurice
Re: Wondering about openbsd way to update for patches.
On Saturday, November 22, 2008 at 06:52:14 -0600, Javier Vasquez wrote: >Hi, > >I'm just looking at how openbsd works to see if it suits my needs. I >have a small old box (piii celeron @797 MHz & 32KB $, with 512 MB >ram), and in my experience compiling just the linux kernel takes ~4 >hrs, and compiling gcc/g++ takes ~24 hrs... > >I read in the documentation that if there are fixes, they come through >patches, and then to keep things simple, the easiest "fastest" way is >to keep the whole stable source tree up to date with patches, which >imply initial compilation + recompiling any time a patch arise... > >I'm wondering whether this would mean lots of compilation time, which >in this small machine might take too much... > >So it's true there's no binary way to keep the system patched, right? I've been making releases of the -stable tree since 4.0. It's not an official part of the OpenBSD project and I don't have the hardware to build them for all architectures, but you might find what you need. You can use the procedure to update a machine to install them. Maurice
Re: help with network connectivity
On Thursday, November 20, 2008 at 20:07:02 -0800, Jon wrote: >the /etc/hostname.em0 has 'inet 255.255.255.0 NONE' in it. > >I can resolve using the gateway as my nameserver in /etc/resolve.conf > >the thing won't allow any traffic to go out - I am trying to ping >yahoo.com... > >But if i update /etc/hostname.em0 to DHCP and do a dhclient - it work.. No >issue. Then stick to DHCP. Why do you want to hardcode the IP to hostname.em0? >What I am doing wrong or missing ? It's very well possible that the DHCP request does a lot more on the other end than just send you an IP. (set a route to your end, for example). Without the DHCP request, this won't happen, hence the problems you're seeing. Maurice
netinet6/in6.c fix for 4.4?
Hi, About a month ago, there was a security fix for -current, 4.2-stable and 4.3-stable. I expected to see the same fix for 4.4-stable just before the release date, but I haven't seen it in cvs yet. Will there be a fix for 4.4-stable or not? Thanks, Maurice
Re: OpenBSD 4.4 CDs have arrived in Bonn/Germany
On Thursday, October 9, 2008 at 10:36:54 +0200, Guido Tschakert wrote: >Hi Folks, > >just a few minutes ago a packet from Wim arrived in my office. The CD's have arrived here (Amersfoort, Netherlands) today as well. Thanks to all developers for another great release! Don't forget to order your copy at https://https.openbsd.org/cgi-bin/order.eu (Europe) or https://https.openbsd.org/cgi-bin/order (rest of the world) >may the source be with us Amen. Maurice
Re: Update release 3.8 on AMD64 with a “fix” for the recent “DNS cache poisoning” vulnerability?
On Wednesday, July 30, 2008 at 22:28:44 +0200, Mark Prins wrote: >you could save some time and energy by using the 4.3-stable release >from ftp://ftp.su.se/pub/mirrors/openbsd_stable/4.3-stable/ as this >has the errata/patches applied... That's correct, but at this moment the latest patch (005) hasn't been applied yet. My switch broke down yesterday, I hope the new one will arrive before the weekend so I can build the new file sets. Maurice
Re: Problems going from 4.3-release to -stable
On Thursday, May 8, 2008 at 21:08:54 +, Mike wrote: >Hello, > >After a fresh install of obsd on a new server, I cannot update my system >to -stable. > >The src has been obtained from cvs in the usual manner. > >Here is the error :- > ># cd /usr/src/sys/arch/sparc64/conf/ ># ls >CVS GENERIC.MP RAMDISK RAMDISKU5 >GENERIC Makefile.sparc64RAMDISKU1 files.sparc64 ># config GENERIC >../../../../conf/files:1038: syntax error >*** Stop. ># uname -a >OpenBSD atom 4.2 GENERIC#1427 sparc64 You are still running 4.2, not 4.3. You cannot compile 4.3-stable on a system running 4.2. Did you really do a fresh install? Maurice BTW: you can find binaries for 4.3-stable at ftp://ftp.z74.net/pub/OpenBSD/4.3-stable/ . Not for all architectures, but sparc64 is available. Of course it's up to you to decide if you have enough trust in me to use them.
Re: problem building release for 4.3 stable
On Sunday, May 4, 2008 at 20:56:03 -0600, Anthony Roberts wrote: >I've been having trouble building releases for 4.3. It fails on >checkflist, apparently it doesn't expect to see /etc/firmware/ral-rt2860. >Output is: Yes, I noticed this as well. I think you can safely ignore this. Maurice
sgi/4.3 slow?
Hi, I installed 4.3-release on an O2 and noticed that it is quite slow compared to 4.1-stable. For example, it took more than 5 hours to build a kernel, that's about the same as my Vax ;-) Right now I'm running a make build and it is dead slow. Load is around 0.10 and top shows that the machine is nearly 100% idle. It seems that something is delaying the system, but I can't tell what it is. Some kind of interrupt problem, perhaps? BTW: /usr/src is NFS-mounted, but that shouldn't be a problem, right? Any pointers are appreciated. Maurice [ using 302776 bytes of bsd ELF symbol table ] Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2008 OpenBSD. All rights reserved. http://www.OpenBSD.org OpenBSD 4.3 (GENERIC) #0: Fri May 2 06:27:48 CEST 2008 [EMAIL PROTECTED]:/usr/src/sys/arch/sgi/compile/GENERIC real mem = 268435456 (256MB) rsvd mem = 7020544 (6MB) avail mem = 243376128 (232MB) mainbus0 at root cpu0 at mainbus0: MIPS R5000 CPU rev 2.1 200 MHz with R5000 based FPC rev 1.0 cpu0: cache L1-I 32KB D 32KB 2 way, L2 1024KB direct macebus0 at mainbus0: crime rev 10.1 macepcibr0 at macebus0: mace rev 1, host system O2 pci0 at macepcibr0 bus 0 ahc0 at pci0 dev 1 function 0 "Adaptec AIC-7880" rev 0x00: irq 9 ahc0: Host Adapter Bios disabled. Using default SCSI device parameters scsibus0 at ahc0: 16 targets sd0 at scsibus0 targ 1 lun 0: SCSI2 0/direct fixed sd0: 8682MB, 8387 cyl, 10 head, 212 sec, 512 bytes/sec, 17781520 sec total cd0 at scsibus0 targ 4 lun 0: SCSI2 5/cdrom removable ahc1 at pci0 dev 2 function 0 "Adaptec AIC-7880" rev 0x00: irq 10 ahc1: Host Adapter Bios disabled. Using default SCSI device parameters scsibus1 at ahc1: 16 targets clock0 at macebus0: TOD with DS1687, ticker on int5 using count register com0 at macebus0 base 0x0039 irq 5: ns16550a, 16 byte fifo com0: console com1 at macebus0 base 0x00398000 irq 5: ns16550a, 16 byte fifo mec0 at macebus0 base 0x0028 irq 4: MAC-110 rev 1, address 08:00:69:0c:98:8e nsphy0 at mec0 phy 8: DP83840 10/100 PHY, rev. 0 mavb0 at macebus0 base 0x0030 irq 7: AD1843 rev 1 audio0 at mavb0 mkbc0 at macebus0 base 0x0032 irq 6 power0 at macebus0 irq 6 gbe0 at mainbus0: device has not been setup by firmware! softraid0 at root ahc0: target 1 using 16bit transfers ahc0: target 1 synchronous at 10.0MHz, offset = 0x8 boot device: sd0 root on sd0a swap on sd0b dump on sd0b
wrong files on ftp://ftp.openbsd.org/pub/OpenBSD/4.2/ ?
Hi, I just noticed that the files PACKAGES, PORTS and README in the 4.2 directory have a relative new date and mention OpenBSD 4.3. Doesn't look right to me. Maurice
Re: Updates for old releases
On Friday, February 22, 2008 at 12:07:43 +, Edd wrote: >On Fri, Feb 22, 2008 at 10:33:00AM +0100, Maurice Janssen wrote: >> About a year ago I started to create regular builds of the -stable >> trees (the two supported trees). You can use them, if you trust me ;-) >> You can find links to some mirrors on http://www.z74.net/openbsd.html > >I think it is great that you are doing this, however why are you a third >party? Can you not upload your binaries to the official mirrors? I'd be happy to upload it to the official ftp-site and mirrors, but I'm not a OpenBSD developer. If the OpenBSD team has enough trust and would like to put these file sets on the official mirrors, then they are of course more than welcome to do so. I'm not sure if all mirrors are able to spare a few extra GB for the stable file sets and I don't have the hardware to build a release for all supported architectures. I don't know if this is a real problem. Maurice
Re: Updates for old releases
On Friday, February 22, 2008 at 05:48:14 -0300, Antonio Lobato wrote: > Hi all! > > I read http://openbsd.org/security.html (and stable.html), but could >not make >sure about my question. > > If today I download old versions (say /pub/OpenBSD/4.0/i386/cd40.iso) of >openbsd, does it already includes the fixes listed in >http://openbsd.org/security.html#40 (or #41)? If no, is there available >the same >cd40.iso but including these fixes or must I to apply the patches on >original >system? > > If there is some doc explaining it with more details, please give me >the pointers. There's more on this on http://www.openbsd.org/faq/faq5.html#Flavors To summarize: what's on the CD's and FTP-servers is -release, it is not updated. The patches for -stable are only distributed as source code. There are no official builds of the -stable tree. About a year ago I started to create regular builds of the -stable trees (the two supported trees). You can use them, if you trust me ;-) You can find links to some mirrors on http://www.z74.net/openbsd.html Maurice
Re: cvs running behind?
OK, I understand. But the 4.1-stable patch still is not present at the mirrors I tried. Isn't this taking too long? I suspect that something is preventing the patch from reaching the mirrors. Maurice On Tuesday, January 29, 2008 at 11:26:35 -0800, Chris Kuethe wrote: >CVS fan-out takes a while. Just keep an eye on it, and I'll try get >the regular patch files and errata entries posted tonight. > >CK > >On Jan 29, 2008 11:06 AM, Maurice Janssen <[EMAIL PROTECTED]> wrote: >> Hi, >> >> I saw an email on the cvs list about some security fixes for 4.1-stable >> and 4.2-stable. It seems that the patches for 4.1-stable didn't make it >> all the way to the cvs-servers. For example, >> http://www.openbsd.org/cgi-bin/cvsweb/XF4/xc/lib/font/bitmap/pcfread.c >> still has the old version and also through anoncvs I can't find the new >> versions. >> >> Am I missing something or is there a hickup somewhere? >> >> Maurice >> >> > > > >-- >GDB has a 'break' feature; why doesn't it have 'fix' too?
