Jan 21 snapshot - fixed kernel crash

Hello, TLDR I just wanted to send a quick message to say that the Jan 21 snapshot fixed a kernel issue for me on amd64. The Intel firmware was installed. It also seems faster than 6.2. Thank you! Background: I have a mini PC for testing Elastic. I decided to use it as my desktop. With 6.1 the

Re: popen from cgi program

> Bingo! I copied all the necessary libs to corresponding usr/lib dirs and got > the chrooted programs to run from a chroot command, but they would still not > work from the cgi program. You pointing out that popen requires sh got me > thinking. Sh was already in /var/www/bin but it had 000

Re: Flatbed scanner that works well with OpenBSD?

On Fri, Jan 19, 2018 at 1:47 PM, Ax0n wrote: > Slightly related, I have a CanoScan LiDE 100 that used to work great with > OpenBSD, using either ScanImage or simple-scan. It's detected, but sometime > around OpenBSD-5.6 it stopped working. I use it infrequently enough, and I >

Re: Kernel panic with openbsd 6.2

Hello Stuart,Thank you for your answer.I had my VM running for months in version 6.1 and had not problem but I reinstalled it in version 6.2 and the problem is happening.It seems to me that something in version 6.2 is producing the error.One crash today again Le dimanche 21 janvier 2018

Re: Jan 20 snapshot

Running on this 20180108 kernel now. Here's the dmesg. Seems to be running stable now. Normally, I'd be completely hung at this point. Hopefully, I haven't screwed all of this up with my intoxication, but, I'm too stubborn to not keep a system running! ;) On 1/21/18 4:10 PM, Stuart Henderson

Re: Jan 20 snapshot

Got it ... I hope ... "Gin"ny and all On 1/21/18 4:10 PM, Stuart Henderson wrote: On 2018-01-21, Base Pr1me wrote: I'll try. Not sure I can keep it running long enough to get dmesg lol. Last upgrade was ~1 1/2 weeks ago. I know, full of information today. I'll try and

Re: Jan 20 snapshot

Cool, thanks. I'll check this out this week. Much gratitude. I'm far too 'ginned' up at the moment. ;) On Jan 21, 2018 16:13, "Stuart Henderson" wrote: > On 2018-01-21, Base Pr1me wrote: > > I'll try. Not sure I can keep it running long enough to

Re: Jan 20 snapshot

On 2018-01-21, Base Pr1me wrote: > I'll try. Not sure I can keep it running long enough to get dmesg lol. Last > upgrade was ~1 1/2 weeks ago. I know, full of information today. I'll try > and get dmesg this week, when I have more time ... Or wait until newer > snaps and

Re: popen from cgi program

> popen() requires a shell. You are most likely running it in a chroot and > don't have /bin/sh. Bingo! I copied all the necessary libs to corresponding usr/lib dirs and got the chrooted programs to run from a chroot command, but they would still not work from the cgi program. You pointing

Re: Jan 20 snapshot

Ok, thanks. On Jan 21, 2018 11:02, "Sebastien Marie" wrote: > On Sun, Jan 21, 2018 at 06:44:56PM +0100, Adam Wolk wrote: > > On Sun, Jan 21, 2018 at 09:30:22AM -0700, Base Pr1me wrote: > > > Anyone else's system hanging randomly after upgrading to yesterday's > > > snapshot?

Re: Jan 20 snapshot

On Sun, Jan 21, 2018 at 06:44:56PM +0100, Adam Wolk wrote: > On Sun, Jan 21, 2018 at 09:30:22AM -0700, Base Pr1me wrote: > > Anyone else's system hanging randomly after upgrading to yesterday's > > snapshot? This isn't a panic that drops to ddb. It's just freezing with no > > response to anything.

Re: Jan 20 snapshot

Ty. On Jan 21, 2018 10:45, "Adam Wolk" wrote: > On Sun, Jan 21, 2018 at 09:30:22AM -0700, Base Pr1me wrote: > > Anyone else's system hanging randomly after upgrading to yesterday's > > snapshot? This isn't a panic that drops to ddb. It's just freezing with > no > >

