Re: Boot installation problem on laptop with Intel N3350 CPU

On Thu, 12 Oct 2017 00:46:20 -0400 Ken Withee wrote: > I had something similar and had to change to legacy in bios or something like > that. > > Sent from ProtonMail Mobile > > On Wed, Oct 11, 2017 at 4:51 PM, Pedro Ramos wrote: > >> Hello, I am

Re: CoDel Flows

> Also, the pf.conf man page says the default qlimit is 1024, but, if I > don't specify a qlimit, pfctl –vsq shows a qlength of 50 when I was > expecting it to be 1024. What am I missing? Why would you want to have a pool of 1024 oppose to the default of 50 slots for your queue? You will

CoDel Flows

In playing around with the new CoDel/fair traffic sharing, it's not clear to me the best way to work with this when also using the previous queuing. pfctl balks when I specify a flow on the root queue with child queues present, so I only specify flows on child queues. Will CoDel still work as

Could anyone please kindly try too if "xrandr -o left/right" works on wsfb(UEFI EFIFB)-driven X? Thanks!

Hi! Just to get this one clarified, could anyone else give a try for if X driven by WSFB (that's EFIFB of UEFI) can do screen rotation? So the steps are, UEFI-boot OpenBSD 6.1 AMD64, use this /etc/X11/xorg.conf : Section "Device" Identifier "Card0" Driver "wsfb" EndSection Start X

daemon(8)

The current daemons discussion prompts a vaguely related question. We have a small but growing collection of in-house daemons written in Go. Go's runtime isn't amenable to the fork/setsid dance you would normally do to push a daemon process into the background. As a workaround, I ported

Re: Automatically restarting services/daemons after crash

> That's sensible, but if money or lives were on the line, I think It'd > be better to have a running but potentially vulnerable service. For my > use case, this is completely acceptable, I'm just curious about the > implications for others. Then you can do that on your own, if it suits your use

Re: Automatically restarting services/daemons after crash

>If software has a bug, you want to fix it. You don't want to keep running it. That's sensible, but if money or lives were on the line, I think It'd be better to have a running but potentially vulnerable service. For my use case, this is completely acceptable, I'm just curious about the

Re: Automatically restarting services/daemons after crash

> Perhaps I'm mistaken, but it doesn't seem like there's a facility for > automatically restarting daemons after a crash or similar. Is the idea > just that daemons should be designed to not crash? Yes. Fail closed. It is the only secure thing to do. > I'm familiar with 3rd party tools like

Automatically restarting services/daemons after crash

Perhaps I'm mistaken, but it doesn't seem like there's a facility for automatically restarting daemons after a crash or similar. Is the idea just that daemons should be designed to not crash? I'm familiar with 3rd party tools like daemontools and such that provide these facilities, but I can't

Re: Need help setting http headers using relayd (and httpd)

There is a book called relayd and httpd. I think it has what you need. V/r, Bryan > On Oct 12, 2017, at 1:33 PM, Andreas Thulin wrote: > > Hi! > > Before anything, thanks for yet another awesome OpenBSD release! I’ll > extend my gratitude into the pockets of the

Re: vmm issues - vioblk_notifyq: unsupported command 0x8

On Thu, Oct 12, 2017 at 03:15:45PM -0700, Mike Larkin wrote: > On Thu, Oct 12, 2017 at 05:07:24PM -0500, Andrew Daugherity wrote: > > On Tue, Oct 3, 2017 at 3:49 AM, Jiri B wrote: > > >> > I was able to boot opensuse from that dvd, although later on I got an > > >> > error in the

Re: vmm issues - vioblk_notifyq: unsupported command 0x8

On Thu, Oct 12, 2017 at 05:07:24PM -0500, Andrew Daugherity wrote: > On Tue, Oct 3, 2017 at 3:49 AM, Jiri B wrote: > >> > I was able to boot opensuse from that dvd, although later on I got an > >> > error in the installer :/ > >> > >> This was because the installer couldn't locate

Re: VMM Serial Console issues with Alpine Linux in -current

On Fri, Oct 13, 2017 at 03:55:25AM +0700, Kamil Shakirov wrote: > Hello Mike, > > Just wanted to update you that I can now successfully run Debian 9 x64 VM on > recently released OpenBSD 6.2. All I did was fresh Debian install in Qemu, > then configured serial console in grub settings. > >

Re: VMM Serial Console issues with Alpine Linux in -current

On Fri, Oct 13, 2017 at 03:55:25AM +0700, Kamil Shakirov wrote: > Hello Mike, > > Just wanted to update you that I can now successfully run Debian 9 x64 VM on > recently released OpenBSD 6.2. All I did was fresh Debian install in Qemu, > then configured serial console in grub settings. > >

Re: Openbsd 6.1 and Current Console Freezes and lockup Proxmox PVE5.0

On Thu, Oct 12, 2017 at 10:36:42PM +0200, Michał Koc wrote: > > > On Thu, Oct 12, 2017 at 01:23:36PM +0200, Michał Koc wrote: > > > On Sun, Oct 08, 2017 at 11:59:52PM +0200, Oliver Marugg wrote: > > > > > On 7 Oct 2017, at 22:01, Mike Larkin wrote: > > > > > > > > > > > On Sat, Oct 07, 2017 at

Re: vmm issues - vioblk_notifyq: unsupported command 0x8

On Tue, Oct 3, 2017 at 3:49 AM, Jiri B wrote: >> > I was able to boot opensuse from that dvd, although later on I got an >> > error in the installer :/ >> >> This was because the installer couldn't locate the "dvd", correct? > > Unable to create repository > from URL

Re: VMM Serial Console issues with Alpine Linux in -current

Hello Mike, Just wanted to update you that I can now successfully run Debian 9 x64 VM on recently released OpenBSD 6.2. All I did was fresh Debian install in Qemu, then configured serial console in grub settings. Thank you for your work on vmm. By the way, is it possible to allocate more

Re: Openbsd 6.1 and Current Console Freezes and lockup Proxmox PVE5.0

On Thu, Oct 12, 2017 at 01:23:36PM +0200, Michał Koc wrote: On Sun, Oct 08, 2017 at 11:59:52PM +0200, Oliver Marugg wrote: On 7 Oct 2017, at 22:01, Mike Larkin wrote: On Sat, Oct 07, 2017 at 02:19:58PM +0200, Oliver Marugg wrote: Just to add a 4th situation of hangs: Login via proxmox

Re: size of size_t

On Thu, Oct 12, 2017 at 3:18 PM, wrote: > On a related note, would you folks be interested in patches removing > said assumpting of equivalence from programs like dd(1)? I would assume yes, unless those patches broke dd on some platforms. (Patches which break things tend to

RE: size of size_t

"Ian Sutton" wrote: > > An important thing to ask yourself before suggesting things like this > is "if this is such an obvious and trivial improvement, then why > hasn't anyone already done it?". To put things in perspective, we had > an entire release primarily predicated upon

Re: size of size_t

On Thu, Oct 12, 2017 at 12:58 PM, wrote: > Hi, > > I just discovered, to my dismay, that size_t is only 32 bits, even on > 64-bit processors. Is there a particular pressing reason for this? A > quick investigation reveals that even dd(1) is affected -- this is IMO > not good. >

RE: size of size_t

Hi, "Janne Johansson" wrote: > >> Okay, I don't have a 64-bit machine running OpenBSD to check -- but is >> 'long' >> 64-bits on those? > > How did you manage to come to the first conclusion, given the second part > later? *shrugs* an incorrect assumption.

Re: size of size_t

2017-10-12 20:04 GMT+02:00 : > Hi, > > >> I just discovered, to my dismay, that size_t is only 32 bits, even on > >> 64-bit processors. > Okay, I don't have a 64-bit machine running OpenBSD to check -- but is > 'long' > 64-bits on those? How did you manage to come to the first

RE: RE: FU: size of size_t

theo wrote: > > Time to begin buffing the 'd' key. Learning never ends, does it? --schaafuit.

RE: amd64 OpenBSD 6.2 doesn't see hard disks when controller in RAID mode

theo wrote: > > Unfortunately we are still stuck here: > > 0. No code being developered, email and wiki discussion, gnashing of teeth Seems par for the course these days. Blah blah, entitlement, whatnot, and no work being done. --zeur.

RE: RE: size of size_t

theo wrote: > > No, not really. If you won't use the publically available source tree > and vast amounts of documentation about POSIX but instead jump > straight towards assertive dialogue on a mailing list, then I don't > see how we can help. Funny thing is, you already explained in your other

Re: reordering libraries:/etc/rc[443]: ./test-ld.so: Permission denied

On Tue, Oct 10, 2017 at 06:35:49PM +, Kevin Chadwick wrote: > On Wed, 27 Sep 2017 21:43:48 -0500 > > > > Why is this happening, and is there anything that I should do to > > correct > > > > The system has been getting more and more dynamic to make attackers > fumble in the dark. > > > the

Re: amd64 OpenBSD 6.2 doesn't see hard disks when controller in RAID mode

> On Wed, Oct 11, 2017 at 11:01 AM, Stuart Henderson > wrote: > > What is not good is when you do have a RAID array, the controller is > > in RAID mode, but OpenBSD doesn't understand the metadata, so it corrupts > > data on the disk. > > > > This is a difficult area. We

RE: FU: size of size_t

theo wrote: > > off_t is used where it should be used. size_t is used where it should > be used. In that case I change the proposal to the introduction of an uoff_t, or is there already something appropriate? If so, why doesn't dd(1) use it? > You are showing inexperience. Yes, you got that

Re: amd64 OpenBSD 6.2 doesn't see hard disks when controller in RAID mode

On Wed, Oct 11, 2017 at 11:01 AM, Stuart Henderson wrote: > What is not good is when you do have a RAID array, the controller is > in RAID mode, but OpenBSD doesn't understand the metadata, so it corrupts > data on the disk. > > This is a difficult area. We don't want to

Re: RE: size of size_t

> >> I just discovered, to my dismay, that size_t is only 32 bits, even on > >> 64-bit processors. Is there a particular pressing reason for this? A > >> quick investigation reveals that even dd(1) is affected -- this is IMO > >> not good. > > > > You are wrong. > > > > limits.h:#define SIZE_T_MAX

RE: size of size_t

Hi, >> I just discovered, to my dismay, that size_t is only 32 bits, even on >> 64-bit processors. Is there a particular pressing reason for this? A >> quick investigation reveals that even dd(1) is affected -- this is IMO >> not good. > > You are wrong. > > limits.h:#define SIZE_T_MAX ULONG_MAX

Re: FU: size of size_t

> I wrote: > > I'd suggest, given modern file sizes, that we bump it to 64 bits on all > > platforms. > > Oh, and off_t *is* 64 bits, at least on i386; pity most routines don't > use it: they use size_t. off_t is used where it should be used. size_t is used where it should be used. You are

FU: size of size_t

I wrote: > I'd suggest, given modern file sizes, that we bump it to 64 bits on all > platforms. Oh, and off_t *is* 64 bits, at least on i386; pity most routines don't use it: they use size_t. --schaafuit.

Re: size of size_t

> I just discovered, to my dismay, that size_t is only 32 bits, even on > 64-bit processors. Is there a particular pressing reason for this? A > quick investigation reveals that even dd(1) is affected -- this is IMO > not good. You are wrong. limits.h:#defineSIZE_T_MAX ULONG_MAX

size of size_t

Hi, I just discovered, to my dismay, that size_t is only 32 bits, even on 64-bit processors. Is there a particular pressing reason for this? A quick investigation reveals that even dd(1) is affected -- this is IMO not good. I'd suggest, given modern file sizes, that we bump it to 64 bits on all

Need help setting http headers using relayd (and httpd)

Hi! Before anything, thanks for yet another awesome OpenBSD release! I’ll extend my gratitude into the pockets of the Foundation and finally donate this time. Then: I’m a relayd virgin. Consider all the following a lab exercise, I want to learn and understand more. My target: Understanding how

Re: Openbsd 6.1 and Current Console Freezes and lockup Proxmox PVE5.0

On Thu, Oct 12, 2017 at 01:23:36PM +0200, Michał Koc wrote: > On Sun, Oct 08, 2017 at 11:59:52PM +0200, Oliver Marugg wrote: > > > On 7 Oct 2017, at 22:01, Mike Larkin wrote: > > > > > > > On Sat, Oct 07, 2017 at 02:19:58PM +0200, Oliver Marugg wrote: > > > > > Just to add a 4th situation of

Re: Trouble with VMM/VMD

On Thu, Oct 12, 2017 at 10:24:39AM +0200, Roar Waagsbø wrote: > Sorry. > > I will try to clear this up. > > My problem is: > > I setup a openbsd box, and setup vmm. > > After one week, I noticed that one of my vms had shutdown. > I started it back up again without thinking so much about it. >

Re: Porter's Handbook obsolete info

Hi Steve, Steve Shockley wrote on Wed, Oct 11, 2017 at 08:11:24PM -0400: > FYI, http://www.openbsd.org/faq/ports/specialtopics.html refers to the > security/nessus port, which was retired some time ago. The section does > show a useful example though, but I'm not sure what would make a good

Re: Trouble with VMM/VMD

Sorry. I will try to clear this up. My problem is: I setup a openbsd box, and setup vmm. After one week, I noticed that one of my vms had shutdown. I started it back up again without thinking so much about it. After a few days my other vm had shutdown. Then I thought maybe it was an error in

Re: reordering libraries:/etc/rc[443]: ./test-ld.so: Permission denied

You own all the pieces. > RO /usr also breaks the shiny new kernel relinking. > > So the best I have come up with is crontab lines > > @reboot sleep 60 mount -urf /usr > > The 60 may be too short on very old systems. > > Perhaps it's time to drop the ro but I'm quite attached to my security >

Re: Openbsd 6.1 and Current Console Freezes and lockup Proxmox PVE5.0

Dear all, I tried to run OpenBSD 6.2 on Debian GNU/Linux 9.2 and qemu-kvm 2.8 no issue so far too. Proxmox is using Debian GNU/Linux as the core OS. Next step will be to use the same version of qemu-kvm that Proxmox 5.0 ship by default. Regards, On 12/10/2017 13:38, Scott Reese wrote:

I'm stuck with pf - can someone with some experience check my rules please? Thanks

I have been reading through the Book of PF (3rd edition) and other resources on the web (FAQ), so far so good but I'm hitting some roadblocks. This router I have built is also acting as a client to an external VPN server, it works and my client is getting a connection just fine. The problem

Re: Openbsd 6.1 and Current Console Freezes and lockup Proxmox PVE5.0

> On 8 Oct 2017, at 23:59, Oliver Marugg wrote: >>> >> Thanks Mike, will do so. The proxmox guys have also the idea that it >> could be a bug in kvm hypervisor (which is the hypervisor part for >> proxmox) and will affect OpenBSD since 4.9, they wrote me in their >> public forum. As far as I

Re: Openbsd 6.1 and Current Console Freezes and lockup Proxmox PVE5.0

On Sun, Oct 08, 2017 at 11:59:52PM +0200, Oliver Marugg wrote: On 7 Oct 2017, at 22:01, Mike Larkin wrote: On Sat, Oct 07, 2017 at 02:19:58PM +0200, Oliver Marugg wrote: Just to add a 4th situation of hangs: Login via proxmox (pve)/kvm serial console (via noVNC), login successful: Vm guest in

Re: amd64 OpenBSD 6.2 doesn't see hard disks when controller in RAID mode

On Thu, Oct 12, 2017 at 03:16:44AM +0300, Rostislav Krasny wrote: > Boasty? I just try to help you to fix this bug by providing the > information I've found. It's hard to fix it by myself because of the > several times mentioned reasons. If you don't want to fix it just > because you don't want I

Re: reordering libraries:/etc/rc[443]: ./test-ld.so: Permission denied

On Tue, 10 Oct 2017 19:35:49 +0100 > From: Kevin Chadwick > To: misc@openbsd.org > Subject: Re: reordering libraries:/etc/rc[443]: ./test-ld.so: > Permission denied Date: Tue, 10 Oct 2017 19:35:49 +0100 > > On Wed, 27 Sep 2017 21:43:48 -0500 > > > > Why is this

Re: sysmerge is not needed when updating to 6.2?

On Thu, 12 Oct 2017 09:34:44 + > But I have only one question: Is sysmerge not longer needed for > updating process like in previous releases? It shall tell you if you need to re-run manually in the boot output for edited files.

Re: sysmerge is not needed when updating to 6.2?

On Thu, Oct 12, 2017 at 11:45:24AM +0200, Theo Buehler wrote: > > But I have only one question: Is sysmerge not longer needed for > > updating process like in previous releases? > > Since 6.0 the installer installs an rc.sysmerge that runs 'sysmerge -b' > on first boot of the updated system. >

Re: sysmerge is not needed when updating to 6.2?

On Thu, Oct 12, 2017 at 09:34:44AM +, C. L. Martinez wrote: > But I have only one question: Is sysmerge not longer needed for updating > process like in previous releases? sysmerge will be run when booting the system after the upgrade.

Re: sysmerge is not needed when updating to 6.2?

> But I have only one question: Is sysmerge not longer needed for > updating process like in previous releases? Since 6.0 the installer installs an rc.sysmerge that runs 'sysmerge -b' on first boot of the updated system.

sysmerge is not needed when updating to 6.2?

Hi all, Today I have updated two OpenBSD 6.1 hosts to 6.2 after reading the FAQ and all works really well. Congratulations to all OpenBSD's developers for their hard work. But I have only one question: Is sysmerge not longer needed for updating process like in previous releases? Many

spamd pf rule question

Hi there, it's a quiet simple question :) I have a rule like this pass in log(to $log_spamd_if) on $ext_if proto tcp to port smtp rdr-to 127.0.0.1 port spamd and was wondering if it's better to use pass in log(to $log_spamd_if) on $ext_if proto tcp to port smtp divert-to 127.0.0.1 port

Re: amd64 OpenBSD 6.2 doesn't see hard disks when controller in RAID mode

On 2017/10/12 00:18, Rostislav Krasny wrote: > On Wed, Oct 11, 2017 at 7:01 PM, Stuart Henderson > wrote: > > On 2017-10-11, Rostislav Krasny wrote: > >> On Wed, Oct 11, 2017 at 6:28 AM, Eric Furman > >> wrote: > >>> On Tue,

Re: php-fpm and OpenBSD 6.2

Hi Peter, thank you for the hint :) In the end I would simply try to run a php script and see if it works ;) regards Markus Am 12.10.2017 um 10:20 schrieb Peter Faiman: On Oct 12, 2017, at 00:39, Markus Rosjat wrote: Hi there, I can't find a php-fpm package under 6.2 but

