Re: httpd setup info?

[IL Ka]

>>What's the appropriate way to let the browser
>> know it should open it in Acrobat
See "Content-Disposition" header.
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Disposition

It tells client to download document or open it inline.

Re: FAQ: dmesg archive

[IL Ka]

See Otto's comment

https://marc.info/?l=openbsd-misc&m=117169914814561&w=2

On Tue, Jun 26, 2018 at 3:59 PM, Rupert Gallagher 
wrote:

> There seems to be a dm...@openbsd.org address where to post such stuff,
> but I could not find its archive, nor I could find a searchable database.
> Do I have to search harder?
>

Re: how to know the progressive state of dd

[IL Ka]

I do not understand what are you trying to achieve, but instead of  killall you
may use pkill(1)



On Tue, Jun 26, 2018 at 1:33 AM, Tuyosi T  wrote:

> hi all .
>
> on Linux
>
> dd-progress.bat  <
> ---
> while true
> do
> date
> killall -USR1 dd
> echo
> echo
> sleep 30
> done
>
> but killall is not possibele on OpenBSD .
> ---
> regards
>

Re: Partitioning recommendations for 6.3?

[IL Ka]

Do you want to really build all ports or just fetch skeletons and build
some of them?

For skeletons, automatic layout is good enough, but I recommend to increase
/usr/src a little and decrease /home.
Make sure you have ~ 5GB for /usr/src/ and /usr/obj.





On Mon, Jun 25, 2018 at 3:17 PM, John Long  wrote:

> Been a while and don't have my other OpenBSD boxes accessible.
>
> What are the recommended partitions and appropriate sizes for people
> who want to track stable and possibly build the whole ports tree?
>
> Thanks,
>
> /jl
>
>

Re: Have a 1 Gbit connection but I not all devices are getting 1 Gbit speed from my ISP

[IL Ka]

>
>
> >Lenovo G500 with USB 3.0 Ethernet and OpenBSD 6.2 - 100mbit
> >Lenovo T400 with motherboard Ethernet Ubuntu 14.04 - 100mbit
> >Lenovo T560 with motherboard Ethernet Windows 10 - 1 Gbit
> >
>

Boot all 3 laptops with OpenBSD flashdrive to see if it is OS/driver issue
of hardware issue.
Try to set speen explicitly and see if it works

Re: Poor browser performance in OpenBSD

[IL Ka]

Have you tried vmstat to find bottleneck: is it CPU in userspace or in
kernel or storage?
Which WM are you using? Could it be WM issue?
Try to use lower resolution   (I know that resolution is locked for LCDs,
but you can try just to make sure it is not the problem)

Re: Web store

[IL Ka]

AFAIK ACME (used by acme-client(1)) is supported by letsencrypt , so you do
not ever need certbot:

https://www.vultr.com/docs/using-let-s-encrypt-on-openbsd-6-1

Seems that everything should work with base system only (I have not tried
though)

On Wed, Jun 13, 2018 at 2:37 AM, Daniel Corbe 
wrote:

> at 5:52 PM, Stuart Henderson  wrote:
>
> On 2018-06-12, Base Pr1me  wrote:
>>
>>> Who runs https://www.openbsdstore.com? I went to buy a couple of shirts
>>> last Friday, but cert returns errors and paypal linking stuff is quite
>>> broken. Also, no one is responding to the ord...@openbsdstore.com
>>> address.
>>>
>>> Any info available? I'm in the US, so that might be the difference.
>>>
>>
>> The cert is returning errors on google browsers due to their sunsetting
>> of certificates from certain Symantec CAs. I had a reply from Lyn in May,
>> "Really sorry about this, we're having issues at the moment, as the
>> 'admin' person is no longer around, so struggling to change the cert…"
>>
>
> Do they not have access to their own box?   Letsencrypt is free and easy
> to set up and I’m sure any number of individuals on this list are both
> qualified and willing to lend support for system administration, hosting or
> both.
>
> -Daniel
>
>

Re: [OT] VirtualBox guest additions support for OpenBSD

[IL Ka]

I am also interested in this feature, but here is lifehack I use to share
clipboard and workaround poor desktop experience of vesa(4):
I run X server on my host machine, and redirect output to it using DISPLAY
env var.
So, all apps are running on OpenBSD/VBox but with full screen and shared
clipboard because they use my host X11 server.
I also use smbclient to share files.

Re: USB power management

[IL Ka]

I am not 100% sure, but I believe that to disable USB device OS uses
"suspend" device hub controller feature.

According to
http://openbsd-archive.7691.n7.nabble.com/Suspending-USB-devices-from-userland-td259075.html

This is not possible in OpenBSD.


On Tue, Jun 12, 2018 at 9:22 PM, Jeff Ross  wrote:

> Black electrical tape is my go to solution for those obnoxious flashing
> leds.
>
> Jeff
>
>
> On 6/12/18 12:17 PM, Thuban wrote:
>
>> Hi,
>> this might look as a stupid question, but I'm stuck and don't know where
>> to look at this point.
>> How would you disable an USB port?
>> I would like to power off a USB drive (flashing blue LED at night) but
>> keep it plugged, and power on when I need it.
>>
>> Any advice?
>>
>> Regards.
>>
>
>

Re: Web store

[IL Ka]

..And certificate is still broken for chrome:(


On Tue, Jun 12, 2018 at 7:08 PM, Base Pr1me  wrote:

> Who runs https://www.openbsdstore.com? I went to buy a couple of shirts
> last Friday, but cert returns errors and paypal linking stuff is quite
> broken. Also, no one is responding to the ord...@openbsdstore.com address.
>
> Any info available? I'm in the US, so that might be the difference.
>

Re: Reboot loop

[IL Ka]

 >  OpenBSD doesn't use ACPI to find an isa UART, it only looks in the fixed
> locations compiled in to the kernel.

Ok, I see that  "com.c" does it by reading register, it even has comment
"Probe for all known forms of UART"


>  For a system console (with access to DDB etc.) you need a "standard" com
port.
Do you mean I can use "com", but not "ucom(4)", right?

Thank you,

Ilya.

Re: Reboot loop

[IL Ka]

There is
> com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
in your dmesg.

So, I assume your box reports com port somehow (via ACPI probably)
Some boxes may have comport built into chipset but no external cable for it.
I have one, I bought cable separately.

Another option is to use UART that connects to USB

Re: Reboot loop

[IL Ka]

Ok, then try to follow Stuart Longland's advice: use serial console.
Connect your PC using null-modem cable to another pc, and in boot(8) prompt
type:

boot> set tty com0

On another PC run cu(1) or minicom or screen (or for Windows you may use
PuTTY), connect to OpenBSD and you will
see all your console output which you should be able to capture.

Re: Reboot loop

[IL Ka]

ddb(4):
"ddb is invoked upon a kernel panic when the sysctl(8) ddb.panic is set to
1".

I belive this value is default. So, kernel should be dropped into ddb on
panic.
Does it happen?

What exactly do you see on screen along with uvm_fault?

Do you see whole stacktrace?

Check
https://www.openbsd.org/ddb.html
for "Minimum information for kernel problems" section

Re: Reboot loop

[IL Ka]

https://www.openbsd.org/report.html
See "How to create a problem report" step 5

Re: relayd(8) relay to unix domain socket

[IL Ka]

>
>
> That's a good question. A similar question I would have is whether it is
> able to relay connections arbitrarily between IPv4 and IPv6.
>

from relayd.conf:
inet6 address-prefix:
 If the requested destination is an IPv4 address,
 relayd(8) will forward the connection to an IPv6
address

So I believe it should work, but I have not tried it because I do not use
ipv6.


>
> I wonder if it wouldn't be easier to hack something together with
> inetd(8) if you want to serve a unix domain socket over TCP/IP.
>

I like application level (level 7)  relay that relayd does for me,
I do not think inetd(8) is aware of http:)

And I also need TLS (https) that httpd and relayd can do.

It seems that I have 2 solutions:

1) client--relayd--(http over tcp)--my_app_server
2) client--httpd--(fastcgi over domain socket)--my_app_server

I want to serve my static files with httpd
(should be faster than my application server, and more secure thanks to
chroot),
so I will go with second approach probably.

relayd(8) relay to unix domain socket

[IL Ka]

Hello,

Is it possible to relay to unix domain socket using relayd(8)?
It seems that relayd(8) only works with protocols on top of IP.

Here is my usecase: I have application server that only able to listen HTTP.
(there are alternatives that work with fastcgi, and I can use them with
httpd(8),
but I want to run this one).

I can make my server listen localhost, but I believe that two servers
running
on same machine should use domain sockets: it is simpler to implement
security
(no need to use pf, I can stay with file permissions to restrict which
processes may access it)
and in theory there is no TCP/IP overhead.

Ilya

Re: OT: how do you write your tools /scripts for everyday tasks

[IL Ka]

>
>
> Or when the tool would be running long enough that the performance
> difference matters. Also, Javascript/Perl/Python/Ruby/shell all tend
> to be lousy at dealing with anything where control over timing is the
> overriding issue.
>


> Or when your target environment needs you to be miserly with your memory
> use.
>
> Or, for practice.
>
> Or, sometimes, just because there are some things where C is more
> convenient and comprehensible.
>

