Re: Create a bootable usb key?
Stuart Henderson s...@spacehopper.org a icrit : On 2009-01-10, Guillaume Thouvenin guillaume.thouve...@polymtl.ca wrote: Now next step is to have wired network working and so add support to my Attansic Technology L1E. This chip is not yet supported in OpenBSD. N.B. it is not the same as either Attansic L1 or L2. Yes right. I will have a look how driver are implemented in OpenBSD and I will try to add the support of Attansic L1E. Do you know if someone is working on it? Regards, Guillaume
Postprocessing pf label data
Hi all! Now that pfctl -sl gives me a neat lot of detailed traffic stats, I'm wondering: Is there some tool around that can handle this data right out of the box, similar to what Cacti does for interface statistics? -martin -- Martin Schmitt / Schmitt Systemberatung / www.scsy.de -- http://www.pug.org/index.php/Benutzer:Martin --
xterm and home-dir with automounter
Hello, for flexibility I have configured my computer (OpenBSD 4.4; macppc) with the home directory being auto mounted. that is /etc/amd/amd.home reads: # * type:=link;fs:=/usr/home;sublink:=${key} This works as desired. The programs use /home/username as they should, the real data locates in /usr/home. Of course, useradd becomes a two step process. But, the only program that doesn't play nicely is xterm. Either from within an xsession or when login in remotely via ssh the initial path is always: /usr/home/username despite $PATH being /home/username That is, xterm initially reads: ibook:/usr/home/rudi$ instead of just:ibook:~$ Is this a configuration issue or a bug/feature of xterm? Rudi
Re: newbie - migrating - home drive, UIDs, and etc/group, and such
HiHi Vadim! You can specify exact UIDs for each user you create with adduser. Problems start to arrive only when existing (old) UIDs or GIDs interfere with (new) system ones. And even in this case something like this will do the job: set -e cd /home for U in alex joe paul; do I thought about doing something like that and IFF this'd been a major enterprise situation I certainly would have. Turns out that I threw away a few old test/junk accounts and only about 30 do do manually. Adduser took about 30 seconds each just running down a list of names, about 10 mins to create the chown script and 10 mins to run that. The real advantage of manual adduser was that I wanted to stick with *absolute* 'uname/user name/user account/whatever-detail-compatibility' with anything the formal process might be doing along the way, rather than kludge/fudge/massage the ownerships, passwd/group files. Being unfamiliar with OBSD I thought the -risk- of missing something along the way or otherwise screwing something up was pretty high. TY and have a :) day! Jim -- jim barchuk j...@jbarchuk.com
Re: xterm and home-dir with automounter
On Sunday 11 January 2009 12:44:31 Rudi Ludwig wrote: i ... despite $PATH being /home/username That is, xterm initially reads:ibook:/usr/home/rudi$ ..Argh, of course despite $HOME being ... you might have guessed. Rudi
Clean PlusĀ® International Wishes You a Happy Holiday OTC:FLKI
o;? JOY, PEACE, HAPPINESS: These are the feelings we wish you for this very special season. And may all your wishes come true MERRY CHRISTMAS AND HAPPY NEW YEAR 2009 Clean Plus. International Team www.cleanplus.com www.cleanplus.comwww.cleanplus.com FALKEN EUROPE A.S. Clean Plus. Product Group European Headquarters Holbergs Gate 19, 3rd Floor 0166 Oslo Norway Tel : +47 2298 2080 Fax : +47 2298 2089 [demime 1.01d removed an attachment of type image/jpeg which had a name of xmas wishes 2008.jpg]
Re: i386 kernel panic with 1/9/09 snapshot
This appears to be fixed in -current/the latest snapshot. Can you try a version = the following (which fixed exactly the same problem on my laptop): OpenBSD 4.4-current (GENERIC.MP) #32: Fri Jan 9 10:34:10 MST 2009 t...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP cpu0: Intel(R) Atom(TM) CPU N270 @ 1.60GHz (GenuineIntel 686-class) 1.60 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,EST,TM2,xTPR real mem = 1060163584 (1011MB) avail mem = 1016823808 (969MB) mainbus0 at root Thanks Tom Barry Commander 9-Jan-09 14:59 Hi This is the first problem I've had with OpenBSD, I think I've attached all relevant information but if i've neglected anything please let me know. I'm getting the following panic at boot time with the latest snapshot dated 1/9/09 uvm_fault(0xd08084a0, 0x12e3e000, 0, 3) - e kernel: page fault trap, code=0 Stopped at apic_vectorset+0x50:movl%esi,apic_maxlevel(,%eax,4) apic_vectorset(d128fb00,0,ff,0,0) at apic_vectorset+0x50 ioapic_enable(d08084a0,0,d0961fa0,d034bc99,d08bd540) at ioapic_enable+0x8f cpu_configure(d08bd540,1,3,0,2) at cpu_configure+0x42 main(0,0,0,0,0) at main+0x399 ddb trace apic_vectorset(d128fb00,0,ff,0,0) at apic_vectorset+0x50 ioapic_enable(d08084a0,0,d0961fa0,d034bc99,d08bd540) at ioapic_enable+0x8f cpu_configure(d08bd540,1,3,0,2) at cpu_configure+0x42 main(0,0,0,0,0) at main+0x399
Re: Libretto 70CT crash on cpu_switch
On Sun, Jan 11, 2009 at 12:44 PM, Stuart Henderson s...@spacehopper.org wrote: please try a newer snap, if it still fails and nobody else picks it up from your list post, use sendbug to open a PR with this information (some developers don't read misc@) cheers, Stuart Hi Misc, Following Stuart's advice I've just upgraded my Libretto 70CT to the latest snapshot but the kernel is still giving me the following error: kernel: integer divide fault trap, code=0 Following is the dmesg and the output of ps and trace. I'll submit a PR tomorrow if the combined genius of misc@ cannot suggest an alternative approach to solving this issue. Thanks Fred Script started on Sun Jan 11 23:59:45 2009 x41:fred ~ cu -l /dev/cuaU0 -s9600 can't open log file /var/log/aculog. Connected OpenBSD/i386 BOOT 3.02 boot booting hd0a:/bsd: /-\|/6018908-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/+1058856 [52+334096-\|/-\|/-\|/-\|/-\|/+316668-\|/-\|/-\|/-\|/-\|/]=0x75ef38 entry point at 0x200120 [ using 651188 bytes of bsd ELF symbol table ] Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2009 OpenBSD. All rights reserved. http://www.OpenBSD.org OpenBSD 4.4-current (GENERIC) #1648: Fri Jan 9 10:26:32 MST 2009 t...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel Pentium/MMX (GenuineIntel 586-class) 121 MHz cpu0: FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,MMX cpu0: F00F bug workaround installed real mem = 16478208 (15MB) avail mem = 5857280 (5MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 11/11/97 apm0 at bios0: Power Management spec V1.2 apm0: battery life expectancy 51% apm0: AC on, battery charge high, charging pcibios at bios0 function 0x1a not configured bios0: ROM list: 0xe4000/0xc000 cpu0 at mainbus0: (uniprocessor) isa0 at mainbus0 isadma0 at isa0 com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo com0: console 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 pms0 at pckbc0 (aux slot) pckbc0: using irq 12 for aux slot wsmouse0 at pms0 mux 0 vga0 at isa0 port 0x3b0/48 iomem 0xa/131072 wsdisplay0 at vga0 mux 1: console (80x25, vt100 emulation), using wskbd0 wsdisplay0: screen 1-5 added (80x25, vt100 emulation) wdc0 at isa0 port 0x1f0/8 irq 14 wd0 at wdc0 channel 0 drive 0: IBM-DDLA-21620 wd0: 16-sector PIO, LBA, 1551MB, 3177216 sectors wd0(wdc0:0:0): using BIOS timings sb0 at isa0 port 0x220/24 irq 5 drq 1: dsp v3.01 midi0 at sb0: SB MIDI UART audio0 at sb0 opl0 at sb0: model OPL3 midi1 at opl0: SB Yamaha OPL3 wss0 at isa0 port 0x530/8 irq 10 drq 0: CS4231 or AD1845 (vers 4) audio1 at wss0 pcppi0 at isa0 port 0x61 midi2 at pcppi0: PC speaker spkr0 at pcppi0 lpt0 at isa0 port 0x378/4 irq 7 npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 pcic0 at isa0 port 0x3e0/2 iomem 0xd/65536 pcic0 controller 0: Intel 82365SL rev 1 has sockets A and B pcmcia0 at pcic0 controller 0 socket 0 xe0 at pcmcia0 function 0 Xircom, CreditCard 10Base-T, PS-CE2-10 port 0x340/16, irq 9: address 00:80:c7:42:37:d9 pcmcia1 at pcic0 controller 0 socket 1 pcic0: irq 11, polling enabled biomask e145 netmask e345 ttymask fbdf softraid0 at root kernel: integer divide fault trap, code=0 Stopped at cpu_switchto+0x90: popl%ebx ddb ps PID PPID PGRPUID S FLAGS WAIT COMMAND 8 0 0 0 20x100200pfpurge 7 0 0 0 20x100200pcic0,0,1 6 0 0 0 20x100200pcic0,0,0 5 0 0 0 20x100200apm0 4 0 0 0 20x100200syswq 3 0 0 0 20x100200idle0 2 0 0 0 20x100200kmthread *1 0 0 0 7 0swapper 0 -1 0 0 3 0x80200 wdccmdswapper ddb trace cpu_switchto(d07a1194,d0b22000,d0961f18,d036048d,d0b22000) at cpu_switchto+0x90 cfdata(d0b22000,d0b22000,0,d0961f20,100) at cfdata+0x41d0 config_attach(0,d0799020,0,0,d07a37f8) at config_attach+0xfd config_rootfound(d06e4a57,0,d0961fa0,d034bd85,2) at config_rootfound+0x27 main(0,0,0,0,0) at main+0x4af ddb boot power off Symbol not found ddb boot poweroff Attempting to power down... ~ [EOT] x41:fred ~ exit Script done on Mon Jan 12 00:02:41 2009
Re: i386 kernel panic with 1/9/09 snapshot
On Sun, Jan 11, 2009 at 1:40 PM, Tom Cosgrove tom.cosgr...@arches-consulting.com wrote: This appears to be fixed in -current/the latest snapshot. Can you try a version = the following (which fixed exactly the same problem on my laptop): OpenBSD 4.4-current (GENERIC.MP) #32: Fri Jan 9 10:34:10 MST 2009 t...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP cpu0: Intel(R) Atom(TM) CPU N270 @ 1.60GHz (GenuineIntel 686-class) 1.60 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,EST,TM2,xTPR real mem = 1060163584 (1011MB) avail mem = 1016823808 (969MB) mainbus0 at root Thanks Tom Barry Commander 9-Jan-09 14:59 Hi This is the first problem I've had with OpenBSD, I think I've attached all relevant information but if i've neglected anything please let me know. I'm getting the following panic at boot time with the latest snapshot dated 1/9/09 uvm_fault(0xd08084a0, 0x12e3e000, 0, 3) - e kernel: page fault trap, code=0 Stopped at apic_vectorset+0x50:movl%esi,apic_maxlevel(,%eax,4) apic_vectorset(d128fb00,0,ff,0,0) at apic_vectorset+0x50 ioapic_enable(d08084a0,0,d0961fa0,d034bc99,d08bd540) at ioapic_enable+0x8f cpu_configure(d08bd540,1,3,0,2) at cpu_configure+0x42 main(0,0,0,0,0) at main+0x399 ddb trace apic_vectorset(d128fb00,0,ff,0,0) at apic_vectorset+0x50 ioapic_enable(d08084a0,0,d0961fa0,d034bc99,d08bd540) at ioapic_enable+0x8f cpu_configure(d08bd540,1,3,0,2) at cpu_configure+0x42 main(0,0,0,0,0) at main+0x399 Greetings, The issue was fixed, at least for me it was. I'm still having issues with my re(4) nic causing a panic, but I need to produce the error again (which I can), and use sendbug(1), which I was correctly chastised for not using... Just have to read up on how to send a proper bug report... :) regards, Bryan
Re: xterm and home-dir with automounter
On Sun, Jan 11, 2009 at 05:15:33PM +0100, Rudi Ludwig wrote: On Sunday 11 January 2009 12:44:31 Rudi Ludwig wrote: i ... despite $PATH being /home/username That is, xterm initially reads: ibook:/usr/home/rudi$ ..Argh, of course despite $HOME being ... you might have guessed. I don't know anything of automounter, but if /home/username is provided as a symlink to /usr/home/username, then that behaviour is expected: entering a symlinked directory changes the path to the expanded form of the symlink. Probably, if you try: cd /home/rudi ; /bin/pwd You get the same path. Ariane