Re: Qemu Agent assistance needed

[Strahil Nikolov]

Yes , but not only.
I'm using oVirt - a KVM management tool and I can currently make a snapshot 
only by pausing the VM or by completely stopping it first.
For now, it's not a big deal - as I'm still exploring openBSD , but who knows.
Also the management interface cannot provide details about CPU and RAM usage , 
nor I cannot gracefully shut the VM down from the interface.
The oVirt manager allows automatic evacuation of the VM, if it requires more 
memory/cpu than the host can currently providing (for a lab overcommitting is 
normal).

I'm just looking to enable those fancy things that make our life easier.

Best Regards,
Strahil Nikolov

On April 29, 2019 12:07:32 AM GMT+03:00, Tom Smyth 
 wrote:
>Hello Strahil,
>what are you trying to achieve with the Qemu Guest Agent ?
>
>is it  quiescing during backups .>?
>
>
>
>
>
>
>On Sun, 28 Apr 2019 at 20:59, Kristjan Komloši
> wrote:
>>
>> On Sun, 2019-04-28 at 11:10 +, Strahil Nikolov wrote:
>> > Hi All,
>> > I am new to openBSD and I really like the idea. Sadly I do not have
>> > suitable hardware to run on , thus I use KVM and I would be happy
>if
>> > anyone hint me of a working solution for Qemu Guest Agent.
>> > Anything I dig up (via google searches) show up only suggestions ,
>> > but nothing more.In openBSD 6.4  I successfully installed qemu (and
>> > thus the agent), but I can't understand how to get the device
>needed
>> > for communication with the host up and running.
>> > As I mainly know linux - I know that we need a kernel module that
>to
>> > be loaded and with combination of udev rules - the devices is
>created
>> > on the necessary location and with the correct rights.According to
>> > many google findings - openBSD doesn't support any more loadable
>> > kernel module support.
>> > I have tried to figure it out by myself, but I cannot find the
>> > necessary module needed, nor how to load it in a proper manner.
>> > Any hint is well appreciated.
>> > Best Regards,Strahil Nikolov
>>
>> Kernel modules don't exist under OpenBSD to ensure security, so don't
>> go there. Communication with host is probably best done through the
>> serial console. Take a look at the boot.conf(8) manpage.
>>

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: headphone volume levels cannot be manipulated by mixerctl

[Christian Weisgerber]

On 2019-04-27, Christian Weisgerber  wrote:

> It is my theoretical understanding that USB audio gadgets typically
> come with a uhid(4) device, as does yours above, and you would use
> usbhidctl(1) to list and manipulate the available controls.

No, that is wrong.

Looking over uaudio.c, I now see that mixer controls are an inherent
part of the USB audio spec and that the driver automatically provides
them.

So the correct answer is this: If your USB audio gadget attaches
as audioN, use "mixerctl -f /dev/mixerN" to access the corresponding
controls.  If you don't specify a device, mixerctl uses /dev/mixer,
which by default is a symlink to /dev/mixer0.  You can point this
symlink to a different unit.  Alternatively, you can set MIXERDEVICE
in the enironment.

(Personally, I have only used USB audio dongles to add an S/PDIF
output to machines that lacked one, so the mixer didn't really come
up.)

-- 
Christian "naddy" Weisgerber  na...@mips.inka.de

Re: Xorg blanks until I switch to a TTY and back on 6.5

[Jordan Geoghegan]

On 4/28/19 4:26 PM, Charles wrote:

Hello list,

Ever since the new inteldrm driver got merged into -current, shortly
before the 6.5 release, I'm seeing an odd new behavior on my Thinkpad
T430 -- when an external display is connected, Xorg blanks all screens
(but the mouse can still be seen) until I switch to a TTY and back with
(i.e. C-A-F4 then C-A-F5) after which point it goes back to normal.



You're not the only one. I've had the same thing happen on my Thinkpad 
X1C6 which is running the April 24 snapshot I think.

Re: Xorg blanks until I switch to a TTY and back on 6.5

[Daniel Bolgheroni]

On Sun, Apr 28, 2019 at 11:26:54PM +, Charles wrote:
> Is anyone else experiencing this issue on third gen core-I series Intel
> chips with integrated graphics? Or on any other chips for that matter?

Yes, can confirm on a ThinkPad X220.

Also, with the latest snapshot, the correct modes for LVDS-1 and HDMI-1 (an
external 2560x1080 monitor) are not correctly detected. In fact, the 2560x1080
mode isn't listed by xrandr.

Thank you.