All points are valid, but I believe they rarely happen with onetime tools.
At least on x86.

AFAIK, initial approach was to create "big" tools with C, and then
use scripts to "glue" them.

See:
https://wikipedia.org/wiki/Programming_in_the_large_and_programming_in_the_small
https://wikipedia.org/wiki/Ousterhout%27s_dichotomy

But nowadays many big projects are written with scripts.

C is ok, but it has price: manual memory management, no separate type for
strings,
no fancy exceptions that report errors to stderr automatically etc)

Re: OT: how do you write your tools /scripts for everyday tasks

[IL Ka]

Hello,

Running external process from Python script is not good in most cases.
It is better to use wrapper or binding. Search pypi.org for it.

I use shell (ksh,sed,awk,tr,mail etc) for simple tools, and Python for
something which is more complex.
Python is used for scripting in many modern linux distros,
but OpenBSD base system has Perl which was "defacto" script language in
**nix world since late 80th.
Package management is writtern with Perl.
Both languages have excelent package collections. Perl CPAN and Python pypi
have everything from tmux session management to webservers.
Some people also use Ruby which is somewhere between Perl and Python, and
also works well on OpenBSD.
I've even seen nodejs/javascript used for system scripting.

There is no reason to use C for "onetime tools" except cases when no other
API exist.

Re: socket permissions inside /var/www chroot

[IL Ka]

Hello,

I am definitely not an expert in this field, but here are some thoughts:

connect to a fastcgi socket unless the socket's user and group are also
> www:www.
>

Should not unix domain sockets be treated as regular files in case
permissions?
If yes, then httpd should be able to access any file if:
1) httpd is member of some group
2)  this group has appropriate permisions (rxw?) to this file

So, you can create "_fastcgi" group, add www to this group, and configure
php-fpm
to create socket with this group (it must be main group of user used by
php-fpm).

See listen.group and listen.mode options.


> are much more common for
> "web" type applications,
>
In PHP world maybe, but for Python/Django Postgres is default database.



>
> which really does have to be world readable and
> writable with the sticky bit set in order for the user _postgresql to
> place the socket there,
>
Again, you can add _postgres to some group, and give it permissions to
create
socket in this folder.



> although the chrooted user must specify the username together with a
> dummy password (which is not used) to connect to the socket inside the
> chroot, apparently because there is no access to /etc/passwd
> or /etc/group inside the chroot.
>
/etc/passwd must be accessed by postgres (which is not chrooted, right?)
but not by client.
Client (php) just opens socket file, and postgres uses openbsd API to get
its user id.

Re: Building OpenBSD and ports VS installing from packages

[IL Ka]

>> do I still get the same package ?
Yes.

cc(1) does not use microarchitecture-specific features unless you provide
"-march" explicitly.
Other BSDs do it, but OpenBSD does not. So, cc(1) only knows that you are
building something for amd64.
There should not be any difference between nehalem and coffee lake (
both running
openbsd amd64 of course).

Some applications detect AVX extensions dynamically (using cpuid probably),
and use them if can.
OpenBSD is good example (from 5.8):
"Kernel supports x86 AVX instructions on CPUs that have them."

You do not need to recompile kernel to get AVX.
You just install it, and it uses AVX if CPU provides such instructions.
Same with packages.

Re: Building OpenBSD and ports VS installing from packages

[IL Ka]

Hello.

OpenBSD team does not recommend to build anything that exists in packages.

>>If so, building from ports would produce a different code?
In most cases ports are not aware of your microarchitecture.
See my question and Theo's answer.

https://www.mail-archive.com/misc@openbsd.org/msg160878.html

Re: Viewport for man.openbsd.org -- readability on phones

[IL Ka]

>
>
> If it is not a secret, what runs behind man.openbsd.org? Like httpd, CGI?
>

According to response headers:
"Server: OpenBSD httpd".

And with httpd(8) it must be FastCGI implemented either by perl script
directly or
with aid of slowcgi(8)

Re: print usb printer by [ Google Cloud Print for Chromium ]

[IL Ka]

Hello Jordan,
>> you can do some neat things and avoid having to remove the ulpt(4)
driver from the kernel

What can be the reason to remove it?

If I understand it correctly, this driver provides support for "USB printer
class"
( http://www.usb.org/developers/docs/devclass_docs/usbprint11a021811.pdf )

It creates some kind of "channel" (like LPT port) which can be used to
query printer status,
obtain its ID etc.
Application then sends plaintext or PCL or PostScript or whatever printer
supports to this "channel".

Sysadmin configures "printcap" by adding filters that convert data to PCL
or postscript, and
lpd creates "pool", while CUPS ties all layers providing IP Printing and
other protocols to submit print jobs.

Obsd does not have FAQ about that, but freebsd has pretty good article:
https://www.freebsd.org/doc/handbook/printing.html
And almost everything covered by it is true for openbsd.

Re: OpenBSD 6.3 AMD63 ond Dell Vostro 5470 System BIOS problems

[IL Ka]

Are you using BIOS/MBR or UEFI/GPT?
It latter case, try BIOS/MBR.

Re: Remote kernel debugging with kgdb and vmm

[IL Ka]

AFAIK kgdb (remote debug) is not supported:
http://openbsd-archive.7691.n7.nabble.com/on-line-kernel-
debugging-tt335833.html#a341551

You can debug running kernel but functionality is limited.

Re: CVE-2018-8897

[IL Ka]

>
>
>> Then how do they implement memory watch?
>>
>
> Got me, but even the ancient, in-tree gdb is able to do so.  Have you
> consulted the gdb source?
>

I read gdb sources and found an asnwer,  but later I read docs and here it
is:
https://sourceware.org/gdb/onlinedocs/gdb/Set-Watchpoints.html

"Depending on your system, watchpoints may be implemented in software or
hardware.
GDB does software watchpointing by single-stepping your program and testing
the variable’s value each time,
which is hundreds of times slower than normal execution. "

For bsd, configure script checks GETDBREGS in ptrace.h. It exists in
freebsd but not in openbsd.
Then, "target_can_use_hardware_watchpoint" returns 0, and
"breakpoint.c" checks it, and switches to software watchpoints.
Same happens when debug registers are full even on linux, I assume.

Re: CVE-2018-8897

[IL Ka]

Hello Mike,

>> OpenBSD does not allow userspace to access the hardware debug registers.

Does it mean that gdb and other debuggers can't use hardware breakpoints?
Then how do they implement memory watch?

AFAIK in other OSes they modify DR* registers using ptrace(2),
but "struct reg” from  used by PT_SETREGS  ptrace(2)
does not have field for "dr" registers.

Thanks in advance.
Ilya.

Re: Can SSH report successful connections to pf?

[IL Ka]

If you want to open gate for those, who authenticated using ssh, you may
need authpf(8)  (known as Authentication Gateway)
https://www.openbsd.org/faq/pf/authpf.html

Re: Best Practices python virtualenv

[IL Ka]

> while there are Python modules which rely on W|X.
Yes, but I do not use them.

I only run Python and Django.
I am aware of the fact that my python is not compatible with some modules,
and I am ok with it since I do not need them.

>  use ports instead of pkg_add to get Python binary without W|X
That is exactly what I did: built python from official openbsd port with
USE_WXNEEDED=no.
I now have python that works from /home, but does not support some modules.

While I am still happy with my approach, I'll not suggest it anymore,
because everyone else says it is not correct,
and I do not want to give bad advice to people on this list:)

Fixing every single port that needs WX seems like a huge amount of work.
People do not care about W|X security  too much outside of openbsd
community:(

Re: Best Practices python virtualenv

[IL Ka]

>
> So you're now on a custom built python and are unable to use standard

pkg_add upgrades to new versions. I'd say that on balance, this is more
> likely to *reduce* your security.


I built it from ports, so I can update it using standard port update
procedure.
Since packages are built from ports, the only difference between default
package
and my package is wxneeded header.

However, using ports instead of pkg_add is painful.

To the topic starter:
It seems that I am the only person on this list who uses this approach.
Everyone else (including openbsd veterans) argue against it,
that means I am probably wrong..

Re: Best Practices python virtualenv

[IL Ka]

The only difference is venv creates link to python, it does not copy binary
itself.
You now have
python3 -> /usr/local/bin/python3
in your venv.

Since /usr/local/ has wxallowed by default (see your /etc/fstab) it works.

Does it affect security?

In theory -- yes, because python can now create WX pages.
One may say that it sounds paranoic, and in fact it is,
but OpenBSD is _paranoic_ about security.
That is why it has W^X.

They left wxallowed for /usr/local because there are a lot
of software in ports, written by less "secure paranoics" than openbsd
developers, and
this software needs WX.

Some python packages are good examples.

Python port maintainer added wxneeded to python because
of these packages.

But if you do not use any of these packages, you can
disable wxneeded removing any (theoretical) threat that may use WX.

That will make python more secure and (as side-effect) fix virtualenv
problems.

It is less important for developer laptop, but if you can improve security,
why
not?

You will not create "big security hole"  with your current approach.
You will not create it even by adding wxallowed to /home.
So, it is not a critical issue.

But I feel that decreasing security by running wxneeded app with
out of good reason(if you do not need these packages of course) is not
"OpenBSD way":)

Re: Best Practices python virtualenv

[IL Ka]

