vpnc and OpenSSL
I just spend two hours trouble shutting VPN connection with one of external customer servers (Cisco 3000). It boils down to the fact that VPNC client in our ports tree is compiled without OpenSSL support. I noticed that customer's server was planting self-signed SSL certificate while playing on Windows 7. Is there any workaround to this problem? Red Hat had the same problem. VPN tunnel would establish but no route to destination would be available. I would hate to have Ubuntu or Windows proxy for this VPN tunnel. Most Kind Regards, Predrag
Re: Exploiting PCI-based DMA in OpenBSD
On Sun, Apr 05, 2015 at 09:43:55AM -0600, Theo de Raadt wrote: Why don't you craft the attack yourself and report to OpenBSD your results? Quite obvious why the question was asked, rather than studied. Yes, it is obvious. Because I'm incompetent, otherwise I would not ask. (But this troll, Theo, of course believes that people need to get answers to all your questions hard way)
Re: jwm ; speedy window manager
On 4/6/15, L.R. D.S. arrowscr...@mail.com wrote: At 6 Apr 2015 23:12:43 + (UTC) from Brian Callahan bcal...@devio.us: Or, and this is just a hypothesis, you don't have all those other things and FVWM lists those for convenience. No, I can load everything normally... ok, I'm a bit worried now. I always check the signatures before/after install. You folks just have the Fvwm and no more? $ echo /usr/X11R6/bin/*wm* /usr/X11R6/bin/cwm /usr/X11R6/bin/fvwm /usr/X11R6/bin/twm --patrick I usually don't use X, but that's what I see here. No joking. dmesg ** OpenBSD 5.7-current (GENERIC.MP) #781: Wed Mar 18 19:03:42 MDT 2015 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP cpu0: Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz (GenuineIntel 686-class) 2.01 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,NXE,LONG,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,XSAVE,LAHF,PERF real mem = 3217440768 (3068MB) avail mem = 3152490496 (3006MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: date 02/05/09, BIOS32 rev. 0 @ 0xfb080, SMBIOS rev. 2.4 @ 0xf0100 (33 entries) bios0: vendor Award Software International, Inc. version F6 date 02/05/2009 bios0: Gigabyte Technology Co., Ltd. G31M-ES2C acpi0 at bios0: rev 0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP MCFG APIC acpi0: wakeup devices PEX0(S5) PEX1(S5) PEX2(S5) PEX3(S5) PEX4(S5) PEX5(S5) HUB0(S5) UAR1(S3) USB0(S3) USB1(S3) USB2(S3) USB3(S3) USBE(S3) AZAL(S5) PCI0(S5) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimcfg0 at acpi0 addr 0xc000, bus 0-255 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 182MHz cpu0: mwait min=45313, max=22512 (bogus) cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz (GenuineIntel 686-class) 2.01 GHz cpu1: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,NXE,LONG,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,XSAVE,LAHF,PERF ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 0, remapped to apid 2 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (PEX0) acpiprt2 at acpi0: bus 2 (PEX1) acpiprt3 at acpi0: bus -1 (PEX2) acpiprt4 at acpi0: bus -1 (PEX3) acpiprt5 at acpi0: bus -1 (PEX4) acpiprt6 at acpi0: bus -1 (PEX5) acpiprt7 at acpi0: bus 3 (HUB0) acpicpu0 at acpi0 acpicpu1 at acpi0 acpibtn0 at acpi0: PWRB bios0: ROM list: 0xc/0xb400! cpu0: Enhanced SpeedStep disabled by BIOS pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 Intel 82G33 Host rev 0x10 vga1 at pci0 dev 2 function 0 Intel 82G33 Video rev 0x10 intagp0 at vga1 agp0 at intagp0: aperture at 0xd000, size 0x1000 inteldrm0 at vga1 drm0 at inteldrm0 inteldrm0: 1920x1080 wsdisplay0 at vga1 mux 1: console (std, vt100 emulation) wsdisplay0: screen 1-5 added (std, vt100 emulation) ppb0 at pci0 dev 28 function 0 Intel 82801GB PCIE rev 0x01: apic 2 int 16 pci1 at ppb0 bus 1 ppb1 at pci0 dev 28 function 1 Intel 82801GB PCIE rev 0x01: apic 2 int 17 pci2 at ppb1 bus 2 re0 at pci2 dev 0 function 0 Realtek 8101E rev 0x02: RTL8102E (0x3480), msi, address 00:24:1d:fb:96:f7 rlphy0 at re0 phy 7: RTL8201L 10/100 PHY, rev. 1 uhci0 at pci0 dev 29 function 0 Intel 82801GB USB rev 0x01: apic 2 int 23 uhci1 at pci0 dev 29 function 1 Intel 82801GB USB rev 0x01: apic 2 int 19 uhci2 at pci0 dev 29 function 2 Intel 82801GB USB rev 0x01: apic 2 int 18 uhci3 at pci0 dev 29 function 3 Intel 82801GB USB rev 0x01: apic 2 int 16 ehci0 at pci0 dev 29 function 7 Intel 82801GB USB rev 0x01: apic 2 int 23 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 ppb2 at pci0 dev 30 function 0 Intel 82801BA Hub-to-PCI rev 0xe1 pci3 at ppb2 bus 3 ichpcib0 at pci0 dev 31 function 0 Intel 82801GB LPC rev 0x01: PM disabled pciide0 at pci0 dev 31 function 2 Intel 82801GB SATA rev 0x01: DMA, channel 0 configured to native-PCI, channel 1 configured to native-PCI pciide0: using apic 2 int 19 for native-PCI interrupt wd0 at pciide0 channel 0 drive 1: HTS541060G9SA00 wd0: 16-sector PIO, LBA48, 57230MB, 117208127 sectors wd0(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 5 atapiscsi0 at pciide0 channel 1 drive 0 scsibus1 at atapiscsi0: 2 targets cd0 at scsibus1 targ 0 lun 0: TSSTcorp, DVD+-RW TS-H653G, D200 ATAPI 5/cdrom removable cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 5 ichiic0 at pci0 dev 31 function 3 Intel 82801GB SMBus rev 0x01: apic 2 int 19 iic0 at ichiic0 spdmem0 at iic0 addr 0x50: 2GB DDR2 SDRAM non-parity PC2-5300CL5 spdmem1 at iic0 addr 0x52: 2GB
Re: jwm ; speedy window manager
On Mon, Apr 06, 2015 at 07:12:43PM -0400, Brian Callahan wrote: Or, and this is just a hypothesis, you don't have all those other things and FVWM lists those for convenience. I include CWM and FVWM, I don't know why include two WM. -- Regards Henrique Lengler
Re: jwm ; speedy window manager
At 6 Apr 2015 22:55:07 + (UTC) from Ted Unangst t...@tedunangst.com: Huh? Well, I was MitM'd ? The current snapshot (install57.iso) have all that packages here... When 'startx' they enter on Fvwm by default and when click on screen have: (Re)Start WM's
Re: jwm ; speedy window manager
I think developers could do with WM the same done with lynx, remove and put on ports. I don't think someone need all the 9 WM on base system (fvwm, cwm, wm2, twm, ctwm, flwm, mwm, openbox and tvtwm). That's bloat. And flwm need fltk 1.3.X. JWM is really user friendly, minimal, don't have dependence of some C++ library. I personally don't like the fancy colours (maybe change to 18% gray or black). I seconded this to be the default. Also, a artwork of puffy as background would be nice :)
Re: jwm ; speedy window manager
L.R. D.S. wrote: I think developers could do with WM the same done with lynx, remove and put on ports. I don't think someone need all the 9 WM on base system (fvwm, cwm, wm2, twm, ctwm, flwm, mwm, openbox and tvtwm). Huh? carbolite:~ wm2 ksh: wm2: not found carbolite:~ ctwm ksh: ctwm: not found carbolite:~ flwm ksh: flwm: not found carbolite:~ mwm ksh: mwm: not found carbolite:~ openbox ksh: openbox: not found carbolite:~ tvtwm ksh: tvtwm: not found
Re: jwm ; speedy window manager
At 6 Apr 2015 23:12:43 + (UTC) from Brian Callahan bcal...@devio.us: Or, and this is just a hypothesis, you don't have all those other things and FVWM lists those for convenience. No, I can load everything normally... ok, I'm a bit worried now. I always check the signatures before/after install. You folks just have the Fvwm and no more? I usually don't use X, but that's what I see here. No joking. dmesg ** OpenBSD 5.7-current (GENERIC.MP) #781: Wed Mar 18 19:03:42 MDT 2015 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP cpu0: Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz (GenuineIntel 686-class) 2.01 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,NXE,LONG,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,XSAVE,LAHF,PERF real mem = 3217440768 (3068MB) avail mem = 3152490496 (3006MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: date 02/05/09, BIOS32 rev. 0 @ 0xfb080, SMBIOS rev. 2.4 @ 0xf0100 (33 entries) bios0: vendor Award Software International, Inc. version F6 date 02/05/2009 bios0: Gigabyte Technology Co., Ltd. G31M-ES2C acpi0 at bios0: rev 0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP MCFG APIC acpi0: wakeup devices PEX0(S5) PEX1(S5) PEX2(S5) PEX3(S5) PEX4(S5) PEX5(S5) HUB0(S5) UAR1(S3) USB0(S3) USB1(S3) USB2(S3) USB3(S3) USBE(S3) AZAL(S5) PCI0(S5) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimcfg0 at acpi0 addr 0xc000, bus 0-255 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 182MHz cpu0: mwait min=45313, max=22512 (bogus) cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz (GenuineIntel 686-class) 2.01 GHz cpu1: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,NXE,LONG,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,XSAVE,LAHF,PERF ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 0, remapped to apid 2 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (PEX0) acpiprt2 at acpi0: bus 2 (PEX1) acpiprt3 at acpi0: bus -1 (PEX2) acpiprt4 at acpi0: bus -1 (PEX3) acpiprt5 at acpi0: bus -1 (PEX4) acpiprt6 at acpi0: bus -1 (PEX5) acpiprt7 at acpi0: bus 3 (HUB0) acpicpu0 at acpi0 acpicpu1 at acpi0 acpibtn0 at acpi0: PWRB bios0: ROM list: 0xc/0xb400! cpu0: Enhanced SpeedStep disabled by BIOS pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 Intel 82G33 Host rev 0x10 vga1 at pci0 dev 2 function 0 Intel 82G33 Video rev 0x10 intagp0 at vga1 agp0 at intagp0: aperture at 0xd000, size 0x1000 inteldrm0 at vga1 drm0 at inteldrm0 inteldrm0: 1920x1080 wsdisplay0 at vga1 mux 1: console (std, vt100 emulation) wsdisplay0: screen 1-5 added (std, vt100 emulation) ppb0 at pci0 dev 28 function 0 Intel 82801GB PCIE rev 0x01: apic 2 int 16 pci1 at ppb0 bus 1 ppb1 at pci0 dev 28 function 1 Intel 82801GB PCIE rev 0x01: apic 2 int 17 pci2 at ppb1 bus 2 re0 at pci2 dev 0 function 0 Realtek 8101E rev 0x02: RTL8102E (0x3480), msi, address 00:24:1d:fb:96:f7 rlphy0 at re0 phy 7: RTL8201L 10/100 PHY, rev. 1 uhci0 at pci0 dev 29 function 0 Intel 82801GB USB rev 0x01: apic 2 int 23 uhci1 at pci0 dev 29 function 1 Intel 82801GB USB rev 0x01: apic 2 int 19 uhci2 at pci0 dev 29 function 2 Intel 82801GB USB rev 0x01: apic 2 int 18 uhci3 at pci0 dev 29 function 3 Intel 82801GB USB rev 0x01: apic 2 int 16 ehci0 at pci0 dev 29 function 7 Intel 82801GB USB rev 0x01: apic 2 int 23 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 ppb2 at pci0 dev 30 function 0 Intel 82801BA Hub-to-PCI rev 0xe1 pci3 at ppb2 bus 3 ichpcib0 at pci0 dev 31 function 0 Intel 82801GB LPC rev 0x01: PM disabled pciide0 at pci0 dev 31 function 2 Intel 82801GB SATA rev 0x01: DMA, channel 0 configured to native-PCI, channel 1 configured to native-PCI pciide0: using apic 2 int 19 for native-PCI interrupt wd0 at pciide0 channel 0 drive 1: HTS541060G9SA00 wd0: 16-sector PIO, LBA48, 57230MB, 117208127 sectors wd0(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 5 atapiscsi0 at pciide0 channel 1 drive 0 scsibus1 at atapiscsi0: 2 targets cd0 at scsibus1 targ 0 lun 0: TSSTcorp, DVD+-RW TS-H653G, D200 ATAPI 5/cdrom removable cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 5 ichiic0 at pci0 dev 31 function 3 Intel 82801GB SMBus rev 0x01: apic 2 int 19 iic0 at ichiic0 spdmem0 at iic0 addr 0x50: 2GB DDR2 SDRAM non-parity PC2-5300CL5 spdmem1 at iic0 addr 0x52: 2GB DDR2 SDRAM non-parity PC2-5300CL5 usb1 at uhci0: USB revision 1.0 uhub1 at usb1 Intel UHCI root hub rev 1.00/1.00 addr 1 usb2 at uhci1: USB revision 1.0 uhub2 at usb2 Intel UHCI root hub rev 1.00/1.00 addr 1 usb3 at uhci2: USB revision
Re: jwm ; speedy window manager
On 04/06/15 19:08, L.R. D.S. wrote: At 6 Apr 2015 22:55:07 + (UTC) from Ted Unangst t...@tedunangst.com: Huh? Well, I was MitM'd ? The current snapshot (install57.iso) have all that packages here... When 'startx' they enter on Fvwm by default and when click on screen have: (Re)Start WM's Or, and this is just a hypothesis, you don't have all those other things and FVWM lists those for convenience.
Fwd: CVS: cvs.openbsd.org: src
A heads up on this commit: if you're following -current and using any perl modules that pull in threaded libraries from packages, such as mysql/mariadb integration via DBD::mysql, then you may want to wait the day or so until the ports package builds have caught up with the change. The perl in base built against libpthread.19.0 cannot load the mysql.so shared object linked against libpthread.18.1 Philip Guenther -- Forwarded message -- From: Philip Guenther guent...@cvs.openbsd.org Date: Mon, Apr 6, 2015 at 6:27 PM Subject: CVS: cvs.openbsd.org: src To: source-chan...@cvs.openbsd.org CVSROOT:/cvs Module name:src Changes by: guent...@cvs.openbsd.org2015/04/06 19:27:07 Modified files: lib/csu: crtbegin.c crtbeginS.c lib/libc : shlib_version lib/libc/arch/alpha: SYS.h lib/libc/arch/alpha/sys: fork.S lib/libc/arch/amd64: SYS.h lib/libc/arch/amd64/sys: fork.S lib/libc/arch/arm: SYS.h lib/libc/arch/arm/sys: fork.S lib/libc/arch/hppa: SYS.h lib/libc/arch/hppa/sys: fork.S lib/libc/arch/hppa64: SYS.h lib/libc/arch/hppa64/sys: fork.S lib/libc/arch/i386: SYS.h lib/libc/arch/i386/sys: fork.S lib/libc/arch/m88k: SYS.h lib/libc/arch/m88k/sys: fork.S lib/libc/arch/mips64: SYS.h lib/libc/arch/mips64/sys: fork.S lib/libc/arch/powerpc: SYS.h lib/libc/arch/powerpc/sys: fork.S lib/libc/arch/sh: SYS.h lib/libc/arch/sh/sys: fork.S lib/libc/arch/sparc: SYS.h lib/libc/arch/sparc/sys: fork.S lib/libc/arch/sparc64: SYS.h lib/libc/arch/sparc64/sys: fork.S lib/libc/arch/vax: SYS.h lib/libc/arch/vax/sys: fork.S lib/libc/include: thread_private.h lib/libc/stdlib: atexit.c lib/libc/sys : Makefile.inc lib/libc/thread: Makefile.inc unithread_malloc_lock.c lib/librthread : rthread.c rthread_fork.c rthread_libc.c shlib_version regress/lib/csu/callbacks: Makefile regress/lib/csu/callbacks/pthread_atfork: Makefile pthread_atfork_test.c Added files: lib/libc/include: atfork.h lib/libc/sys : w_fork.c lib/libc/thread: atfork.c regress/lib/csu/callbacks/pthread_atfork: expected_child.out expected_parent.out Log message: Make pthread_atfork() track the DSO that called it like atexit() does, unregistering callbacks if the DSO is unloaded. Move the callback handling from libpthread to libc, though libpthread still overrides the inner call to handle locking and thread-library reinitialization. Major version bump for both libc and libpthread. verification that this fixes various ports ajacoutot@ asm assistance miod@; ok millert@ deraadt@
Expending on usbdevs
Hi list.
I am wondering if someone could shed some light on what I am trying to do.
I have been playing around trying to come up with something that kind of have
the verbosity of lsusb but use OpenBSD's #include dev/usb/usb.h and avoid all
of libusb stuff.
I hit a wall when I try to use USB_DEVICE_GET_FDESC :
Breakpoint 1, get_usb_device_fdesc (f=7, a=1, u=0x7f7d40d0) at usbdevs.c:219
219 int e = ioctl(f, USB_DEVICE_GET_FDESC, u);
(gdb) s
218 u-udf_size=25;
(gdb)
219 int e = ioctl(f, USB_DEVICE_GET_FDESC, u);
(gdb)
__cerror () at /usr/src/lib/libc/arch/amd64/sys/cerror.S:48
48 movqPIC_GOT(_C_LABEL(errno)), %rcx
Current language: auto; currently asm
(gdb) bt
#0 __cerror () at /usr/src/lib/libc/arch/amd64/sys/cerror.S:48
#1 0x048cfe7022cc in usbdev (f=7, a=1, rec=Variable rec is not available.
) at usbdevs.c:285
#2 0x048cfe70235b in usbdump (f=7) at usbdevs.c:308
#3 0x048cfe70259b in main (argc=3, argv=0x7f7d4258) at usbdevs.c:419
At the moment, I can get my small program to produce ouput like this:
Controller /dev/usb0:
Device Information:
addr 1:
idVendor Intel
VendorNo 0x8086
idProduct0x
Product EHCI root hub
Release 1.00
ReleaseNo0x0100
Config 1
Power0 Self powered
Speed3 (High Speed)
iSerialNumbernone
Device Name[0] uhub2
nPorts 4
port 1 powered
port 2 powered
port 3 powered
port 4 powered
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 0x0200
bDeviceClass 9 (Hub)
bDeviceSubClass 0
bDeviceProtocol 1
bMaxPacketSize 64
idVendor 0x8086
bNumConfigurations 1
Configuration Descriptor
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterface1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x40 (Self Powered)
bMaxPower (mA) 0
So basically I have the following function that fails.
I set udf_size=25 as this is the value I get from wTotalLength shown above as
explained in the man.
int
get_usb_device_fdesc(int f, int a, struct usb_device_fdesc *u)
{
u-udf_addr = a;
u-udf_config_index = USB_CURRENT_CONFIG_INDEX;
u-udf_size=25;
int e = ioctl(f, USB_DEVICE_GET_FDESC, u);
return e;
}
Clearly I don't seem to use USB_DEVICE_GET_FDESC correctly.
Grepping /usr/src only reveals little on USB_DEVICE_GET_FDESC
/usr/src:
$find . -name *.c|xargs grep USB_DEVICE_GET_FDESC
./sys/dev/usb/usb.c:case USB_DEVICE_GET_FDESC:
ma...@t61.my.domain:18:40:45
/usr/src:
$find . -name *.c|xargs grep -n USB_DEVICE_GET_FDESC
./sys/dev/usb/usb.c:752:case USB_DEVICE_GET_FDESC:
Regards
Mario St-Gelais
Re: Expending on usbdevs
On Mon, Apr 6, 2015 at 3:59 PM, Mario St-Gelais mario@videotron.ca wrote:
I have been playing around trying to come up with something that kind of have
the verbosity of lsusb but use OpenBSD's #include dev/usb/usb.h and avoid
all of libusb stuff.
I hit a wall when I try to use USB_DEVICE_GET_FDESC :
...
So basically I have the following function that fails.
I set udf_size=25 as this is the value I get from wTotalLength shown above as
explained in the man.
int
get_usb_device_fdesc(int f, int a, struct usb_device_fdesc *u)
{
u-udf_addr = a;
u-udf_config_index = USB_CURRENT_CONFIG_INDEX;
u-udf_size=25;
int e = ioctl(f, USB_DEVICE_GET_FDESC, u);
return e;
}
First, when a system call fails you should be looking at errno to see
why the call failed, or at least get a hint. I strongly advise using
the err(3) family of functions, even in test or 'toy' programs,
because one wrong assumption can waste *hours* of time. So:
#include err.h
and then use it like
if (ioctl(f, USB_DEVICE_GET_FDESC, u) == -1)
err(1, ioctl(GET_FDESC));
Now, my guess in this case is that it would report Bad Address
indicating the errno was EFAULT. Why? Well, let's look at usb(4):
USB_DEVICE_GET_FDESC (struct usb_device_fdesc *)
This command can be used to retrieve all descriptors for the
given configuration of a device on the bus. The udf_addr field
needs to be filled with the bus device address. The
udf_config_index field needs to be filled with the configuration
index for the relevant configuration descriptor. For convenience
the current configuration can be specified by
USB_CURRENT_CONFIG_INDEX. The udf_data field needs to point to a
memory area of the size given in the udf_size field. The proper
size can be determined by first issuing a USB_DEVICE_GET_CDESC
command and inspecting the wTotalLength field:
...
So, where's the allocation of wTotalLength bytes of memory and the
initialization of u-udf_data to point to it?
Philip Guenther
Re: jwm ; speedy window manager
sorry for low level response , about openbox , all know that $ cp -R /etc/xdg/openbox/* ~/.config/openbox $ cat .xinitrc exec openbox-session by the way in linux , i love lxde (speed=xfce4 , but more modern). and i have recieved email. that recommend i3 ( http://i3wm.org/ ) which says that i3 is a tiling window manager, completely written from scratch. The target platforms are GNU/Linux and BSD operating systems, our code is Free and Open Source Software (FOSS) under the BSD license. --- tuyosi takesima
Re: jwm ; speedy window manager
On Apr 7, 2015 8:42 AM, patrick keshishian pkeshish pkesh...@gmail.com@ pkesh...@gmail.comgmail.com pkesh...@gmail.com wrote: On 4/6/15, L.R. D.S. arrowscript arrowscr...@mail.com@ arrowscr...@mail.commail.com arrowscr...@mail.com wrote: At 6 Apr 2015 23:12:43 + (UTC) from Brian Callahan bcallah bcal...@devio.us@ bcal...@devio.usdevio.us bcal...@devio.us: Or, and this is just a hypothesis, you don't have all those other things and FVWM lists those for convenience. No, I can load everything normally... ok, I'm a bit worried now. I always check the signatures before/after install. You folks just have the Fvwm and no more? $ echo /usr/X11R6/bin/*wm* /usr/X11R6/bin/cwm /usr/X11R6/bin/fvwm /usr/X11R6/bin/twm --patrick [...] Switch back to the virtual console you ran startx from after you try the menu items and read the messages waiting there for you. (Of course, I was confused until yesterday, too.) Joel Rees Computer memory is just fancy paper, CPUs just fancy pens. All is a stream of text flowing from the past into the future.
Re: make build errors on me (perl does not install properly)
On Sun, Apr 5, 2015 at 9:27 PM, Philip Guenther guent...@gmail.com wrote: On Thu, Mar 26, 2015 at 4:36 AM, Gregory Edigarov ediga...@qarea.com wrote: Ok, so if somebody interested in - h2ph is expecting files on its command line, not something else. (that was an issue with a unix socket, sneaked in to the /usr/include as the the result of maybe a power loss issue I had. the system builds ok now. the proposed patch, to eliminate the possibility of such problems in the future: Committed (approximately), thanks. ...and reverted. With the diff, not all the files that should be created are, and make release would warn (and then barf in distrib list check). If you still think this needs to be solved, h2ph itself is probably the place to put the check...but it must handle symlinks to files! Philip Guenther
Re: SSL_ENABLE_FALLBACK_SCSV not defined error building firefox-esr-31.5.3 Re: differences between pk_add -u and building from source at stable
I'm sorry, but you've generated so many threads over the same build error
that i dont understand anymore what you're trying to achieve, what
situation you're coming from, and what you're doing to get this error.
Is this on 5.6/i386 ? with -stable patches applied ? Trying to build a port
from the stable branch ?
SSL_ENABLE_FALLBACK_SCSV is defined in nss (see
http://mxr.mozilla.org/mozilla-central/ident?i=SSL_ENABLE_FALLBACK_SCSV) ,
so you'll have to figure out if firefox build correctly detects the version
of nss installed on your system, and if that version has this define.
On current this is what i have with nss 3.18:
/usr/local/include/nss/ssl.h:#define SSL_ENABLE_FALLBACK_SCSV 28
On plain 5.6 with nss 3.16.2., i dont have that define, so maybe esr is
subtly messing up requirements here.
At some point, if you encounter too many build issues you're not able to
deal with, you should give some trust to the people who know what they're
doing, and just use the stable packages from mtier (which, of course,
managed to build that firefox esr version afaict)
Landry
On Mon, Apr 6, 2015 at 1:40 AM, Joel Rees joel.r...@gmail.com wrote:
On Apr 4, 2015 7:26 PM, Joel Rees joel.r...@gmail.com wrote:
After about six hours
More like eight hours.
Just finished a re-compile without the room fan and got to the same
error. (No overheating, either, with one less drive.)
with a room fan aimed at the computer to keep it from overheating, I get
this error about SSL_ENABLE_FALLBACK_SCSV undefined. Most of the error
scrolled off the screen and is not in the buffer because I had a different
virtual console up monitoring the CPU temperature. Was not using tee to
capture the output because I was trying to keep the burden on the drive
controller light.
(I'm pretty sure it was the drive controller overheating rather than the
CPU. I had to move it to a different slot to get it close enough to the
case fan.)
I have this much information still on the screen:
Kept the scrollback this time:
--
[...Need to find a place to post the screen shots. ...]
/usr/ports/pobj/firefox-esr-31.5.3/mozilla-esr31/security/manager/ssl/src/nsNSSIOLayer.cpp:
In function 'bool {anonymous}::retryDueToTLSIntolerance(PRErrorCode,
nsSSSocketInfo*)':
/usr/ports/pobj/firefox-esr-31.5.3/mozilla-esr31/security/manager/ssl/src/nsNSSIOLayer.cpp:959:10:
error: 'SSL_ERROR_INAPPROPRIATE_FALLBACK_ALERT' was not declared in
this scope
case SSL_ERROR_INAPPROPRIATE_FALLBACK_ALERT:
^
/usr/ports/pobj/firefox-esr-31.5.3/mozilla-esr31/security/manager/ssl/src/nsNSSIOLayer.cpp:
In function 'nsresult nsSSLIOLayerSetOptions(PRFileDesc*, bool, const
char*, const char*, int32_t, nsNSSSocketInfo*)':
/usr/ports/pobj/firefox-esr-31.5.3/mozilla-esr31/security/manager/ssl/src/nsNSSIOLayer.cpp:2328:41:
error: 'SSL_ENABLE_FALLBACK_SCSV' was not declared in this scope
if (SECSuccess != SSL_OptionSet(fd, SSL_ENABLE_FALLBACK_SCSV,
true)) {
/usr/ports/pobj/firefox-esr-31.5.3/mozilla-esr31/config/rules.mk:1001:
recipe for target 'nsNSSIOLayer.o' failed
gmake[3]: *** [nsNSSIOLayer.o] Error 1
gmake[3]: Leaving directory
'/usr/ports/pobj/firefox-esr-31.5.3/build-i386/security/manager/ssl/src'
/usr/ports/pobj/firefox-esr-31.5.3/mozilla-esr31/config/recurse.mk:95:
recipe for target 'security/manager/ssl/src/compile' failed
gmake[2]: *** [security/manager/ssl/src/compile] Error 2
gmake[2]: Leaving directory
'/usr/ports/pobj/firefox-esr-31.5.3/build-i386'
/usr/ports/pobj/firefox-esr-31.5.3/mozilla-esr31/config/recurse.mk:95:
recipe for target 'compile' failed
gmake[1]: [compile] Error 2
gmake[1]: Leaving directory
'/usr/ports/pobj/firefox-esr-31.5.3/build-i386'
/usr/ports/pobj/firefox-esr-31.5.3/mozilla-esr31/config/recurse.mk:592:
recipe for target 'all' failed
gmake: *** [all] Error 2
*** Error 2 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2727
'/usr/ports/pobj/firefox-esr-31.5.3/build-i386/.build_done')
*** Error 1 in /usr/ports/www/firefox-esr (/usr/ports/infrastructure/mk/
bsd.port.mk:2455 'build')
if I didn't make a mistake typing that in. I did a pwd and lost the line
about SSL_ENABLE_FALLBACK_SCSV being undefined, sorry.
Any thoughts while I muck around in that directory and go looking for
the source, after I get back from a family errand? (Maybe I'll just give up
on firefox-esr v. 31.5.3.)
On Apr 3, 2015 4:22 PM, Joel Rees joel.r...@gmail.com wrote:
On Apr 3, 2015 6:35 AM, Joel Rees joel.r...@gmail.com wrote:
[...]
Probably should grab something to monitor the temperatures, etc.,
while I try building the compiler again. Maybe use job control to suspend
the build process every five minutes or so and let things cool down. (Since
I can't afford a new motherboard right now.)
Moving keyboards and books away from the case vents helps a lot.
Temperature was holding steady at 42 C or below
Re: jwm ; speedy window manager
Otsukaresama desu. On Mon, Apr 6, 2015 at 9:59 AM, Tuyosi Takesima nakajin.fu...@gmail.com wrote: thanks fo reply . i understand jwm's state at present. openbsd's default X window manager(i don't know it's name) is difficult to use especially non-english language user . it's defect is that it doesn't show the state of input method. jwm show the state of input method(right under) and speedy . due to http://d.hatena.ne.jp/linuzau/20090201/1233468585 Window manager Memory usageGUI Window placement amiwm Small # Floating awesome Small × Tile type blackboxSmall # Floating dwm Small × Tile type enlightment Small # Floating evilwm Small × Floating fluxbox Small # Floating flwmSmall # Floating fvwm2 Small # Floating gnome Large # Floating jwm Small # Floating kde Large # Floating lwm Small × Floating metacitySmall × Floating olwmSmall # Floating openbox Small # Floating qvwmSmall # Floating ratpoison Small × Tile type sawfish Small × Floating stumpwm Medium × Tile type twm Small # Floating wmii2 Medium × Tile type xfce4 Medium # Floating is there another light X window manager in openbsd ? --- tuyosi takesima I'm using XFCE4 okay. It's a bit heavy, but I can use it, with patience. (I need to check my X11 configuration.) But fvwm, the default window manager, is no lighter than XFCE4. I just looked for window managers with # cd /usr/ports #make search key=window manager and got a lot of responses. I can't recommend any yet for Japanese. I need to try some of them first. :-) (/usr/local/bin/ibus-setup doesn't seem to have a nearby cursor option, but I have seen the effect in XFCE sometimes.) -- Joel Rees Be careful when you look at conspiracy. Look first in your own heart, and ask yourself if you are not your own worst enemy. Arm yourself with knowledge of yourself, as well.
Re: jwm ; speedy window manager
On Mon, Apr 6, 2015 at 9:04 PM, Kevin Chadwick m8il1i...@gmail.com wrote: On Mon, 6 Apr 2015 15:19:57 +0900 Joel Rees wrote: I'm using XFCE4 okay. It's a bit heavy, but I can use it, with patience. (I need to check my X11 configuration.) But fvwm, the default window manager, is no lighter than XFCE4. Do you mean xfwm which is based on fvwm, if so the lightness is likely similar but full XFCE is obviously heavier as it takes longer to load up, but ofc ourse it does a lot more. On my twelve or thirteen year old single-processor 32-bit box running a Japanese IME and stuff that works with Japanese, fvwm doesn't really feel any lighter. Typing really lags sometimes when the processor gets busy. Which is what I should have said and didn't. Sorry. I've also had instances where the whole of XFCE locks up, which doesn't happen with fvwm. I've locked up fvwm twice today, but I'm sure it's because I don't know what I'm doing yet. Also one xfce-terminal seems to be able to take out all the others which doesn't happen with xterm and you hit process limits. I still use fvwm1 rather than fvwm2 but that is mainly because I see little need. Pcmanfm has a terminal here and find built in by default that Thunar doesn't have but whilst pcmanfm is still usable it does core dump sometimes with fvwm1 whilst it doesn't seem to with fvwm2, perhaps that is because I only enable some dbus services. Whatever the reason that has to be primarily a bug in pcmanfm and not the fault of fvwm. I still haven't worked out if fvwm2 is as easy to lock down as fvwm1 either and the config migration seems to have dropped fvwm1 support now too. https://opensource.conformal.com/wiki/spectrwm Is a tiling wm and hacked up by OpenBSD devs. I'd be using that but I'm not sure I could make it easy for my users to use it (not it's aim) and until I have time to find out then I like to use whatever I give my users. Of course that's chicken and egg so it's probably time I switched and found out. However simply getting a consistent dark theme across apps with differences between current and release is challenge enough. Yeah, I need to make time to experiment and learn better ways to do things, too. -- Joel Rees Be careful when you look at conspiracy. Look first in your own heart, and ask yourself if you are not your own worst enemy. Arm yourself with knowledge of yourself, as well.
Re: jwm ; speedy window manager
On Mon, 6 Apr 2015 15:19:57 +0900 Joel Rees wrote: I'm using XFCE4 okay. It's a bit heavy, but I can use it, with patience. (I need to check my X11 configuration.) But fvwm, the default window manager, is no lighter than XFCE4. Do you mean xfwm which is based on fvwm, if so the lightness is likely similar but full XFCE is obviously heavier as it takes longer to load up, but ofc ourse it does a lot more. I've also had instances where the whole of XFCE locks up, which doesn't happen with fvwm. Also one xfce-terminal seems to be able to take out all the others which doesn't happen with xterm and you hit process limits. I still use fvwm1 rather than fvwm2 but that is mainly because I see little need. Pcmanfm has a terminal here and find built in by default that Thunar doesn't have but whilst pcmanfm is still usable it does core dump sometimes with fvwm1 whilst it doesn't seem to with fvwm2, perhaps that is because I only enable some dbus services. Whatever the reason that has to be primarily a bug in pcmanfm and not the fault of fvwm. I still haven't worked out if fvwm2 is as easy to lock down as fvwm1 either and the config migration seems to have dropped fvwm1 support now too. https://opensource.conformal.com/wiki/spectrwm Is a tiling wm and hacked up by OpenBSD devs. I'd be using that but I'm not sure I could make it easy for my users to use it (not it's aim) and until I have time to find out then I like to use whatever I give my users. Of course that's chicken and egg so it's probably time I switched and found out. However simply getting a consistent dark theme across apps with differences between current and release is challenge enough.
Re: .kshrc Definitions under X
Hi, does the tips here help? http://www.openbsd.org/faq/faq8.html#ksh 2015-04-06 7:22 GMT+03:00 Philip Guenther guent...@gmail.com: On Sun, Apr 5, 2015 at 9:12 PM, Andrew Fresh and...@afresh1.com wrote: On Sun, Apr 05, 2015 at 10:50:47PM -0300, Henrique Lengler wrote: And it is called in ~.profile with this: . /home/henri/.kshrc The problem is that these definitions work out of X, in the console, logged as the same user (henri) but don't work under X. I open a xterm window and and type clr, I receive: /bin/ksh: clr: not found But out of X it works, can someone help me to make this thing work normally? What I have done is set ENV=$HOME/.kshrc in .profile, then whenever you open a new shell, it will use that file as a shell startup file. That's step one, but whether it's enough depends on how you start X. If you start X from the command line with 'startx' then yes, using export ENV=$HOME/.kshrc in your .profile should be enough, because your X clients will inherit that in the environment from startx. If you start X with xdm, then you need to either A) manually set ENV (or source your entire .profile) from your .xsession that xdm invokes, OR B) tell xterm to start the shell inside it as a login shell, so that *that* will read your .profile. This can be done by either: B1) start xterm with the -ls option, or B2) set *loginShell: true in your X resource database (c.f. xrdb(1)) Philip Guenther
[softraid] how to debug system lock?
I have an old softraid crypto image (huge file). While accessing its files (vnd-softraid crypto-ffs) the OS locks = I can't get output of any command and I can't kill a process touching the softraid crypto filesystem. Hard power reset is only way. The kernel doesn't panic, I can access ddb but no idea what to look at. Any tip how could i obtain more info which I could provide here? My OS: kern.version=OpenBSD 5.7-current (GENERIC.MP) #903: Thu Apr 2 13:47:34 MDT 2015 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP The softraid crypto file is old... no idea, cca 1 year old. j.
Re: SSL_ENABLE_FALLBACK_SCSV not defined error building firefox-esr-31.5.3 Re: differences between pk_add -u and building from source at stable
On Mon, Apr 6, 2015 at 7:02 PM, Landry Breuil landry.bre...@gmail.com wrote:
I'm sorry, but you've generated so many threads over the same build error
that i dont understand anymore what you're trying to achieve, what situation
you're coming from, and what you're doing to get this error.
And it doesn't help that I'm confused.
I've finally convinced myself that updates to stable in packages are
really serious issues and updates in ports are things that may not be
necessary for everyone. That's one thread that just happened to get
tangled up in this one.
Hardware issues are possibly the reason for this thread, and I've sort
of solved those. I need to get heat sink brackets for the hard drive
that I unplugged. That's another thread and maybe this
Is this on 5.6/i386 ? with -stable patches applied ? Trying to build a port
from the stable branch ?
SSL_ENABLE_FALLBACK_SCSV is defined in nss (see
http://mxr.mozilla.org/mozilla-central/ident?i=SSL_ENABLE_FALLBACK_SCSV) ,
so you'll have to figure out if firefox build correctly detects the version
of nss installed on your system, and if that version has this define.
On current this is what i have with nss 3.18:
/usr/local/include/nss/ssl.h:#define SSL_ENABLE_FALLBACK_SCSV 28
On plain 5.6 with nss 3.16.2., i dont have that define, so maybe esr is
subtly messing up requirements here.
At some point, if you encounter too many build issues you're not able to
deal with, you should give some trust to the people who know what they're
doing, and just use the stable packages from mtier (which, of course,
managed to build that firefox esr version afaict)
Landry
On Mon, Apr 6, 2015 at 1:40 AM, Joel Rees joel.r...@gmail.com wrote:
On Apr 4, 2015 7:26 PM, Joel Rees joel.r...@gmail.com wrote:
After about six hours
More like eight hours.
Just finished a re-compile without the room fan and got to the same
error. (No overheating, either, with one less drive.)
with a room fan aimed at the computer to keep it from overheating, I get
this error about SSL_ENABLE_FALLBACK_SCSV undefined. Most of the error
scrolled off the screen and is not in the buffer because I had a different
virtual console up monitoring the CPU temperature. Was not using tee to
capture the output because I was trying to keep the burden on the drive
controller light.
(I'm pretty sure it was the drive controller overheating rather than the
CPU. I had to move it to a different slot to get it close enough to the
case
fan.)
I have this much information still on the screen:
Kept the scrollback this time:
--
[...Need to find a place to post the screen shots. ...]
/usr/ports/pobj/firefox-esr-31.5.3/mozilla-esr31/security/manager/ssl/src/nsNSSIOLayer.cpp:
In function 'bool {anonymous}::retryDueToTLSIntolerance(PRErrorCode,
nsSSSocketInfo*)':
/usr/ports/pobj/firefox-esr-31.5.3/mozilla-esr31/security/manager/ssl/src/nsNSSIOLayer.cpp:959:10:
error: 'SSL_ERROR_INAPPROPRIATE_FALLBACK_ALERT' was not declared in
this scope
case SSL_ERROR_INAPPROPRIATE_FALLBACK_ALERT:
^
/usr/ports/pobj/firefox-esr-31.5.3/mozilla-esr31/security/manager/ssl/src/nsNSSIOLayer.cpp:
In function 'nsresult nsSSLIOLayerSetOptions(PRFileDesc*, bool, const
char*, const char*, int32_t, nsNSSSocketInfo*)':
/usr/ports/pobj/firefox-esr-31.5.3/mozilla-esr31/security/manager/ssl/src/nsNSSIOLayer.cpp:2328:41:
error: 'SSL_ENABLE_FALLBACK_SCSV' was not declared in this scope
if (SECSuccess != SSL_OptionSet(fd, SSL_ENABLE_FALLBACK_SCSV,
true)) {
/usr/ports/pobj/firefox-esr-31.5.3/mozilla-esr31/config/rules.mk:1001:
recipe for target 'nsNSSIOLayer.o' failed
gmake[3]: *** [nsNSSIOLayer.o] Error 1
gmake[3]: Leaving directory
'/usr/ports/pobj/firefox-esr-31.5.3/build-i386/security/manager/ssl/src'
/usr/ports/pobj/firefox-esr-31.5.3/mozilla-esr31/config/recurse.mk:95:
recipe for target 'security/manager/ssl/src/compile' failed
gmake[2]: *** [security/manager/ssl/src/compile] Error 2
gmake[2]: Leaving directory
'/usr/ports/pobj/firefox-esr-31.5.3/build-i386'
/usr/ports/pobj/firefox-esr-31.5.3/mozilla-esr31/config/recurse.mk:95:
recipe for target 'compile' failed
gmake[1]: [compile] Error 2
gmake[1]: Leaving directory
'/usr/ports/pobj/firefox-esr-31.5.3/build-i386'
/usr/ports/pobj/firefox-esr-31.5.3/mozilla-esr31/config/recurse.mk:592:
recipe for target 'all' failed
gmake: *** [all] Error 2
*** Error 2 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2727
'/usr/ports/pobj/firefox-esr-31.5.3/build-i386/.build_done')
*** Error 1 in /usr/ports/www/firefox-esr
(/usr/ports/infrastructure/mk/bsd.port.mk:2455 'build')
if I didn't make a mistake typing that in. I did a pwd and lost the line
about SSL_ENABLE_FALLBACK_SCSV being undefined, sorry.
Any thoughts while I muck around in that directory and go looking for
the source, after I get back from a family errand? (Maybe I'll just
Re: jwm ; speedy window manager
Eivind Eide xeno...@gmail.com writes: i recommend jwm as window manager . Second that. It's a good WM for slow systems. But obsd port sticks at 2.1.0 http://openports.se/x11/jwm while upstreams have 2.2.2 http://www.joewing.net/projects/jwm/release-2.2.shtml#v2.2.2 ...probably have to read myself up on updating obsd ports one day instead of whining... We couldn't see the updates since upstream changed the location where the releases are stored. This has now been fixed and the road is clear if anyone wants to give a shot at updating it. ;) -- jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
Re: jwm ; speedy window manager
On Mon, 6 Apr 2015 22:11:21 +0900 Joel Rees wrote: On my twelve or thirteen year old single-processor 32-bit box running a Japanese IME and stuff that works with Japanese, fvwm doesn't really feel any lighter. Typing really lags sometimes when the processor gets busy. Which is what I should have said and didn't. Sorry. nice or renice whatever is doing the work. If you have multicore then it's less symptomatic but I don't see how anything else can solve that but using scheduling. Maybe some environments do some automated nicing but not that I know of.
Re: jwm ; speedy window manager
On Mon, 6 Apr 2015 22:11:21 +0900 Joel Rees joel.r...@gmail.com wrote: On Mon, Apr 6, 2015 at 9:04 PM, Kevin Chadwick m8il1i...@gmail.com wrote: On Mon, 6 Apr 2015 15:19:57 +0900 Joel Rees wrote: I'm using XFCE4 okay. It's a bit heavy, but I can use it, with patience. (I need to check my X11 configuration.) But fvwm, the default window manager, is no lighter than XFCE4. Do you mean xfwm which is based on fvwm, if so the lightness is likely similar but full XFCE is obviously heavier as it takes longer to load up, but ofc ourse it does a lot more. On my twelve or thirteen year old single-processor 32-bit box running a Japanese IME and stuff that works with Japanese, fvwm doesn't really feel any lighter. Typing really lags sometimes when the processor gets busy. Which is what I should have said and didn't. Sorry. I've also had instances where the whole of XFCE locks up, which doesn't happen with fvwm. I've locked up fvwm twice today, but I'm sure it's because I don't know what I'm doing yet. Also one xfce-terminal seems to be able to take out all the others which doesn't happen with xterm and you hit process limits. I still use fvwm1 rather than fvwm2 but that is mainly because I see little need. Pcmanfm has a terminal here and find built in by default that Thunar doesn't have but whilst pcmanfm is still usable it does core dump sometimes with fvwm1 whilst it doesn't seem to with fvwm2, perhaps that is because I only enable some dbus services. Whatever the reason that has to be primarily a bug in pcmanfm and not the fault of fvwm. I still haven't worked out if fvwm2 is as easy to lock down as fvwm1 either and the config migration seems to have dropped fvwm1 support now too. https://opensource.conformal.com/wiki/spectrwm Is a tiling wm and hacked up by OpenBSD devs. I'd be using that but I'm not sure I could make it easy for my users to use it (not it's aim) and until I have time to find out then I like to use whatever I give my users. Of course that's chicken and egg so it's probably time I switched and found out. However simply getting a consistent dark theme across apps with differences between current and release is challenge enough. Yeah, I need to make time to experiment and learn better ways to do things, too. I'm *extremely* pleased with Openbox with customized hotkeys, including a hotkey for dmenu. Please note that Openbox is not the slightest bit useful unless and until you make customized keystrokes and make a 6 pixel margin on the left so you can always click the desktop. SteveT Steve Litt Twenty Eight Tales of Troubleshooting http://www.troubleshooters.com/28