Re: Jan 20 snapshot

I'll try. Not sure I can keep it running long enough to get dmesg lol. Last upgrade was ~1 1/2 weeks ago. I know, full of information today. I'll try and get dmesg this week, when I have more time ... Or wait until newer snaps and try again. On Jan 21, 2018 10:37, "Sebastien Marie"

Re: Jan 20 snapshot

On Sun, Jan 21, 2018 at 09:30:22AM -0700, Base Pr1me wrote: > Anyone else's system hanging randomly after upgrading to yesterday's > snapshot? This isn't a panic that drops to ddb. It's just freezing with no > response to anything. I haven't notice any problems with: kern.version=OpenBSD

Re: Jan 20 snapshot

On Sun, Jan 21, 2018 at 09:30:22AM -0700, Base Pr1me wrote: > Anyone else's system hanging randomly after upgrading to yesterday's > snapshot? This isn't a panic that drops to ddb. It's just freezing with no > response to anything. A full dmesg would be welcome, and having the date of your

Jan 20 snapshot

Anyone else's system hanging randomly after upgrading to yesterday's snapshot? This isn't a panic that drops to ddb. It's just freezing with no response to anything.

Re: Flatbed scanner that works well with OpenBSD?

I have an Epson WP-4595 Network Multifunction Printer, and the scanner works fine with XSane. I also have an older Epson Perfection 2480 Photo USB scanner, but it needs a Firmware to run.

Re: usewithtor lynx core: pledge "getpw", syscall 33

On 2018/01/21 12:35, Sebastien Marie wrote: > On Sun, Jan 21, 2018 at 10:25:30AM +, Stuart Henderson wrote: > > On 2018-01-20, clematis wrote: > > > Hello, > > > 'usewithtor' (torsocks) works fine with ftp and ssh but it will core > > > with lynx. > > > running:

Re: usewithtor lynx core: pledge "getpw", syscall 33

On 2018-01-21, Juan Francisco Cantero Hurtado wrote: > Another idea. Create a special user only for tor use, then add the > proper rules to pf to pass its traffic to the tor daemon. Oh, please no. Not until it's fixed to avoid the DIOCNATLOOK crap that requires giving tor

Re: usewithtor lynx core: pledge "getpw", syscall 33

Hello, 2018-01-20 22:13 GMT+03:00 clematis : > > > > Any idea on how to torify lynx? > > Fresh tor 0.3.2.9 from ports can works as HTTP proxy: --- HTTPTunnelPort [address:]port|auto [isolation flags] Open this port to listen for proxy connections using the "HTTP CONNECT"

Re: usewithtor lynx core: pledge "getpw", syscall 33

On Sun, Jan 21, 2018 at 07:05:20AM +0100, Sebastien Marie wrote: > On Sat, Jan 20, 2018 at 07:13:54PM +, clematis wrote: > > Hello, > > 'usewithtor' (torsocks) works fine with ftp and ssh but it will core > > with lynx. > > running: usewithtor lynx > > will start lynx, resolve openbsd.org but

Re: usewithtor lynx core: pledge "getpw", syscall 33

Hi Sebastien, Stuart, Thank you both for your reply. On Sun, Jan 21, 2018 at 10:25:30AM +, Stuart Henderson wrote: > What happens if you just replace the getpwuid functions in torsocks > with NULL? They don't seem terribly useful for sending to a local tor > proxy, they're more relevant for

Re: usewithtor lynx core: pledge "getpw", syscall 33

On Sun, Jan 21, 2018 at 10:25:30AM +, Stuart Henderson wrote: > On 2018-01-20, clematis wrote: > > Hello, > > 'usewithtor' (torsocks) works fine with ftp and ssh but it will core > > with lynx. > > running: usewithtor lynx > > will start lynx, resolve openbsd.org but

Re: Flatbed scanner that works well with OpenBSD?