It is up to you, but I still belive that best solution is to rebuild python
without of wxneeded.
1) It improves security
2) It fixes your virtualenv issue.

If you do not use packages that need WX, why do you need wxneed?

Re: Best Practices python virtualenv

[IL Ka]

Hello.
Short answer: if you do not need py-cryptography and QtWebKit, just rebuild
python from ports disabling
USE_WXNEEDED.
I run Django using virtualenv in my $HOME and it works.

Long answer:
To use mmap(2) with PROT_EXEC | PROT_WRITE you need to link binary with
-z wxneeded (See ld(1)).
It adds OPENBSD_WXNEEDED header to binary.
You can check it with
$ readelf -a /usr/local/bin/python2 | grep WX
There should be "OPENBSD_WXNEED".

With out of it, mmap(2) returns "Not supported" for such requests.

When mounted with out of wxallowed, binaries with this header can't be
executed.
You will get "Permission denied".

At some moment, people found that  py-cryptography and QtWebKit
need this header, so they added  USE_WXNEEDED=yes to port.
http://openbsd-archive.7691.n7.nabble.com/Patch-Python-for-non-wxallowed-usr-local-td335767.html

See /usr/ports/lang/python/Makefile.inc
See also /usr/ports/infrastructure/mk/bsd.port.mk
for how this option is used and how Makefile.inc is included.

/usr/local has wxallowed, so   py-cryptography and QtWebKit works there.
But they did not care about virtualenv.

We now have python linked with  wxneeded by default:
$ readelf -a /usr/local/bin/python2 | grep WX
OPENBSD_WXNEED 0x 0x 0x
and its execution is not allowed on FS mounted with out of wxallowed.

To fix it, simply rebuild python with this option disabled.

Better solution is to create to flavors of python (with this option and
with out), but
that has not been done.

Ilya.

Re: Disk disappeared from system after cold reboot .

[IL Ka]

Hello.
I am not OVH expert, but from dmesg
I can't see second drive.

I see only sd0 (20480MB) connected to your VirtIO.
Dobule check that both drives are connected.

> why is it mentioning GUID and not disk path ?

It can work with drive names also, i.e:

"/dev/sd0a /"
but name may be changed when you connect drive to different port.
That is why people use unique disk id

Id is written on disklabel, so you can move drive to different port,
making it appear as sd1 or even sd4, and it still be supported.

To check DUID, use disklabel(8):

$ doas disklabel sd0 | grep duid







On Fri, Apr 27, 2018 at 5:18 PM, Paul Florence <
pflor...@etud.insa-toulouse.fr> wrote:

> Hello everyone,
> I am sending this mail because I currently have a problem with
> OpenBSD 6.2 running on a VM on an OVH server
> (OpenBSD ovhvps.openstacklocal 6.2 GENERIC#132 amd64).
>
> I followed this tutorial for the installation, since it is not
> natively supported by OVH [0].
>
>
> Now my problem is that I have a disk that changed DUID an I can't find it.
> I have two hard-drive : a 20 Gb one for the system, and a 50 Gb one for
> the data. On the OVH control panel both disk are labeled as connected.
>
> Now this is my  `/etc/fstab` :
> a8e29a56dba81f59.b none swap sw
> a8e29a56dba81f59.a / ffs rw 1 1
> a8e29a56dba81f59.k /home ffs rw,nodev,nosuid 1 2
> a8e29a56dba81f59.d /tmp ffs rw,nodev,nosuid 1 2
> a8e29a56dba81f59.f /usr ffs rw,nodev 1 2
> a8e29a56dba81f59.g /usr/X11R6 ffs rw,nodev 1 2
> a8e29a56dba81f59.h /usr/local ffs rw,wxallowed,nodev 1 2
> a8e29a56dba81f59.j /usr/obj ffs rw,nodev,nosuid 1 2
> a8e29a56dba81f59.i /usr/src ffs rw,nodev,nosuid 1 2
> a8e29a56dba81f59.e /var ffs rw,nodev,nosuid 1 2
> 00e91f190cdc9d32.a /var/www/data ffs rw,nodev,auto 1 2
>
> The problem is that upon loading fsck and mount can't find
> `00e91f190cdc9d32`.
>
> Here is the output of `sysctl -a | grep -i disk` :
> hw.disknames=sd0:a8e29a56dba81f59,fd0:
> hw.diskcount=2
> machdep.bios.diskinfo.128=bootdev = 0xa204, \
> cylinders = 1023, heads = 255, sectors = 63
> machdep.bios.diskinfo.129=bootdev = 0xa0010204, \
> cylinders = 1023, heads = 255, sectors = 63
>
> I also have to mention that at first this setup was working perfectly
> but I had to do a cold reboot and then this problem appeared.
>
> I hope I didn't make too much grammar mistakes since English is not my
> native language I try to do my best to write as perfectly as possible.
>
> Please be patient, I am still a student and posting here to learn as
> much as possible. I spent a few weeks searching for solutions, reading
> man pages and trying to understand the root of this problem but I just
> can't figure it out.
>
> Do you have any idea what should I do to recover this disk and finally
> mount it ? What about my strange fstab file, why is it mentioning GUID
> and not disk path ? Does it comes from my installation process ?
>
> I attached the output of dmesg to this mail.
>
> Thanks for your time,
>
> Paul
>
> [0] : (https://raby.sh/installing-openbsd-on-ovhs-vps-2016-kvm-mac
> hines.html).
>
>

Re: Clarification re: rebuilding softraid mirror

[IL Ka]

Hello,

No, you do not need to reboot. At least this is how it worked for me for
raid 1:

1) bioctl softraid0 said raid degraded
2) I installed new disk (sd2).
3) kenrel reported on console that disk is detected
4) I created MBR using fdisk on it
5) I created disklabel with RAID type on it
6) bioctl -R /dev/sd2a sd0

I suggest you to try it yourself, but not on production system)



On Fri, Apr 27, 2018 at 2:21 AM, Jordan Geoghegan 
wrote:

> Hello,
>
> Sorry for my ignorance, I was hoping someone could clarify for me the
> proper procedure for rebuilding a softraid mirror. The man page/faq says:
>
>
>> Rebuilding a mirror
>>
>> When a drive failure happens, you will replace the failed drive, create
>> the RAID and other disklabel partitions, then rebuild the mirror. Assuming
>> your RAID volume is sd2 and you are replacing the failed device with sd1m,
>> the following commands should work:
>>
>> #*bioctl -R /dev/sd1m sd2*
>> #*reboot*
>>
>> These steps can be performed in either single user mode <
>> https://www.openbsd.org/faq/faq8.html#LostPW> or from the install kernel
>> .
>>
> Does this mean that a RAID rebuild can *only* be performed from single
> user mode or install kernel, or is it possible to rebuild an array while
> the system is in full operation?
>
> To phrase my question a different way:
> Is it possible to hot swap drives and rebuild arrays on the fly, or will
> this bork my system?
>
> Thanks,
> Jordan Geoghegan
>
>

Re: Virtualbox vs latest snapshot

[IL Ka]

Latest snapshot running on 5.2.8 @win7x64 (everything works and seems to be
stable)
Do you use GPT or MBR?
Is it SATA or PATA/IDE?

Can you boot your hda0:/bsd from cd?
Can you boot from CD, mount drive and fsck it?


