Re: syslog-ng+ELK

Michael Shirk wrote: > On May 23, 2015 10:42, "Predrag Punosevac" > wrote: > > > > 5. Finally I am open for simpler ideas. Any opinions on > sysutils/logfmon > > Is it possible to visualize on the web output from logfmon? > > > > Best, > > Predrag Punosevac > > > > There

Yo, all yous Developers

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I've just moved an application (written in gprolog) from OBSD_i386 4.1 to 5.9. I needed to recompile things, and some of the periferal glue (sudo, nsupdate...) needed to be added from packages, but so far as I can tell it all works. All told it

Re: Dell XPS13 9333 Touchpad doesn't work

Hi, it might be that you are out of luck with your hardware. If I'm not mistaken, it has a Cypress touchpad, which isn't supported. On 05/06/2016 05:16 AM, Gabriel Guzman wrote: > Hello misc@ > > I have a Dell XPS 13 9333 that I recently installed OpenBSD on. For the > most part everything runs

Re: Creative USB Headset on 5.9

On Fri, May 6, 2016, at 11:01 PM, joekiser wrote: > > Is this plugged into a USB 2 port? > > Joe No, it was plugged into a USB3 port, it works fine over USB 2! I assume that is a driver limitation? And any idea if it's possible to switch audio devices in xfce4-mixer? It still doesn't show up

Re: Creative USB Headset on 5.9

On Fri, May 6, 2016, at 15:16, Jakob Gillich wrote: > I'm pretty new to OpenBSD in general, and recently installed 5.9. Now > I'm wondering if it's possible to get my USB headset working. According > to dmesg, a audio1 device gets created: > [snip] > > Does this mean it's not supported, or is

Creative USB Headset on 5.9

I'm pretty new to OpenBSD in general, and recently installed 5.9. Now I'm wondering if it's possible to get my USB headset working. According to dmesg, a audio1 device gets created: uaudio0 at uhub0 port 4 configuration 1 interface 0 "Creative Technology Ltd. SB Tactic(3D) Wrath Wireless" rev

Re: dhclient.conf and hostname.if

On Fri, May 06, 2016 at 06:21:00AM -0600, Duncan Patton a Campbell wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Fri, 06 May 2016 12:06:58 +0100 > Mark Carroll wrote: > > > On 06 May 2016, Duncan Patton a. Campbell wrote: > > > > > Is there any similar tag to

Re: non-wintel hardware choices

Michael, The challenge is device drivers for the video cards. Especially in the PA-RISC case because there really is no documentation for them. I've spent some time on the HP end of things and unfortunately was in over my head pretty quickly. Thanks, Bryan On Fri, May 6, 2016 at 10:54 AM,

Re: [patch] bgpctl more info in terse format

On Mon, Apr 18, 2016 at 08:09:50PM +0200, Claudio Jeker wrote: > The idea of terse is that you don't need to parse. So in a way I agree > with the diff. What I don't like is the inclusion of the number of > prefixes. That count requires a roundtrip to the RDE to find and sometimes > this takes a

[no subject]

Re: Performance of Firefox and Chromium > I'm not sure what hardware you guys run OpenBSD on, but on my (old, > crusty, crummy, shitty) laptop, it and a lot of Gui-requiring and My laptop was made in 2008, my desktop in 2002. > javascript heavy sites send > javascript from many

Re: non-wintel hardware choices

> On 5 May 2016, at 19:52, Bryan Everly wrote: > > Unfortunately PA-RISC doesn't have X support at the console. You can > run X on it and have the Windows render on a SPARC, MIPS or Intel > platform though. Neither does Alpha (AXP). Does anyone know if there are

Re: non-wintel hardware choices

Hi, Bryan Everly wrote: Unfortunately PA-RISC doesn't have X support at the console. You can run X on it and have the Windows render on a SPARC, MIPS or Intel platform though. sorry, didn't know that. I always did run my HP hardware headless... so I never noticed. I always liked the CPU

Re: Short maximum interpreter length

> Why is MAXINTERP in only 128? I can think of a few: > > 1. It's been that way a while and nobody's complained > 2. If someone's shebangs are longer than that, they're probably doing > whatever they're doing horribly, horribly wrong > 3. Historical compatibility > > Is it one of those? If

Re: dhclient.conf and hostname.if

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Fri, 06 May 2016 12:06:58 +0100 Mark Carroll wrote: > On 06 May 2016, Duncan Patton a. Campbell wrote: > > > Is there any similar tag to access the addess assigned by dhcp? > > What other mechanisms exist to update dynamic dns

Re: dhclient.conf and hostname.if

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Fri, 6 May 2016 11:56:31 +0100 Raf Czlonka wrote: > On Fri, May 06, 2016 at 11:35:47AM BST, Duncan Patton a Campbell > wrote: > > > > Back when the script tag was removed from dhclient.conf the > > functionality to do

Re: dhclient.conf and hostname.if

On 06 May 2016, Duncan Patton a. Campbell wrote: > Is there any similar tag to access the addess assigned by dhcp? > What other mechanisms exist to update dynamic dns assignments? Could ifstated(8) help here? I've separately wondered if I ought to be using it to kick pf because it otherwise

Re: SMP implementation

On 05/05/16(Thu) 19:03, Pavan Maddamsetti wrote: > I have been reading about ongoing improvements to SMP in OpenBSD. My > understanding is that context switching from userspace to the kernel can be > hazardous if shared resources are not protected by locking. The context switching it not the

Re: dhclient.conf and hostname.if

On Fri, May 06, 2016 at 11:35:47AM BST, Duncan Patton a Campbell wrote: > > Back when the script tag was removed from dhclient.conf the > functionality to do external commands was ostensibly moved > into hostname.if via the > > !command mechanism. > > in man hostname.if it says > > "It is

dhclient.conf and hostname.if

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Back when the script tag was removed from dhclient.conf the functionality to do external commands was ostensibly moved into hostname.if via the !command mechanism. in man hostname.if it says "It is worth noting that ``\$if'' in a command