A couple of people started to recommend network-attached devices. I would be careful with this. Those devices often utilize an ancient embedded Linux or Windows, with lots of proprietary daemons of questionable quality ("features before security!") exposed to the network. There are tons of CVEs

Re: Kernel panic with openbsd 6.2

On 2018-01-19, Mik J wrote: > I had many kernel panic these past days. This is a 6.2 openbsd VM running o= > n esxi 5.5 > > # grep "" /tmp/if_vmx.dis I've reported a lot of vmxnet3_getbuf panics, nobody seems interested. I suggest switching to e1000 in the vmx file, this

Re: After 6.1amd64 -> 6.2amd64 upgrade namecoind malloc(): free(): error

On Sun, Jan 21, 2018 at 11:21:12AM +0100, Otto Moerbeek wrote: > On Sun, Jan 21, 2018 at 12:41:50PM +0300, Denis wrote: > > > I used namecoin on 6.1amd64 statically builded from source using boost > > 1.61 library. All works pretty fine before upgrade to 6.2amd64. > > > > I have rebuilt the the

Re: Flatbed scanner that works well with OpenBSD?

On 2018-01-19, Predrag Punosevac wrote: > Bryan Linton writes: >> Hello misc@ >> >> I'm currently looking to purchase a scanner that works well with OpenBSD. >> >> I'm aware of the list provided at: >> >> 0211038.pdf Desktop Documents Downloads Library Movies Music

Re: popen from cgi program

On 2018-01-20, Jordon wrote: > I am still learning cgi/web stuff and stumbled upon an issue.  I am > trying to popen() a program to catch what it dumps to stdout.  To start > simply, I am just trying to run uname.  I get nothing.  No errors on > popen() or pclose(), but

Re: Trying to use OpenBSD as webserver, inside home network (ADSL internet connection)

Thank you! I received several answers, mostly in private. I was able to solve the issue, but it had nothing to do with the OpenBSD machine. Some brief comments: 1) About DMZ (Demilitarised Zone), I tried configuring the router with and without putting my OpenBSD laptop in DMZ (unfortunately it

Re: usewithtor lynx core: pledge "getpw", syscall 33

On 2018-01-20, clematis wrote: > Hello, > 'usewithtor' (torsocks) works fine with ftp and ssh but it will core > with lynx. > running: usewithtor lynx > will start lynx, resolve openbsd.org but core when trying to make the > http connection. > In /var/log/messages I get:

Re: After 6.1amd64 -> 6.2amd64 upgrade namecoind malloc(): free(): error

On Sun, Jan 21, 2018 at 12:41:50PM +0300, Denis wrote: > I used namecoin on 6.1amd64 statically builded from source using boost > 1.61 library. All works pretty fine before upgrade to 6.2amd64. > > I have rebuilt the the same namecoin source with boost 1.61 lib statically. > After running it on

After 6.1amd64 -> 6.2amd64 upgrade namecoind malloc(): free(): error

I used namecoin on 6.1amd64 statically builded from source using boost 1.61 library. All works pretty fine before upgrade to 6.2amd64. I have rebuilt the the same namecoin source with boost 1.61 lib statically. After running it on OpenBSD6.2amd64 I see the error with malloc() and free() listed

Re: Intel C610 azalia (ALC888) not configuring at /dev/audio

On Fri, Jan 19, 2018 at 05:23:06PM -0800, yu...@cock.li wrote: > Hello, > > I have just installed the latest snapshot and audio is not configuring, > i.e. the output of mixerctl, audioctl, et al are "device not configured". > My motherboard is a Supermicro X10DAL-I-O, which has the Intel C610 >

Re: Problems with inteldrm on ASRock J3455-ITX (Apollo Lake)

Hi all, with the help of Chris i finally got it working and i'm happily writing this email from X! I broke it down to these two settings one has to change in the UEFI: * Disable c-states and enable legacy BIOS: - Advanced -> CPU Configuration -> CPU C States Support => Disable - Boot ->