xx:2$ dmesg
OpenBSD 6.3-current (GENERIC) #13: Thu Apr 26 07:46:22 MDT 2018
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
real mem = 1056899072 (1007MB)
avail mem = 1017061376 (969MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.5 @ 0xe1000 (10 entries)
bios0: vendor innotek GmbH version "VirtualBox" date 12/01/2006
bios0: innotek GmbH VirtualBox
acpi0 at bios0: rev 2
acpi0: sleep states S0 S5
acpi0: tables DSDT FACP APIC SSDT
acpi0: wakeup devices
acpitimer0 at acpi0: 3579545 Hz, 32 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz, 3492.51 MHz
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,PCLMUL,MWAIT,SSSE3,CX16,PCID,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,RDRAND,NXE,RDTSCP,LONG,LAHF,ITSC,FSGSBASE,MELTDOWN
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: CPU supports MTRRs but not enabled by BIOS
cpu0: apic clock running at 1000MHz
cpu0: mwait min=64, max=64
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins
, remapped to apid 1
acpiprt0 at acpi0: bus 0 (PCI0)
acpicpu0 at acpi0: C1(@1 halt!)
acpiac0 at acpi0: AC unit online
acpivideo0 at acpi0: GFX0
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel 82441FX" rev 0x02
pcib0 at pci0 dev 1 function 0 "Intel 82371SB ISA" rev 0x00
pciide0 at pci0 dev 1 function 1 "Intel 82371AB IDE" rev 0x01: DMA, channel
0 configured to compatibility, channel 1 configured to compatibility
atapiscsi0 at pciide0 channel 0 drive 0
scsibus1 at atapiscsi0: 2 targets
cd0 at scsibus1 targ 0 lun 0:  ATAPI 5/cdrom removable
wd0 at pciide0 channel 0 drive 1: 
wd0: 128-sector PIO, LBA, 20480MB, 41943040 sectors
cd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2
wd0(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 2
pciide0: channel 1 disabled (no drives)
vga1 at pci0 dev 2 function 0 "InnoTek VirtualBox Graphics Adapter" rev 0x00
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
em0 at pci0 dev 3 function 0 "Intel 82540EM" rev 0x02: apic 1 int 19,
address 08:00:27:7d:19:91
"InnoTek VirtualBox Guest Service" rev 0x00 at pci0 dev 4 function 0 not
configured
auich0 at pci0 dev 5 function 0 "Intel 82801AA AC97" rev 0x01: apic 1 int
21, ICH
ac97: codec id 0x83847600 (SigmaTel STAC9700)
audio0 at auich0
ohci0 at pci0 dev 6 function 0 "Apple Intrepid USB" rev 0x00: apic 1 int
22, version 1.0
piixpm0 at pci0 dev 7 function 0 "Intel 82371AB Power" rev 0x08: apic 1 int
23
iic0 at piixpm0
isa0 at pcib0
isadma0 at isa0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
pckbc0 at isa0 port 0x60/5 irq 1 irq 12
pckbd0 at pckbc0 (kbd slot)
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pms0 at pckbc0 (aux slot)
wsmouse0 at pms0 mux 0
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
usb0 at ohci0: USB revision 1.0
uhub0 at usb0 configuration 1 interface 0 "Apple OHCI root hub" rev
1.00/1.00 addr 1
uhidev0 at uhub0 port 1 configuration 1 interface 0 "VirtualBox USB Tablet"
rev 1.10/1.00 addr 2
uhidev0: iclass 3/0
ums0 at uhidev0: 5 buttons, Z and W dir
wsmouse1 at ums0 mux 0
vscsi0 at root
scsibus2 at vscsi0: 256 targets
softraid0 at root
scsibus3 at softraid0: 256 targets
root on wd0a (c157cae92dc08f0c.a) swap on wd0b dump on wd0b
xx:3$


> > Hi! I installed the latest 04.10 snapshot, the install procedure went
> fine, but after reboot the VM stucks at endless boot loop . It prints only
> the "booting hda0:/bsd" line.. before reboot The 04.03 snapshot works fine.
> There is a similar experience for someone with Virtualbox 5.2.8?
>

Re: PERC 6/i existence of Virtual Drives hangs boot

[IL Ka]

>>  Or, is there a gdb method of booting the kernel?

Short answer:
http://openbsd-archive.7691.n7.nabble.com/on-line-kernel-debugging-td335833.html

Long answer:
/dev/kmem (kmem(4)) could be used to access kernel memory.
gdb has special target (kvm) that uses it to debug bsd kernels   (
https://sourceware.org/gdb//onlinedocs/gdb/BSD-libkvm-Interface.html)

so, we need 2 things here:
1) Access to /dev/kmem is disabled by default (due to securelevel(7)).
We need to enable it with "kern.allowkmem=1" in /etc/sysctl.conf
Or we can switch to insecure level (echo "sysctl kernl.securelevel=-1 >
/etc/rc.securelevel")
Make sure to reboot before it.

Never set these values for production system!!

2) Kernel with debug symbols
You can build your kernel (man config).
As last step in "compile" folder you will have /bsd (stripped) and /bsd.gdb
(symbolized)

Then, copy /bsd.gdb to root, reboot and boot it:
boot> boot hd0a:/bsd.gdb

I think we should have article about it in FAQ:)

Re: NFS keeps crashing

[IL Ka]

> I use it on osx: it is a crippled version of the original that causes
endless problems with file permissions. Rock solid for the rest.
File permissions are always hard to maintain between Windows and *nix,
because of Windows ACL's and posix permissions differences.

One person on this list mentioned that SMB is slower than NFS. I googled
for that and it seems to be true,
but article was about SMB2. It could be that SMB3 (supported by Win10) is
slightly faster, need to check.
See "SMB3 Multi-Channel"  experimental feature: https://www.samba.org/samba/
history/samba-4.4.0.html

>  but its package requires x11,

I do not see any X11 here, but some dependencies are strange:
xx4$ pkg_info -f samba | grep "@depend"
@depend converters/libiconv:libiconv-*:libiconv-1.14p3
@depend databases/openldap,-main:openldap-client-*:openldap-client-2.4.45p4
@depend databases/tdb:tdb->=1.3.14:tdb-1.3.15
@depend devel/gettext:gettext-*:gettext-0.19.8.1p1
@depend devel/jansson:jansson-*:jansson-2.10
@depend devel/libexecinfo:libexecinfo-*:libexecinfo-0.3p0v0
@depend devel/libtalloc:libtalloc->=2.1.9:libtalloc-2.1.11
@depend net/avahi,-main:avahi-*:avahi-0.7p1
@depend net/py-dnspython:py-dnspython-*:py-dnspython-1.15.0
@depend net/samba,-ldb:ldb->=1.2.3:ldb-1.2.3p0
@depend net/samba,-util:samba-util->=4.7.6:samba-util-4.7.6
@depend print/cups,-libs:cups-libs-*:cups-libs-2.2.6
@depend security/gnutls:gnutls-*:gnutls-3.5.18
@depend security/openpam:openpam-*:openpam-20141014
@depend sysutils/gamin,-main:gamin-*:gamin-0.1.10p23

Why do I need OpenLDAP if I do not have domain?
What for should I use CUPS if I do not use Samba printing server?
Same with avahi which is zeroconf

Samba does not have any FLAVORs, unfortunatelly.

Probably, you could contact port maintainers and ask them for permission
to create several flavors of samba if you have time to create patch.

Re: 6.3/amd64 Thinkpad T530 touchpad problem (was ok in 6.2/amd64)

[IL Ka]

+1 for trying synaptics(4).
It uses  wsmouse "absolute mode"  (covered by wsmouse(4))
and has a lot of Options (more than ws(4) which is used by default), some
of them may help.
Check log file then, you should see "synaptics" driver there.

You can also try to stop wsmoused(8) before launching X.
Although its man page says it should coexist with X (at least when wsmouse
is used)

But if your USB mouse also has troubles, it could also be accel. issue:
You may try to play with "xinput --set-ptr-feedback " or "xset m"

Re: NFS keeps crashing

[IL Ka]

>  I mean sponsors who pay for projects and compatibility updates. I also
mean broader user base.

IMHO:
To increase userbase and attract
serious sponsors attention, OpenBSD needs to be converted
to "friendly-for-non-IT-people" OS like Ubuntu.
Do you want to have polkit and Systemd in base system?:)

It seems than in obsd you should either investigate issue
by reading source code and using debugger or trace,
or write to bugs@ and wait for developer answer.

I belive NFS is rarely used nowadays, especially with Windows clients.
People use samba/smb to connect *nix to Windows in most cases.
Samba should be pretty stable because OS X uses it to coexist with MS oses.

Re: Boot problem after power failure in OpenBSD 6.2 and later versions

[IL Ka]

>
> Reinstalling the operating system seems to solve the problem.
>
Almost never you need to reinstall OpenBSD.

There are only 2 parts that could be broken in your case:
boot(8) and kernel itself (/bsd).
Both could be downloaded from CD or ftp.OpenBSD.org website

That is why I told you to try to boot CD kernel using your boot(8) (and
vice versa)
to check which one is broken and then replace it.

But you reinstalled OS, so we will not know it.

But my main question is different: Why does this problem happen in the
> release 6.2 and later versions? The same process does not cause the problem
> in version 6.1.
>
I do not know..
Unexpected reboot is always some kind of lottery, that is why people use
backups and even store /etc/ in vcs
and OpenBSD has /altroot where it copies kernel and other files

FFS does its best to save filesystem metadata (unless you enable async
mount option explicitly, which you did not do I am sure)
and fsck (fsck -f ?) almost always helps.

It could be that it has nothing to do with OpenBSD version: just an accident

Re: Boot problem after power failure in OpenBSD 6.2 and later versions

[IL Ka]

Please provide list of disks reported by boot(8) (i.e. hd0..)

Try to boot CD kernel from your disk boot ]
i.e: boot from harddrive, and in boot> prompt try
something like "cd0:/6.3/bsd" (not sure about exact syntax, check man)