Re: php-fpm and OpenBSD 6.2

On 10/12/17 09:39, Markus Rosjat wrote: > Hi there, > > I can't find a php-fpm package under 6.2 but there are php-fastcgi packages. > Is this the new php-fpm naming convention starting with 6.2 or do I get this > wrong here? > > regards > php-fpm is currently part of the PHP package

Re: php-fpm and OpenBSD 6.2

> On Oct 12, 2017, at 00:39, Markus Rosjat wrote: > > Hi there, > > I can't find a php-fpm package under 6.2 but there are php-fastcgi packages. > Is this the new php-fpm naming convention starting with 6.2 or do I get this > wrong here? > > regards > > -- > Markus Rosjat

Re: OpenBSD 6.2: okular crash if passed any file

On 10/12/17 09:53, Dorian Büttner wrote: On 10/11/17 20:03, Federico Giannici wrote: Hi. I just upgraded to OpenBSD 6.2 (amd64). Everything seems OK... apart from okular (the KDE files viewer). Am I the only one with is problem? I'm using snapshots and I've seen this for say 3 months or

Re: Trouble with VMM/VMD

On Thu, Oct 12, 2017 at 09:44:07AM +0200, Roar Waagsbø wrote: > Hi. > > No the console is not stuck. > > I check doas vmctl status right after its stuck and its gone.. So I dont > run it again. > > So its not just a stuck console im afraid, it shut downs my vm :/ > > Not sure? Just what I read