/var/log/Xorg.0.log:
[  7548.941] (WW) checkDevMem: failed to open /dev/xf86 and /dev/mem
(Operation not permitted)
Check that you have set 'machdep.allowaperture=1'
in /etc/sysctl.conf and reboot your machine
refer to xf86(4) for details
[  7548.941]linear framebuffer access unavailable
[  7548.966] (--) Using wscons driver on /dev/ttyC4
[  7548.986]
X.Org X Server 1.19.7
Release Date: 2019-03-02
[  7548.986] X Protocol Version 11, Revision 0
[  7548.986] Build Operating System: OpenBSD 6.5 amd64
[  7548.986] Current Operating System: OpenBSD bike.home 6.5 GENERIC.MP#38 amd64
[  7548.986] Build Date: 28 April 2019  07:11:21AM
[  7548.986]
[  7548.987] Current version of pixman: 0.36.0
[  7548.987]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[  7548.987] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[  7548.987] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Apr 28 14:03:51 
2019
[  7548.987] (==) Using system config directory 
"/usr/X11R6/share/X11/xorg.conf.d"
[  7548.990] (==) No Layout section.  Using the first Screen section.
[  7548.990] (==) No screen section available. Using defaults.
[  7548.990] (**) |-->Screen "Default Screen Section" (0)
[  7548.990] (**) |   |-->Monitor ""
[  7548.990] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[  7548.990] (==) Automatically adding devices
[  7548.990] (==) Automatically enabling devices
[  7548.990] (==) Not automatically adding GPU devices
[  7548.990] (==) Max clients allowed: 256, resource mask: 0x1f
[  7548.991] (==) FontPath set to:
/usr/X11R6/lib/X11/fonts/misc/,
/usr/X11R6/lib/X11/fonts/TTF/,
/usr/X11R6/lib/X11/fonts/OTF/,
/usr/X11R6/lib/X11/fonts/Type1/,
/usr/X11R6/lib/X11/fonts/100dpi/,
/usr/X11R6/lib/X11/fonts/75dpi/
[  7548.991] (==) ModulePath set to "/usr/X11R6/lib/modules"
[  7548.991] (II) The server relies on wscons to provide the list of input 
devices.
If no devices become available, reconfigure wscons or disable 
AutoAddDevices.
[  7548.991] (II) Loader magic: 0xff502cd
[  7548.991] (II) Module ABI versions:
[  7548.991]X.Org ANSI C Emulation: 0.4
[  7548.991]X.Org Video Driver: 23.0
[  7548.991]X.Org XInput driver : 24.1
[  7548.991]X.Org Server Extension : 10.0
[  7548.991] (--) PCI:*(0:0:2:0) 8086:0126:17aa:21da rev 9, Mem @ 
0xf000/4194304, 0xe000/268435456, I/O @ 0x5000/64
[  7548.991] (II) LoadModule: "glx"
[  7548.992] (II) Loading /usr/X11R6/lib/modules/extensions/libglx.so
[  7548.996] (II) Module glx: vendor="X.Org Foundation"
[  7548.996]compiled for 1.19.7, module version = 1.0.0
[  7548.996]ABI class: X.Org Server Extension, version 10.0
[  7548.997] (==) Matched modesetting as autoconfigured driver 0
[  7548.997] (==) Assigned the driver to the xf86ConfigLayout
[  7548.997] (II) LoadModule: "modesetting"
[  7548.997] (II) Loading /usr/X11R6/lib/modules/drivers/modesetting_drv.so
[  7548.998] (II) Module modesetting: vendor="X.Org Foundation"
[  7548.998]compiled for 1.19.7, module version = 1.19.7
[  7548.998]Module class: X.Org Video Driver
[  7548.998]ABI class: X.Org Video Driver, version 23.0
[  7548.998] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[  7549.010] (**) modeset(0): claimed PCI slot 0@0:2:0
[  7549.010] (II) modeset(0): using default device
[  7549.027] (II) modeset(0): Creating default Display subsection in Screen 
section
"Default Screen Section" for depth/fbbpp 24/32
[  7549.027] (==) modeset(0): Depth 24, (==) framebuffer bpp 32
[  7549.027] (==) modeset(0): RGB weight 888
[  7549.027] (==) modeset(0): Default visual is TrueColor
[  7549.027] (II) Loading sub module "glamoregl"
[  7549.027] (II) LoadModule: "glamoregl"
[  7549.030] (II) Loading /usr/X11R6/lib/modules/libglamoregl.so
[  7549.036] (II) Module glamoregl: vendor="X.Org Foundation"
[  7549.036]compiled for 1.19.7, module version = 1.0.0
[  7549.036]ABI class: X.Org ANSI C Emulation, version 0.4
[  7549.036] (II) glamor: OpenGL accelerated X.org driver based.
[  7549.069] (II) glamor: EGL version 1.4:
[  7549.073] (II) modeset(0): glamor initialized
[  7549.073] (II) modeset(0): Output LVDS-1 has no monitor section
[  7549.075] (II) modeset(0): Output 

Re: [6.5] minidlna error: accept(http): Too many open files

[Todd C . Miller]

On Sun, 28 Apr 2019 22:35:36 +0200, "Stephane HUC \"PengouinBSD\"" wrote:

> After upgrading OpenBSD from 6.4 to 6.5, I've problem to use minidlna.
> It fill the /var/log/minidlna/minidlna.log with severals errors
> messages, as:
> [2019/04/25 15:26:29] monitor_kqueue.c:226: error:
> open(/home/z2/Music/xyz) [Too many open files]
> (...)
> [2019/04/25 20:15:05] minidlna.c:165: error: accept(http): Too many
> open files

It seems that minidlna now tries to keep every directory open to
tell when there is a modification.  My suggestion is to disable
inotify in /etc/minidlna.conf.  E.g.

# set this to no to disable kqueue monitoring to automatically discover new 
files
# note: the default is yes
inotify=no

That fixed the problem for me.

 - todd

Re: Code of Conduct location

[Daniel Ouellet]

On 4/28/19 9:33 AM, Rachel Roch wrote:
> Apr 28, 2019, 9:16 AM by cho...@jtan.com :
> 
>> Strahil Nikolov writes:
>>
>>> Hello All,
>>>
>>> can someone point me to the link of the OpenBSD code of Conduct ?
>>>
>>
>> I believe OpenBSD's code of conduct can be summed up as "if you are the
>> type of person who needs a code of conduct to teach to you how to human
>> then you are not welcome here".
>>
>> At least I hope so.
>>
>> Matthew
>>
> 
> I always thought it could be summed up as "Don't piss off Theo".  ;-)