If it does not work, then you need to reinstall your boot and kernel from
/altroot or cd or openbsd website.
 (and you will
need to reinstall biosboot also (see installboot(8))


On Fri, Apr 20, 2018 at 11:48 PM, augusta bonaventura 
wrote:

> It is constantly restarting itself without of any message.
> When I type in "boot -s", the device reboots itself again.
> As you said, I booted from flash / cdrom and fsck all the partitions, but
> that did not help either.
> Also I checked /bsd exists on root
> However, the system can not be booted.
>
> I dont know what is the weakness.
> Thanks.
>
> 2018-04-20 23:34 GMT+03:00 IL Ka :
>
>> Does it reboot itself without of any message?
>>
>> Try to break in boot(8) menu (by clicking any key when boot prompt
>> created)
>> and boot kernel in single user mode (boot -s).
>>
>> If it does not help, boot from flash/cdrom (as you probably done
>> accroding to dmesg) and fsck your harddrive/ssd partitions.
>> Are they clean?
>> Mount them, and check /bsd exists on root (.a)
>>
>>
>> On Fri, Apr 20, 2018 at 11:23 PM, augusta bonaventura <
>> augusta...@gmail.com> wrote:
>>
>>> It means OpenBSD is constantly restarting itself.
>>>
>>> 2018-04-20 23:01 GMT+03:00 IL Ka :
>>>
>>>> > When the device reboots, it reboots itself when
>>>> >  it comes to the "boot>" menu.
>>>>
>>>> What do you mean "reboots itself "?
>>>>
>>>> boot(8) reboots your machine instead of booting kernel with out of any
>>>> output?
>>>>
>>>>
>>>
>>
>

Re: Boot problem after power failure in OpenBSD 6.2 and later versions

[IL Ka]

Does it reboot itself without of any message?

Try to break in boot(8) menu (by clicking any key when boot prompt created)
and boot kernel in single user mode (boot -s).

If it does not help, boot from flash/cdrom (as you probably done accroding
to dmesg) and fsck your harddrive/ssd partitions.
Are they clean?
Mount them, and check /bsd exists on root (.a)


On Fri, Apr 20, 2018 at 11:23 PM, augusta bonaventura 
wrote:

> It means OpenBSD is constantly restarting itself.
>
> 2018-04-20 23:01 GMT+03:00 IL Ka :
>
>> > When the device reboots, it reboots itself when
>> >  it comes to the "boot>" menu.
>>
>> What do you mean "reboots itself "?
>>
>> boot(8) reboots your machine instead of booting kernel with out of any
>> output?
>>
>>
>

Re: Boot problem after power failure in OpenBSD 6.2 and later versions

[IL Ka]

 > When the device reboots, it reboots itself when
>  it comes to the "boot>" menu.

What do you mean "reboots itself "?

boot(8) reboots your machine instead of booting kernel with out of any
output?

Re: OpenBSD + 3G/4G USB modem

[IL Ka]

 Do you have ucom at umodem in dmesg?
Or ucom at umsm?




On Fri, Apr 20, 2018 at 9:17 PM, MS  wrote:

> I forgot to mention it but the modem doesn't respond on any of the
> /dev/cuaUX
>
> 2018-04-20 11:17 GMT+02:00 Roderick :
>
> >
> >
> > On Fri, 20 Apr 2018, MS wrote:
> >
> > ok, so I ejected the cd1 and OBSD started seeing ZTE as a umodem, but
> >> umodem0, 1 and 2 at the same time. Is it normal?
> >>
> >
> > That some modems attach to many devs is normal. You must try with any
> > of them until you find the one that responds to AT commands.
> >
> > Is the modem pluged to a USB port?
> >
> > You should see in dmesg something like: ucom0 at umodem0
> >
> > That would be not normal in your dmesg!
> >
> > Rodrigo.
> >
> >
>

Re: How to maintain/debug OpenBSD

[IL Ka]

This book is quite old, but it has a good chapter about BSD performance
tools
and about performance measurement in general

https://www.amazon.com/Optimizing-UNIX-Performance-Amir-Majidimehr/dp/0131115510

Such books are rare because if you know how operation systems and computers
work,
you do not need anything except man pages for tools.




On Fri, Apr 20, 2018 at 6:35 PM,  wrote:

> Is there any books that describe how to deal with these tools ?
>
> Sunny Naqvi
>
> On Fri, Apr 20, 2018 at 04:42 PM, IL Ka  wrote:
>
> high load
>
>
> top, vmstat. You can also try to profile app with dtrace.
>
> low space disk
>
>
> ``du -d1 -h`` to find huge dir
>
> see opened files
>
>
> fstat
>
> On Fri, Apr 20, 2018 at 9:56 AM,  wrote:
>
> Hi
>
> Sometimes we need to maintain or debug OpenBSD.
> I found these links useful :
> https://www.openbsd.org/ddb.html (https://www.openbsd.org/ddb.html)
> https://man.openbsd.org/crash (https://man.openbsd.org/crash)
> https://www.openbsd.org/report.html (https://www.openbsd.org/report.html)
> But what do you use guys ? any tricks when things go wrong ?
> Like for example facing to 'high load', 'low space disk', 'see opened
> files'...
>
> Thanks
> Sunny Naqvi
>
>

Re: vmstat

[IL Ka]

vmstat can't be used for that.
Use top(1) and check its SIZE (virtual mem size) and RES (mem currently in
RAM) columns.

You can also use ps(1) with -m argument to sort by memory usage.
It has %MEM (compared to other processes), RSS (like RES), VSZ (like SIZE)

read man pages for ps and top:)

On Fri, Apr 20, 2018 at 3:54 PM,  wrote:

> Hi,
> Can you explain me how to use vmstat to detect which software are taking
> more memory ?
> Thank's
> Sunny Naqvi
>

Re: How to maintain/debug OpenBSD

[IL Ka]

> high load
top, vmstat. You can also try to profile app with dtrace.

> low space disk
``du -d1 -h`` to find huge dir

> see opened files
fstat




On Fri, Apr 20, 2018 at 9:56 AM,  wrote:

> Hi
>
> Sometimes we need to maintain or debug OpenBSD.
> I found these links useful :
> https://www.openbsd.org/ddb.html (https://www.openbsd.org/ddb.html)
> https://man.openbsd.org/crash (https://man.openbsd.org/crash)
> https://www.openbsd.org/report.html (https://www.openbsd.org/report.html)
> But what do you use guys ? any tricks when things go wrong ?
> Like for example facing to 'high load', 'low space disk', 'see opened
> files'...
>
> Thanks
> Sunny Naqvi
>

Re: sshfuse: fusefs: libfuse vnode reclaim failed

[IL Ka]

Process could be in "uninterruptible sleep" when it is inside of disk
access operation for example.

>From ps(1):
state
Alias: stat. The state is given by a sequence of letters, for example,
“RWN”. The first letter indicates the run state of the process:
Marks a process in disk (or other short term, uninterruptible (!)) wait.

See also
https://www.novell.com/support/kb/doc.php?id=7002725


On Fri, Apr 20, 2018 at 9:40 AM, Rudolf Sykora 
wrote:

> Dear IL,
>
> On 20 April 2018 at 02:34, IL Ka  wrote:
> > First, make sure your SSH connection is stable.
> > ...
> > I can't help you unfortunatelly because
> > this issue is not reproducible for me: I tried sshfs: it works like
> charm.
>
> thanks for the information!
> I will keep using it and we will see.
>
> What surprised me the most was the state into which I got,
> i.e., that I couldn't kill it, reboot, ...
>
> Best regards
> Ruda
>

Re: sshfuse: fusefs: libfuse vnode reclaim failed

[IL Ka]

First, make sure your SSH connection is stable.

Try to SSH to your server, run some commands,
download big (several megabytes) file
using SCP or SFTP.
It could be that your SSH problems.

If it works, then we can try
to investigate it:


> libfuse vnode reclaim failed

This message is from following code:
if (fb_queue(fmp->dev, fbuf))
printf("fusefs: libfuse vnode reclaim failed\n");

"fuse_lookup.c"

As we can see, "fb_queue" retruns error, but we do not know
which error.

I think we need to know this error to understand what happened.

In "fb_queue" source (fusebuf.c) we can see that error is
return code from "tsleep" or "fbuf->fb_err".


This code is part of this commit:
https://github.com/openbsd/src/commit/5e69e0b69176a7f878c899ef5828a6273ab7f0bb
Written by https://github.com/natano , while file originally written by
Sylvestre Gallon 

So, you have 2 options here:

Debug it yourself by kernel debugging (gdb)
or patch kernel and print this error value to kernel log
(printf(9)) (could be good contribution to kernel btw)

Or you can write to tech@ or bugs@
about this problem and wait for developer's attention.

I can't help you unfortunatelly because
this issue is not reproducible for me: I tried sshfs: it works like charm.

Re: kernel relink segfaults on ALIX

[IL Ka]

> commented out the call to
> reorder_kernel in rc.

I still believe that  ``chmod -x /usr/libexec/reorder_kernel`` is much
better and safer  than patching ``/etc/rc``,
but it is up to you)

Re: kernel relink segfaults on ALIX

[IL Ka]

I am sorry, I skipped your last line:
> Just comment in rc -_- for kernel

You are right. But it is safer to "chmod -x" reorder_kernel (touching rc is
not good)

On Thu, Apr 19, 2018 at 9:58 PM, sven falempin 
wrote:

> On Thu, Apr 19, 2018 at 1:01 PM, IL Ka  wrote:
>
> > Upgrade may affect kernel, so you need to reorder it at least once after
> > upgrade!
> >
> > I am not sure which policy do OpenBSD use, but generally if something is
> > not documented it is subject to be changed in minor upgrade.
> >
> > The only reference to this script is ``/etc/rc`` (line 620) without of
> any
> > variable, and since "reorder_kernel" is
> > not documented it would be absolutelly legal to rename it and update
> > /etc/rc accordingly.
> >
> > So, this little hack may be broken after upgrade anyway.
> >
> > I wish there were ``man reorder_kernel(8)`` and ``reorder_kernel=NO``
> > documented in ``rc.conf(8)``
> > But if I understood everything correct, developers say we should not
> > disable this script,
> > that is why they do not document it nor create an option in rc.conf.
> >
> >
> > On Thu, Apr 19, 2018 at 7:42 PM,  wrote:
> >
> > > One step further would be to put that in your rc.local so it survives
> an
> > > upgrade.
> > > On Apr 19, 2018 9:44 AM, IL Ka  wrote:
> > > >
> > > > Ancient UNIX way to disable anything: ``doas chmod -x
> > > > /usr/libexec/reorder_kernel`` ;)
> > > >
> > > > Although ``reorder_kernel`` is very simple ksh script, I agree it
> > should
> > > be
> > > > documented.
> > > >
> > >
> >
>
> grep aslr /etc/rc.conf  >> /etc/rc.conf.local
>
> When you reboot often on crap drive, or if you are not exposed (test
> device), relinking is waste of time
> IF you are online , keep it .
>
> Just comment in rc -_- for kernel
>
> --
> --
> 
> -
> Knowing is not enough; we must apply. Willing is not enough; we must do
>

