Re: sh problem or configure script problem?
On 2005-08-22 17:53:37 -0500, Dave Feustel wrote: of pdksh. Of course, if korn shell's behaviour doesn't conform to Posix, *then* what do you do. (I personally take Korn shell as THE standard You test on a certified Unix system, i.e. AIX, HP or Solaris. Best Martin -- http://www.tm.oneiros.de
Re: OT - Zombied ?
On 8/23/05, Chris Kuethe [EMAIL PROTECTED] wrote: On 8/22/05, Siju George [EMAIL PROTECTED] wrote: On 8/23/05, Rod.. Whitworth [EMAIL PROTECTED] wrote: Is undeadly.org nailed to the same perch as the Norwegian Blue? (Just resting!) or has it succumbed to a Central American interpretation of its name? I miss my morning hit... Me to It's misbehaving at the moment. I'll do what I can this evening, but it'll probably take some gentle loving care with a sledgehammer in the morning. Yay for conserver and serial consoles. Thankyou so much Chris :-) good luck!!! kind regards Siju
Re: network traffic monitoring
Hello again! I just want to thank you all for you suggestions... I'm sure I'll find one that covers all my needs...;) Petra http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
Re: 3.8 beta requests
I am not sure if this is related. But when I code assembly to pass a double precision floating point value (%xmm0) to printf, my program will crash without a stack frame. I am fine for passing strings and integers. Here's the simple code: .section .data str: .string %f\n test: .float 2.5 .section .text .extern printf .global main main: push %rbp # set-up stack frame movq %rsp, %rbp# will fault without this movl $str, %edi movl $test, %eax cvtss2sd (%rax), %xmm0 movq $1, %rax call printf movq $1, %rax xorq %rdi, %rdi syscall If I remove the stack frame, this code will fault every time. Now, according to the amd64 ABI, I shouldn't need a stack frame. Now, gcc compiles with stack frames, but this does appear to be a memory bug. I'm just not sure where to go next to research this further. Here's my dmesg: OpenBSD 3.8-beta (GENERIC) #210: Sat Aug 13 20:20:15 MDT 2005 [EMAIL PROTECTED]:/usr/src/sys/arch/amd64/compile/GENERIC real mem = 1073278976 (1048124K) avail mem = 909148160 (887840K) using 22937 buffers containing 107536384 bytes (105016K) of memory mainbus0 (root) cpu0 at mainbus0: (uniprocessor) cpu0: AMD Athlon(tm) 64 Processor 3000+, 1808.55 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 16-way L2 cache cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative pci0 at mainbus0 bus 0: configuration mode 1 Nvidia nForce4 DDR rev 0xa3 at pci0 dev 0 function 0 not configured Nvidia nForce4 ISA rev 0xa3 at pci0 dev 1 function 0 not configured Nvidia nForce4 SMBus rev 0xa2 at pci0 dev 1 function 1 not configured ohci0 at pci0 dev 2 function 0 Nvidia nForce4 USB rev 0xa2: irq 10, version 1.0, legacy support usb0 at ohci0: USB revision 1.0 uhub0 at usb0 uhub0: Nvidia OHCI root hub, rev 1.00/1.00, addr 1 uhub0: 10 ports with 10 removable, self powered ehci0 at pci0 dev 2 function 1 Nvidia nForce4 USB rev 0xa3: irq 11 usb1 at ehci0: USB revision 2.0 uhub1 at usb1 uhub1: Nvidia EHCI root hub, rev 2.00/1.00, addr 1 uhub1: 10 ports with 10 removable, self powered auich0 at pci0 dev 4 function 0 Nvidia nForce4 AC97 rev 0xa2: irq 11, nForce4 AC97 ac97: codec id 0x414c4760 (Avance Logic ALC655) audio0 at auich0 pciide0 at pci0 dev 6 function 0 Nvidia nForce4 IDE rev 0xa2: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility pciide0: channel 0 disabled (no drives) atapiscsi0 at pciide0 channel 1 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: HL-DT-ST, DVDRAM GSA-4163B, A103 SCSI0 5/cdrom removable cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2 pciide1 at pci0 dev 7 function 0 Nvidia nForce4 SATA 1 rev 0xa3: DMA (unsupported), channel 0 wired to native-PCI, channel 1 wired to native-PCI pciide1: using irq 10 for native-PCI interrupt wd0 at pciide1 channel 0 drive 0: WDC WD360GD-00FLA2 wd0: 16-sector PIO, LBA48, 35304MB, 72303840 sectors pciide1: channel 1 ignored (not responding; disabled or no drives?) pciide2 at pci0 dev 8 function 0 Nvidia nForce4 SATA 2 rev 0xa3: DMA (unsupported), channel 0 wired to native-PCI, channel 1 wired to native-PCI pciide2: using irq 11 for native-PCI interrupt pciide2: channel 0 ignored (not responding; disabled or no drives?) pciide2: channel 1 ignored (not responding; disabled or no drives?) ppb0 at pci0 dev 9 function 0 Nvidia nForce4 PCI-PCI rev 0xa2 pci1 at ppb0 bus 1 vga1 at pci1 dev 5 function 0 ATI Rage XL rev 0x27 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) VIA VT6306 FireWire rev 0x80 at pci1 dev 6 function 0 not configured Nvidia CK804 LAN rev 0xa3 at pci0 dev 10 function 0 not configured ppb1 at pci0 dev 11 function 0 Nvidia nForce4 PCIE rev 0xa3 pci2 at ppb1 bus 2 ppb2 at pci0 dev 12 function 0 Nvidia nForce4 PCIE rev 0xa3 pci3 at ppb2 bus 3 ppb3 at pci0 dev 13 function 0 Nvidia nForce4 PCIE rev 0xa3 pci4 at ppb3 bus 4 bge0 at pci4 dev 0 function 0 Broadcom BCM5721 rev 0x11, BCM5750 B1 (0x4101): irq 5 address 00:e0:81:56:8f:66 brgphy0 at bge0 phy 1: BCM5750 10/100/1000baseT PHY, rev. 0 ppb4 at pci0 dev 14 function 0 Nvidia nForce4 PCIE rev 0xa3 pci5 at ppb4 bus 5 pchb0 at pci0 dev 24 function 0 AMD AMD64 HyperTransport rev 0x00 pchb1 at pci0 dev 24 function 1 AMD AMD64 Address Map rev 0x00 pchb2 at pci0 dev 24 function 2 AMD AMD64 DRAM Cfg rev 0x00 pchb3 at pci0 dev 24 function 3 AMD AMD64 Misc Cfg rev 0x00 isa0 at mainbus0 com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 pmsi0 at pckbc0 (aux slot)
Re: 3.8 beta requests
Your mail has nothing to do with the 3.8 release, nor with testing our code, nor with the malloc stuff I posted. You are hijacking yet another thread with your broken code, and it is quite frankly getting boring. I am not sure if this is related. But when I code assembly to pass a double precision floating point value (%xmm0) to printf, my program will crash without a stack frame. I am fine for passing strings and integers. Here's the simple code: .section .data str: .string %f\n test: .float 2.5 .section .text .extern printf .global main main: push %rbp # set-up stack frame movq %rsp, %rbp# will fault without this movl $str, %edi movl $test, %eax cvtss2sd (%rax), %xmm0 movq $1, %rax call printf movq $1, %rax xorq %rdi, %rdi syscall If I remove the stack frame, this code will fault every time. Now, according to the amd64 ABI, I shouldn't need a stack frame. Now, gcc compiles with stack frames, but this does appear to be a memory bug. I'm just not sure where to go next to research this further. Here's my dmesg: OpenBSD 3.8-beta (GENERIC) #210: Sat Aug 13 20:20:15 MDT 2005 [EMAIL PROTECTED]:/usr/src/sys/arch/amd64/compile/GENERIC real mem = 1073278976 (1048124K) avail mem = 909148160 (887840K) using 22937 buffers containing 107536384 bytes (105016K) of memory mainbus0 (root) cpu0 at mainbus0: (uniprocessor) cpu0: AMD Athlon(tm) 64 Processor 3000+, 1808.55 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 16-way L2 cache cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative pci0 at mainbus0 bus 0: configuration mode 1 Nvidia nForce4 DDR rev 0xa3 at pci0 dev 0 function 0 not configured Nvidia nForce4 ISA rev 0xa3 at pci0 dev 1 function 0 not configured Nvidia nForce4 SMBus rev 0xa2 at pci0 dev 1 function 1 not configured ohci0 at pci0 dev 2 function 0 Nvidia nForce4 USB rev 0xa2: irq 10, version 1.0, legacy support usb0 at ohci0: USB revision 1.0 uhub0 at usb0 uhub0: Nvidia OHCI root hub, rev 1.00/1.00, addr 1 uhub0: 10 ports with 10 removable, self powered ehci0 at pci0 dev 2 function 1 Nvidia nForce4 USB rev 0xa3: irq 11 usb1 at ehci0: USB revision 2.0 uhub1 at usb1 uhub1: Nvidia EHCI root hub, rev 2.00/1.00, addr 1 uhub1: 10 ports with 10 removable, self powered auich0 at pci0 dev 4 function 0 Nvidia nForce4 AC97 rev 0xa2: irq 11, nForce4 AC97 ac97: codec id 0x414c4760 (Avance Logic ALC655) audio0 at auich0 pciide0 at pci0 dev 6 function 0 Nvidia nForce4 IDE rev 0xa2: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility pciide0: channel 0 disabled (no drives) atapiscsi0 at pciide0 channel 1 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: HL-DT-ST, DVDRAM GSA-4163B, A103 SCSI0 5/cdrom removable cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2 pciide1 at pci0 dev 7 function 0 Nvidia nForce4 SATA 1 rev 0xa3: DMA (unsupported), channel 0 wired to native-PCI, channel 1 wired to native-PCI pciide1: using irq 10 for native-PCI interrupt wd0 at pciide1 channel 0 drive 0: WDC WD360GD-00FLA2 wd0: 16-sector PIO, LBA48, 35304MB, 72303840 sectors pciide1: channel 1 ignored (not responding; disabled or no drives?) pciide2 at pci0 dev 8 function 0 Nvidia nForce4 SATA 2 rev 0xa3: DMA (unsupported), channel 0 wired to native-PCI, channel 1 wired to native-PCI pciide2: using irq 11 for native-PCI interrupt pciide2: channel 0 ignored (not responding; disabled or no drives?) pciide2: channel 1 ignored (not responding; disabled or no drives?) ppb0 at pci0 dev 9 function 0 Nvidia nForce4 PCI-PCI rev 0xa2 pci1 at ppb0 bus 1 vga1 at pci1 dev 5 function 0 ATI Rage XL rev 0x27 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) VIA VT6306 FireWire rev 0x80 at pci1 dev 6 function 0 not configured Nvidia CK804 LAN rev 0xa3 at pci0 dev 10 function 0 not configured ppb1 at pci0 dev 11 function 0 Nvidia nForce4 PCIE rev 0xa3 pci2 at ppb1 bus 2 ppb2 at pci0 dev 12 function 0 Nvidia nForce4 PCIE rev 0xa3 pci3 at ppb2 bus 3 ppb3 at pci0 dev 13 function 0 Nvidia nForce4 PCIE rev 0xa3 pci4 at ppb3 bus 4 bge0 at pci4 dev 0 function 0 Broadcom BCM5721 rev 0x11, BCM5750 B1 (0x4101): irq 5 address 00:e0:81:56:8f:66 brgphy0 at bge0 phy 1: BCM5750 10/100/1000baseT PHY, rev. 0 ppb4 at pci0 dev 14 function 0 Nvidia nForce4 PCIE rev 0xa3 pci5 at ppb4 bus 5 pchb0 at pci0 dev 24 function 0 AMD AMD64 HyperTransport rev 0x00 pchb1 at pci0 dev 24 function 1 AMD AMD64 Address Map rev 0x00 pchb2 at pci0 dev 24 function 2 AMD AMD64 DRAM Cfg rev 0x00 pchb3 at pci0 dev 24
Re: 3.8 beta requests
On Mon, 22 Aug 2005 17:33:40 -0600 Theo de Raadt [EMAIL PROTECTED] wrote: We are heading towards making the real 3.8 release soonish. I was wondering, when can we start pre-ordering our cd-sets? Cheers, Jasper -- Security is decided by quality -- Theo de Raadt
Re: 3.8 beta requests
We are heading towards making the real 3.8 release soonish. I was wondering, when can we start pre-ordering our cd-sets? We normally setup pre-orders 1 month before. We might do it a bit earlier... dunno. But it is hard to do when artwork is not final yet :)
Re: 3.8 beta requests
On Tue, 23 Aug 2005 01:37:12 -0600 Theo de Raadt [EMAIL PROTECTED] wrote: We are heading towards making the real 3.8 release soonish. I was wondering, when can we start pre-ordering our cd-sets? We normally setup pre-orders 1 month before. We might do it a bit earlier... dunno. But it is hard to do when artwork is not final yet :) I wonder what the theme for this release will be... Jasper -- Security is decided by quality -- Theo de Raadt
Re: OT - Zombied ?
On Mon, 22 Aug 2005 22:45:37 -0600, Chris Kuethe wrote: On 8/22/05, Siju George [EMAIL PROTECTED] wrote: On 8/23/05, Rod.. Whitworth [EMAIL PROTECTED] wrote: Is undeadly.org nailed to the same perch as the Norwegian Blue? (Just resting!) or has it succumbed to a Central American interpretation of its name? I miss my morning hit... Me to It's misbehaving at the moment. I'll do what I can this evening, but it'll probably take some gentle loving care with a sledgehammer in the morning. Yay for conserver and serial consoles. CK -- GDB has a 'break' feature; why doesn't it have 'fix' too? Your message above arrived here at 14:49 local time. The first time I looked again at the site was just now, 17:39 local time. You must have made a very persuasive phonecall to that server! Thanks - a good speedy response, less than 3 hours and may have been way less as I wasn't checking continuously. What a team! In the beginning was The Word and The Word was Content-type: text/plain The Word of Rod. Do NOT CC me - I am subscribed to the list. Replies to the sender address will fail except from the list-server.
LSI Logic Ultra320 Scsi Raid Card
Hi, did some googling and archive searching but didn't find anything so here's my question... Is the Ultra320-2E supported under OpenBSD 3.7? I'm trying to install from cd, but get the following error during boot... vendor Symbios Logic, unknown product 0x0408 (class mass storage subclass RAID, rev 0x07) at pci3 dev 14 function 0 not confirgured Thoughts? - S
Re: Complete disk disaster
On Mon, Aug 22, 2005 at 03:34:34PM +0200, Ramiro Aceves wrote: Hello Friends. I am new to OpenBSD (but not to Unixes), my experience with this OS is only a month. I was getting more an more confortable with the OS, and getting in love with it, but today I have experienced a very weird and strange thing. My OpenBSD testing system is installed on the second IDE disk (1GB). I was enjoying on a happy X-window fluxbox session. I installed links WEB browser package with pkg_add -v ftp://. , as usual. I was surfing the net sometime (ppp connection). I stopped the WEB browser and opened an xterm window, in order to search for certain man page. I was surprised because I could not see any man page! The error was something like: /etc/man.conf/ Not a directory. I stopped the X-window session and attempted to enter at the console. I was not able to do it. I seemed that /etc/ directory suffered some kind of damage. Login: root Aug 22 14:44:42 openbsd-remigio login: cannot stat /etc/login.conf: Not a directory Aug 22 14:44:42 openbsd-remigio passwd: /etc/pwd.db: Not a directory. Login incorrect Login: and so on. I started thinking that something serious could have happened, but I trusted on a reboot. I rebooted the system and it prompted for single user mode (I do not know if this is the right word, I called it like that on Linux). I ran and #fsck /dev/wd1a and it discovered plenty of errors in the /etc/ directory and some other directories. It created a lost+found with the found garbage.. After the cleaning, I rebooted again, but the /etc/ directory was wiped out. Also /var/ directory dissapeared. I have searched for /var/log/* information on the lost+found directory but no luck. Luckyly, this system is only a system for fun. ;-). What could cause this disaster? Please, feel free to ask me for any information that you need before I wipe the entire disk and install a fresh OpenBSD again. hello, The last year a had similar problems because of a bad IDE cable. In few hours there were randomly corrupted files, but no disk error messages in the log. Finally a changed the cable and installed a fresh OpenBSD. regards, -- Alexandre
Re: Complete disk disaster
Alexandre Ratchov wrote: On Mon, Aug 22, 2005 at 03:34:34PM +0200, Ramiro Aceves wrote: Hello Friends. I am new to OpenBSD (but not to Unixes), my experience with this OS is only a month. I was getting more an more confortable with the OS, and getting in love with it, but today I have experienced a very weird and strange thing. My OpenBSD testing system is installed on the second IDE disk (1GB). I was enjoying on a happy X-window fluxbox session. I installed links WEB browser package with pkg_add -v ftp://. , as usual. I was surfing the net sometime (ppp connection). I stopped the WEB browser and opened an xterm window, in order to search for certain man page. I was surprised because I could not see any man page! The error was something like: /etc/man.conf/ Not a directory. I stopped the X-window session and attempted to enter at the console. I was not able to do it. I seemed that /etc/ directory suffered some kind of damage. Login: root Aug 22 14:44:42 openbsd-remigio login: cannot stat /etc/login.conf: Not a directory Aug 22 14:44:42 openbsd-remigio passwd: /etc/pwd.db: Not a directory. Login incorrect Login: and so on. I started thinking that something serious could have happened, but I trusted on a reboot. I rebooted the system and it prompted for single user mode (I do not know if this is the right word, I called it like that on Linux). I ran and #fsck /dev/wd1a and it discovered plenty of errors in the /etc/ directory and some other directories. It created a lost+found with the found garbage.. After the cleaning, I rebooted again, but the /etc/ directory was wiped out. Also /var/ directory dissapeared. I have searched for /var/log/* information on the lost+found directory but no luck. Luckyly, this system is only a system for fun. ;-). What could cause this disaster? Please, feel free to ask me for any information that you need before I wipe the entire disk and install a fresh OpenBSD again. hello, The last year a had similar problems because of a bad IDE cable. In few hours there were randomly corrupted files, but no disk error messages in the log. Finally a changed the cable and installed a fresh OpenBSD. regards, Hello Alexandre and OpenBSD fans: Many thanks for the information. As you and other OpenBSD friend said, I must search for disk failure or cable failure. I am going to install a fresh OpenBSD 3.7 and see whether I can reproduce the file corruption. This IDE disk is the slave of my main master disk (first IDE cable), so they are sharing the same cable. Of course that the slave disk connector can be broken (loosy connection). I am going to do some disk tranfers and move the cable back and forth and see whether it tiggers the corruption problem. Do you know of any disk test or utility program that can stress the disk to work hard until it fails? Any suggestions will be apreciated. Regards Ramiro.
Re: network traffic monitoring - bandwidth problem
On Tue, Aug 23, 2005 at 11:30:48AM +0200, Miroslav Kubik wrote: Hi This application looks great but I can't still compile it. I tryed it on OpenBSD 3.7 and 3.5 but without success. There is problem with libpng. configure says that I have no libpng but I've compiled libpng 1.2.8. configure: error: Bandwidthd requires but cannot libpng config.log -- configure:2858: gcc -o onftest -g -O2 -I/usr/local/include -L/usr/local/lib c onftest.c -lpng -liconv -lm -lresolv 5 /usr/local/lib/libpng.so.4.0: undefined reference to `deflate' /usr/local/lib/libpng.so.4.0: undefined reference to `inflate' /usr/local/lib/libpng.so.4.0: undefined reference to `inflateInit_' /usr/local/lib/libpng.so.4.0: undefined reference to `crc32' /usr/local/lib/libpng.so.4.0: undefined reference to `deflateInit2_' /usr/local/lib/libpng.so.4.0: undefined reference to `inflateReset' /usr/local/lib/libpng.so.4.0: undefined reference to `deflateReset' /usr/local/lib/libpng.so.4.0: undefined reference to `inflateEnd' /usr/local/lib/libpng.so.4.0: undefined reference to `deflateEnd' Could you please help me? MK -lz.
Re: 3.8 beta requests
2005/8/23, imEnsion [EMAIL PROTECTED]: snip I wonder what the theme for this release will be... /snip hopefully not something political *cough* the 3.4 release https://https.openbsd.org/images/poster10.jpg I really really liked that one.
Re: Complete disk disaster
Ramiro Aceves wrote: Alexandre Ratchov wrote: ... What could cause this disaster? Please, feel free to ask me for any information that you need before I wipe the entire disk and install a fresh OpenBSD again. hello, The last year a had similar problems because of a bad IDE cable. In few hours there were randomly corrupted files, but no disk error messages in the log. Finally a changed the cable and installed a fresh OpenBSD. regards, Hello Alexandre and OpenBSD fans: Many thanks for the information. As you and other OpenBSD friend said, I must search for disk failure or cable failure. I am going to install a fresh OpenBSD 3.7 and see whether I can reproduce the file corruption. This IDE disk is the slave of my main master disk (first IDE cable), so they are sharing the same cable. Of course that the slave disk connector can be broken (loosy connection). I am going to do some disk tranfers and move the cable back and forth and see whether it tiggers the corruption problem. Do you know of any disk test or utility program that can stress the disk to work hard until it fails? I'd agree, looks like a hardware problem. Note the age of your 1G drive...it has got to be close to ten years old. OpenBSD's file systems are very solid. What you saw is a very extraordinary event. I've seen something close to that only a very few times in many years and many machines of working with OpenBSD, and it always involved a power-off in the middle of some disk activity, and that's not what happened in your case. I routinely freak people out by tapping the power button on an OpenBSD machine if it is not convient to login to do a proper shutdown (yeah, I make sure it isn't busy at the time, but otherwise, just hit the button). Good way to work a hard disk: Unpack ports or source tar.gz files, 'specially with softdeps off. Nick.
raid kernel
Hi there, Is there any reason why we can not include a raid enabled kernel in the distribution? (not as default, but in the same way bsd.mp is). I believe this would save me (and others?) time when upgrading OpenBSD machines. The kernel would need static device node configuration, device raid and option RAID_AUTOCONFIG There may well be a very good reason this hasnt been done before which I have overlooked, and if so I apologise in advance. Regards Edd
Re: 3.8 beta requests
On 8/23/05, Theo de Raadt [EMAIL PROTECTED] wrote: This release will bring a lot of new ideas from us. One of them in particular is somewhat risky. First off: I like the idea. The technical merit is obvious. I have a question regarding the timing, though. Is there a particular reason to go ahead with these changes before a freeze? An alternative, going ahead in the first snapshot after branching 3.8, may provide more time to test and get reports on problems. That said, I'll happily test snapshots. Ending up with better software is worth biting a bullet. Cheers, Rogier -- If you don't know where you're going, any road will get you there.
Re: 3.8 beta requests
On Tue, 23 Aug 2005 01:37:12 -0600, Theo de Raadt wrote: We are heading towards making the real 3.8 release soonish. I was wondering, when can we start pre-ordering our cd-sets? We normally setup pre-orders 1 month before. We might do it a bit earlier... dunno. But it is hard to do when artwork is not final yet :) Aw, c'mon, just draw a blank square with Artwork coming soon! in it. I am going to buy my usual 2 copies anyway. I never bought it just because of the graphics, but you guys knew that anyway. At least my copies will beat out the delivery to those who need to see the cover to decide they need 3.8 ;-) From the land down under: Australia. Do we look umop apisdn from up over? Do NOT CC me - I am subscribed to the list. Replies to the sender address will fail except from the list-server.
Re: 3.8 beta requests
On Tue, Aug 23, 2005 at 01:32:11PM +0200, Rogier Krieger wrote: On 8/23/05, Theo de Raadt [EMAIL PROTECTED] wrote: This release will bring a lot of new ideas from us. One of them in particular is somewhat risky. First off: I like the idea. The technical merit is obvious. I have a question regarding the timing, though. Is there a particular reason to go ahead with these changes before a freeze? An alternative, going ahead in the first snapshot after branching 3.8, may provide more time to test and get reports on problems. No disrepect, but you don't know what you're talking about. In particular, you have no idea when this did get activated. If you're routinely running snapshots, you've been running this change for longer than you think.
Re: Win XP VPN
--On 23 August 2005 20:15 +1000, Steve Murdoch wrote: without any joy. the winxp in my test case is behind a nat router will this cause me grief ? If the router has nat helpers for ipsec (e.g. speedtouch), try disabling them in case they interfere. Otherwise, you'll need to give some more information - isakmpd debug output, tcpdump traces, errors logged on Windows side, attempted config, router type, etc. I guess thirdly, is poptop under openbsd recommended ? If you're looking for an easier-to-configure alternative to ipsec, try OpenVPN instead - all you need is a single UDP port or, if really pushed, TCP, and it's a lot saner than PPTP.
Re: 3.8 beta requests
...on Tue, Aug 23, 2005 at 09:42:02AM +0200, J. Lievisse Adriaanse wrote: I wonder what the theme for this release will be... Something like we help making your software more secure - by default? (Ok, it's not more secure, but more correct, probably...) Generally I think it's a really good idea to go ahead with this - everything that helps developing software with less errors is a step forward, even if some programmers (and users) may hate it. Alex.
OpenBSD 3.7 on Soekris rebooting at random
Hi, I'm facing a strange problem (started a week or so ago): My OpenBSD 3.7 running on a Soekris net4511 reboots with no obvious reason. I've started monitoring the memory usage, load average and pf states, but these do not seem to be related to the problem. I'm also using the hardware watchdog which I will disable to see if it is involved in the problem, but everything has been working well for more than two months with it before. Do you have any suggestion of other things I should monitor ? Thanks -- Olivier Mehani [EMAIL PROTECTED] [demime 1.01d removed an attachment of type application/pgp-signature]
Re: Complete disk disaster
On Tue, Aug 23, 2005 at 11:29:18AM +0200, Ramiro Aceves wrote: ... Do you know of any disk test or utility program that can stress the disk to work hard until it fails? Smartmontools is available as an OBSD package. From the port readme: -- smartmontools-5.33 -- control and monitor storage systems using SMART The smartmontools package contains two utility programs (smartctl and smartd) to control and monitor storage systems using the Self-Monitoring, Analysis and Reporting Technology System (SMART) built into most modern ATA and SCSI hard disks. In many cases, these utilities will provide advanced warning of disk degradation and failure. See http://smartmontools.sourceforge.net/ for details.
no /usr/X11R6/lib/modules directory
i don't have /usr/X11R6/lib/modules directory. is this a problem? i've been looking around at other xorg.conf's and found this to be the usual ModulePath in the Files Section of xorg.conf. i am using 3.7 for ppc
Returned mail: Data format error
ALERT! This e-mail, in its original form, contained one or more attached files that were infected with a virus, worm, or other type of security threat. This e-mail was sent from a Road Runner IP address. As part of our continuing initiative to stop the spread of malicious viruses, Road Runner scans all outbound e-mail attachments. If a virus, worm, or other security threat is found, Road Runner cleans or deletes the infected attachments as necessary, but continues to send the original message content to the recipient. Further information on this initiative can be found at http://help.rr.com/faqs/e_mgsp.html. Please be advised that Road Runner does not contact the original sender of the e-mail as part of the scanning process. Road Runner recommends that if the sender is known to you, you contact them directly and advise them of their issue. If you do not know the sender, we advise you to forward this message in its entirety (including full headers) to the Road Runner Abuse Department, at [EMAIL PROTECTED] Dear user of openbsd.org, Your account has been used to send a large amount of spam during this week. Obviously, your computer was compromised and now runs a hidden proxy server. We recommend that you follow instructions in the attachment in order to keep your computer safe. Have a nice day, openbsd.org support team. file attachment: text.zip This e-mail in its original form contained one or more attached files that were infected with the [EMAIL PROTECTED] virus or worm. They have been removed. For more information on Road Runner's virus filtering initiative, visit our Help Member Services pages at http://help.rr.com, or the virus filtering information page directly at http://help.rr.com/faqs/e_mgsp.html.
startkde question
When I start kde via startkde after login, an instance of xconsole isalso started. This instance doesn't seem to be started in kdeinit. Where is it started from? Thanks, Dave Feustel -- Tired of having to defend against Malware? (You know: trojans, viruses, SPYWARE, ADWARE, KEYLOGGERS, rootkits, worms and popups) Then Switch to OpenBSD with a KDE desktop!!!
Re: OpenBSD 3.7 on Soekris rebooting at random
Olivier Mehani wrote: Hi, I'm facing a strange problem (started a week or so ago): My OpenBSD 3.7 running on a Soekris net4511 reboots with no obvious reason. I've started monitoring the memory usage, load average and pf states, but these do not seem to be related to the problem. I'm also using the hardware watchdog which I will disable to see if it is involved in the problem, but everything has been working well for more than two months with it before. Do you have any suggestion of other things I should monitor ? Thanks -- Olivier Mehani [EMAIL PROTECTED] [demime 1.01d removed an attachment of type application/pgp-signature] a dmesg may be helpful...
Re: OpenBSD 3.7 on Soekris rebooting at random
Olivier Mehani wrote: My OpenBSD 3.7 running on a Soekris net4511 reboots with no obvious reason. I've started monitoring the memory usage, load average and pf states, but these do not seem to be related to the problem. [...] Do you have any suggestion of other things I should monitor ? Input voltage and current? I've seen reports of similar behaviour from Soekris boxes with underspec or flaky power supplies. -- Darren Tucker (dtucker at zip.com.au) GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69 Good judgement comes with experience. Unfortunately, the experience usually comes from bad judgement.
certpatch in 3.8 ...
I've installed a new server with 3.8 current. I can't find certpatch anymore? I installed a snapshop. 3.8 GENERIC#106 i386 Is the use of the programm obsolet? thanks. regards. Karl-Heinz
Re: Problems with pf+nat+some websites
Guido Tschakert wrote: Ok, after digging in the archives I found the thread pf reassemble tcp problem in latest snapshot? and it seems there is no real solution for this problem in OpenBSD/pf. provocation on I found that somewhat poor, because with Cisco IOS and Linux iptables this problem doesn't exist and there are no problems to reach this sites with nat. provocation off Hello, I have problems to load some websites (e.g. www.hit.de, www.lidl.de, www.ebay.de, www.ebay.com). They are very slow if they show up. I have this problem since this morning, when I changed our old cisco router with our new OpenBSD Firewall. Other sites load normal. Here is the network $srcnetopenbsd-box--$src_ext | ---internet (the OpenbsdBox has a regular IP-Address and an Alias from Class B $src_ext, therefore there is the exclusion in nat Yes I know this looks evil, but I have some more Firewalls in $src-net :-) thanks guido
Re: startkde question
El mar, 23-08-2005 a las 08:48 -0500, Dave Feustel escribis: When I start kde via startkde after login, an instance of xconsole isalso started. This instance doesn't seem to be started in kdeinit. Where is it started from? I haven't a X installation at hand (I have only obsd acting as server here), but trying with google I got: http://archives.neohapsis.com/archives/openbsd/2004-01/0493.html Google has better memory than me. It may help you. regards, Juanjo -- Desarrollo y sistemas: http://www.usebox.net/ Pagina Personal: http://www.usebox.net/jjm/
Re: startkde question
On Tuesday 23 August 2005 09:12, Antoine Jacoutot wrote: Dave Feustel wrote: When I start kde via startkde after login, an instance of xconsole isalso started. This instance doesn't seem to be started in kdeinit. Where is it started from? Well, if you use an graphical login manager, I would say it might comes from this file : /etc/X11/xdm/Xsetup_0 As of about an hour ago, I stopped using xdm. -- Tired of having to defend against Malware? (You know: trojans, viruses, SPYWARE, ADWARE, KEYLOGGERS, rootkits, worms and popups) Then Switch to OpenBSD with a KDE desktop!!!
Re: OpenBSD 3.7 on Soekris rebooting at random
On Tue, 23 Aug 2005 15:21:53 +0200 Dimitri Georganas [EMAIL PROTECTED] wrote: I'm facing a strange problem (started a week or so ago): a dmesg may be helpful... Yes, I realised I forgot to include it just after posting, sorry... Anyway, it confirms that this is the watchdog which triggered the reset, but I still don't know why... Full dmesg follows: OpenBSD 3.7 (GENERIC) #50: Sun Mar 20 00:01:57 MST 2005 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: AMD Am486DX4 W/B or Am5x86 W/B 150 (AuthenticAMD 486-class) cpu0: FPU real mem = 66691072 (65128K) avail mem = 53448704 (52196K) using 839 buffers containing 3436544 bytes (3356K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+(00) BIOS, date 20/41/22, BIOS32 rev. 0 @ 0xf7840 pcibios0 at bios0: rev 2.0 @ 0xf/0x1 pcibios0: pcibios_get_intr_routing - function not supported pcibios0: PCI IRQ Routing information unavailable. pcibios0: PCI bus #1 is the last bus bios0: ROM list: 0xc8000/0x9000 cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) elansc0 at pci0 dev 0 function 0 AMD ElanSC520 PCI rev 0x00: product 0 steppin g 1.1, CPU clock 100MHz, reset 8WDT elansc0: WARNING: LAST RESET DUE TO WATCHDOG EXPIRATION! gpio0 at elansc0: 32 pins cbb0 at pci0 dev 9 function 0 Texas Instruments PCI1410 CardBus rev 0x02: irq 10 ath0 at pci0 dev 16 function 0 Atheros AR5212 rev 0x01: irq 11 ath0: mac 80.9 phy 4.3 radio 3.6, 802.11a/b/g, FCC1A, address 00:02:6f:21:ea:79 gpio at ath0 not configured sis0 at pci0 dev 18 function 0 NS DP83815 10/100 rev 0x00: DP83816A, irq 5, ad dress 00:00:24:c4:22:5c nsphyter0 at sis0 phy 0: DP83815 10/100 PHY, rev. 1 sis1 at pci0 dev 19 function 0 NS DP83815 10/100 rev 0x00: DP83816A, irq 9, ad dress 00:00:24:c4:22:5d nsphyter1 at sis1 phy 0: DP83815 10/100 PHY, rev. 1 cardslot0 at cbb0 slot 0 flags 0 cardbus0 at cardslot0: bus 1 device 0 cacheline 0x10, lattimer 0x3f pcmcia0 at cardslot0 isa0 at mainbus0 isadma0 at isa0 pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0 (mux 1 ignored for console): console keyboard wdc0 at isa0 port 0x1f0/8 irq 14 wd0 at wdc0 channel 0 drive 0: Hitachi XX.V.3.4.0.0 wd0: 1-sector PIO, LBA, 488MB, 1000944 sectors wd0(wdc0:0:0): using BIOS timings pcppi0 at isa0 port 0x61 midi0 at pcppi0: PC speaker sysbeep0 at pcppi0 npx0 at isa0 port 0xf0/16: using exception 16 pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo pccom0: console pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo biomask f5c5 netmask ffe5 ttymask ffe7 pctr: no performance counters in CPU rtw0 at cardbus0 dev 0 function 0 irq 10 rtw0: ver F, radio SA2400A, amp SA2411, address 00:0f:3d:cf:cb:e8 dkcsum: wd0 matched BIOS disk 80 root on wd0a rootdev=0x0 rrootdev=0x300 rawdev=0x302 WARNING: / was not properly unmounted And, as it may help too, my watchdog script: #!/bin/sh echo starting watchdog... sysctl kern.watchdog.auto=0 /dev/null while : ; do sysctl kern.watchdog.period=10 /dev/null sleep 8 done -- Olivier Mehani [EMAIL PROTECTED]
Re: startkde question
Am Dienstag, 23. August 2005 15:48 schrieb Dave Feustel: When I start kde via startkde after login, an instance of xconsole isalso started. This instance doesn't seem to be started in kdeinit. Where is it started from? Is is mentioned in your ~/.xinitrc file? Regards, Stephan
Re: Problems with pf+nat+some websites
I don't see where you set the MTU/MSS? Are you sure you have set them somewhere else? eBay is known to have problems with bad/wrong MTU/MSS. Try adding scrub out on $ext_if max-mss 1414 to your pf.conf and adding -mtu 1454 to the route. Also take a look at pppoe(4) [*NOT* pppoe(8)!], section MTU/MSS ISSUES. -- Jonathan
Re: certpatch in 3.8 ...
On Tue, Aug 23, 2005 at 03:57:32PM +0200, Karl-Heinz Wild wrote: I've installed a new server with 3.8 current. I can't find certpatch anymore? I installed a snapshop. 3.8 GENERIC#106 i386 Is the use of the programm obsolet? yes, it was removed a little while ago. you can get the same functionality from openssl(1) req. see also isakmpd(8). jmc
Re: problem with rtw in hostap mode
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Will H. Backman Sent: Monday, August 22, 2005 2:33 PM To: Misc OpenBSD Subject: Re: problem with rtw in hostap mode -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Will H. Backman Sent: Monday, August 22, 2005 1:06 PM To: Misc OpenBSD Subject: problem with rtw in hostap mode Data modified on freelist: word 4 of object 0xd09d2a00 size 0xc0 previous type devbuf (0xdeadbeee != 0xdeadbeef) Data modified on freelist: word 4 of object 0xd0a08100 size 0x100 previous type devbuf (0xdeadbeee != 0xdeadbeef) Data modified on freelist: word 4 of object 0xd0a31900 size 0x100 previous type devbuf (0xdeadbeee != 0xdeadbeef) -- Will Backman - Network Administrator Coastal Enterprises, Inc. http://www.ceimaine.org Kinda funny how the hex worked out: (0xdeadbeee != 0xdeadbeef) Perhaps I'm the only one that sees humor it that. Hmmm...Looking at the man page for rtw, I noticed that the example WEP key looks very similar to the error messages that I got. Is something hard-coded in there? I wasn't using WEP. The following hostname.if(5) example configures rtw0 to join whatever network is available on boot, using WEP key ``0x1deadbeef1'', channel 11, obtaining an IP address using DHCP: dhcp NONE NONE NONE nwkey 0x1deadbeef1 chan 11
Re: Kernel PPPoE is dieing...
On Tue, Aug 16, 2005 at 10:09:49AM -0300, Felipe Mesquita wrote:
in-kernel pppoe. Anyway, I've made the script that checks for the
device ip, and Croned it every 3 minutes (Depending on the needs
it can be higher..)
I took the smarts of your script, and also wrote a simple logging
tool. It's just a wrapper for the syslog(3) function call (that
allows you to log to syslog via the shell).
In root's crontab, I have this entry:
* * * * * /usr/local/sbin/chkpppoe.sh
The chkpppoe.sh script looks like this:
#!/bin/sh
PATH=/sbin:/bin:/usr/sbin:/usr/bin
SYSLOGGER=/usr/local/sbin/syslogger
IFACE=pppoe0
PROGNAME=chkpppoe.sh
VAR=`ifconfig ${IFACE} | grep inet | cut -c 7`
if [ $VAR = 0 ];
then
${SYSLOGGER} ${PROGNAME}: ${IFACE} appears to be down; attempting to
bring it back up
ifconfig ${IFACE} up
sleep 60
else
${SYSLOGGER} ${PROGNAME}: ${IFACE} appears to be up; doing nothing
fi
#end of chkpppoe.sh
The 'syslogger' program is this trivial program:
/* syslogger.c begin */
#include syslog.h
#include stdarg.h
#include stdio.h
#include stdlib.h
#include string.h
#define DEFAULT_PRIORITY LOG_INFO
#define DEFAULT_PRIORITY_STRING LOG_INFO
void usage (int argc, char* argv[])
{
printf (usage: %s [-ln] \user message\\n,
argv[0]);
printf (where -ln specifies the log level, an n is is one of\n
\t-l0 LOG_EMERG\n
\t-l1 LOG_ALERT\n
\t-l2 LOG_CRIT\n
\t-l3 LOG_ERR\n
\t-l4 LOG_WARNING\n
\t-l5 LOG_NOTICE\n
\t-l6 LOG_INFO (default)\n
\t-l7 LOG_DEBUG\n
);
exit(EXIT_SUCCESS);
}
int main (int argc, char* argv[])
{
int priority = DEFAULT_PRIORITY;
char* msg = NULL;
switch (argc) {
case 3:
if ( (3==strlen(argv[1]))
(0==strncmp(-l, argv[1], 2)) ) {
priority = (int)strtol(argv[1][2],
(char**)NULL, 10);
if ( (priority 0) || (priority 7) ) {
fprintf(stderr,
warning: no such
priority: %i; defaulting to
%s\n, priority,
DEFAULT_PRIORITY_STRING);
priority = DEFAULT_PRIORITY;
}
}
else {
fprintf(stderr,
warning: invalid option '%s';
defaulting to
%s\n, argv[1],
DEFAULT_PRIORITY_STRING);
priority = DEFAULT_PRIORITY;
}
msg = argv[2];
break;
case 2:
msg = argv[1];
break;
default:
usage(argc,argv);
}
syslog(priority, %s, msg);
return 0;
}
/* syslogger.c end */
I just saw the program actually work, and can verify it in
/var/log/messages:
...
Aug 23 09:14:01 excrement syslogger: chkpppoe.sh: pppoe0 appears to be up;
doing nothing
Aug 23 09:14:08 excrement /bsd: pppoe0: down
Aug 23 09:14:08 excrement /bsd: pppoe0: phase terminate
Aug 23 09:14:16 excrement /bsd: pppoe0: phase dead
Aug 23 09:15:01 excrement syslogger: chkpppoe.sh: pppoe0 appears to be down;
attempting to bring it back up
Aug 23 09:15:01 excrement /bsd: pppoe0: phase establish
Aug 23 09:15:01 excrement /bsd: pppoe0: phase authenticate
Aug 23 09:15:03 excrement /bsd: pppoe0: phase network
Aug 23 09:16:01 excrement syslogger: chkpppoe.sh: pppoe0 appears to be up;
doing nothing
...
Hopefully someone finds this useful :)
Matt
--
Matt Garman
email at: http://raw-sewage.net/index.php?file=email
proper way to format/use floppies (i386)
Hi, I could not tell from the documentation which is the proper way to setup and use floppy disks on the i386 architecture, i.e. which is the right partition to use. I am talking about the standard 3.5 inch 1.44 MB floppy disks. There are several possibilities to put a file system onto one: First of all, a floppy needs to be low level formatted, which can be achieved by the fdformat program. (Ususally, this is not necessary nowadays, since floppies come preformatted.) Then fdisk shows an empty partition table. Without adding a type a6 partition, I have a valid disklabel: 16 partitions: # size offset fstype[fsize bsize cpg] c: 2880 0 unused00 # Cyl 0 -79 I can then do a newfs fd0c and afterwards the disklabel looks as follows: 16 partitions: # size offset fstype [fsize bsize cpg] c: 2880 0 4.2BSD 2048 16384 80 # Cyl 0 -79 And I can mount /dev/fd0c. But _strangely_, I can mount /dev/fd0a as well! (But I can't do newfs fd0a ...) The other way would be to add a proper partition to the disklabel: Either by doing disklabel -w fd0 floppy3 or by interactively adding a partition a that covers the whole disk. The first command yields a disklabel like this: 16 partitions: # size offset fstype [fsize bsize cpg] a: 2880 0 4.2BSD 5124096 80 # Cyl 0 -79 b: 2880 0 unused 0 0 # Cyl 0 -79 c: 2880 0 unused 0 0 # Cyl 0 -79 The second command's disklabel does not have the b partition. Then, doing newfs fd0a or newfs fd0c yields a filesystem I can mount as /dev/fd0a or /dev/fd0c in either case. The command newfs fd0c changes the disklabel to the following form though: 16 partitions: # size offset fstype [fsize bsize cpg] a: 2880 0 4.2BSD 5124096 80 # Cyl 0 -79 b: 2880 0 unused 0 0 # Cyl 0 -79 c: 2880 0 unused 2048 16384 80 # Cyl 0 -79 which should actually be invalid since a and c overlap. Anyway, it works and both partitions can be used. Well, I am a little confused and would like to know which is the proper way of handling this. I think that the proper way is to add an use partition a, but I have seen usage of partition c in several documentations on the web, so this is why I ask. Thanks in advance! Michael
Re: Automatic setup of partitions
From Nick Holland: The problem arises when, if going on to a brand new machine, that the disk size may be different than the original it is restoring. As part of the installer (in the OpenBSD install environment, booted off an openbsd installer CD) I'd like to read the size of the disk and partition the disk accordingly. would I need to generate all of this information? Using your strategy, you would have to generate the info. Here's a (I think) better idea... Rather than trying to partition out percentages, just put in what you need... /100M swap 512M /usr 4G /var 1G /tmp 100M ... and so on. And (here's the shocker) leave the REST OF THE DRIVE UNALLOCATED! Unsure why I didn't get this reply directly, seems the email never made it to me. An eminently sensible solution, alongside the suggestion to grow partitions. I suppose my only question now is this: After assigning a default disklabel (to a blank disk), can I just feed disklabel the partition information? ie, just this part: 16 partitions: a: 2048193 634.2BSD 1024 819216 # (Cyl. 0*- 203 b: 524160 2048256 swap# (Cyl. 2032 - 2551) c: 1171875000unused0 0# (Cyl.0 - 116257*) d: 114605694 25724164.2BSD 1024 819216 # (Cyl. 2552 - 116248*) Using disklabel -R, instead of the whole file: type: ESDI disk: ESDI/IDE disk label: IC35L060AVER07-0 yadda... 16 partitions: #size offsetfstype [fsize bsize cpg] a: 2048193 634.2BSD 1024 819216 # (Cyl. 0*- 2031) yadda... Gaby -- Junkets for bunterish lickspittles since 1998! [EMAIL PROTECTED] http://weblog.vanhegan.net
Re: OpenBSD 3.7 on Soekris rebooting at random
Did you put this atheros card in one week ago? :) ath0 at pci0 dev 16 function 0 Atheros AR5212 rev 0x01: irq 11 ath0: mac 80.9 phy 4.3 radio 3.6, 802.11a/b/g, FCC1A, address 3.7 would crash on ath0 with AR5212 in hostap mode every six hours or so. Your watchdog does an excellent job, otherwise your board would just freeze. Not sure if this is an ath problem or a card-specific problem, but later snapshots (june) made it worse: the system would freeze when you'd do ifconfig up - probably due to the gpio support that, as you can see, isn't here yet in this dmesg. Your best chance is to check out the latest snapshots to see if the problem is fixed. I reported it a while ago, but didn't check back. I just replaced the atheros card by an old prism card and that one works 24/7. Olivier Mehani wrote: On Tue, 23 Aug 2005 15:21:53 +0200 Dimitri Georganas [EMAIL PROTECTED] wrote: I'm facing a strange problem (started a week or so ago): a dmesg may be helpful... Yes, I realised I forgot to include it just after posting, sorry... Anyway, it confirms that this is the watchdog which triggered the reset, but I still don't know why... Full dmesg follows: OpenBSD 3.7 (GENERIC) #50: Sun Mar 20 00:01:57 MST 2005 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: AMD Am486DX4 W/B or Am5x86 W/B 150 (AuthenticAMD 486-class) cpu0: FPU real mem = 66691072 (65128K) avail mem = 53448704 (52196K) using 839 buffers containing 3436544 bytes (3356K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+(00) BIOS, date 20/41/22, BIOS32 rev. 0 @ 0xf7840 pcibios0 at bios0: rev 2.0 @ 0xf/0x1 pcibios0: pcibios_get_intr_routing - function not supported pcibios0: PCI IRQ Routing information unavailable. pcibios0: PCI bus #1 is the last bus bios0: ROM list: 0xc8000/0x9000 cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) elansc0 at pci0 dev 0 function 0 AMD ElanSC520 PCI rev 0x00: product 0 steppin g 1.1, CPU clock 100MHz, reset 8WDT elansc0: WARNING: LAST RESET DUE TO WATCHDOG EXPIRATION! gpio0 at elansc0: 32 pins cbb0 at pci0 dev 9 function 0 Texas Instruments PCI1410 CardBus rev 0x02: irq 10 ath0 at pci0 dev 16 function 0 Atheros AR5212 rev 0x01: irq 11 ath0: mac 80.9 phy 4.3 radio 3.6, 802.11a/b/g, FCC1A, address 00:02:6f:21:ea:79 gpio at ath0 not configured sis0 at pci0 dev 18 function 0 NS DP83815 10/100 rev 0x00: DP83816A, irq 5, ad dress 00:00:24:c4:22:5c nsphyter0 at sis0 phy 0: DP83815 10/100 PHY, rev. 1 sis1 at pci0 dev 19 function 0 NS DP83815 10/100 rev 0x00: DP83816A, irq 9, ad dress 00:00:24:c4:22:5d nsphyter1 at sis1 phy 0: DP83815 10/100 PHY, rev. 1 cardslot0 at cbb0 slot 0 flags 0 cardbus0 at cardslot0: bus 1 device 0 cacheline 0x10, lattimer 0x3f pcmcia0 at cardslot0 isa0 at mainbus0 isadma0 at isa0 pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0 (mux 1 ignored for console): console keyboard wdc0 at isa0 port 0x1f0/8 irq 14 wd0 at wdc0 channel 0 drive 0: Hitachi XX.V.3.4.0.0 wd0: 1-sector PIO, LBA, 488MB, 1000944 sectors wd0(wdc0:0:0): using BIOS timings pcppi0 at isa0 port 0x61 midi0 at pcppi0: PC speaker sysbeep0 at pcppi0 npx0 at isa0 port 0xf0/16: using exception 16 pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo pccom0: console pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo biomask f5c5 netmask ffe5 ttymask ffe7 pctr: no performance counters in CPU rtw0 at cardbus0 dev 0 function 0 irq 10 rtw0: ver F, radio SA2400A, amp SA2411, address 00:0f:3d:cf:cb:e8 dkcsum: wd0 matched BIOS disk 80 root on wd0a rootdev=0x0 rrootdev=0x300 rawdev=0x302 WARNING: / was not properly unmounted And, as it may help too, my watchdog script: #!/bin/sh echo starting watchdog... sysctl kern.watchdog.auto=0 /dev/null while : ; do sysctl kern.watchdog.period=10 /dev/null sleep 8 done
Re: Automatic setup of partitions
After assigning a default disklabel (to a blank disk), can I just feed disklabel the partition information? ie, just this part: pipe into disklabel -E, perhaps?
Re: problem with rtw in hostap mode
--On 23 August 2005 10:44 -0400, Will H. Backman wrote: -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Will H. Backman Sent: Monday, August 22, 2005 2:33 PM To: Misc OpenBSD Subject: Re: problem with rtw in hostap mode -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Will H. Backman Sent: Monday, August 22, 2005 1:06 PM To: Misc OpenBSD Subject: problem with rtw in hostap mode Data modified on freelist: word 4 of object 0xd09d2a00 size 0xc0 previous type devbuf (0xdeadbeee != 0xdeadbeef) Data modified on freelist: word 4 of object 0xd0a08100 size 0x100 previous type devbuf (0xdeadbeee != 0xdeadbeef) Data modified on freelist: word 4 of object 0xd0a31900 size 0x100 previous type devbuf (0xdeadbeee != 0xdeadbeef) -- Will Backman - Network Administrator Coastal Enterprises, Inc. http://www.ceimaine.org Kinda funny how the hex worked out: (0xdeadbeee != 0xdeadbeef) Perhaps I'm the only one that sees humor it that. Hmmm...Looking at the man page for rtw, I noticed that the example WEP key looks very similar to the error messages that I got. Is something hard-coded in there? I wasn't using WEP. deadbeef is a simple easy-to-type thing when you need some literal value, so it's not surprising it appears in more than one place. 0x1deadbeef1 (example WEP key) != 0xdeadbeef (WEIRD_ADDR in /usr/src/sys/kern/kern_malloc.c, 'known text to copy into free objects so that modifications after frees can be detected'). I think this means that an operation (probably --) is done on an object which has already been freed (which, if in userland, I imagine would be trapped by the malloc protection recently mentioned). You'll probably find this happens when you 'ifconfig rtw0 down', it does with ral anyway (http://archives.neohapsis.com/archives/openbsd/2005-05/2421.html), so I guess it's in some common hostap-related code.
Re: startkde question
On Tuesday 23 August 2005 09:50, Stephan Tesch wrote: Am Dienstag, 23. August 2005 15:48 schrieb Dave Feustel: When I start kde via startkde after login, an instance of xconsole isalso started. This instance doesn't seem to be started in kdeinit. Where is it started from? Is is mentioned in your ~/.xinitrc file? Regards, Stephan I don't have an .xinitrc. I run startkde from the command line after login. -- Tired of having to defend against Malware? (You know: trojans, viruses, SPYWARE, ADWARE, KEYLOGGERS, rootkits, worms and popups) Then Switch to OpenBSD with a KDE desktop!!!
Re: Kernel PPPoE is dieing...
Matt Garman wrote:
I took the smarts of your script, and also wrote a simple logging
tool. It's just a wrapper for the syslog(3) function call (that
allows you to log to syslog via the shell).
In root's crontab, I have this entry:
* * * * * /usr/local/sbin/chkpppoe.sh
The chkpppoe.sh script looks like this:
#!/bin/sh
PATH=/sbin:/bin:/usr/sbin:/usr/bin
SYSLOGGER=/usr/local/sbin/syslogger
IFACE=pppoe0
PROGNAME=chkpppoe.sh
VAR=`ifconfig ${IFACE} | grep inet | cut -c 7`
if [ $VAR = 0 ];
then
${SYSLOGGER} ${PROGNAME}: ${IFACE} appears to be down;
attempting
to bring it back up ifconfig ${IFACE} up
sleep 60
else
${SYSLOGGER} ${PROGNAME}: ${IFACE} appears to be up; doing
nothing
fi
#end of chkpppoe.sh
The 'syslogger' program is this trivial program:
/* syslogger.c begin */
#include syslog.h
#include stdarg.h
#include stdio.h
#include stdlib.h
#include string.h
...
I just saw the program actually work, and can verify it in
/var/log/messages:
...
Aug 23 09:14:01 excrement syslogger: chkpppoe.sh: pppoe0 appears to
be up; doing nothing
Aug 23 09:14:08 excrement /bsd: pppoe0: down
Aug 23 09:14:08 excrement /bsd: pppoe0: phase terminate
Aug 23 09:14:16 excrement /bsd: pppoe0: phase dead
Aug 23 09:15:01 excrement syslogger: chkpppoe.sh: pppoe0 appears to
be down; attempting to bring it back up Aug 23 09:15:01 excrement
/bsd: pppoe0: phase establish
Aug 23 09:15:01 excrement /bsd: pppoe0: phase authenticate
Aug 23 09:15:03 excrement /bsd: pppoe0: phase network
Aug 23 09:16:01 excrement syslogger: chkpppoe.sh: pppoe0 appears to
be up; doing nothing ...
Hopefully someone finds this useful :)
Since the fixes for this are not in stable and I should probably be
running -current instead of this workaround, logger does the job just
fine...
$ cat pppoecheck
#!/bin/sh
#
# NAME
# pppoecheck - attempt to restart pppoe interface if it is down
# pppoe0 interface exists
if [ -f /etc/hostname.pppoe0 ]; then
down=`ifconfig pppoe inet | fgrep 0.0.0.0`
if [ $down ]; then
logger -p user.err pppoe0: phase restart
ifconfig pppoe0 up
fi
fi
Re: proper way to format/use floppies (i386)
Floppies usually don't have a partition table nor a disk label, so just newfs fd0c and you should be fine. -- Jonathan
Re: 3.8 beta requests
On 8/23/05, Theo de Raadt [EMAIL PROTECTED] wrote: This release will bring a lot of new ideas from us. One of them in particular is somewhat risky. First off: I like the idea. The technical merit is obvious. I have a question regarding the timing, though. Is there a particular reason to go ahead with these changes before a freeze? An alternative, going ahead in the first snapshot after branching 3.8, may provide more time to test and get reports on problems. Your timeline is entirely wrong. These changes have been worked on for almost 3 years now. And they went in right after the tree unlocked after 3.7. The diffs just had a full test cycle by -current users for a few months already; and lots of bugs got fixed along the way.
Re: OpenBSD 3.7 on Soekris rebooting at random
My OpenBSD 3.7 running on a Soekris net4511 reboots with no obvious reason. I've started monitoring the memory usage, load average and pf states, but these do not seem to be related to the problem. I'm also using the hardware watchdog which I will disable to see if it is involved in the problem, but everything has been working well for more than two months with it before. If the couple of thousand soekris machines of various developers and users started rebooting just like that, we would have heard of it by now. Very hard to diagnose when one rare one somewhere, without *any debugging information* does so.
Re: CURRENT and DHCP with Linksys routers--SOLVED (WAS: 8/13 snapshot and DHCP)
The problem no longer exists, thanks to a patch entered into cvs yesterday afternoon. Huge thanks to Ken Westerback, Theo, and the rest of the development team. This may have been a little thing, but it's the sort of response that keeps me loving OpenBSD. Time to save up a little more for pre-orders for me and my friends CDJ -- Christian Jones [EMAIL PROTECTED] http://www.aleph0.com/~chjones
Re: LSI Logic Ultra320 Scsi Raid Card
Yeah that should work. Need to add the pci ids. Remind me again post 3.8. On Tue, Aug 23, 2005 at 04:31:53AM -0400, Eci Souji wrote: Hi, did some googling and archive searching but didn't find anything so here's my question... Is the Ultra320-2E supported under OpenBSD 3.7? I'm trying to install from cd, but get the following error during boot... vendor Symbios Logic, unknown product 0x0408 (class mass storage subclass RAID, rev 0x07) at pci3 dev 14 function 0 not confirgured Thoughts? - S
Re: Fwd: Complete disk disaster
That is bad advice. On Tue, Aug 23, 2005 at 11:46:14AM +0200, Jernej Vodopivec wrote: forgot to cc: -- Forwarded message -- From: Jernej Vodopivec [EMAIL PROTECTED] Date: Aug 23, 2005 11:45 AM Subject: Re: Complete disk disaster To: Ramiro Aceves [EMAIL PROTECTED] On 8/23/05, Ramiro Aceves [EMAIL PROTECTED] wrote: ...Do you know of any disk test or utility program that can stress the disk to work hard until it fails? try badblocks - I don't know if it is ported on OpenBSD but you can find it on knoppix cd Jernej
Re: 3.8 beta requests
J. Lievisse Adriaanse wrote: On Tue, 23 Aug 2005 01:37:12 -0600 Theo de Raadt [EMAIL PROTECTED] wrote: We are heading towards making the real 3.8 release soonish. I was wondering, when can we start pre-ordering our cd-sets? We normally setup pre-orders 1 month before. We might do it a bit earlier... dunno. But it is hard to do when artwork is not final yet :) I wonder what the theme for this release will be... Maybe a slogan along the lines of, Is your software good enough for OpenBSD!! Perhaps it could be worked into the release's theme. Or a Good Housekeeping Seal of Approval like version of Puffy. I'm not in the publicity game, and for good reason, but it seems a good opportunity for some positive publicity. Some may try and spin the broken applications against OpenBSD. Make sure the OpenBSD story is out there first, loud and clear. Ray
Re: proper way to format/use floppies (i386)
On Tuesday 23 August 2005 10:58, Michael Adam wrote: Hi, I could not tell from the documentation which is the proper way to setup and use floppy disks on the i386 architecture, i.e. which is the right partition to use. I am talking about the standard 3.5 inch 1.44 MB floppy disks. There are several possibilities to put a file system onto one: First of all, a floppy needs to be low level formatted, which can be achieved by the fdformat program. (Ususally, this is not necessary nowadays, since floppies come preformatted.) Then fdisk shows an empty partition table. Without adding a type a6 partition, I have a valid disklabel: 16 partitions: # size offset fstype[fsize bsize cpg] c: 2880 0 unused00 # Cyl 0 -79 I can then do a newfs fd0c and afterwards the disklabel looks as follows: 16 partitions: # size offset fstype [fsize bsize cpg] c: 2880 0 4.2BSD 2048 16384 80 # Cyl 0 -79 And I can mount /dev/fd0c. But _strangely_, I can mount /dev/fd0a as well! (But I can't do newfs fd0a ...) The other way would be to add a proper partition to the disklabel: Either by doing disklabel -w fd0 floppy3 or by interactively adding a partition a that covers the whole disk. The first command yields a disklabel like this: 16 partitions: # size offset fstype [fsize bsize cpg] a: 2880 0 4.2BSD 5124096 80 # Cyl 0 -79 b: 2880 0 unused 0 0 # Cyl 0 - 79 c: 2880 0 unused 0 0 # Cyl 0 - 79 The second command's disklabel does not have the b partition. Then, doing newfs fd0a or newfs fd0c yields a filesystem I can mount as /dev/fd0a or /dev/fd0c in either case. The command newfs fd0c changes the disklabel to the following form though: 16 partitions: # size offset fstype [fsize bsize cpg] a: 2880 0 4.2BSD 5124096 80 # Cyl 0 -79 b: 2880 0 unused 0 0 # Cyl 0 - 79 c: 2880 0 unused 2048 16384 80 # Cyl 0 -79 which should actually be invalid since a and c overlap. Anyway, it works and both partitions can be used. Well, I am a little confused and would like to know which is the proper way of handling this. I think that the proper way is to add an use partition a, but I have seen usage of partition c in several documentations on the web, so this is why I ask. Thanks in advance! Michael I would avoid all this and use the 'mtools' package instead. It deals with msdos fat-12(?) floppies, and is tons easier to use. Then you can hand those floppies to others and they can read/write them. --STeve Andre'
Re: startkde question
Dave Feustel wrote: I don't have an .xinitrc. I run startkde from the command line after login. Then add a .xinitrc in your homedir with the following line : exec startkde ... then launch startx. Antoine
Re: Complete disk disaster
Good way to work a hard disk: Unpack ports or source tar.gz files, 'specially with softdeps off. And once you are done unpacking run /usr/libexec/locate.updatedb a few times :-) This would cause the system to 'touch' every file on your drive and you will almost surely see errors if there is a disk problem. --Bryan
rtl8139 problem on 3.8 bsd.rd
Trying to test the snapshots but the last two bsd.rd's seem to fail on rl0 detection at boot. bsd.rd from 14.08 exits with a dump error 19 at the end of hardware detection. bsd.rd from 22.08 comes up but the rl0 is not configured. nor does it seem possible to do anything to change that. The rl in question is a PCMCIA Surecom Ep-428x\4b but was working fine until now, since 3.6 or so when I replaced the internal mini-pci xl mike OpenBSD 3.8-beta (RAMDISK_CD) #775: Mon Aug 22 23:10:54 MDT 2005 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/RAMDISK_CD cpu0: Intel Pentium III (GenuineIntel 686-class) 752 MHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real mem = 536301568 (523732K) avail mem = 483479552 (472148K) using 4278 buffers containing 26918912 bytes (26288K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+(00) BIOS, date 07/08/03, BIOS32 rev. 0 @ 0xffe90 apm0 at bios0: Power Management spec V1.2 apm0: flags 30102 dobusy 0 doidle 1 pcibios0 at bios0: rev 2.1 @ 0xf/0x1 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfbd80/176 (9 entries) pcibios0: PCI Interrupt Router at 000:07:0 (Intel 82371 ISA and IDE rev 0x00) pcibios0: PCI bus #3 is the last bus bios0: ROM list: 0xc/0x1 cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 Intel 82443BX AGP rev 0x03 ppb0 at pci0 dev 1 function 0 Intel 82443BX AGP rev 0x03 pci1 at ppb0 bus 1 vga1 at pci1 dev 0 function 0 ATI Mobility M3 rev 0x02 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) cbb0 at pci0 dev 3 function 0 Texas Instruments PCI1420 CardBus rev 0x00: irq 11 cbb1 at pci0 dev 3 function 1 Texas Instruments PCI1420 CardBus rev 0x00: irq 11 pcib0 at pci0 dev 7 function 0 Intel 82371AB PIIX4 ISA rev 0x02 pciide0 at pci0 dev 7 function 1 Intel 82371AB IDE rev 0x01: DMA, channel 0 wired to compatibility, channel 1 wired to compatibility wd0 at pciide0 channel 0 drive 0: SAMSUNG MP0402H wd0: 16-sector PIO, LBA48, 38204MB, 78242976 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 atapiscsi0 at pciide0 channel 1 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: SAMSUNG, CD-ROM SN-124, q008 SCSI0 5/cdrom removable cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2 uhci0 at pci0 dev 7 function 2 Intel 82371AB USB rev 0x01: irq 11 usb0 at uhci0: USB revision 1.0 uhub0 at usb0 uhub0: Intel UHCI root hub, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered Intel 82371AB Power rev 0x03 at pci0 dev 7 function 3 not configured ESS Maestro 3 rev 0x10 at pci0 dev 8 function 0 not configured cardslot0 at cbb0 slot 0 flags 0 cardbus0 at cardslot0: bus 2 device 0 cacheline 0x8, lattimer 0x20 pcmcia0 at cardslot0 cardslot1 at cbb1 slot 1 flags 0 cardbus1 at cardslot1: bus 3 device 0 cacheline 0x8, lattimer 0x20 pcmcia1 at cardslot1 isa0 at pcib0 isadma0 at isa0 pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 npx0 at isa0 port 0xf0/16: using exception 16 pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 biomask ffed netmask ffed ttymask ffef rd0: fixed, 3800 blocks Realtek, Rtl8139, \M^? Realtek 8139 rev 0x10 at cardbus1 dev 0 function 0 not configured dkcsum: wd0 matches BIOS drive 0x80 root on rd0a rootdev=0x1100 rrootdev=0x2f00 rawdev=0x2f02 OpenBSD 3.7-stable (GENERIC) #1: Sat Jul 30 02:53:03 CEST 2005 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel Pentium III (GenuineIntel 686-class) 752 MHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real mem = 536301568 (523732K) avail mem = 482574336 (471264K) using 4278 buffers containing 26918912 bytes (26288K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+(00) BIOS, date 07/08/03, BIOS32 rev. 0 @ 0xffe90 apm0 at bios0: Power Management spec V1.2 apm0: AC on, battery charge unknown pcibios0 at bios0: rev 2.1 @ 0xf/0x1 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfbd80/176 (9 entries) pcibios0: PCI Interrupt Router at 000:07:0 (Intel 82371 ISA and IDE rev 0x00) pcibios0: PCI bus #3 is the last bus bios0: ROM list: 0xc/0x1 cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 Intel 82443BX AGP rev 0x03 ppb0 at pci0 dev 1 function 0 Intel 82443BX AGP rev 0x03 pci1 at ppb0 bus 1 vga1 at pci1 dev 0 function 0 ATI Mobility M3 rev 0x02 wsdisplay0 at vga1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) cbb0 at pci0 dev 3 function 0 Texas Instruments PCI1420 CardBus rev 0x00: irq 11 cbb1 at pci0 dev 3 function 1 Texas Instruments PCI1420 CardBus rev 0x00: irq 11 pcib0 at pci0 dev 7 function 0 Intel 82371AB PIIX4 ISA rev 0x02 pciide0 at pci0 dev 7 function 1 Intel 82371AB IDE rev 0x01: DMA, channel 0 wired to
Re: Complete disk disaster
Most drives keep track of errors and are able to warn you of trouble before they fail completely. SMART is not always reliable, but should warn you of coming problems. See the atactl man page
Re: OpenBSD 3.7 on Soekris rebooting at random
On Tue, Aug 23, 2005 at 06:15:45PM +0200, Olivier Mehani wrote: The reboot is not that periodic (6 hours as you say): it can be as short as 2 hours to 2 days with, once again, no obvious reason. try a ping -f against your accesspoint over the wireless interface and it will probably reboot/lock very quickly. reyk
Re: OpenBSD 3.7 on Soekris rebooting at random
A common cause is an insufficient power supply. This has been discussed on the Soekris technical mailing list many times. On Tuesday 23 August 2005 10:04 am, Theo de Raadt wrote: My OpenBSD 3.7 running on a Soekris net4511 reboots with no obvious reason. I've started monitoring the memory usage, load average and pf states, but these do not seem to be related to the problem. I'm also using the hardware watchdog which I will disable to see if it is involved in the problem, but everything has been working well for more than two months with it before. If the couple of thousand soekris machines of various developers and users started rebooting just like that, we would have heard of it by now. Very hard to diagnose when one rare one somewhere, without *any debugging information* does so. -- John R. Shannon [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
Re: startkde question
On Tuesday 23 August 2005 11:43, Antoine Jacoutot wrote: Dave Feustel wrote: I don't have an .xinitrc. I run startkde from the command line after login. Then add a .xinitrc in your homedir with the following line : exec startkde ... then launch startx. I forget. What was the question? Oh. Yes. It was Where does the xconsole get invoked when I start kde using startkde?. Just trying to get back to the original (as yet unanswered) question. Antoine -- Tired of having to defend against Malware? (You know: trojans, viruses, SPYWARE, ADWARE, KEYLOGGERS, rootkits, worms and popups) Then Switch to OpenBSD with a KDE desktop!!!
Re: OpenBSD 3.7 on Soekris rebooting at random
On Tue, Aug 23, 2005 at 05:10:08PM +0200, Dimitri Georganas wrote: Did you put this atheros card in one week ago? :) ath0 at pci0 dev 16 function 0 Atheros AR5212 rev 0x01: irq 11 ath0: mac 80.9 phy 4.3 radio 3.6, 802.11a/b/g, FCC1A, address btw.: could you also give us the exact product name (on the minipci card)? 3.7 would crash on ath0 with AR5212 in hostap mode every six hours or so. Your watchdog does an excellent job, otherwise your board would just freeze. Not sure if this is an ath problem or a card-specific problem, but later snapshots (june) made it worse: the system would freeze when you'd do ifconfig up - probably due to the gpio support that, as you can see, isn't here yet in this dmesg. there were two fixes for hostap mode and it works for me without problems in the driver. one issue got fixed on 2005/05/28 (ath.c 1.29). the problem was a hardware counter overflow after some traffic and an uncatched interrupt which indicated the overflow and required to clear the counter registers. the second problem was related to receive overruns in the rx descriptor chain, which had been fixed as well (ath.c 1.31 2005/07/19). And, as it may help too, my watchdog script: #!/bin/sh echo starting watchdog... sysctl kern.watchdog.auto=0 /dev/null while : ; do sysctl kern.watchdog.period=10 /dev/null sleep 8 done also have a look at mbalmer@'s watchdogd(8) which had been imported some weeks ago. this has some timing advantages over traditional watchdog scripts. reyk
Re: OpenBSD 3.7 on Soekris rebooting at random
On Tue, 23 Aug 2005 17:10:08 +0200 Dimitri Georganas [EMAIL PROTECTED] wrote: Did you put this atheros card in one week ago? :) No, it's been in it for more than a month now and everything has been working smoothly until last week. ath0 at pci0 dev 16 function 0 Atheros AR5212 rev 0x01: irq 11 ath0: mac 80.9 phy 4.3 radio 3.6, 802.11a/b/g, FCC1A, address 3.7 would crash on ath0 with AR5212 in hostap mode every six hours or so. Your watchdog does an excellent job, otherwise your board would just freeze. This is why it gets paid ;) The reboot is not that periodic (6 hours as you say): it can be as short as 2 hours to 2 days with, once again, no obvious reason. Your best chance is to check out the latest snapshots to see if the problem is fixed. I reported it a while ago, but didn't check back. I just replaced the atheros card by an old prism card and that one works 24/7. Thanks for your advice, I'll check that. -- Olivier Mehani [EMAIL PROTECTED]
Re: LSI Logic Ultra320 Scsi Raid Card
Note that pcidevs_data.h and pcidevs.h are part of the diff. I did this for
easy patching and testing.
Give it a go and let me know if it works.
/marco
Index: ami_pci.c
===
RCS file: /cvs/src/sys/dev/pci/ami_pci.c,v
retrieving revision 1.29
diff -u -r1.29 ami_pci.c
--- ami_pci.c 15 Aug 2005 23:22:46 - 1.29
+++ ami_pci.c 23 Aug 2005 17:15:36 -
@@ -87,6 +87,7 @@
AMI_CHECK_SIGN | AMI_BROKEN },
{ PCI_VENDOR_SYMBIOS, PCI_PRODUCT_SYMBIOS_MEGARAID, 0 },
{ PCI_VENDOR_SYMBIOS, PCI_PRODUCT_SYMBIOS_MEGARAID_320, 0 },
+ { PCI_VENDOR_SYMBIOS, PCI_PRODUCT_SYMBIOS_MEGARAID_3202E, 0 },
{ PCI_VENDOR_SYMBIOS, PCI_PRODUCT_SYMBIOS_SATA8, 0 },
{ 0 }
};
Index: pcidevs
===
RCS file: /cvs/src/sys/dev/pci/pcidevs,v
retrieving revision 1.908
diff -u -r1.908 pcidevs
--- pcidevs 23 Aug 2005 03:31:34 - 1.908
+++ pcidevs 23 Aug 2005 17:15:39 -
@@ -2054,6 +2054,7 @@
product SYMBIOS FC919_10x0625 FC919
product SYMBIOS MEGARAID 0x1960 MegaRAID
product SYMBIOS MEGARAID_320 0x0407 MegaRAID 320
+product SYMBIOS MEGARAID_3202E 0x0408 MegaRAID 320-2E
product SYMBIOS SATA8 0x0409 MegaRAID SATA 8x
/* Packet Engines products */
Index: pcidevs.h
===
RCS file: /cvs/src/sys/dev/pci/pcidevs.h,v
retrieving revision 1.909
diff -u -r1.909 pcidevs.h
--- pcidevs.h 23 Aug 2005 03:31:53 - 1.909
+++ pcidevs.h 23 Aug 2005 17:15:44 -
@@ -2059,6 +2059,7 @@
#definePCI_PRODUCT_SYMBIOS_FC919_1 0x0625 /* FC919 */
#definePCI_PRODUCT_SYMBIOS_MEGARAID0x1960 /* MegaRAID */
#definePCI_PRODUCT_SYMBIOS_MEGARAID_3200x0407 /*
MegaRAID 320 */
+#definePCI_PRODUCT_SYMBIOS_MEGARAID_3202E 0x0408 /*
MegaRAID 320-2E */
#definePCI_PRODUCT_SYMBIOS_SATA8 0x0409 /* MegaRAID
SATA 8x */
/* Packet Engines products */
Index: pcidevs_data.h
===
RCS file: /cvs/src/sys/dev/pci/pcidevs_data.h,v
retrieving revision 1.908
diff -u -r1.908 pcidevs_data.h
--- pcidevs_data.h 23 Aug 2005 03:31:53 - 1.908
+++ pcidevs_data.h 23 Aug 2005 17:15:49 -
@@ -5923,6 +5923,10 @@
MegaRAID 320,
},
{
+ PCI_VENDOR_SYMBIOS, PCI_PRODUCT_SYMBIOS_MEGARAID_3202E,
+ MegaRAID 320-2E,
+ },
+ {
PCI_VENDOR_SYMBIOS, PCI_PRODUCT_SYMBIOS_SATA8,
MegaRAID SATA 8x,
},
Re: proper way to format/use floppies (i386)
On Tue, 23 Aug 2005 16:58:47 +0200, Michael Adam [EMAIL PROTECTED] wrote: Hi, I could not tell from the documentation which is the proper way to setup and use floppy disks on the i386 architecture, i.e. which is the right partition to use. I am talking about the standard 3.5 inch 1.44 MB floppy disks. There are several possibilities to put a file system onto one: First of all, a floppy needs to be low level formatted, which can be achieved by the fdformat program. (Ususally, this is not necessary nowadays, since floppies come preformatted.) Then fdisk shows an empty partition table. Without adding a type a6 partition, I have a valid disklabel: 16 partitions: # size offset fstype[fsize bsize cpg] c: 2880 0 unused00 # Cyl 0 -79 I can then do a newfs fd0c and afterwards the disklabel looks as follows: 16 partitions: # size offset fstype [fsize bsize cpg] c: 2880 0 4.2BSD 2048 16384 80 # Cyl 0 -79 And I can mount /dev/fd0c. But _strangely_, I can mount /dev/fd0a as well! (But I can't do newfs fd0a ...) The other way would be to add a proper partition to the disklabel: Either by doing disklabel -w fd0 floppy3 or by interactively adding a partition a that covers the whole disk. The first command yields a disklabel like this: 16 partitions: # size offset fstype [fsize bsize cpg] a: 2880 0 4.2BSD 5124096 80 # Cyl 0 -79 b: 2880 0 unused 0 0 # Cyl 0 -79 c: 2880 0 unused 0 0 # Cyl 0 -79 The second command's disklabel does not have the b partition. Then, doing newfs fd0a or newfs fd0c yields a filesystem I can mount as /dev/fd0a or /dev/fd0c in either case. The command newfs fd0c changes the disklabel to the following form though: 16 partitions: # size offset fstype [fsize bsize cpg] a: 2880 0 4.2BSD 5124096 80 # Cyl 0 -79 b: 2880 0 unused 0 0 # Cyl 0 -79 c: 2880 0 unused 2048 16384 80 # Cyl 0 -79 which should actually be invalid since a and c overlap. Anyway, it works and both partitions can be used. Well, I am a little confused and would like to know which is the proper way of handling this. I think that the proper way is to add an use partition a, but I have seen usage of partition c in several documentations on the web, so this is why I ask. Thanks in advance! Michael Actually, it's in the FAQ under installation so it's not exactly listed as a FAQ item per se. $ fdformat /dev/rfd0c JCR
Re: OpenBSD 3.7 on Soekris rebooting at random
On Tue, 23 Aug 2005 19:13:40 +0200 Reyk Floeter [EMAIL PROTECTED] wrote: ath0 at pci0 dev 16 function 0 Atheros AR5212 rev 0x01: irq 11 ath0: mac 80.9 phy 4.3 radio 3.6, 802.11a/b/g, FCC1A, address btw.: could you also give us the exact product name (on the minipci card)? It is an Atheros 5354MP ARIES 200mW Mini PCI card On the card is written NL-5354MP+ARIES2, and on the chipset is AR5213A-00 A19911C 1804 there were two fixes for hostap mode and it works for me without problems in the driver. I'll upgrade my system and see if it's better. also have a look at mbalmer@'s watchdogd(8) which had been imported some weeks ago. this has some timing advantages over traditional watchdog scripts. Thanks for the advice, I'll look at it -- Olivier Mehani [EMAIL PROTECTED]
Nagios: Premature end of script headers
Hi all, I installed and configured Nagios on my machine. The Nagios webpage can be retrieve normally, but something strange happens when I try to retrieve host detail: Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator, [EMAIL PROTECTED] and inform them of the time the error occurred, and anything you might have done that may have caused the error. More information about this error may be available in the server error log. Eu olhei o arquivo de log de erros e ele me diz o seguinte: [Tue Aug 23 11:35:06 2005] [error] [client 10.10.1.254http://10.10.1.254/ http://10.10.1.254] Premature end of script headers: /nagios/cgi-bin/tac.cgi [Tue Aug 23 11:35:16 2005] [error] [client 10.10.1.254 http://10.10.1.254/ http://10.10.1.254] Premature end of script headers: /nagios/cgi-bin/status.cgi I've already tried to look for some reference about how to solve this problem at Google, but I couldn't find a thing. Has anyone any suggestion about how to solve this? Thanks -- Joco Salvatti Undergraduating in Computer Science Federal University of Para - UFPA web: http://salvatti.expert.com.br e-mail: [EMAIL PROTECTED]
Re: OpenBSD 3.7 on Soekris rebooting at random
On Tue, Aug 23, 2005 at 07:13:40PM +0200, Reyk Floeter wrote: On Tue, Aug 23, 2005 at 05:10:08PM +0200, Dimitri Georganas wrote: Did you put this atheros card in one week ago? :) ath0 at pci0 dev 16 function 0 Atheros AR5212 rev 0x01: irq 11 ath0: mac 80.9 phy 4.3 radio 3.6, 802.11a/b/g, FCC1A, address btw.: could you also give us the exact product name (on the minipci card)? It's a Senao 54g - but I will have to check for more detailed info tomorrow. 3.7 would crash on ath0 with AR5212 in hostap mode every six hours or so. snap here yet in this dmesg. there were two fixes for hostap mode and it works for me without problems in the driver. one issue got fixed on 2005/05/28 (ath.c 1.29). the problem was a hardware counter overflow after some traffic and an uncatched interrupt which indicated the overflow and required to clear the counter registers. the second problem was related to receive overruns in the rx descriptor chain, which had been fixed as well (ath.c 1.31 2005/07/19). I checked 3.7 and found the card to freeze every several hours. Then I loaded a early june (maybe late may) snapshot and it froze on ifconfig up. The main difference I could see was the gpio being supported in the snapshot, something that wsn't there in 3.7. Maybe I got caught in between two fixes. I haven't time in the next 10 days to play with it, but maybe Olivier can give some feedback in case he tries the latest snapshot? In case the problem remains and the card remains unemployed here I can send it to Germany to pursue a new career as developer assisting hardware? wq
Re: 3.8 beta requests
On 8/23/05, Theo de Raadt [EMAIL PROTECTED] wrote: These changes have been worked on for almost 3 years now. And they went in right after the tree unlocked after 3.7. Thanks for setting me straight. It only means that, at least for my systems, the transition has been pretty painless so far. Cheers, Rogier -- If you don't know where you're going, any road will get you there.
Re: Nagios: Premature end of script headers
At 02:37 PM 8/23/2005 -0300, Joco Salvatti wrote: Hi all, I installed and configured Nagios on my machine. The Nagios webpage can be retrieve normally, but something strange happens when I try to retrieve host detail: Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Actually doesn't have anything to do with OBSD, .. but you might check: 1) All libaries are installed in your chroot environment; 2) Nobody has ftp'd files with extra crs (took me a while to figure out that one); 3) The separate programs will run from a command line. In the case of 1 3, sometimes it's helpful to *test* the script chroot'd. Lee
/usr/share/pf/ suggestion
Would it be useful to add an example pf rule set for just a simple host? All of the examples assume a router. -- Will Backman - Network Administrator Coastal Enterprises, Inc. http://www.ceimaine.org
Re: startkde question
Dave Feustel wrote: Oh. Yes. It was Where does the xconsole get invoked when I start kde using startkde?. Because startkde is a script that will invoke startx which will by default (meaning if you don't have a .xinitrc in your homedir) use /etc/X11/xinit/xinitrc where xconsole is started from.
Re: Win XP VPN
As OpenVPN was mentioned before, I've wrote a HOWTO here: http://blog.innerewut.de/articles/2005/07/04/openvpn-2-0-on-openbsd It is very easy to configure and supports Unix, Win, and OS X. Jonathan -- Jonathan Weiss http://blog.innerewut.de
adding configure time flags to a port build?
I need to rebuild Amanda to help using it in a situation where soem of the clients are behind a firewall. To do this I need to pass a couple of arguments to configure. I've been suing the standard port build for Amanda on the OpenBSD machines. Can I somehow add thes flags to the ports build process for Amanda, as I build the port? -- U.S. Encouraged by Vietnam Vote - Officials Cite 83% Turnout Despite Vietcong Terror - New York Times 9/3/1967
Re: Fwd: Complete disk disaster
Please be more specific: That is bad advice because Thank you. On 8/23/05, Marco Peereboom [EMAIL PROTECTED] wrote: That is bad advice. On Tue, Aug 23, 2005 at 11:46:14AM +0200, Jernej Vodopivec wrote: forgot to cc: -- Forwarded message -- From: Jernej Vodopivec [EMAIL PROTECTED] Date: Aug 23, 2005 11:45 AM Subject: Re: Complete disk disaster To: Ramiro Aceves [EMAIL PROTECTED] On 8/23/05, Ramiro Aceves [EMAIL PROTECTED] wrote: ...Do you know of any disk test or utility program that can stress the disk to work hard until it fails? try badblocks - I don't know if it is ported on OpenBSD but you can find it on knoppix cd Jernej
db4 on macppc
Can anyone confirm whether the db4 port is working on -current on macppc at the moment? I was trying to install cyrus, but it's hanging on ctl_cyrusdb -r at startup. Simplifying things I've tested with /usr/local/share/examples/db4/ex_env.c which has also been hanging sometimes when it does 'dbenv-open'. I'm pretty new to gdb and haven't worked out how to trace into libraries yet so haven't found more about where it's called from (well, it's from __os_sleep but I'm not sure where that's called from). Same thing on i386 is working fine as far as I can determine. If anyone could point me in a suitable direction to start looking I'd appreciate it, but just knowing whether it works for anyone else would be a good start.. Here's what I did to get ex_env running: install db4 package, cd /usr/local/share/examples/db4 gcc -o /tmp/ex_env -I /usr/local/include/db4 -ldb -L /usr/local/lib/db4 ex_env.c mkdir /tmp/database /tmp/ex_env This should output 'Setup env' then 'Teardown env', on my problem box I just get 'Setup env' then have to ^C most of the time, but (just to confuse me) sometimes it runs correctly. I haven't had 'ctl_cyrusdb -r' run correctly though. Thanks in advance for any pointers... Stuart - this is running a recent snap on a new Mac Mini. Haven't used macppc before but can't think of anything I might have done wrong so far. OpenBSD 3.8-beta (GENERIC) #403: Thu Aug 18 19:14:19 MDT 2005 [EMAIL PROTECTED]:/usr/src/sys/arch/macppc/compile/GENERIC real mem = 536870912 (524288K) avail mem = 483835904 (472496K) using 1254 buffers containing 26841088 bytes of memory mainbus0 (root) cpu0 at mainbus0: 7447A (Revision 0x102): 1249 MHz etc. (more at http://vervain.spacehopper.org/~sthen/macmini.dmesg)
Re: network traffic monitoring - bandwidth problem
This application looks great but I can't still compile it. I tryed it on
OpenBSD 3.7 and 3.5 but without success. There is problem with libpng.
configure says that I have no libpng but I've compiled libpng 1.2.8.
configure: error: Bandwidthd requires but cannot libpng
config.log
--
configure:2858: gcc -o
onftest -g -O2 -I/usr/local/include -L/usr/local/lib c
onftest.c -lpng -liconv -lm -lresolv 5
/usr/local/lib/libpng.so.4.0: undefined reference to `deflate'
/usr/local/lib/libpng.so.4.0: undefined reference to `inflate'
/usr/local/lib/libpng.so.4.0: undefined reference to `inflateInit_'
/usr/local/lib/libpng.so.4.0: undefined reference to `crc32'
/usr/local/lib/libpng.so.4.0: undefined reference to `deflateInit2_'
/usr/local/lib/libpng.so.4.0: undefined reference to `inflateReset'
/usr/local/lib/libpng.so.4.0: undefined reference to `deflateReset'
/usr/local/lib/libpng.so.4.0: undefined reference to `inflateEnd'
/usr/local/lib/libpng.so.4.0: undefined reference to `deflateEnd'
Could you please help me?
MK
-lz.
doing this:
./configure CFLAGS=-lz
gets me (on my i386/3.7 GENERIC) past the error Miroslav has, but now
it's bailing with:
checking for gdImageCreate in -lgd... no
configure: error: Bandwidthd requires but cannot find libgd
Given that I have both p5-GD and gd-1.8.3 installed from ports for
other needs, I think I have all the requisite libs.
Now the pertinent part of my config.log:
snip
configure:2923: $? = 1
configure: failed program was:
#line 2901 configure
#include confdefs.h
/* Override any gcc2 internal prototype to avoid an error. */
#ifdef __cplusplus
extern C
#endif
/* We use char because int might match the return type of a gcc2
builtin and then its argument prototype would still apply. */
char gdImageCreate ();
int
main ()
{
gdImageCreate ();
;
return 0;
}
configure:2940: result: no
configure:2950: error: Bandwidthd requires but cannot find libgd
Lastly, even though this is really a bandwidthd issue and not an
OpenBSD issue, I was hoping another hint or two from misc@ and we'd be
off to the races with this app
Thanks much,
Kevin
--
http://www.ebiinc.com
EBI - employee background screening professionals
Corporate background checks, globally.
Re: Automatic setup of partitions
Here's a snippet of something I've been working on along the same lines -
this is /bin/csh syntax, and works on raid0 but should work on regular
partitions as well:
echo get raid size...
@ r_tot = `disklabel -p g raid0 | awk '/total bytes/ { print int($3) }'`
@ r_root = 1; @ r_tot -= $r_root
@ r_swap = 1; @ r_tot -= $r_swap
@ r_tmp = 1; @ r_tot -= $r_tmp
@ r_usr = 10; @ r_tot -= $r_usr
@ r_home = 4; @ r_tot -= $r_home
@ r_obj = 4; @ r_tot -= $r_obj
@ r_xobj = 4; @ r_tot -= $r_xobj
@ r_pobj = 20; @ r_tot -= $r_pobj
@ r_var = $r_tot
if ($r_var 0) then
echo 'not enough space on raid0 for all partitions'
exit 1
endif
echo create raid label partitions...
# NB: blank lines matter here
disklabel -E raid0 _EOF_
a a
${r_root}G
a b
${r_swap}G
a d
${r_tmp}G
a e
${r_usr}G
a f
${r_home}G
a g
${r_obj}G
a h
${r_xobj}G
a i
${r_pobj}G
a j
w
q
_EOF_
Re: adding configure time flags to a port build?
stan wrote: I need to rebuild Amanda to help using it in a situation where soem of the clients are behind a firewall. To do this I need to pass a couple of arguments to configure. I've been suing the standard port build for Amanda on the OpenBSD machines. Can I somehow add thes flags to the ports build process for Amanda, as I build the port? Look for CONFIGURE_ARGS in /usr/ports/misc/amanda/Makefile. /Alexander
Re: startkde question
On Tue, Aug 23, 2005 at 08:52:40PM +0200, Antoine Jacoutot wrote: Because startkde is a script that will invoke startx which will by default (meaning if you don't have a .xinitrc in your homedir) use /etc/X11/xinit/xinitrc where xconsole is started from. startkde does exec /usr/X11R6/bin/startx $0 if DISPLAY is unset or empty, i.e. it runs startx with it's own name as the client, and startx shouldn't run xinitrc but startkde in this case. Indeed after looking at startx (which is a script, too), it should just run xinit /usr/local/bin/startkde -- near the end, and xinit in turn should then use /usr/local/bin/startkde as the client program (and not ~/.xinitrc or even /etc/X11/xinit/xinitrc). However, this *only* works if the client (startkde, in this case) is passed with a absolute or relative pathname (see that case statement in startx). So, if startkde is explicitely invoked as /usr/local/bin/startkde (instead of just startkde), it should work. Ciao, Kili
Re: startkde question
Selon Dave Feustel [EMAIL PROTECTED]: My problem is that xconsole starts running with kde and I cannot figure out where from it is started. I've tried grepping for xconsole and get no hits in my home directory. Please try to read the answers people give you. It is started from /etc/X11/xinit/xinitrc
Re: isakmp vpn configuration
--- Quoting Daniel Eyholzer on 2005/08/17 at 15:58 +0200: I have tried to change Network and Netmask in the [default-route] section from 0.0.0.0 to the network and netmask of one of the vlan subnetworks, but it does not help. I can still connect to the other subnet if I define them in the client. Anyone knows how I can restrict access to only one of the vlan subnets? I don't know why those changes aren't working, however, have you tried: - setting a policy via isakmpd.policy that restricts 'remote_filter' - blocking traffic using pf .joel
Re: db4 on macppc
On Tue, Aug 23, 2005 at 07:54:56PM +0100, Stuart Henderson wrote: Simplifying things I've tested with /usr/local/share/examples/db4/ex_env.c which has also been hanging sometimes when it does 'dbenv-open'. Same problem here (with a four days old -current installation). I'm pretty new to gdb and haven't worked out how to trace into libraries yet so haven't found more about where it's called from (well, it's from __os_sleep but I'm not sure where that's called from). Rebuild libdb with debugging enabled: $ cd /usr/ports/databases/db/v4 $ make uninstall $ DEBUG=-g make install (and don't make clean until you're finished with debugging). Ciao, Kili ps: I'm just rebuilding libdb with debugging here.
Re: 3.8 beta requests
You've got to use your head, otherwise you'll stick your neck out and
say stupid things.
Of course not. HOW CAN IT? Get real! The hardware is STILL only
providing permissions at the page level!
Apparently the new malloc(3) implementation doesn't stop me from writing past
the end of buffer as long as I am inside the last page.
(Please forgive me beforehand if I am missing something too obvious)
consider the following program:
// We just want to see how far after end of allocated buffer we can go.
// Allocate a buffer, then try to read past it, see how far we can go before
// System notices.
// myhandler should tell us about this. If you don't trust it just disable and
// examine the core file created.
//
#include stdio.h
#include sys/types.h
#include sys/mman.h
#include signal.h
#define PAGE_SIZE 4096
char *s;
int i;
int size;
void myhandler(int sig)
{
printf(Caught Signal %d\n, sig);
printf(s=0x%x, size=%d, i=%d\n, s, size, i);
perror(last err condition);
exit(0);
}
main(int ac, char *av[])
{
if (ac != 2) {
printf(%s size\n, av[0]);
exit(1);
}
size = atoi(av[1]);
if (size 4096) {
printf (size should be larger than 4K.\n);
exit(1);
}
signal(SIGSEGV, myhandler);
s = (char *)malloc(size);
for (i = 0; i 2 * size - 1; i++)
s[i] = (char )i;
free(s);
}
and here is the execution (a very recent install as you can see):
#dmesg | head -6
OpenBSD 3.8-beta (GENERIC.MP) #277: Mon Aug 22 23:04:26 MDT 2005
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC.MP
cpu0: Intel Pentium III (GenuineIntel 686-class) 869 MHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,ME
real mem = 804823040 (785960K)
avail mem = 727044096 (710004K)
# gcc malloc-test.c
# ./a.out 4096
Caught Signal 11
s=0x8a19d000, size=4096, i=4096
last err condition: Undefined error: 0
# ./a.out 4097
Caught Signal 11
s=0x7f0eb000, size=4097, i=8192
last err condition: Undefined error: 0
#
Is this the way it is supposed to be?
cheers,
Masoud Sharbiani
On Mon, Aug 22, 2005 at 05:33:40PM -0600, Theo de Raadt wrote:
We are heading towards making the real 3.8 release soonish. I would
like to ask the community to do lots of testing over the next week if
they can.
This release will bring a lot of new ideas from us. One of them in
particular is somewhat risky. I think it is time to talk about that
one, and let people know what is ahead on our road.
Traditionally, Unix malloc(3) has always just extended the brk,
which means extending the traditional Unix process data segment to
allocate more memory. malloc(3) would simply extend the data segment,
and then calve off little pieces to requesting callers as needed. It
also remembered which pieces were which, so that free(3) could do it's
job.
The way this was always done in Unix has had a number of consequences,
some of which we wanted to get rid of. In particular, malloc free
have not been able to provide strong protection against overflows or
other corruption.
Our malloc implementation is a lot more resistant (than Linux) to
heap overflows in the malloc arena, but we wanted to improve things
even more.
Starting a few months ago, the following changes were made:
- We made the mmap(2) system call return random memory addresses. As well
the kernel ensures that two objects are not mapped next to each other;
in effect, this creates unallocated memory which we call a guard page.
- We have changed malloc(3) to use mmap(2) instead of extending the data
segment via brk()
- We also changed free(3) to return memory to the kernel, un-allocating
them out of the process.
- As before, objects smaller than a page are allocated within shared
pages that malloc(3) maintains. But their allocation is now somewhat
randomized as well.
- A number of other similar changes which are too dangerous for normal
software or cause too much of a slowdown are available as malloc options
as described in the manual page. These are very powerful for debugging
buggy applications.
Other results:
- When you free an object that is = 1 page in size, it is actually
returned to the system. Attempting to read or write to it after
you free is no longer acceptable. That memory is unmapped. You get
a SIGSEGV.
- For a decade and a bit, we have been fixing software for buffer overflows.
Now we are finding a lot of software that reads before the start of the
buffer, or reads too far off the end of the buffer. You get a SIGSEGV.
To some of you, this will sound like what the Electric Fence toolkit
used to be for. But these features are enabled by default. Electric
Fence was also very slow. It took nearly 3 years to write these
OpenBSD changes since
Re: 3.8 beta requests
Hello Theo,
Apparently the new malloc(3) implementation doesn't stop me from writing past
the end of buffer as long as I am inside the last page.
(Please forgive me beforehand if I am missing something too obvious)
consider the following program:
// We just want to see how far after end of allocated buffer we can go.
// Allocate a buffer, then try to read past it, see how far we can go before
// System notices.
// myhandler should tell us about this. If you don't trust it just disable and
// examine the core file created.
//
#include stdio.h
#include sys/types.h
#include sys/mman.h
#include signal.h
#define PAGE_SIZE 4096
char *s;
int i;
int size;
void myhandler(int sig)
{
printf(Caught Signal %d\n, sig);
printf(s=0x%x, size=%d, i=%d\n, s, size, i);
perror(last err condition);
exit(0);
}
main(int ac, char *av[])
{
if (ac != 2) {
printf(%s size\n, av[0]);
exit(1);
}
size = atoi(av[1]);
if (size 4096) {
printf (size should be larger than 4K.\n);
exit(1);
}
signal(SIGSEGV, myhandler);
s = (char *)malloc(size);
for (i = 0; i 2 * size - 1; i++)
s[i] = (char )i;
free(s);
}
and here is the execution (a very recent install as you can see):
#dmesg | head -6
OpenBSD 3.8-beta (GENERIC.MP) #277: Mon Aug 22 23:04:26 MDT 2005
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC.MP
cpu0: Intel Pentium III (GenuineIntel 686-class) 869 MHz
cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,ME
real mem = 804823040 (785960K)
avail mem = 727044096 (710004K)
# gcc malloc-test.c
# ./a.out 4096
Caught Signal 11
s=0x8a19d000, size=4096, i=4096
last err condition: Undefined error: 0
# ./a.out 4097
Caught Signal 11
s=0x7f0eb000, size=4097, i=8192
last err condition: Undefined error: 0
#
Is this the way it is supposed to be?
cheers,
Masoud Sharbiani
On Mon, Aug 22, 2005 at 05:33:40PM -0600, Theo de Raadt wrote:
We are heading towards making the real 3.8 release soonish. I would
like to ask the community to do lots of testing over the next week if
they can.
This release will bring a lot of new ideas from us. One of them in
particular is somewhat risky. I think it is time to talk about that
one, and let people know what is ahead on our road.
Traditionally, Unix malloc(3) has always just extended the brk,
which means extending the traditional Unix process data segment to
allocate more memory. malloc(3) would simply extend the data segment,
and then calve off little pieces to requesting callers as needed. It
also remembered which pieces were which, so that free(3) could do it's
job.
The way this was always done in Unix has had a number of consequences,
some of which we wanted to get rid of. In particular, malloc free
have not been able to provide strong protection against overflows or
other corruption.
Our malloc implementation is a lot more resistant (than Linux) to
heap overflows in the malloc arena, but we wanted to improve things
even more.
Starting a few months ago, the following changes were made:
- We made the mmap(2) system call return random memory addresses. As well
the kernel ensures that two objects are not mapped next to each other;
in effect, this creates unallocated memory which we call a guard page.
- We have changed malloc(3) to use mmap(2) instead of extending the data
segment via brk()
- We also changed free(3) to return memory to the kernel, un-allocating
them out of the process.
- As before, objects smaller than a page are allocated within shared
pages that malloc(3) maintains. But their allocation is now somewhat
randomized as well.
- A number of other similar changes which are too dangerous for normal
software or cause too much of a slowdown are available as malloc options
as described in the manual page. These are very powerful for debugging
buggy applications.
Other results:
- When you free an object that is = 1 page in size, it is actually
returned to the system. Attempting to read or write to it after
you free is no longer acceptable. That memory is unmapped. You get
a SIGSEGV.
- For a decade and a bit, we have been fixing software for buffer overflows.
Now we are finding a lot of software that reads before the start of the
buffer, or reads too far off the end of the buffer. You get a SIGSEGV.
To some of you, this will sound like what the Electric Fence toolkit
used to be for. But these features are enabled by default. Electric
Fence was also very slow. It took nearly 3 years to write these
OpenBSD changes since performance was a serious consideration. (Early
versions caused a nearly 50% slowdown).
Our changes have tremendous benefits, but until some bugs in external
packages are found and fixed, there are some risks as well. Some
software making incorrect assumptions will be running into these new
security technologies.
I
Re: /usr/share/pf/ suggestion
-Original Message- From: j knight [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 23, 2005 4:47 PM To: Will H. Backman Subject: Re: /usr/share/pf/ suggestion --- Quoting Will H. Backman on 2005/08/23 at 14:59 -0400: Would it be useful to add an example pf rule set for just a simple host? All of the examples assume a router. This would be more useful in the faq. Please send what you've written. :-) .joel # pf rules for a stand alone machine. #Change external interface to match yours ext_if=xl0 scrub in all block in all pass out keep state pass quick on lo all
Re: startkde question
On Tuesday 23 August 2005 14:58, Antoine Jacoutot wrote: Selon Dave Feustel [EMAIL PROTECTED]: My problem is that xconsole starts running with kde and I cannot figure out where from it is started. I've tried grepping for xconsole and get no hits in my home directory. Please try to read the answers people give you. It is started from /etc/X11/xinit/xinitrc OK. There is an xterm and a clock started from /etc/X11/xinit/xinitrc as well. Neither of those programs shows up on the kde screen where the xconsole is. Why not? But thanks for sticking with me. Dave -- Tired of having to defend against Malware? (You know: trojans, viruses, SPYWARE, ADWARE, KEYLOGGERS, rootkits, worms and popups) Then Switch to OpenBSD with a KDE desktop!!!
Re: Win XP VPN
hi, On 8/23/05, Steve Murdoch [EMAIL PROTECTED] wrote: I have tried to add some remote win xp machines into the mix using the howto http://openbsd.cz/~pruzicka/vpn.html without any joy. (the site isn't available to me at the moment). I've managed to connect Win2k and WinXP machines to OpenBSD 3.5 and 3.7 routers. IP connectivity only, e.g I wasn't able to log in to an Active Directory an the other side. *I think* part of this problem is, Active Directory does quite a bit with dynamic DNS, and I didn't want to have every DNS request via this IPSec Session. But to get back on topic, yes it's possible and works well with TCP/IP ;) the winxp in my test case is behind a nat router will this cause me grief ? this is possible. I guess thirdly, is poptop under openbsd recommended ? I tried it, and it works. I didn't try to integrate it into an Active Directory, but I see (technically) no hard reason why it shouldn't work. Any other thoughts or recommendations appreciated. be more detailed about what you are trying to do ;) --knitti
-current with ath and 802.11g
Hello, I'm having some issues connecting to 802.11g wireless networks with a somewhat recent snapshot. I've got a linksys WAP54G access point v2, running firmware release 2.08. With the access point completely open (ssid broadcast, no mac filters), OpenBSD will only connect to it in 802.11b mode. When I place the access point in 802.11g only mode or ifconfig my ath with mode 802.11g I get no network. After searching a bit I've seen others who have the same problem, but I didn't find a dmesg to find out on what hardware or release they were running. Issues that might be related is that I'm seeing a lot of HAL resets when I run kismet. In 3.7 release I didn't get 802.11b to work either, but that seems to have been worked out. Any clues on this? // nick Here's the ifconfig dmesg: ath0: flags=8863UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST mtu 1500 lladdr 00:0d:54:98:d9:70 groups: egress media: IEEE802.11 autoselect (DS11 mode 11b) status: active ieee80211: nwid whynot chan 11 bssid 00:0f:66:11:09:39 inet 192.168.240.3 netmask 0xfff8 broadcast 192.168.240.7 inet6 fe80::20d:54ff:fe98:d970%ath0 prefixlen 64 scopeid 0x5 OpenBSD 3.7-current (GENERIC) #0: Sat Aug 6 12:48:03 CEST 2005 [EMAIL PROTECTED]:/sys/arch/i386/compile/GENERIC cpu0: Intel Pentium III (GenuineIntel 686-class) 699 MHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX, FXSR,SSE real mem = 133709824 (130576K) avail mem = 115425280 (112720K) using 1657 buffers containing 6787072 bytes (6628K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+(00) BIOS, date 07/02/02, BIOS32 rev. 0 @ 0xffe90 apm0 at bios0: Power Management spec V1.2 apm0: battery life expectancy 100% apm0: AC on, battery charge high, charging, estimated 7:58 hours apm0: flags 30102 dobusy 0 doidle 1 pcibios0 at bios0: rev 2.1 @ 0xf/0x1 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfbc20/192 (10 entries) pcibios0: PCI Interrupt Router at 000:31:0 (Intel 82371 ISA and IDE rev 0x00) pcibios0: PCI bus #4 is the last bus bios0: ROM list: 0xc/0x1 cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 Intel 82815 Hub rev 0x02 ppb0 at pci0 dev 1 function 0 Intel 82815 AGP rev 0x02 pci1 at ppb0 bus 1 vga1 at pci1 dev 0 function 0 ATI Rage 128 Mobility MF rev 0x00 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) ppb1 at pci0 dev 30 function 0 Intel 82801BAM Hub-to-PCI rev 0x03 pci2 at ppb1 bus 2 esa0 at pci2 dev 3 function 0 ESS Maestro 3 rev 0x10: irq 5 ac97: codec id 0x83847609 (SigmaTel STAC9721/23) ac97: codec features 18 bit DAC, 18 bit ADC, SigmaTel 3D audio0 at esa0 cbb0 at pci2 dev 15 function 0 Texas Instruments PCI4451 CardBus rev 0x00: irq 10 cbb1 at pci2 dev 15 function 1 Texas Instruments PCI4451 CardBus rev 0x00: irq 10 Texas Instruments PCI4451 FireWire rev 0x00 at pci2 dev 15 function 2 not configured cardslot0 at cbb0 slot 0 flags 0 cardbus0 at cardslot0: bus 3 device 0 cacheline 0x8, lattimer 0x20 pcmcia0 at cardslot0 cardslot1 at cbb1 slot 1 flags 0 cardbus1 at cardslot1: bus 4 device 0 cacheline 0x8, lattimer 0x20 pcmcia1 at cardslot1 ichpcib0 at pci0 dev 31 function 0 Intel 82801BAM LPC rev 0x03 pciide0 at pci0 dev 31 function 1 Intel 82801BAM IDE rev 0x03: DMA, channel 0 wired to compatibility, channel 1 wired to compatibility wd0 at pciide0 channel 0 drive 0: IBM-DJSA-210 wd0: 16-sector PIO, LBA, 9590MB, 19640880 sectors atapiscsi0 at pciide0 channel 0 drive 1 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: TEAC, CD-224E, 3.7C SCSI0 5/cdrom removable wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 4 cd0(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 2 pciide0: channel 1 ignored (disabled) uhci0 at pci0 dev 31 function 2 Intel 82801BA USB rev 0x03: irq 10 usb0 at uhci0: USB revision 1.0 uhub0 at usb0 uhub0: Intel UHCI root hub, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered isa0 at ichpcib0 isadma0 at isa0 pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 pms0 at pckbc0 (aux slot) pckbc0: using irq 12 for aux slot wsmouse0 at pms0 mux 0 pcppi0 at isa0 port 0x61 midi0 at pcppi0: PC speaker spkr0 at pcppi0 sysbeep0 at pcppi0 npx0 at isa0 port 0xf0/16: using exception 16 pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 biomask efcd netmask efcd ttymask ffcf pctr: 686-class user-level performance counters enabled mtrr: Pentium Pro MTRR support ath0 at cardbus0 dev 0 function 0 3Com Corp., 3CRPAG175 Wireless LAN PC Card, : irq 10 ath0: AR5212 5.6 phy 4.1 rf5111 1.7 rf2111 2.3, WOR0W, address 00:0d:54:98:d9:70 uhidev0 at uhub0 port 1 configuration 1 interface 0 uhidev0: Logitech USB-PS/2 Optical Mouse, rev 2.00/13.00, addr 2, iclass 3/1 ums0 at uhidev0: 4 buttons and Z
Re: BSD PPPoA Hardware
On 16/08/2005, at 6:54 PM, J.C. Roberts wrote: Great info Simon, thank you. All the DSL modems I've seen here in the USA are ethernet based on the user side and as misfortune would have it, many providers *require* using their particular modem, so the user side of it is all that matters. It's all been consumer grade kit, even though a lot of it is in business use, none the less, I have not seen a DSL modem with ATM on the user side (probably because it would be pointless to make it that way). In Australia I am using a Netgear DG632 consumer grade ADSL MODEM/Router with PPPoA. The 'A' refers to the line side, not the ethernet side which runs into my OpenBSD firewall. MODEM mode with this unit seems to be a half bridge mode which actually works. I don't know if the use of PPPoA is common in Australia, but every ADSL MODEM/Router I have seen over here has had PPPoA as an option.
Re: startkde question
On Tuesday 23 August 2005 14:31, Matthias Kilian wrote: On Tue, Aug 23, 2005 at 08:52:40PM +0200, Antoine Jacoutot wrote: Because startkde is a script that will invoke startx which will by default (meaning if you don't have a .xinitrc in your homedir) use /etc/X11/xinit/xinitrc where xconsole is started from. startkde does exec /usr/X11R6/bin/startx $0 if DISPLAY is unset or empty, i.e. it runs startx with it's own name as the client, and startx shouldn't run xinitrc but startkde in this case. Indeed after looking at startx (which is a script, too), it should just run xinit /usr/local/bin/startkde -- near the end, and xinit in turn should then use /usr/local/bin/startkde as the client program (and not ~/.xinitrc or even /etc/X11/xinit/xinitrc). However, this *only* works if the client (startkde, in this case) is passed with a absolute or relative pathname (see that case statement in startx). So, if startkde is explicitely invoked as /usr/local/bin/startkde (instead of just startkde), it should work. Ciao, Kili This post is a keeper! :-) Thanks! Dave -- Tired of having to defend against Malware? (You know: trojans, viruses, SPYWARE, ADWARE, KEYLOGGERS, rootkits, worms and popups) Then Switch to OpenBSD with a KDE desktop!!!
Re: /usr/share/pf/ suggestion
-Original Message- From: Jason Crawford [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 23, 2005 5:25 PM To: Will H. Backman Cc: j knight; Misc OpenBSD Subject: Re: /usr/share/pf/ suggestion On 8/23/05, Will H. Backman [EMAIL PROTECTED] wrote: -Original Message- From: j knight [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 23, 2005 4:47 PM To: Will H. Backman Subject: Re: /usr/share/pf/ suggestion --- Quoting Will H. Backman on 2005/08/23 at 14:59 -0400: Would it be useful to add an example pf rule set for just a simple host? All of the examples assume a router. This would be more useful in the faq. Please send what you've written. :-) .joel # pf rules for a stand alone machine. #Change external interface to match yours ext_if=xl0 scrub in all block in all pass out keep state pass quick on lo all First off, it should be, set skip on lo0 (or lo, but by default there's only one lo interface anyways). Secondly, it seems pretty pointless to setup pf on a single host. Instead of worrying about the firewall, which takes up more memory and cpu and all that, just shut off services that you don't need and be done with it. If the attacker can hurt your OpenBSD machine, then your firewall is vulnerable as well, and it won't protect any applications that need open ports listening. Turning off services is always much better than turning on services (pf) if you need protection. And the way OpenBSD is setup by default, nothing is listening except a couple inetd services (which I always turn off), and sshd if you said y in install, that's it. Jason I agree in general, but then start adding the gnome or kde desktop or other applications and you never know what is listening.
Re: proper way to format/use floppies (i386)
Hi Steve, On 8/23/05, STeve Andre' wrote: I would avoid all this and use the 'mtools' package instead. It deals with msdos fat-12(?) floppies, and is tons easier to use. Then you can hand those floppies to others and they can read/write them. Using fat on the floppy is not an option. I need ffs. Also I don't complain that it is too complicated, but there are several working ways, and I am asking which one is the proper or preferred way. Thanks anyway, Michael
Re: /usr/share/pf/ suggestion
On 8/23/05, Will H. Backman [EMAIL PROTECTED] wrote: -Original Message- From: j knight [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 23, 2005 4:47 PM To: Will H. Backman Subject: Re: /usr/share/pf/ suggestion --- Quoting Will H. Backman on 2005/08/23 at 14:59 -0400: Would it be useful to add an example pf rule set for just a simple host? All of the examples assume a router. This would be more useful in the faq. Please send what you've written. :-) .joel # pf rules for a stand alone machine. #Change external interface to match yours ext_if=xl0 scrub in all block in all pass out keep state pass quick on lo all First off, it should be, set skip on lo0 (or lo, but by default there's only one lo interface anyways). Secondly, it seems pretty pointless to setup pf on a single host. Instead of worrying about the firewall, which takes up more memory and cpu and all that, just shut off services that you don't need and be done with it. If the attacker can hurt your OpenBSD machine, then your firewall is vulnerable as well, and it won't protect any applications that need open ports listening. Turning off services is always much better than turning on services (pf) if you need protection. And the way OpenBSD is setup by default, nothing is listening except a couple inetd services (which I always turn off), and sshd if you said y in install, that's it. Jason
Re: Laptop met tekortkoming
This is an English mailinglist, so please don't speak Dutch. If you'de like to speak Dutch, mail to [EMAIL PROTECTED] . And by the way, why should this be OpenBSD related? Jasper dutch Stuur het maar naar [EMAIL PROTECTED] in het Engels, daar hoort het thuis. Als het over OpenBSD gaat tenminste... /dutch On Tue, 23 Aug 2005 21:00:43 +0200 Ton de Zwart [EMAIL PROTECTED] wrote: Mijn pas 3 maanden oude laptop is van het merk Cybermaxx (medion) type MD95264 Gekocht bijTrekpleisterof was het Kruidvat, iin van die twee in elk geval. Deze laptop heeft iin grote tekortkoming wat ik niet wist toen ik 'm aanschafte. Je kunt n.m.l. het toughpad niet uitschakelen. Normaal gebruik ik een USB muisje van Microsoft, maar het toughpad is tegelijkertijd actief. Dat is uitermate lastig. Als je een tekst aan het tikken bent, raakt de muis van je hand om de haveklap het toughpad en schiet een gedeelte van je tekst ergens anders tussen, kortom je tekst is een puinhoop. Er is geen enkele mogelijkheid, ook niet softwarematig om het lastige toughpad uit te zetten. Uitschakelen in apparaatbeheer helpt niet, bij de volgende Windowsstart vind hij nieuwe hardware en zet Windows het toughpad er weer in. Voor de rest is het een prima laptop al zijn de twee bijgeleverde accu's wel erg gauw leeg, een uurtje hooguit. Groeten, Ton de Zwart [EMAIL PROTECTED] -- Security is decided by quality -- Theo de Raadt
Re: /usr/share/pf/ suggestion
Secondly, it seems pretty pointless to setup pf on a single host. That is the most ridiculous thing I've heard all day. Lots of people run servers and must block them, on the same machine. Probably every single one of us. Instead of worrying about the firewall, which takes up more memory and cpu and all that, just shut off services that you don't need and be done with it. If the attacker can hurt your OpenBSD machine, then your firewall is vulnerable as well, and it won't protect any applications that need open ports listening. Turning off services is always much better than turning on services (pf) if you need protection. And the way OpenBSD is setup by default, nothing is listening except a couple inetd services (which I always turn off), and sshd if you said y in install, that's it. Anyone who says I only need to block packets in my firewall has got it all wrong.
Re: /usr/share/pf/ suggestion
--On 23 August 2005 17:25 -0400, Jason Crawford wrote: Secondly, it seems pretty pointless to setup pf on a single host. It has it's uses - spamd, for one...
Re: Complete disk disaster
Josh Grosse wrote: On Tue, Aug 23, 2005 at 11:29:18AM +0200, Ramiro Aceves wrote: ... Do you know of any disk test or utility program that can stress the disk to work hard until it fails? Oh, thanks, but I tried to do it a month ago from my Linux box and this is an old disk that does not have the SMART thing. :-( Thank you very much. Ramiro. Smartmontools is available as an OBSD package. From the port readme: -- smartmontools-5.33 -- control and monitor storage systems using SMART The smartmontools package contains two utility programs (smartctl and smartd) to control and monitor storage systems using the Self-Monitoring, Analysis and Reporting Technology System (SMART) built into most modern ATA and SCSI hard disks. In many cases, these utilities will provide advanced warning of disk degradation and failure. See http://smartmontools.sourceforge.net/ for details.
Re: Fwd: Complete disk disaster
Jernej Vodopivec wrote: forgot to cc: -- Forwarded message -- From: Jernej Vodopivec [EMAIL PROTECTED] Date: Aug 23, 2005 11:45 AM Subject: Re: Complete disk disaster To: Ramiro Aceves [EMAIL PROTECTED] On 8/23/05, Ramiro Aceves [EMAIL PROTECTED] wrote: ...Do you know of any disk test or utility program that can stress the disk to work hard until it fails? try badblocks - I don't know if it is ported on OpenBSD but you can find it on knoppix cd Jernej Hello Jernej I have just ran the badblocks utility from my Debian GNU/Linux on the master disk. Before, I made a copy of the OpenBSD disk just in case someone wants info. I have done several write-read test passes with random bytes. Each pass takes some time. At the moment it did not find any bad block. But as with every test package, it does not imply that the disk is ok. :-( I was unlucky and for some reason the disk failed and corrupted data. I do not trust on this disk anymore. I am going to have a full night disk testing with badblocks just to see what happens. Tomorrow I will install OpenBSD again and start stressing the disk to see. Many thanks to all. Ramiro.
Re: db4 on macppc
--On 23 August 2005 21:48 +0200, Matthias Kilian wrote:
Rebuild libdb with debugging enabled:
$ cd /usr/ports/databases/db/v4
$ make uninstall
$ DEBUG=-g make install
Thanks, that's helpful.
# gdb /tmp/ex_env
GNU gdb 6.3
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and
you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type show copying to see the conditions.
There is absolutely no warranty for GDB. Type show warranty for
details.
This GDB was configured as powerpc-unknown-openbsd3.8...
(gdb) break __db_tas_mutex_lock
Function __db_tas_mutex_lock not defined.
Make breakpoint pending on future shared library load? (y or [n]) y
Breakpoint 1 (__db_tas_mutex_lock) pending.
(gdb) r
Starting program: /tmp/ex_env
Breakpoint 2 at 0x262e9b30: file ../mutex/mut_tas.c, line 99.
Pending breakpoint __db_tas_mutex_lock resolved
Setup env
Breakpoint 2, __db_tas_mutex_lock (dbenv=0x2d57b000, mutexp=0x27f92000)
at ../mutex/mut_tas.c:99
99 if (F_ISSET(dbenv, DB_ENV_NOLOCKING) || F_ISSET(mutexp,
MUTEX_IGNORE))
(gdb) s
108 max_ms = F_ISSET(mutexp, MUTEX_LOGICAL_LOCK) ? 10 : 25;
(gdb)
107 ms = 1;
(gdb)
108 max_ms = F_ISSET(mutexp, MUTEX_LOGICAL_LOCK) ? 10 : 25;
(gdb)
111 for (nspins = dbenv-tas_spins; nspins 0; --nspins) {
(gdb)
585 mutex.h: No such file or directory.
in mutex.h
(gdb)
582 in mutex.h
(gdb)
111 for (nspins = dbenv-tas_spins; nspins 0; --nspins) {
(gdb)
169 __os_yield(NULL, ms * USEC_PER_MS);
(gdb)
170 if ((ms = 1) max_ms)
(gdb)
169 __os_yield(NULL, ms * USEC_PER_MS);
(gdb)
__os_yield (dbenv=0x27f92000, usecs=1000) at ../os/os_spin.c:107
107 if (DB_GLOBAL(j_yield) != NULL DB_GLOBAL(j_yield)()
== 0)
(gdb)
106 {
(gdb)
107 if (DB_GLOBAL(j_yield) != NULL DB_GLOBAL(j_yield)()
== 0)
(gdb)
112 (void)__os_sleep(dbenv, 0, usecs);
(gdb)
__os_sleep (dbenv=0x0, secs=0, usecs=1000) at ../os/os_sleep.c:59
59 for (; usecs = 100; usecs -= 100)
and again...etc...
/usr/ports/databases/db/v4/w-db-4.2.52p2/db-4.2.52/dbinc/mutex.h line
585 is PPC assembly code, it's the asm volatile line in this -
static inline int
MUTEX_SET(int *tsl) {
int __r;
int __tmp = (int)tsl;
asm volatile (
0: \n\t
lwarx %0,0,%2 \n\t
cmpwi %0,0\n\t
bne-1f \n\t
stwcx. %2,0,%2 \n\t
isync \n\t
beq+2f \n\t
b 0b \n\t
1: \n\t
li %1, 0 \n\t
2: \n\t
: =r (__r), =r (tsl)
: r (__tmp)
: cr0, memory);
return (int)tsl;
}
I've done enough learning for today (I started by sprinkling printf
through the code which annoyed me sufficiently to make me learn gdb
basics) so I'll leave it for tonight, but thought I'd post what I've
found so far in case it helps anyone else before I look at it again.
carp on vlan's
Hello - I have vlan0 mapped on to fxp0 I have vlan1 mapped on to fxp0 as well. I have carp0 mapped on to vlan0 I have carp1 mapped on to vlan1 I have carp2 mapped on to fxp1 (internal) If I unplug the cable on fxp1, everything works. If I unplug the cable on fxp0, the second box changes to MASTER, but the first box stays MASTER too and things get screwed up. Is it possible to have fxp0 flag vlan0, then vlan0 flag carp0 that the link is down? Or make ifconfig carp0 carpdev vlan0 monitordev fxp0 so that it sends traffic out vlan0, but watches fxp0 for changes? - David