Re: Upgrade 6.1 -> 6.2: No /mnt/etc/myname

This is, indeed, a symlink. Thanks for opening my eyes. //mxb > 12 okt. 2017 kl. 01:42 skrev Steven McDonald : > > This is a complete guess, but is /etc/myname a symbolic link? If it is > a symlink to an absolute path, that is unlikely to exist in the bsd.rd >

Re: OpenBSD 6.2: okular crash if passed any file

On 10/11/17 20:03, Federico Giannici wrote: Hi. I just upgraded to OpenBSD 6.2 (amd64). Everything seems OK... apart from okular (the KDE files viewer). Am I the only one with is problem? I'm using snapshots and I've seen this for say 3 months or so. I could verify this on a second amd64

RE: amd64 OpenBSD 6.2 doesn't see hard disks when controller in RAID mode

Don't mind if I jump in. "Rostislav Krasny" wrote: > > Boasty? I just try to help you to fix this bug by providing the > information I've found. It's hard to fix it by myself because of the > several times mentioned reasons. If you don't want to fix it just > because you

Re: Trouble with VMM/VMD

Hi. No the console is not stuck. I check doas vmctl status right after its stuck and its gone.. So I dont run it again. So its not just a stuck console im afraid, it shut downs my vm :/ Not sure? Just what I read in the documentation and guide. Its just for booting a new bsd.rd to upgrade to

