Re: OpenBSD 5.1 i386- ports vs packages
I think the remaining difference that's an advantage of ports is that you can configure them differently. At the outermost level you can set a flavor to enable/disable some feature, at a lower level you can modify the makefile, still lower you can get in there and edit the source. Back when you used to choose a machine type (i386,i486,i596, etc.) in the kernel configuration I used to think building from ports got better optimization for your cpu type, assuming you built your kernel first. Packages are smaller to download, at least usually. But I'll still keep using ports just because I like having the code to study. Alan On Sat, 5 May 2012, Dimitry T wrote: After a long reading I am still confused. On OpenBSD FAQ recommend to use packages, most users speak the same, but some speak that it is safer to compile programs from ports and then programs have better performance. Did I get the better performance of the program on my hardware if i compile that program on my hardware from ports? I try to compare md5 of package compiled from ports with package downloaded from package server, and values bbdo not match. Surely I wrong somewhere, but I would like someone to explain me packages vs ports.
Re: OpenBSD 5.1 i386- ports vs packages
On 6 May 2012 01:15, Dimitry T wrote: > After a long reading I am still confused. On OpenBSD FAQ recommend to use packages, most users speak the same, but some speak that it is safer to compile programs from ports and then programs have better performance. Did I get the better performance of the program on my hardware if i compile that program on my hardware from ports? I try to compare md5 of package compiled from ports with package downloaded from package server, and values b b do not match. Surely I wrong somewhere, but I would like someone to explain me packages vs ports. If you wanted to get better performance, then you would have to change something for your compile, so that it's different from what the creator of the corresponding package did. In other words, you'd have to fiddle with various knobs. Particularly on modern hardware, the performance gain you might achieve by doing this is likely going to be slight and probably unnoticeable if there even is any gain at all. However, by fiddling with all and sundry knobs and parameters, and leaving out various stuff, you'll stand an excellent chance of subtly or not so subtly breaking stuff and @misc generally loves it when people who have shot themselves in the foot by doing something unnecessary and ill advised come asking for help. Basically and I'm not sure if it was Nick who first said it in the FAQ somewhere basically, if you break things, you get to keep all the pieces. I seem to remember seeing this mentioned on @misc a real long time ago: http://funroll-loops.info/ And I believe this is relevant as well: http://www.youtube.com/watch?v=xCIF6JF1O5U The OpenBSD packages. Pre-tuned by Canadian engineers. As for security, since the Openbsd.org packages and ports both come from the same source, there's no security advantage of ports over packages unless you don't trust OpenBSD.org and actually read all of the source code you compile (and, by the way, do the same for your whole compiler toolchain). There are all kinds of reasons why the hashes of your self-compiled ports and pre-made packaged might not match. In particular, your compiler toolchain might slightly differ from what the package maintainer used. Even using an identical toolchain on different hardware could in some cases produce different results. With larger and more complex compiles, I would expect it to be relatively rare that the actual hashes will end up matching. For learning about the process, fiddling and compiling and hacking away with mad abandon can be great. But for when you're just interested in running a quality end product? Heck, no. regards, --ropers
Re: OpenBSD 5.1 i386- ports vs packages
On Sat, May 05, 2012 at 11:15:13PM +, Dimitry T wrote: > After a long reading I am still confused. On OpenBSD FAQ recommend to > use packages, most users speak the same, but some speak that it is > safer to compile programs from ports and then programs have better > performance. It is not more safer and the programs don't have better performance. Please, ignore the users misinformed. > Did I get the better performance of the program on my > hardware if i compile that program on my hardware from ports? I try to > compare md5 of package compiled from ports with package downloaded > from package server, and values bbdo not match. Surely I wrong > somewhere, but I would like someone to explain me packages vs ports. The hash is different because the files are different but the *content* is the same. -- Juan Francisco Cantero Hurtado http://juanfra.info
Problems with Dell ALPS touchpad on -current
Hi misc@, I have a problem with an ALPS touchpad on my Dell Latitude E5420: Moving the cursor is really slow and scrolling does not work. This problem still exists with the latest -current snapshot (amd64). Reading http://www.openbsd.org/plus.html, I saw that some support for Dell ALPS touchpads was added, but it seems that my specific model was left out. Grepping for `mouse' in /var/log/Xorg.0.log results in: $ grep mouse /var/log/Xorg.0.log [515289.032] (==) intel(0): Silken mouse disabled [515293.915] (II) config/wscons: checking input device /dev/wsmouse [515293.937] (II) Using input driver 'ws' for '/dev/wsmouse' [515293.937] (**) /dev/wsmouse: always reports core events [515293.937] (II) ws: /dev/wsmouse: debuglevel 0 [515293.937] (**) Option "Device" "/dev/wsmouse" [515293.937] (**) ws: /dev/wsmouse: ZAxisMapping: buttons 4 and 5 [515293.937] (**) ws: /dev/wsmouse: WAxisMapping: buttons 6 and 7 [515293.937] (**) ws: /dev/wsmouse: associated screen: 0 [515296.107] (II) ws: /dev/wsmouse: minimum x position: 0 [515296.107] (II) ws: /dev/wsmouse: maximum x position: 1599 [515296.107] (II) ws: /dev/wsmouse: minimum y position: 0 [515296.107] (II) ws: /dev/wsmouse: maximum y position: 899 [515296.107] (==) ws: /dev/wsmouse: Buttons: 7 [515296.125] (**) ws: /dev/wsmouse: YAxisMapping: buttons 4 and 5 [515296.125] (II) XINPUT: Adding extended input device "/dev/wsmouse" (type: MOUSE, id 7) [515298.285] (**) /dev/wsmouse: (accel) keeping acceleration scheme 1 [515298.285] (**) /dev/wsmouse: (accel) acceleration profile 0 [515298.285] (**) /dev/wsmouse: (accel) acceleration factor: 2.000 [515298.285] (**) /dev/wsmouse: (accel) acceleration threshold: 4 dmesg says: $ dmesg | grep pms pms0 at pckbc0 (aux slot) wsmouse0 at pms0 mux 0 The same problem existed on Linux up to kernel 3.2, where the touchpad was recognized as a ps/2 device. This was fixed with version 3.3. On Arch Linux, some patches could be applied with this package, just in case that this could be of help: http://aur.archlinux.org/packages.php?ID=52538. I am not sure what else I could supply to solve this problem, so if I forgot something important, please tell me :) For now, I append the full Xorg.0.log and dmesg. Best regards, Nils dmesg: OpenBSD 5.1-current (GENERIC.MP) #290: Thu Apr 26 01:27:14 MDT 2012 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP RTC BIOS diagnostic error 3f real mem = 8481353728 (8088MB) avail mem = 8233230336 (7851MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xf20f0 (80 entries) bios0: vendor Dell Inc. version "A03" date 09/19/2011 bios0: Dell Inc. Latitude E5420 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC TCPA SSDT ASF! MCFG HPET BOOT SSDT SSDT DMAR acpi0: wakeup devices UAR1(S3) HDEF(S4) PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP04(S4) PXSX(S4) RP05(S4) PXSX(S4) RP06(S4) PXSX(S4) RP07(S4) PXSX(S4) RP08(S4) PEG0(S4) PEGP(S4) PEG1(S4) GLAN(S4) PEG2(S4) PEG3(S4) PXSX(S4) RP03(S4) EHC2(S1) EHCI(S1) LID_(S3) PBTN(S3) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz, 2494.71 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,PCLMUL,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,POPCNT,AES,XSAVE,AVX,NXE,LONG,LAHF cpu0: 256KB 64b/line 8-way L2 cache cpu0: apic clock running at 99MHz cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz, 2494.33 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,PCLMUL,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,POPCNT,AES,XSAVE,AVX,NXE,LONG,LAHF cpu1: 256KB 64b/line 8-way L2 cache cpu2 at mainbus0: apid 1 (application processor) cpu2: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz, 2494.33 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,PCLMUL,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,POPCNT,AES,XSAVE,AVX,NXE,LONG,LAHF cpu2: 256KB 64b/line 8-way L2 cache cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz, 2494.33 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,PCLMUL,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,POPCNT,AES,XSAVE,AVX,NXE,LONG,LAHF cpu3: 256KB 64b/line 8-way L2 cache ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (P0P1) acpiprt2 at acpi0: bus 1 (RP01) acpiprt3 at acpi0: bus 2 (RP02) acpiprt4
OpenBSD 5.1 i386- ports vs packages
After a long reading I am still confused. On OpenBSD FAQ recommend to use packages, most users speak the same, but some speak that it is safer to compile programs from ports and then programs have better performance. Did I get the better performance of the program on my hardware if i compile that program on my hardware from ports? I try to compare md5 of package compiled from ports with package downloaded from package server, and values bbdo not match. Surely I wrong somewhere, but I would like someone to explain me packages vs ports.
Re: suspend ok, wake up not so much (on acer aspire one D270)
On 2012-05-04, frantisek holop wrote: > hmm, on Fri, May 04, 2012 at 08:30:43PM +0100, Laurence Rochfort said that >> I have the same experience with a Toshiba R840 with Intel GT2+ Sandy >> Bridge graphics. > > this one has an "Intel GMA 3600". i am not sure thats part of the > sandy family, i dont know. no, those are the proprietary PowerVR-based series, quite different to the usual Intel gpus.
Re: acer aspire one D270
On 05/05/12 10:40 AM, Weldon Goree wrote: On Fri, 2012-05-04 at 19:26 -0400, Ted Unangst wrote: The only google hit for "netbsd ignphy" is... your email. ??? My mistake -- I was seeing igphy(4), which is for the ethernet, not the wireless. At any rate, the iwn(4) driver does not need Intel's firmware, and seems to work pretty well. It *does* need the firmware. The firmware has been installed on your system. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
Re: older firmwares referenced in manpages
On 2012-05-05, Jan Stary wrote: > Certain device's manpages refer to a firmware package to be installed. > I tried to install them all when installing to a USB flash drive, with > # cat /usr/share/man/man4/*.4 | grep http | grep firmware | xargs pkg_add > > That goes fine, but some devices already have a firmware package > that is newer than what is referenced in the manpage: > > Can't install athn-firmware-1.1 because of conflicts (athn-firmware-1.1p0) > Can't install iwn-firmware-5.6 because of conflicts (iwn-firmware-5.6p0) > Can't install rsu-firmware-1.1 because of conflicts (rsu-firmware-1.1p0) > Can't install uvideo-firmware-1.1 because of conflicts (uvideo-firmware-1.2p0) > > (These four I have installed before; in fact, the installer gets > iwn and uvideo for me, and is is the newer one, which is good.) > > Looking at http://firmware.openbsd.org/firmware/ there is more. > Would a diff to the relevant manpages be helpful, or does someone > (possibly the people who prepared the newer firmware packages) > already have this on their mind? I'd prefer a diff to remove the full package names, people should generally just be using fw_update for these, in special cases where you want to 'pre-install' then pointing PKG_PATH at the right url (http://firmware.openbsd.org/firmware/5.1/ etc) then I would expect e.g. 'pkg_add iwn-firmware' to work. > Also, the firmware package at http://firmware.openbsd.org/firmware/ > are immune to 'pkg_add -ui' - what is the rationale behind isolating > them like this, and not being regular packages? They are regular packages and should get updated *if* there are newer versions. That's exactly how fw_update gets them updated. They don't change very often though, you wouldn't normally expect them to update.
Page fault trap when booting GENERIC.MP on Xen
Hi, When booting GENERIC.MP on Xen I get the following page fault trap: root on wd0a (6412ffe6504713d5.a) swap on wd0b dump on wd0b clock: unknown CMOS layout kernel: page fault trap, code = 0 Stopped attrap+0x6a:movq%r13,0x1f0(%r14) ddb{1}> When booting GENERIC all works fine. Below are the specs, sysctl hw, trace, ps and dmesg. Any suggestions? # OS OpenBSD 5.1-RELEASE, AMD64 # Xen XenServer 5.6 Service Pack 2, Build 47101p # sysctl hw hw.machine=amd64 hw.model=Intel(R) Core(TM)2 CPU 6420 @ 2.13GHz hw.ncpu=1 hw.byteorder=1234 hw.pagesize=4096 hw.disknames=wd0:6412ffe6504713d5,cd0:,fd0:,fd1: hw.diskcount=4 hw.cpuspeed=2133 hw.vendor=Xen hw.product=HVM domU hw.version=3.4.2 hw.serialno=6d00c118-f807-8694-d16c-cd186dcb9538 hw.uuid=6d00c118-f807-8694-d16c-cd186dcb9538 hw.physmem=1068498944 hw.usermem=1068486656 hw.ncpufound=2 hw.allowpowerdown=1 # trace ddb{1}> trace trap() at trap+0x6a --- trap (number 13) --- mpidle() at 0 cpu_spinup_trampoline_end() at cpu_spinup_trampoline_end+0x67 end trace frame: 0x0, count: -3 # ps ddb{1}> ps PID PPID PGRPUID S FLAGS WAITCOMMAND 13 0 0 0 30x100200 aiodonedaiodoned 12 0 0 0 30x100200 syncer update 11 0 0 0 30x100200 cleaner cleaner 10 0 0 0 30x100200 reaper reaper 9 0 0 0 30x100200 pgdaemonpagedaemon 8 0 0 0 30x100200 bored crypto 7 0 0 0 30x100200 pftmpfpruge 6 0 0 0 30x100200 usbtsk usbtask 5 0 0 0 30x100200 usbatsk usbatsk 4 0 0 0 3 0x40100200 idle1 3 0 0 0 30x100200 bored syswq 2 0 0 0 7 0x40100200 idle0 1 0 0 0 3 0 biowait swapper 0 -1 0 0 3 0x200 scheduler swapper # dmesg (GENERIC) OpenBSD 5.1 (GENERIC) #181: Sun Feb 12 09:35:53 MST 2012 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC real mem = 1068498944 (1019MB) avail mem = 1025982464 (978MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xeb01f (12 entries) bios0: vendor Xen version "3.4.2" date 03/25/2011 bios0: Xen HVM domU acpi0 at bios0: rev 2, ACPI control unavailable mpbios0 at bios0: Intel MP Specification 1.4 cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM)2 CPU 6420 @ 2.13GHz, 2133.68 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,SSSE3,CX16,LONG,LAHF cpu0: 4MB 64b/line 16-way L2 cache cpu0: apic clock running at 100MHz cpu at mainbus0: not configured mpbios0: bus 0 is type ISA ioapic0 at mainbus0: apid 1 pa 0xfec0, version 11, 48 pins ioapic0: misconfigured as apic 0, remapped to apid 1 pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel 82441FX" rev 0x02 pcib0 at pci0 dev 1 function 0 "Intel 82371SB ISA" rev 0x00 pciide0 at pci0 dev 1 function 1 "Intel 82371SB IDE" rev 0x00: DMA, channel 0 wired to compatibility, channel 1 wired to compatibility wd0 at pciide0 channel 0 drive 0: wd0: 16-sector PIO, LBA48, 40960MB, 83886080 sectors wd0(pciide0:0:0): using PIO mode 0, DMA mode 2 atapiscsi0 at pciide0 channel 1 drive 1 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: ATAPI 5/cdrom removable cd0(pciide0:1:1): using PIO mode 0 uhci0 at pci0 dev 1 function 2 "Intel 82371SB USB" rev 0x01: apic 1 int 5 piixpm0 at pci0 dev 1 function 3 "Intel 82371AB Power" rev 0x01: SMBus disabled vga1 at pci0 dev 2 function 0 "Cirrus Logic CL-GD5446" rev 0x00 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) "XenSource Platform Device" rev 0x01 at pci0 dev 3 function 0 not configured em0 at pci0 dev 4 function 0 "Intel PRO/1000MT (82540EM)" rev 0x03: apic 1 int 5, address 00:11:11:f8:51:c3 isa0 at pcib0 isadma0 at isa0 com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo com0: probed fifo depth: 0 bytes 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 spkr0 at pcppi0 lpt0 at isa0 port 0x378/4 irq 7 fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 fd0 at fdc0 drive 0: density unknown fd1 at fdc0 drive 1: density unknown usb0 at uhci0: USB revision 1.0 uhub0 at usb0 "Intel UHCI root hub" rev 1.00/1.00 addr 1 nvram: invalid checksum mtrr: Pentium Pro MTRR support uhidev0 at uhub0 port 2 configuration 1 interface 0 "QEMU 0.10.2 QEMU USB Tablet" rev 1.00/0.00 addr 2 uhidev0: iclass 3/1 uhid0 at uhidev0: input=6, output=0, feature=0 vscsi0 at root scsibus1 at vscsi0: 256 targets softraid0 at root scsibus2 at softraid0: 256 targets root on wd0
Re: acer aspire one D270
On Fri, 2012-05-04 at 19:26 -0400, Ted Unangst wrote: > The only google hit for "netbsd ignphy" is... your email. ??? > My mistake -- I was seeing igphy(4), which is for the ethernet, not the wireless. At any rate, the iwn(4) driver does not need Intel's firmware, and seems to work pretty well. Weldon
Huawei EM770W modem in GPS mode
Hello, I am using OpenBSD 5.1, i386 version. I own an Acer ao532h netbook which comes with Huawei EM770W, a 3G modem, connected via mini PCI-e bus. I succeeded to make it work as GPS receiver as following 1) echo "AT^WPDGP" > /dev/cuaU0 2) GPS data in NMEA format is being received from /dev/cuaU3. I get these data simply by 'cat /dev/cuaU3'. 3) To stop GPS data, you need to do "echo "AT^WPEND" > /dev/cuaU0" However, it is not possible to undo that command, i.e. when you press Ctrl+C to interrupt the cat /dev/cuaU3, it simply hangs, and system itself freezes. If I send halt or reboot in another terminal, the X server stops working, but system remains at console login prompt mode, and don't react to keyboard. This behavior is specific to /dev/cuaU3 only, cuaU1,2 and 4 works fine with cat. Any advices on what kind of issue this could be are very welcome!
Re: File descriptor -> name?
Alan Corey wrote: | Is there a way to get the name of a file that's open when all you've | got is a file descriptor? | | I'm working on porting something, that I didn't write. with directories | full of source. I'm seeing a problem with an ioctl being the wrong type, | but I'm looking at the code where it happens, I can't see what the file | descriptor passed in is pointing to. Seems like there should be a way. | |Alan | I guess fstat(1) is your friend. --steffen Forza Figa!
netbooks, intel GMA 3600
hi there, honeymoon being over with my acer aspire D270 i am starting to realize that even if i replace the broadcom 4313 wifi (thanks for nothing broadcom) the intel GMA 3600 being not really an intel thing, thus with no chance of an open source driver, i have bought a cheap netbook, but an expensive paperweight (or a cheap netbook that is actually useless for travelling). now before i get the "you should have researched" note, rightfully, i had a long hard look at the netbook market again, and it seems that the damned marriage made in hell: broadcom NIC's + intel GMA's is pretty much the order of the day for almost all recent netbook models, at least the atom ones. judging by some googling, even the penguin camp seems to be in pain about these devices. windows 7 starter edition is the evilest master plan i have ever seen, not only single handedly destroyed the linux netbook market, but strongly encouraged shipping these machines with hw components that will never see open source drivers. thank you very much intel, the great friend of open source. what a shame really, such nice machines otherwise. does anyone have a netbook with amd stuff instead? combos like C-60 APU with Radeon HD 6290 or similar? is that camp better supported? or is it the same tough love coming from a different companies? -f -- it takes about ten years to get used to how old you are.
Re: File descriptor -> name?
that will potentially show up more than one file, not the one that was opened On Sat, May 5, 2012 at 3:49 AM, Stuart Henderson wrote: > On 2012-05-05, Andres Perera wrote: >> not in obsd >> >> plan 9/linux keep the name as it was opened >> >> think about hardlinks, unlinking and how the kernel only stores the inode # > > find(1) can search by inode number, so if you can identify that via ktrace > and if the file still exists, you can use "find /root/of/fs -inum 1234"
Re: ipsec.conf ,routers and endpoints - third try
On 2012-05-04, shadrock wrote: > firewall dual homed > network facing static nic address = 5.5.5.4 (rfc1918/rfc6598) > virgin media router facing static nic address = 3.3.3.2 > (rfc1918/rfc6598) > virgin media router static address = 3.3.3.3 (rfc1918/rfc6598) > virgin media dynamic wan address = 1.1.1.1 (internet-routable) > firewall default route = 3.3.3.3 > network_a default route = 5.5.5.4 So you have no static routable address on either side. This isn't going to work well with isakmpd, you really need a static address on at least one side to use it. DNS lookups are only done when the config is loaded so there's no way to automatically track changed addresses in isakmpd. If you can live with restarting things when the address changes then your local_gw address would be the router-facing rfc1918 address and remote_gw would be the dynamic internet-routable address of the other gateway. OpenVPN might be better in this situation, see the 'float' option and/or http://openvpn.net/index.php/open-source/faq/77-server/299-can-openvpn-handle-the-situation-where-both-ends-of-the-connection-are-dynamic.html
older firmwares referenced in manpages
Certain device's manpages refer to a firmware package to be installed. I tried to install them all when installing to a USB flash drive, with # cat /usr/share/man/man4/*.4 | grep http | grep firmware | xargs pkg_add That goes fine, but some devices already have a firmware package that is newer than what is referenced in the manpage: Can't install athn-firmware-1.1 because of conflicts (athn-firmware-1.1p0) Can't install iwn-firmware-5.6 because of conflicts (iwn-firmware-5.6p0) Can't install rsu-firmware-1.1 because of conflicts (rsu-firmware-1.1p0) Can't install uvideo-firmware-1.1 because of conflicts (uvideo-firmware-1.2p0) (These four I have installed before; in fact, the installer gets iwn and uvideo for me, and is is the newer one, which is good.) Looking at http://firmware.openbsd.org/firmware/ there is more. Would a diff to the relevant manpages be helpful, or does someone (possibly the people who prepared the newer firmware packages) already have this on their mind? Also, the firmware package at http://firmware.openbsd.org/firmware/ are immune to 'pkg_add -ui' - what is the rationale behind isolating them like this, and not being regular packages? Jan
Re: File descriptor -> name?
On 2012-05-05, Andres Perera wrote: > not in obsd > > plan 9/linux keep the name as it was opened > > think about hardlinks, unlinking and how the kernel only stores the inode # find(1) can search by inode number, so if you can identify that via ktrace and if the file still exists, you can use "find /root/of/fs -inum 1234"