Re: kernel relink segfaults on ALIX

[IL Ka]

You are speaking about ``library_aslr`` which is documented by ``man
rc.conf``.
But it is not the same thing as kernel reordering: it reorders libs, so
they'll
be loaded at different memory address next time.
And kernel relink does same for kernel itself (relinks kernel from its
objects in random manner).

We can disable  library_aslr, but there is no same option for kernel..


On Thu, Apr 19, 2018 at 9:58 PM, sven falempin 
wrote:

> On Thu, Apr 19, 2018 at 1:01 PM, IL Ka  wrote:
>
> > Upgrade may affect kernel, so you need to reorder it at least once after
> > upgrade!
> >
> > I am not sure which policy do OpenBSD use, but generally if something is
> > not documented it is subject to be changed in minor upgrade.
> >
> > The only reference to this script is ``/etc/rc`` (line 620) without of
> any
> > variable, and since "reorder_kernel" is
> > not documented it would be absolutelly legal to rename it and update
> > /etc/rc accordingly.
> >
> > So, this little hack may be broken after upgrade anyway.
> >
> > I wish there were ``man reorder_kernel(8)`` and ``reorder_kernel=NO``
> > documented in ``rc.conf(8)``
> > But if I understood everything correct, developers say we should not
> > disable this script,
> > that is why they do not document it nor create an option in rc.conf.
> >
> >
> > On Thu, Apr 19, 2018 at 7:42 PM,  wrote:
> >
> > > One step further would be to put that in your rc.local so it survives
> an
> > > upgrade.
> > > On Apr 19, 2018 9:44 AM, IL Ka  wrote:
> > > >
> > > > Ancient UNIX way to disable anything: ``doas chmod -x
> > > > /usr/libexec/reorder_kernel`` ;)
> > > >
> > > > Although ``reorder_kernel`` is very simple ksh script, I agree it
> > should
> > > be
> > > > documented.
> > > >
> > >
> >
>
> grep aslr /etc/rc.conf  >> /etc/rc.conf.local
>
> When you reboot often on crap drive, or if you are not exposed (test
> device), relinking is waste of time
> IF you are online , keep it .
>
> Just comment in rc -_- for kernel
>
> --
> --
> 
> -
> Knowing is not enough; we must apply. Willing is not enough; we must do
>

Re: kernel relink segfaults on ALIX

[IL Ka]

Upgrade may affect kernel, so you need to reorder it at least once after
upgrade!

I am not sure which policy do OpenBSD use, but generally if something is
not documented it is subject to be changed in minor upgrade.

The only reference to this script is ``/etc/rc`` (line 620) without of any
variable, and since "reorder_kernel" is
not documented it would be absolutelly legal to rename it and update
/etc/rc accordingly.

So, this little hack may be broken after upgrade anyway.

I wish there were ``man reorder_kernel(8)`` and ``reorder_kernel=NO``
documented in ``rc.conf(8)``
But if I understood everything correct, developers say we should not
disable this script,
that is why they do not document it nor create an option in rc.conf.


On Thu, Apr 19, 2018 at 7:42 PM,  wrote:

> One step further would be to put that in your rc.local so it survives an
> upgrade.
> On Apr 19, 2018 9:44 AM, IL Ka  wrote:
> >
> > Ancient UNIX way to disable anything: ``doas chmod -x
> > /usr/libexec/reorder_kernel`` ;)
> >
> > Although ``reorder_kernel`` is very simple ksh script, I agree it should
> be
> > documented.
> >
>

Re: 6.3/amd64 Thinkpad T530 touchpad problem (was ok in 6.2/amd64)

[IL Ka]

I forgot to mention that you can disable extended input devices.
Ie.
$ xinput --list
Then look at list of "Virtual core XTEST pointer" children
And ``xinput --disable [id]`` everything but the first one. It _may_ help.

On Thu, Apr 19, 2018 at 2:38 PM, Jonathan Thornburg <
jth...@astro.indiana.edu> wrote:

> I have a Lenovo Thinkpad T530.  Everything (including the builtin
> touchpad) was fine under 6.2/amd64, but under 6.3/amd64 there is a
> severe problem with the builtin touchpad when running X (autoconfigured
> with no xorg.conf; all other aspects of X operation are fine).
>
> The problem is this: when I first start X the touchpad operates normally.
> But a minute or so of use the X cursor starts jumping to the left and/or
> top side of the screen each time I start a new finger-movement.
>
> That is, a normal sequence of touchpad operation is
> 1. touch finger to touchpad
> 2. drag finger to move X cursor to desired location
> 3. remove finger from touchpad
> but once this problem starts, step 2 causes the X cursor to jump to the
> left side of the screen (if the finger-drag is in a horizontal direction),
> the top side of the screen (if the finger-drag is in a vertical direction),
> or the top-left corner of the screen (if the finger-drag is in a diagonal
> direction).
>
> I see the same symptoms if ...
> * ... I boot GENERIC instead of usual GENERIC.MP
> * ... I comment out the line 'xset m 1/4' (which is the only 'xset m' line)
>   from my $HOME/.xinitrc.
> * ... I change from my usual window manager (twm, started from
> $HOME/.xinitrc),
>   to the OpenBSD default fvwm (started if there is no $HOME/.xinitrc).
> * ... I plug in a USB (optical) mouse, but continue to use the builtin
>   touchpad,
> * ... I plug in a USB (optical) mouse, and use that as a pointer device
>   instead of the builtin touchpad.  In this case mouse movements trigger
>   the X-cursor-jumping behavior: the X cursor jumps to the left side of
>   the screen (if the mouse movement is in a horizontal direction), the top
>   side of the screen (if the mouse movement is in a vertical direction),
>   or the top-left corner of the screen (if the mouse movement is in a
>   diagonal direction).
>
> Once this problem starts, the only "cure" I have found is to kill the
> X server (either 'pkill X' or Ctrl-Shift-Backspace -- the window-manager
> menu is inaccessable due to the X cursor jumping) and start a new X
> session.
> This gets me a minute or so of normal operation before the problem
> reoccurs.
>
> I am not running xenodm -- I login on the console and start (or restart)
> X via 'startx'.
>
> Below I give my dmesg (6.3/amd64), a dmesg from 6.2/amd64 on this same
> machine for comparison, and /var/log/Xorg.0.log (6.3/amd64).
>
> Have other Thinkpad users encountered this behavior?  Is there a known
> workaround?  Is there additional information I could supply to help
> diagnose the problem?  (I could run with a debugging kernel or X server
> for a while if that would help.)
>
> Thanks, ciao,
> -- "Jonathan Thornburg [remove -animal to reply]" <
> jth...@astro.indiana-zebra.edu>
>currently visiting Max-Plack-Institute fuer Gravitationsphysik
>   (Albert-Einstein-Institut), Potsdam-Golm, Germany
>
> --- begin 6.3/amd64 /var/run/dmesg.boot ---
> OpenBSD 6.3 (GENERIC.MP) #107: Sat Mar 24 14:21:59 MDT 2018
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> real mem = 16845565952 (16065MB)
> avail mem = 16327950336 (15571MB)
> mpath0 at root
> scsibus0 at mpath0: 256 targets
> mainbus0 at root
> bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xdae9c000 (69 entries)
> bios0: vendor LENOVO version "G4ETA7WW (2.67 )" date 08/24/2016
> bios0: LENOVO 24292A9
> acpi0 at bios0: rev 2
> acpi0: sleep states S0 S3 S4 S5
> acpi0: tables DSDT FACP SLIC TCPA SSDT SSDT SSDT HPET APIC MCFG ECDT FPDT
> ASF! UEFI UEFI POAT SSDT SSDT UEFI DBG2
> acpi0: wakeup devices LID_(S4) SLPB(S3) IGBE(S4) EXP3(S4) XHCI(S3)
> EHC1(S3) EHC2(S3) HDEF(S4)
> acpitimer0 at acpi0: 3579545 Hz, 24 bits
> acpihpet0 at acpi0: 14318179 Hz
> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz, 2893.80 MHz
> 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,SMX,EST,TM2,SSSE3,
> CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,
> AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,
> FSGSBASE,SMEP,ERMS,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN
> cpu0: 256KB 64b/line 8-way L2 cache
> acpihpet0: recalibrated TSC frequency 2893437769 Hz
> 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.1.2, IBE
> cpu1 at mainbus0: apid 2 (application processor)
> cpu1: Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz, 2893.43 MHz
>

Re: 6.3/amd64 Thinkpad T530 touchpad problem (was ok in 6.2/amd64)