php-fpm and OpenBSD 6.2

Hi there, I can't find a php-fpm package under 6.2 but there are php-fastcgi packages. Is this the new php-fpm naming convention starting with 6.2 or do I get this wrong here? regards -- Markus Rosjatfon: +49 351 8107223mail: ros...@ghweb.de G+H Webservice GbR Gorzolla, Herrmann

Re: The difference between binutils and binutils-2.17?

Hi Philip, Got it! Thanks very much for your response! Best Regards Nan Xiao On Thu, Oct 12, 2017 at 3:22 PM, Philip Guenther wrote: > On Thu, Oct 12, 2017 at 12:14 AM, Nan Xiao wrote: >> >> Maybe a stupid question, as you have mentioned, >> "so

Re: Trouble with VMM/VMD

On Thu, Oct 12, 2017 at 09:16:39AM +0200, Roar Waagsbø wrote: > Hi. > > I've enabled the AHCI in bios now. > > I started the vm now, and downloaded the newest -current and that worked. > > But when I do -c -b to boot I get into console and after a while it just > stops. > > I get into console,

Re: The difference between binutils and binutils-2.17?

On Thu, Oct 12, 2017 at 12:14 AM, Nan Xiao wrote: > > Maybe a stupid question, as you have mentioned, > "so the in-tree gdb is rapidly declining in utility already.", and > egdb seems a better gdb, why does OpenBSD still keep old in-tree gdb > rather than replacing it

Re: Trouble with VMM/VMD

Hi. I've enabled the AHCI in bios now. I started the vm now, and downloaded the newest -current and that worked. But when I do -c -b to boot I get into console and after a while it just stops. I get into console, press U for upgrade and then it hangs here: Welcome to the OpenBSD/amd64 6.2

Re: The difference between binutils and binutils-2.17?

Hi Philip, Thanks for your detailed explanation! Maybe a stupid question, as you have mentioned, "so the in-tree gdb is rapidly declining in utility already.", and egdb seems a better gdb, why does OpenBSD still keep old in-tree gdb rather than replacing it will new egdb? Thanks in advance!