That's a good one! It made me chuckles today thanks for that!

I needed to smile today.

And it's mostly true, If you are an ass, you will get him on you real fast!.

So don't be an ass and you will be fine..

Xorg blanks until I switch to a TTY and back on 6.5

[Charles]

Hello list,

Ever since the new inteldrm driver got merged into -current, shortly
before the 6.5 release, I'm seeing an odd new behavior on my Thinkpad
T430 -- when an external display is connected, Xorg blanks all screens
(but the mouse can still be seen) until I switch to a TTY and back with
(i.e. C-A-F4 then C-A-F5) after which point it goes back to normal.

I'm glad the new inteldrm driver got merged, since it fixes several
other video issues I was having. This problem is very minor since the
workaround is just a few extra keystrokes when I dock or undock, but it
is nevertheless annoying.

Is anyone else experiencing this issue on third gen core-I series Intel
chips with integrated graphics? Or on any other chips for that matter?

I checked Xorg.0.log and didn't see anything suspicious. I also tried
disabling monitor hotplugging via Xorg.conf, but I either did it wrong
or it had no effect.

I would attach xorg logs and dmesg, but AFAIK misc@ does not allow
attachments, and I don't want to annoy people with that much inline
info.

Thanks,

~ Charles

Re: [6.5] Xfce: problem with shutdown menu

[chohag]

Theo de Raadt writes:
> "Stephane HUC \"PengouinBSD\""  wrote:
>
> > Hi, Tom. Ty for your reply.
> > 
> > On my file /etc/doas.conf, i've only one line, as:
> > 
> > "permit nopass setenv { ENV PS1 SSH_AUTH_SOCK } :wheel"
^

> So a javascript exploit in your browser can perform a rm -rf.

... everywhere.

Matthew

Re: [6.5] Xfce: problem with shutdown menu

[Theo de Raadt]

"Stephane HUC \"PengouinBSD\""  wrote:

> Hi, Tom. Ty for your reply.
> 
> On my file /etc/doas.conf, i've only one line, as:
> 
> "permit nopass setenv { ENV PS1 SSH_AUTH_SOCK } :wheel"

So a javascript exploit in your browser can perform a rm -rf.

Cool.

Re: [6.5] Cups + Gutenprint: file rastertogutenprint not found

[Predrag Punosevac]

Stephane HUC wrote:
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> Hi, (just FYI)
> 
> After upgrading OpenBSD from 6.4 to 6.5, I had this problem to print.
> The Webadmin of Cups informs me with this message:
> 
> "/usr/local/libexec/cups/filter/rastertogutenprint.5.2 not found!"
> 
> On the parameters about my printer, (an MFP Epson BX525WD on my local
> network), I change with the new version of Gutenprint's driver. (v5.3.x)
Did you notice that you changed the driver into v5.3 but Webadmin
complains about missing rastertogutenprint.5.2..That doesn't make sense
at all. I would expect that Webadmin complain about missing
rastertogutenprint.5.3. Did you check if you do have
rastertogutenprint.5.3 on your system? Did you check if
rastertogutenprint.5.3 is in CVS source Gutenprint 5.3 which you just
installed. 

Anything in the log files? What is the username you are using for CUPS?
I neither use CUPS nor Gutenprint but searching for similar problems as
yours turns a dozen or so leads. 

IMHO ports list might be a better suitable for further discussion if
this turns out to be the case of the missing file from a package
(happened before due to the upstream).

Cheers,
Predrag


> .
> 
> And, that's run correctly!
> 
> 
> - -- 
> ~ " Fully Basic System Distinguish Life! " ~ " Libre as a BSD " +=<<<
> - 
> Stephane HUC as PengouinBSD or CIOTBSD
> b...@stephane-huc.net
> -BEGIN PGP SIGNATURE-
> 
> iHUEARYKAB0WIQScTRXz7kMlZfGpDZMTq98t3AMG7wUCXMYQ0gAKCRATq98t3AMG
> 78/hAQDHE2kdDyXuuXxpuAbrgPkoVd32HjhmFC05zF56YsJvFAD+L5Q4oxzBIull
> qbouLJ8o1tOcdgbtTo1gZDhfC6NVggk=
> =izfF
> -END PGP SIGNATURE-
> 
> 

Re: [6.5] Xfce: problem with shutdown menu

[Stephane HUC "PengouinBSD"]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512


Hi, Tom. Ty for your reply.

On my file /etc/doas.conf, i've only one line, as:

"permit nopass setenv { ENV PS1 SSH_AUTH_SOCK } :wheel"

And, my userinfo:

(...)
groups    *** wheel operator wsrc _saned
(...)


On 4/28/19 11:09 PM, Tom Smyth wrote:
> Hi Stephane > > I would imagine it is because you dont have shutdown 
> privilege as
the > user in Xfce, > > check your doas config ... > > BTW i was just
lazy and opened a privleged shell and ran halt -p > > > > > On Sun, 28
Apr 2019 at 22:05, Stephane HUC "PengouinBSD" > 
wrote: >> > Hi, (just FYI) > > After upgrading OpenBSD from 6.4 to 6.5,
I cant anymore to stop my > machine when I click on menu shutdown into
Xfce session. > The result is a logout, and not shutdown. > > As see,
the reply by Landry to one user, on forum "Daemons - BSD", it > seems
necessary to add the id user at the group operator. > I try this
solution, log me out, and login new... and the menu run > correctly! > >
http://daemonforums.org/showthread.php?t=10971#post66453 > > >> > > - --
~ " Fully Basic System Distinguish Life! " ~ " Libre as a BSD "    +=<<<
- 
Stephane HUC as PengouinBSD or CIOTBSD
b...@stephane-huc.net
-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQScTRXz7kMlZfGpDZMTq98t3AMG7wUCXMYYWwAKCRATq98t3AMG
72ksAP4/elW7kNVyJ1H8UF2HpmPaFvUpzw/zV/TCHZ6ProMoLgEAkNDObtHrHGrs
zLHNSLU944CForBJoU197/TzhkQFIAk=
=7kjS
-END PGP SIGNATURE-