[IL Ka]

Try to start ``wsmoused(8)`` and check if mouse works in console.
``/etc/rc.d/wsmoused start`` and move mouse around for minute or two.
Does it work?

It will help us to understand if it is a X problem or wmouse(4) problem

Re: kernel relink segfaults on ALIX

[IL Ka]

Ancient UNIX way to disable anything: ``doas chmod -x
/usr/libexec/reorder_kernel`` ;)

Although ``reorder_kernel`` is very simple ksh script, I agree it should be
documented.



On Thu, Apr 19, 2018 at 12:15 PM, Z Ero  wrote:

> Coincidently I just logged in to write the misc  list about relinking
> on boot. Is it possible to disable it? What about just relinking on
> the first boot after install? So then every kernel image is different
> but not re-randomized each boot! There are some low memory / slow CPU
> embedded systems like Alix / Soekris where the benefit, in my opinion,
> of re-linking every single boot is not worth the cost. That said
> granted these systems should not be rebooted frequently anyway once in
> production during normal use. I had a soekris recently that performed
> well for the task I needed it for but that I chose to install OpenBSD
> version 5.8 on...because I did not want to put up with the
> relinking...I would have rather used 6.2...would it be possible to
> give users a "switch" to turn off relinking if they want without
> recompiling the kernel...please forgive my ignorance (or flame
> away...) if this already exists.
>
> Thanks.
>
> On Thu, Apr 19, 2018 at 2:16 AM, Darren Tucker 
> wrote:
> > On 19 April 2018 at 16:52, Jan Stary  wrote:
> >> This is a fresh upgrade of current/i386 on an ALIX 2D3.
> >> Upon start, kernel relinking fails, with relink.log saying:
> >
> > Do you have any swap configured?  Relinking takes a reasonable amount
> > of ram and the ALIX doesn't have a lot.
> >
> > --
> > Darren Tucker (dtucker at dtucker.net)
> > GPG key 11EAA6FA / A86E 3E07 5B19 5880 E860  37F4 9357 ECEF 11EA A6FA
> (new)
> > Good judgement comes with experience. Unfortunately, the experience
> > usually comes from bad judgement.
> >
>
>

Android (MTP) with OpenBSD: Tiny success story

[IL Ka]

I just connected my Android device to OpenBSD, and since
I did not find any article on this subject, I want to share my experience.

OpenBSD supports USB Mass Storage Device  (used in usb drives)
with umass(4).

But Android uses MTP (file-level protocol, not block-level like umass),
So OpenBSD launched ugen(4) to give user-space tools access
to some unknown USB device.

I installed ``simple-mtpfs`` package that uses fuse (user-space fs).

$ mtp-connect
$ simple-mtpfs /mnt

and it worked! You only need to be sure that your screen is unlocked.
For some reason my Android does not allow to connect to it.

There is also ``devel/adb`` port to debug and install .apk, but
I haven't tried it yet.

No place for "wsfontload" and "wsconscfg" in rc?

[IL Ka]

Hello,

It may sound silly: nobody use console these days (except emergency),
but I am curious:
I want to load font and set it using wsconsctl display.font
I also want to change display type.

I can do all of that in rc.local, but there is a separeate place for
wsconsctl :
/etc/wsconsctl.conf

I want to use it, but I can't set font.display there because it is called
by rc, hence before  rc.local, before my font loaded.

And there is no place for wsconscfg except rc.local.

In NetBSD they solved it by having separate file
for all wscons* stuff
https://www.daemon-systems.org/man/wscons.conf.5.html
In FreeBSD they set everything in rc.conf

And OpenBSD has:
1) /etc/kbdtype for kbd
(its weird because I can use keyboard.ecnoding in /etc/wsconsctl.conf)
2) /etc/wsconsctl.conf
(for everything else exception font loading and virtual display management)

So, there is no place for fonts.
And there is no place for wsconscfg
(if I want to creareate display changing its type I should set it to
rc.local)

I like NetBSD approach here, and it seems that it can be implemented
using simple ksh or perl script.

One may say that is it too complicated: why create
separate config file for something that could be done with 3 lines in
rc.local.

But then why do we have  /etc/kbdtype and  /etc/wsconsctl.conf ?

Ilya

Re: NFS server down, again, and again, and again...

[IL Ka]

You could use ktrace(1) to trace all calls and then use kdump(1) to read
them, and may help you to find what cause it to die, but it may be tricky
for anyone except nfsd developer..
You can also try to find person who supports it by looking at last commits
to:
https://github.com/openbsd/src/blame/master/sbin/nfsd/nfsd.c
and email this person, but I do not know if it will help, or talk to people
on bugs@ list.

Or you can move to samba/smbd: SMB must have good support in Windows.


On Wed, Apr 18, 2018 at 2:53 AM, Rupert Gallagher 
wrote:

> > Do you mean nfsd server dies?
>
> I mean the NFS service as delivered by nfsd, portmap and mountd.
>
> > Does it provide core dump?
>
> No!
>
> > You do not need to restart it
> manually: just create script that checks for server existence (like
> ``/etc/rc.d/nfsd check``) and run it if it is dead.
>
> I usually prepare my servers from source with custom patches and settings.
> When a server dies on me, it makes a lot of noise in the logs, and it
> happens rarely. In 30+ years of activity, I have never restarted a
> production server because of clients using it!
>
> NFS is an exception. I am using the obsd default, and it dies on me under
> load and without logs. It is unreliable.
>
>

Re: NFS server down, again, and again, and again...

[IL Ka]

Do you mean nfsd server dies? Does it provide core dump?

You do not need to restart it manually: just create script that checks for
server existence (like ``/etc/rc.d/nfsd check``) and run it if it is dead.

On Wed, Apr 18, 2018 at 12:00 AM, Rupert Gallagher 
wrote:

> The crash usually occurs in the morning, when the 'windows 10 pro' clients
> are powered up. The obsd nfs server must be restarted manually, and the
> clients are happy again. No error messages, clear logs, and yet it crashes.
> A mistery.
>

Re: Beg for Atheros wifi driver

[IL Ka]

 >  0x: Vendor ID: 168c Product ID: 003e

https://vendev.org/pci/ven_168c&dev_003e/

"QCA6174 802.11ac Wireless Network Adapter"

You can try
$ man pci | grep Atheros
or
$ apropos Atheros

To get list all Atheros-related drivers ( ath(4),  athn(4) and same for usb)
but it seems that they do not support it.

Re: trouble installing php on 6.3

[IL Ka]

According to
/usr.sbin/pkg_add/OpenBSD/Temp.pm

If  PKG_TMPDIR is not set, it uses OpenBSD::Paths->vartmp
>our $tempbase = $ENV{'PKG_TMPDIR'} || OpenBSD::Paths->vartmp;

And according to
/usr.sbin/pkg_add/OpenBSD/Paths.pm

Default value is "/var/tmp".
>sub vartmp() { '/var/tmp' }

It seems that pkg_add works for /tmp, but not for /var/tmp.

Lets make sure that
# PKG_TMPDIR=/var/tmp/ pkg_add -r -vvv curl
fails, and we will have 100% guarantee that it is /var/tmp problem.

Do you have enough space in "/var"? Try to fsck -f this partition.

On Tue, Apr 17, 2018 at 5:28 PM, Michael Maurer 
wrote:

> On 17 April 2018 at 14:13, IL Ka  wrote:
> > So, does it work only with PKG_TMPDIR set?
> >
> > # PKG_TMPDIR=/tmp/foo pkg_add -r -vvv curl
> > (-r is used to replace old package)
> >
> > Could it be your harddrive or filesystem problem?
> > Try to fsck partition where pkg_add stores packages.
> >
> > If you are able to download file by wget, you can install it using
> pkg_add
> > by providing path to this file.
>
> Yeah, seems like it's related to PKG_TMPDIR. Everything I need is
> installed now, the only
> thing I fear is that this will bite me during the next upgrade. (fsck
> doesn't generate errors)
>

Re: trouble installing php on 6.3

[IL Ka]

 So, does it work only with PKG_TMPDIR set?

# PKG_TMPDIR=/tmp/foo pkg_add -r -vvv curl
(-r is used to replace old package)

Could it be your harddrive or filesystem problem?
Try to fsck partition where pkg_add stores packages.

If you are able to download file by wget, you can install it using pkg_add
by providing path to this file.


ps: http://www.openbsd.org/faq/faq15.html


> Strangely that worked. I did some googling before I wrote to this
> > list, someone mentioned a similar error that
> > got resolved by adding a PKG_TMPDIR. Might that have been the case?
>
> Never mind, got the same thing trying to install curl, maybe something more
> fundamental is broken. Here's the output of pkg_add -vvv curl
>
> burt# pkg_add -vvv curl
>

CPUTYPE in mk.conf to set -march like in FreeBSD?

[IL Ka]

In FreeBSD they have /etc/make.conf
You set CPUTYPE= there, and
/usr/share/mk/bsd.cpu.mk will read it, and set -march for CPUCFLAGS

This variable is used by ports, kernel, and any random Makefile may use it.
(There are similar things in Linux Gentoo also)

But OpenBSD /etc/mk.conf does not have it nor bsd.cpu.mk
exists in /usr/share/mk

So, OpenBSD does not use this approach, right?
But why? Is it because most ports ignore it?

Re: Beg for Atheros wifi driver

[IL Ka]

Almost all drivers in OpenBSD report themselves, so you can grep your dmesg
for message like "foo0 at pci0 dev0 function 0 [PCI Device name from PCI
configuration space] "
$ man autoconf
$ man dmesg