Re: [6.5] Xfce: problem with shutdown menu

[Ingo Schwarze]

Hi Tom,

Tom Smyth wrote on Sun, Apr 28, 2019 at 10:09:54PM +0100:

> I would imagine it is because you dont have shutdown privilege as the
> user in Xfce,
> 
> check your doas config ...
> 
> BTW i was just lazy and opened a privleged shell and ran halt -p

i wouldn't call that "lazy" but rather "best practice".

Configuring a GUI to do privileged operations would seem pointless
to me: both complicated and risky.

Yours,
  Ingo

Re: [6.5] Xfce: problem with shutdown menu

[Tom Smyth]

Hi Stephane

I would imagine it is because you dont have shutdown privilege as the
user in Xfce,

check your doas config ...

BTW i was just lazy and opened a privleged shell and ran halt -p




On Sun, 28 Apr 2019 at 22:05, Stephane HUC "PengouinBSD"
 wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Hi, (just FYI)
>
> After upgrading OpenBSD from 6.4 to 6.5, I cant anymore to stop my
> machine when I click on menu shutdown into Xfce session.
> The result is a logout, and not shutdown.
>
> As see, the reply by Landry to one user, on forum "Daemons - BSD", it
> seems necessary to add the id user at the group operator.
> I try this solution, log me out, and login new... and the menu run
> correctly!
>
> http://daemonforums.org/showthread.php?t=10971#post66453
>
>
> - --
> ~ " Fully Basic System Distinguish Life! " ~ " Libre as a BSD " +=<<<
> - 
> Stephane HUC as PengouinBSD or CIOTBSD
> b...@stephane-huc.net
> -BEGIN PGP SIGNATURE-
>
> iHUEARYKAB0WIQScTRXz7kMlZfGpDZMTq98t3AMG7wUCXMYS4QAKCRATq98t3AMG
> 7yGlAQCt0p1qRZD/Szt0Yw4sli9RaIu/2LLwfZOQ6zMK1uleUwEAyeBxvoV2onST
> Q0qLG5L7nAGxZJEJl7r1pKkYzAfL7Ak=
> =BQ3J
> -END PGP SIGNATURE-
>


-- 
Kindest regards,
Tom Smyth.

Re: Qemu Agent assistance needed

[Tom Smyth]

Hello Strahil,
what are you trying to achieve with the Qemu Guest Agent ?

is it  quiescing during backups .>?






On Sun, 28 Apr 2019 at 20:59, Kristjan Komloši
 wrote:
>
> On Sun, 2019-04-28 at 11:10 +, Strahil Nikolov wrote:
> > Hi All,
> > I am new to openBSD and I really like the idea. Sadly I do not have
> > suitable hardware to run on , thus I use KVM and I would be happy if
> > anyone hint me of a working solution for Qemu Guest Agent.
> > Anything I dig up (via google searches) show up only suggestions ,
> > but nothing more.In openBSD 6.4  I successfully installed qemu (and
> > thus the agent), but I can't understand how to get the device needed
> > for communication with the host up and running.
> > As I mainly know linux - I know that we need a kernel module that to
> > be loaded and with combination of udev rules - the devices is created
> > on the necessary location and with the correct rights.According to
> > many google findings - openBSD doesn't support any more loadable
> > kernel module support.
> > I have tried to figure it out by myself, but I cannot find the
> > necessary module needed, nor how to load it in a proper manner.
> > Any hint is well appreciated.
> > Best Regards,Strahil Nikolov
>
> Kernel modules don't exist under OpenBSD to ensure security, so don't
> go there. Communication with host is probably best done through the
> serial console. Take a look at the boot.conf(8) manpage.
>


-- 
Kindest regards,
Tom Smyth.

[6.5] Xfce: problem with shutdown menu

[Stephane HUC "PengouinBSD"]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi, (just FYI)

After upgrading OpenBSD from 6.4 to 6.5, I cant anymore to stop my
machine when I click on menu shutdown into Xfce session.
The result is a logout, and not shutdown.

As see, the reply by Landry to one user, on forum "Daemons - BSD", it
seems necessary to add the id user at the group operator.
I try this solution, log me out, and login new... and the menu run
correctly!

http://daemonforums.org/showthread.php?t=10971#post66453


- -- 
~ " Fully Basic System Distinguish Life! " ~ " Libre as a BSD " +=<<<
- 
Stephane HUC as PengouinBSD or CIOTBSD
b...@stephane-huc.net
-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQScTRXz7kMlZfGpDZMTq98t3AMG7wUCXMYS4QAKCRATq98t3AMG
7yGlAQCt0p1qRZD/Szt0Yw4sli9RaIu/2LLwfZOQ6zMK1uleUwEAyeBxvoV2onST
Q0qLG5L7nAGxZJEJl7r1pKkYzAfL7Ak=
=BQ3J
-END PGP SIGNATURE-

[6.5] Cups + Gutenprint: file rastertogutenprint not found

[Stephane HUC "PengouinBSD"]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi, (just FYI)

After upgrading OpenBSD from 6.4 to 6.5, I had this problem to print.
The Webadmin of Cups informs me with this message:

"/usr/local/libexec/cups/filter/rastertogutenprint.5.2 not found!"

On the parameters about my printer, (an MFP Epson BX525WD on my local
network), I change with the new version of Gutenprint's driver. (v5.3.x)
.

And, that's run correctly!


- -- 
~ " Fully Basic System Distinguish Life! " ~ " Libre as a BSD " +=<<<
- 
Stephane HUC as PengouinBSD or CIOTBSD
b...@stephane-huc.net
-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQScTRXz7kMlZfGpDZMTq98t3AMG7wUCXMYQ0gAKCRATq98t3AMG
78/hAQDHE2kdDyXuuXxpuAbrgPkoVd32HjhmFC05zF56YsJvFAD+L5Q4oxzBIull
qbouLJ8o1tOcdgbtTo1gZDhfC6NVggk=
=izfF
-END PGP SIGNATURE-

[6.5] minidlna error: accept(http): Too many open files

[Stephane HUC "PengouinBSD"]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi, all

After upgrading OpenBSD from 6.4 to 6.5, I've problem to use minidlna.
It fill the /var/log/minidlna/minidlna.log with severals errors
messages, as:
[2019/04/25 15:26:29] monitor_kqueue.c:226: error:
open(/home/z2/Music/xyz) [Too many open files]
(...)
[2019/04/25 20:15:05] minidlna.c:165: error: accept(http): Too many
open files

as read on the pkg-readme, I change both files '/etc/sysctl.conf',
'/etc/login.conf'.

I added 'kern.maxfiles=16384' for sysctl.
And on login file, I wrote:
"minidlna:\
:openfiles-cur=16384:\
:openfiles-max=16384:\
:tc=daemon:
"
And after, I rebooted my machine.

But, thoses errors continue, and grow the log until my dedicated slide
/var/log is full. and minidlna not run correctly. Why?
What are the good values of limits systems to run correctly minidlna?

- 