Except dmesg, this information is reported to userspace via /dev/pci and
could be read with pcidump.

$  man pci
$  man pcidump

On Mon, Apr 16, 2018 at 6:05 AM, Stuart Longland  wrote:

> On 16/04/18 08:08, Manuel Solis wrote:
> > Sorry for that, i havent figure it out, maybe i should reinstall windows
> to
> > get the info
> >  My bad.
>
> Does `lspci` work on OpenBSD?  Failing that, boot a Linux LiveCD and run
> `lspci` there, it'll tell you the chipset; `dmesg` might give you some
> more clues.
>
> `lsusb` if it's a USB wifi chip.
> --
> Stuart Longland (aka Redhatter, VK4MSL)
>
> I haven't lost my mind...
>   ...it's backed up on a tape somewhere.
>
>

Re: DMESG / syslog

[IL Ka]

Hello.
This is "kern" facility.

# touch  /var/log/dmesg

And then add
"kern.* /var/log/dmesg" to your "syslog.conf".
Restart syslog and anything printed by kernel will go to /var/log/dmesg

But note that when booting, kernel does not have access to syslog, so it
stores messages in its internal buffer (which you can read by ``dmesg``)
and after boot, its contents are written to /var/run/dmesg.boot

man syslog.conf
man dmesg

PS: when adding new log file, make sure to configure its rotation using
newsysliog

On Mon, Apr 16, 2018 at 7:14 PM, sven falempin 
wrote:

> Dear readers,
>
> This question is probably answer somewhere
> but i m afraid to follow any non openBSD style answer.
>
> How do it get DMESG messages in my log ( like when a usb is attached )
>
> syslog *.*  does not contain them right ?
>
> Best,
>
> --
> --
> 
> -
> Knowing is not enough; we must apply. Willing is not enough; we must do
>

Re: trouble installing php on 6.3

[IL Ka]

Hm.. sounds strange then.

Did you try to call "pkg_add libxml"?
If not, then try and in case of success try pkg_add php again


If it does not work, then lets do the following:

To make sure libxml is deleted
# pkg_delete libxml

use different mirror
# echo "http://ftp.eu.openbsd.org/pub/OpenBSD/"; > /etc/installurl

run pkg_add in verbose mode asking it to use different folder

# mkdir /tmp/foo
PKG_TMPDIR=/tmp/foo pkg_add -vvv libxml

And post output here


On Mon, Apr 16, 2018 at 6:52 PM, Michael Maurer 
wrote:

>
> > Also, try to download this file and unpack it. If
> >
> > $ wget https://ftp.fau.de/pub/OpenBSD/6.3/packages/amd64/
> libxml-2.9.8.tgz
> > $ tar xvfz  libxml-2.9.8.tgz
> >
> > (you may need pkg_add wget)
> > Does it work?
> >
>
> Yeah, that works, no problem.
>

Re: Community-driven OpenBSD tutorials wiki?

[IL Ka]

woman (with out man) is tool used in Emacs to read manual pages with out of
actually running man

https://www.gnu.org/software/emacs/manual/html_mono/woman.html
:)

On Mon, Apr 16, 2018 at 6:25 PM, Mehma Sarja  wrote:

> It is meant as a play on words, a light hearted comment. I see too many
> "shit" and "fuck" comments in posts these days from people trying to sound
> important when the subject matter is not.
>
> Mehma
> ---
>
>
>
> On Mon, Apr 16, 2018, 1:20 AM Stuart Henderson 
> wrote:
>
> > On 2018-04-14, Mehma Sarja  wrote:
> > > Man pages, as opposed to woman pages, help one accomplish a task.
> >
> > What do you mean, "as opposed to woman pages"?
> >
> > In this context it is simply short for "manual".
> >
> >
> >
>

Re: trouble installing php on 6.3

[IL Ka]

 php depends on libxml, pkg_add tries to download it,  and downloaded
archive is broken.
pkg_add uses "/etc/installurl" to find website to download packages. You
may try different website (echo "https://ftp.openbsd.org/pub/OpenBSD/"; >
/etc/installurl)

Also, try to download this file and unpack it. If

$ wget https://ftp.fau.de/pub/OpenBSD/6.3/packages/amd64/libxml-2.9.8.tgz
$ tar xvfz  libxml-2.9.8.tgz

(you may need pkg_add wget)
Does it work?



On Mon, Apr 16, 2018 at 4:37 PM, Michael Maurer 
wrote:

> I'm having trouble setting up php on a fresh install of 6.3. This is what
> I get
>
> -
> burt# pkg_add php
> quirks-2.414 signed on 2018-03-28T14:24:37Z
> Ambiguous: choose package for php
> a   0: 
> 1: php-5.6.34
> 2: php-7.0.28
> Your choice: 1
> Fatal error: Ustar
> [https://ftp.fau.de/pub/OpenBSD/6.3/packages/amd64/
> libxml-2.9.8.tgz][share/gtk-doc/html/libxml2/libxml2-parserInternals.html
> ]:
> Premature end of archive
> Fatal error: Installation of libxml-2.9.8 failed, partial installation
> recorded as partial-libxml-2.9.8
>  at /usr/libdata/perl5/OpenBSD/PkgAdd.pm line 801.
> -
>
> choice doesn't really matter, same answer. I tried googling the error
> code, but found nothing, hence why I post here. New to OpenBSD as
> well.
>
> cheers,
> Michael
>
>

Re: OpenBSD 6.3 kernel panic

[IL Ka]

Technically, you can debug your real machine kernel using serial (aka com)
port, but I do not think you need to do that.
When your kernel panics, it takes your to ddb, right?

You got "uvm_fault  page fault trap": it means kernel tries to access some
invalid memory address.
It happens in  "ihidev_intr" (HID-over-i2c driver) at offset 0x18a.
This address is stored in registry, that is why Mike Larkin aksed you to do
"show reg": get registers values, and send them to list.

So, there is some bug in ihidev_intr driver, you need to post whole
text + "show
reg" output to bugs@ along with your laptop name.




On Mon, Apr 16, 2018 at 4:13 AM, Juan Morado  wrote:

> Rupert, that's a great article, thanks for sharing. I don't see how that
> helps when my OpenBSD host machine would crash (not the QEMU guest) when I
> so much as touch the track pad.
>
> On Sun, Apr 15, 2018 at 2:05 AM, Rupert Gallagher 
> wrote:
>
> > http://bijanebrahimi.github.io/blog/remote-debugging-the-
> > running-openbsd-kernel.html
> >
> > On Sun, Apr 15, 2018 at 08:02, Mike Larkin  wrote:
> >
> > PS, this bug report leaves a lot to be desired... -ml
> >
> >
>

Re: vgafb manpage is in wrong place, should I report it?

[IL Ka]

 > When a manual page applies to more than 1 arch, we place it a level up.

Thank you, but should not we add comment like the one we have for "man pci"

SYNOPSIS
   # macppc, sparc64
   vgafb* at pci?

Btw, I found some more things to improve in mans like:

options(4) APERTURE section should have "See xf86(4)"
remark (it is done for almost all options except aperture)

Installation process asked me if I want my X11 to be "started by xdm(1)"
and it should be rephrased to "started by display manager xenodm(1) (xdm
clone)"
since there is no xdm(1)

Experienced user will never ever notice these small things, but they could
help newbies like me:)

I can fix it and send diff to tech@ (or where should I send it?) but I am
not sure about quality for my English.

Ilya.

Re: OpenBSD 6.3 kernel panic

[IL Ka]

>
> Maybe kernel panic isn't the correct terminology? ddb is invoked anytime I
> touch the track pad while booting.

 You are right: it is kernel panic.

Accroding to ddb(4):
"ddb is invoked upon a kernel panic when the sysctl(8) ddb.panic is set to
1."

I am not sure, but I believe you can disable it and get kernel panic
message on console instead of ddb by disabling this option in
"/etc/sysctl.conf" and reboot
But even with ddb you can get some useful information to report to bugs@.
See https://www.openbsd.org/ddb.html
I think "traceback" and "show panic" could be useful

vgafb manpage is in wrong place, should I report it?

[IL Ka]

Hello,
I am pretty new to OpenBSD and not sure if I should report minor issue to
bugs@, but I just found that vgafb(4) device is supported only on macppc
and sparc64 (according to src/sys). It has nothing to do with i386 nor with
amd64.

But for some reason it's man page sits directly in /usr/share/man/man4
While other platform-specific mans live in  /usr/share/man/man4/${machine}
(lcd(4) is good example).

Ilya.

Re: Xfce with the .xinitrc file

[IL Ka]

 Hi,
So, does  xfce4-session start with out of console kit or does not start at
all?
Do you use display manager or startx?
Note that .xinitrc is used only by xinit (startx), not by xenodm/xdm.

ck-launch-session  is part of ConsoleKit, do you have it installed?


On Fri, Apr 13, 2018 at 1:38 PM, Olivier REGNIER