OpenBSD 6.5 (GENERIC.MP) #3: Sat Apr 13 14:48:43 MDT 2019
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8487260160 (8094MB)
avail mem = 8220409856 (7839MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xec580 (74 entries)
bios0: vendor Alienware version "A08" date 01/25/2018
bios0: Alienware Alienware 13
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC FPDT FIDT MCFG HPET SSDT UEFI SSDT ASF!
SLIC SSDT SSDT SSDT SSDT CSRT SSDT
acpi0: wakeup devices PEGP(S4) PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4)
PEG2(S4) PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4)
PXSX(S4) RP04(S4) RP05(S4) PEGP(S4) [...]
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-4210U CPU @ 1.70GHz, 799.44 MHz, 06-45-01
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,PBE,SSE3,PCLMUL,DTES64,MWAIT,
DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOV
BE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAH
F,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIB
P,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 99MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Core(TM) i5-4210U CPU @ 1.70GHz, 799.32 MHz, 06-45-01
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,PBE,SSE3,PCLMUL,DTES64,MWAIT,
DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOV
BE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAH
F,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIB
P,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 1 (application processor)
cpu2: Intel(R) Core(TM) i5-4210U CPU @ 1.70GHz, 799.31 MHz, 06-45-01
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,PBE,SSE3,PCLMUL,DTES64,MWAIT,
DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOV
BE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAH
F,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIB
P,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 1, core 0, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM) i5-4210U CPU @ 1.70GHz, 799.31 MHz, 06-45-01
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,PBE,SSE3,PCLMUL,DTES64,MWAIT,
DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOV
BE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAH
F,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIB
P,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 1, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 40 pins
acpimadt0: bogus nmi for apid 0
acpimadt0: bogus nmi for apid 2
acpimadt0: bogus nmi for apid 1
acpimadt0: bogus nmi for apid 3
acpimcfg0 at acpi0
acpimcfg0: addr 0xf800, bus 0-63
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (PEG0)
acpiprt2 at acpi0: bus -1 (PEG1)
acpiprt3 at acpi0: bus -1 (PEG2)
acpiprt4 at acpi0: bus -1 (RP01)
acpiprt5 at acpi0: bus -1 (RP02)
acpiprt6 at acpi0: bus 1 (RP03)
acpiprt7 at acpi0: bus 2 (RP04)
acpiprt8 at acpi0: bus 3 (RP05)
acpiprt9 at acpi0: bus -1 (RP06)
acpiprt10 at acpi0: bus -1 (RP07)
acpiprt11 at acpi0: bus -1 (RP08)
acpiec0 at acpi0: not present
acpiec1 at acpi0
acpicpu0 at acpi0: C2(200@148 

Re: Qemu Agent assistance needed

[Kristjan Komloši]

On Sun, 2019-04-28 at 11:10 +, Strahil Nikolov wrote:
> Hi All,
> I am new to openBSD and I really like the idea. Sadly I do not have
> suitable hardware to run on , thus I use KVM and I would be happy if
> anyone hint me of a working solution for Qemu Guest Agent.
> Anything I dig up (via google searches) show up only suggestions ,
> but nothing more.In openBSD 6.4  I successfully installed qemu (and
> thus the agent), but I can't understand how to get the device needed
> for communication with the host up and running.
> As I mainly know linux - I know that we need a kernel module that to
> be loaded and with combination of udev rules - the devices is created
> on the necessary location and with the correct rights.According to
> many google findings - openBSD doesn't support any more loadable
> kernel module support.
> I have tried to figure it out by myself, but I cannot find the
> necessary module needed, nor how to load it in a proper manner.
> Any hint is well appreciated.
> Best Regards,Strahil Nikolov  

Kernel modules don't exist under OpenBSD to ensure security, so don't
go there. Communication with host is probably best done through the
serial console. Take a look at the boot.conf(8) manpage.

reboot when 'shutdown -p -h now' called after upgrade to 6.5

[Damien Thiriet]

Hello @misc,


This is OpenBSD 6.5. After upgrading from 6.4 -stable, my NUC reboots
after calling 'shutdown -p -h now' (with both root and superuser having
access to shutdown with doas). I have to cut the power manualy
immediatly after poweroff was executed to prevent rebooting.

I follow the upgrade guide cleaning instruction before upgrading.

Dmesg below (begins rather strangely, don't remember seeing this in
previous OpenBSD dmesg on this box)



\M^@\M^@\^D@\^A\^P\^D\^P\^P\^A\^D\^D\^B\^H\M^@@\^H\^B\^B\^P@\^A\^P\^H\^H\^P\^H 
\^P @\^H @ \^B@\^B\^D \^A\^A\^B@ \^P\^H@\^H\^B\^A@ \^B\^C@\M^@@ 
\^A\M^@\^B\^A\^A@@\^D@ \^P\^A\^B\M^@\^B\^B \^H\^B\^B\^H\^P\^B\^H\^H\M^@ 
\^B\^B\^A\^A\^P\^P@\^B \^B\^B\^P @\^P@\^A\^B\^B\^B 
\^A\M^@\^P\M^@\^A\^H\M^@\^P\^D\M^@\^B\^A\^P\^A\^P\M^@@\^P\^B 
\^B\M^@\M^@\^A\^H\^P@\M^@\M^@@\^P\^B\M^@@ \^A\M^@\^P\M^@\^H@\M^@\M^@  
\^P\^B\^D@\^H\^P@\^H\M^@\^H@\M^@@\M^@\^D\^A\^A\^A\^D\^HOpenBSD 6.5 (GENERIC.MP) 
#3: Sat Apr 13 14:48:43 MDT 2019
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 4203208704 (4008MB)
avail mem = 4066197504 (3877MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xec170 (83 entries)
bios0: vendor Intel Corp. version "WYLPT10H.86A.0024.2014.0210.1909" date 
02/10/2014
bios0: ThinkPenguin PocketWee
\M-acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC FPDT SSDT SSDT MCFG HPET SSDT SSDT DMAR CSRT
acpy0: wakeup devices PXSX(S4) RP01(S4) PXSX(S4) PXSX(S4) PXSX(S4) RP04(S4) 
PXSX(S4) PXSx(S4) PXSX(S4) PXSX(S4) GLAN(S4) EHC1(S4) EHC2(S4) XHC_(S4) 
HDEF(S4) PEG0(S4) [...]
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) i3-4010U CPU @ 1.70GHz, 1696.36 MHz, 06-45-01
cpu0: 
FPU,VME,DE,@SE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,CSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 99MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Core(TM) i3-4010U CPU @ 1.70GHz, 1696.08 MHz, 07-45-01
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,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG$FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 1 (application processor)
cpu2: Intel(R) Core(TM) i3-4010U CPU @ 1.70GHz, 1696.08 MHz, 06-45-01
cpu2: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,ES,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 1, core 0, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM) i3-4010U CPU @ 1.70GHz, 1696.08 MHz, 06-45-01
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,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 1, core 1, package 0
ioapic0 at mainbus0: apid 8 pa 0xfec0, version 20, 40 pins
acpimcfg0 at acpi0
acpimcfg0: addr 0xf800, bus 0-63*acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (RP01)
acpiprt2 at acpi0: bus 2 (RP04)
acpiprt3 at acpi0: bus -1 (PEG0)
acpiec0 at acpi0: not present
acpicpu0 at acpi0: C2(500@67 mwait.1@0x10), C1(1000@1 mwait.1), PSS
acpicpu1 at acpi0: C2(500@67 mwait.1@0x10), C1(1000@1 mwait.1), PSS
acpicpu2 at acpi0: C2(500@67 mwait.1@0x10), C1(1000@1 mwait.1), PSS
acpicpu3 at acpi0: C2(500@67`mwait.1@0x10), C1(1000@1 mwait.1), PSS
acpipwrres0 at acpi0: FN00, resource for FAN0
acpipwrres1 at acpi0: FN01, resource for FAN1
acpipwrres2 at acpi0: 

Re: some more info about ?? hangs

[Gregory Edigarov]

Updated and rebuilt. Still hangs The same way and place.

On Sun, Apr 28, 2019, 07:02 Jonathan Gray  wrote:

> On Sat, Apr 27, 2019 at 04:55:50PM +0300, Gregory Edigarov wrote:
> > attached please find  dmesg and backtrace of X when that happen again
> > hope this bug report will be more useful than previous one.
> >
> > thank you.
> > --
> > With best regards,
> >   Gregory Edigarov
>
> Likely fixed by
>
> xenocara/xserver/hw/xfree86/common/xf86VGAarbiterPriv.h
>
> 
> revision 1.9
> date: 2019/04/28 03:12:53;  author: jsg;  state: Exp;  lines: +13 -7;
> commitid: gMqza1DBk6OCnvP4;
> Backport cf7517675d988c2d1ff967d6d162a17acbdad46 from xserver 1.20
> xfree86: Hold input_lock across SPRITE functions in VGA arbiter
>
> Fixes stack overflow crash with VGA arbiter used with multi GPU systems.
> Report and fix identified by 'Joe M' on misc@. ok matthieu@
> 
>

Re: Code of Conduct location

[Mario Theodoridis]

On 28/04/19 14:27, tfrohw...@fastmail.com wrote:

On April 28, 2019 10:47:25 AM UTC, Strahil Nikolov  
wrote:

Well, the link gives enough info.

Did anyone test the html to plaintext reformat option?
Sadly my phone apps do not support plain text (maybe someone can
recoomend one for Android).

K9 mail on Android supports plaintext (account settings -> message format). 
This is how I'm typing this email.

You can also run most of the usual Unix tools like mutt via termux if that 
happens to be your thing.

I can recommend FairEmail on Android. It does multipart/alternative and 
you can set plain text only in the identity management settings.


It also has some nice security perks, and is open source.

https://email.faircode.eu/

--
Mit freundlichen Grüßen/Kind regards

Mario Theodoridis

nat-to random : A couple of questions

[Rachel Roch]

Hi,

I've read the delightful manual but its a little terse in this area, so I hope 
some knowledgeable soul can enlighten me:

1) Looking at tcpdumps, I've noticed (on 6.5 have no prior experience with 
nat-to random to compare against) that 'random' seems to operate more like 
'round-robin'  (e.g. if I send traffic, pause, send traffic again it just loops 
through the IP pool in order). 

2) I'm unclear when 'sticky-address' should be appended to random ? In my mind 
I'm thinking about, say, "secure websites" which may track your (apparent) 
source-IP during the time you are logged in, and if it changes you could be 
booted out.  Or am I overthinking things and 'sticky-address' is potentially 
less useful than I think it might be ?

Finally, is there any reason why there isn't (yet?) a more intelligent mapping 
? (e.g. similar to the options in LACP ... e.g. source plus destination, not 
just source).

Thanks !

Rachel

Re: Code of Conduct location

[Rachel Roch]

Apr 28, 2019, 9:16 AM by cho...@jtan.com :

> Strahil Nikolov writes:
>
>> Hello All,
>>
>> can someone point me to the link of the OpenBSD code of Conduct ?
>>
>
> I believe OpenBSD's code of conduct can be summed up as "if you are the
> type of person who needs a code of conduct to teach to you how to human
> then you are not welcome here".
>
> At least I hope so.
>
> Matthew
>

I always thought it could be summed up as "Don't piss off Theo".  ;-)

Re: Code of Conduct location

[tfrohw...@fastmail.com]

On April 28, 2019 10:47:25 AM UTC, Strahil Nikolov  
wrote:
>Well, the link gives enough info.
>
>Did anyone test the html to plaintext reformat option?
>Sadly my phone apps do not support plain text (maybe someone can
>recoomend one for Android).

K9 mail on Android supports plaintext (account settings -> message format). 
This is how I'm typing this email.

You can also run most of the usual Unix tools like mutt via termux if that 
happens to be your thing.

Qemu Agent assistance needed

[Strahil Nikolov]

Hi All,
I am new to openBSD and I really like the idea. Sadly I do not have suitable 
hardware to run on , thus I use KVM and I would be happy if anyone hint me of a 
working solution for Qemu Guest Agent.
Anything I dig up (via google searches) show up only suggestions , but nothing 
more.In openBSD 6.4  I successfully installed qemu (and thus the agent), but I 
can't understand how to get the device needed for communication with the host 
up and running.
As I mainly know linux - I know that we need a kernel module that to be loaded 
and with combination of udev rules - the devices is created on the necessary 
location and with the correct rights.According to many google findings - 
openBSD doesn't support any more loadable kernel module support.
I have tried to figure it out by myself, but I cannot find the necessary module 
needed, nor how to load it in a proper manner.
Any hint is well appreciated.
Best Regards,Strahil Nikolov  

Re: Code of Conduct location

[Strahil Nikolov]

Well, the link gives enough info.

Did anyone test the html to plaintext reformat option?
Sadly my phone apps do not support plain text (maybe someone can recoomend one 
for Android).

I've asked about Code of Conduct , as I didn't want to step someone on his toes 
:) . I'm always trying to be polite , despite the attitude of the opposite side.

Best Regards,
Strahil Nikolov


В неделя, 28 април 2019 г., 6:29:53 ч. Гринуич-4, Anders Andersson 
 написа: 

On Sun, Apr 28, 2019 at 10:04 AM Martijn van Duren

 wrote:
>
> You mean something like this the following?
> https://www.openbsd.org/mail.html
>
> martijn@


This one sadly seems to be lacking from every code of conduct:
"Respect differences in opinion and philosophy".

Re: Code of Conduct location

[Anders Andersson]

On Sun, Apr 28, 2019 at 10:04 AM Martijn van Duren
 wrote:
>
> You mean something like this the following?
> https://www.openbsd.org/mail.html
>
> martijn@

This one sadly seems to be lacking from every code of conduct:
"Respect differences in opinion and philosophy".

Re: Code of Conduct location

[STeve Andre']

On 4/28/19 3:58 AM, Strahil Nikolov wrote:

Hello All,

can someone point me to the link of the OpenBSD code of Conduct ?

It seems that I can't find it even with the help of google.

Best Regards,
Strahil Nikolov



There isn't one that I have ever seen.  But the code of conduct here

is really the same as in life: be honest and fair, try to help and not

harass.  Deal with others as you would wish others would do to you.


A formal Code of Conduct is a rabbit hole, with no bottom.  The very

people who might need it will be its abusers, and how do you enforce

it on open mailing list?


--STeve Andre'

Re: headphone volume levels cannot be manipulated by mixerctl

[Alexandre Ratchov]

On Sat, Apr 27, 2019 at 10:10:07AM -0500, joshua stein wrote:
> On Sat, 27 Apr 2019 at 14:20:32 -, Christian Weisgerber wrote:
> > However, as in this example, I think you will only get a few generic
> > controls.
> > 
> > It is my theoretical understanding that USB audio gadgets typically
> > come with a uhid(4) device, as does yours above, and you would use
> > usbhidctl(1) to list and manipulate the available controls.
> > 
> > In practice, I only get some variant of
> > 
> > usbhidctl: USB_GET_REPORT (probably not supported by device): Input/output 
> > error
> > 
> > when I try this.  So either I'm mistaken or there is a problem
> > somewhere.
> 
> Some devices just don't supply hardware volume controls, so it must 
> be done in software on the sending device.
> 
> With sndiod, you can use aucatctl to change the software volume 
> per-application (or the master volume).
> 
> It's all kind of complicated though.  If you plug in a new USB audio 
> device like this, you have to restart sndiod and pass in a new 
> device name, then use aucatctl to adjust the volume.  But if you 
> unplug the USB device, you have to restart sndiod again to use the 
> default audio device and use mixerctl instead.

Here's a small aucatctl-like program to control sndiod volume in X:

http://caoua.org/alex/obsd/xvolkeys-1.0.tar.gz

In the .xinitrc or .xsession add:

xvolkeys -D

Then, use Ctrl-Alt-Plus and Ctrl-Alt-Minus to increment and decrement
sndiod master volume.

Re: Code of Conduct location

[chohag]

Strahil Nikolov writes:
> Hello All,
>
> can someone point me to the link of the OpenBSD code of Conduct ?

I believe OpenBSD's code of conduct can be summed up as "if you are the
type of person who needs a code of conduct to teach to you how to human
then you are not welcome here".

At least I hope so.

Matthew

Re: Code of Conduct location

[Martijn van Duren]

You mean something like this the following?
https://www.openbsd.org/mail.html

martijn@

On 4/28/19 9:58 AM, Strahil Nikolov wrote:
> Hello All,
> 
> can someone point me to the link of the OpenBSD code of Conduct ?
> 
> It seems that I can't find it even with the help of google.
> 
> Best Regards,
> Strahil Nikolov
> 

Code of Conduct location

[Strahil Nikolov]

Hello All,

can someone point me to the link of the OpenBSD code of Conduct ?

It seems that I can't find it even with the help of google.

Best Regards,
Strahil Nikolov

Re: [website] Incorrect release date on the front page

[Otto Moerbeek]

On Sat, Apr 27, 2019 at 09:11:00PM +, Anonymous wrote:

> Theo de Raadt:
> > cho...@jtan.com wrote:
> > 
> >> Anonymous writes:
> >>> Otto Moerbeek:
>  On Sat, Apr 27, 2019 at 03:13:00PM +, Anonymous wrote:
> 
> > Here too: https://www.openbsd.org/65.html
> 
>  Does it matter? It is very common for publications to be dated in the
>  future. 
> 
>   -Otto
> >>>
> >>> No, it's not common, neither for software releases nor for texts
> >>> published online (blogposts, fiction, etc). Maybe you're talking about
> >>> some niche. And yes, it matters because it's confusing: I opened the
> >>> front page soon after the release but was in doubt whether it's for real
> >>> because of the date.
> >>
> >> Well I'm not an author, editor, publisher or printer but I'm fairly sure
> >> nobody's ever gone from "I'm going to write a book" to "this book has been
> >> printed and is already on the shelves" in less than 24 hours, so
> >> publishing "in advance" like this makes total sense.
> >>
> >> A bit weird but luckily I'm not a complete fucking moron so I'm able to
> >> work out that when something says "released* on [future date]" that time
> >> travel was not invented while I wasn't looking and that a week here or
> >> there just doesn't matter.
> >>
> >> People pointing out spelling mistakes have more utility than this thread.
> > 
> > Looking closer, the release directory contains root.mail which is dated
> > May 1.  That file is also contained in the base set for each
> > architecture, which is hashed and signed.  Sometimes tar'd, hashed, and
> > signed.  There are also many binaries and files throughout the release
> > which aren't date May 1.  It is a pretty unkempt state of affairs.
> > 
> > Obviously to repair some of these issues, we should change the date in
> > that file (and some other files also) and re-roll all the release
> > builds.  Starting now.  Which will take some time.  Sadly, those
> > repaired files will miss May 1, which is sure to elicit new complaints.
> > 
> > Ironic isn't it?  Just-in-time is difficult in the real world.
> > 
> > I suggest the OP learns to let it go.  Or visiting a clinic for some
> > therapy, in most countries this is government subsidized.
> > 
> > The observant among you will have noticed that most errata+syspatch go
> > out a day early also.  We've got a good justification for that though --
> > we are pandering to folk on the early side of the dateline.  You can
> > conclude the 6.5 release was made available on-time, as we are pandering
> > to people on the early side of the weekline.  I'll probably pander to
> > someone else for the 6.6 release.
> > 
> > I'm late, I'm late! For a very important date! No time to say `hello,
> > goodbye,' I'm late, I'm late, I'm late!
> The reason for concern is that if the date is wrong then the
> infrastructure used to roll out the release has a bug which can have
> whatever consequences so rushing to download is unwise. But yes, I see
> that nothing has changed since the 70s, same moronic attitude towards
> people confused by Unix shit. At least you are funny morons, I give you
> that:)
> 

We have better mechanisms to check a release than a date on a website.

Maybe we should wait next time until the release date? Would give me
the time to catch up on reading my National Geographic May issue.

-Otto