Fixed! (was: unwindctl doesn't connect to unwind, error message: "unwindctl: connect: /var/run/unwind.sock: No such file or directory")

[Felix Maschek]

Hi,

with the latest snapshot the problem is solved:

    vatrox$ unwindctl status DoT
        selected type status
           *  DoT validating

           histogram[ms]
           <10   <20   <40   <60   <80  <100 <200  <400  <600  <800 
<1000 >
             5 0 1 0 0 0 0 0 0 0 
0 0


Thank you!

Kind regards

Felix

Re: Is there an easier way to browse ports?

[Adam Thompson]

On 2019-11-01 06:12, Mischa wrote:

On 1 Nov 2019, at 12:08, Alfred Morgan  wrote:

My current workflow looks something like this:

$ cd /usr/ports
$ make print-index | less
I search and scroll through and find something interesting such as
opensonic.
I read the Info: game based on the Sonic the Hedgehog universe
^Z
$ cat games/opensonic/pkg/DESCR # I can't get make describe to work
I read more about it.
I google opensonic for screenshots.
$ pkg_add opensonic
$ opensonic
$ fg

Ideally I would like a graphical ports browser with name, screenshots, 
and
description that I can scroll and search through. Curation would be 
nice:

ports suggestions, popular ports, dev team ports picks, etc.

-alfred


Have a look at: https://openports.pl 

I think it ticks some of your boxes. :)

Mischa


Also http://openports.se/ and http://ports.su/ .

-Adam

Re: Tools for writers

[Adam Thompson]

On 2019-11-02 11:14, Peter Nicolai Mathias Hansteen wrote:

2. nov. 2019 kl. 16:00 skrev Oliver Leaver-Smith :

What tools do people find useful for writing on OpenBSD? By writing I 
mean long form such as novels and technical books, including plot and 
character development, outlining, and formatting for publishing (not 
all the same application necessarily)


I have found a number which boast Linux support, but not really 
anything that stands out which supports OpenBSD (aside from the 
obvious LaTeX et al.)


I really can’t speak to plot and character development, but all three
editions of The Book of PF were written using OpenOffice and later
LibreOffice write on OpenBSD snapshots.

Earlier versions of that manuscript were developed using DocBook SGML
(editing with emacs), but the publisher (fortunately) did not want any
truck with that.

For any new projects I would likely look half-heartedly for something
markdown based but would probably end up going the LibreOffice route
again.



FWIW, Brian Kernighan's new book was written using groff(1), with final 
rasterization done by gs(1), obviously there's a number of other tools 
involved.


On the other hand, unless you name is Brian Kernighan (or possibly 
Kristaps, Ingo, or jmc@) I doubt that toolset will satisfy you :-).


A few people around here have used TeX, LaTeX, and LyX (a LaTeX 
front-end) all of which are very much capable of large projects split 
into sections/chapters/etc.
 AFAIK OpenBSD's LaTeX / TeX packages are all more than adequate to the 
task, and all of the necessary tools are in ports.


-Adam

Re: Tools for writers

[Martin Schröder]

Am Sa., 2. Nov. 2019 um 16:06 Uhr schrieb Oliver Leaver-Smith
:
> What tools do people find useful for writing on OpenBSD? By writing I mean 
> long form such as novels and technical books, including plot and character 
> development, outlining, and formatting for publishing (not all the same 
> application necessarily)

Some writers swear on Scrivener. It's proprietary and Mac/Win only, though.

Best
Martin

build error on octeon, 6.6

[Christian Groessler]

Hi,

I've installed OpenBSD 6.6 on an EdgeRouter Lite. I wanted to rebuild 
the system.


/usr/src and /usr/obj are on a NFS server, I've changed /etc/mk.conf 
accordingly:


routie$ cat /etc/mk.conf
BSDSRCDIR=/net/sirius/temp/routie-build/6.6/src
BSDOBJDIR=/net/sirius/temp/routie-build/6.6/obj
SKIPDIR=games
routie$
routie$ ls -l /usr/obj /usr/src
lrwxr-xr-x  1 root  wheel  37 Nov  5 19:38 /usr/obj -> 
/net/sirius/temp/routie-build/6.6/obj
lrwxr-xr-x  1 root  wheel  37 Nov  5 19:38 /usr/src -> 
/net/sirius/temp/routie-build/6.6/src

routie$


In /usr/src I typed "make obj" and then "make build". After building for 
~1 day it fails with


...
ild/6.6/src/gnu/usr.bin/clang/libLLVM/../../../llvm/include/llvm/Transforms/Utils 
-I/net/sirius/temp/routie-build/6.6/src/gnu/usr.bin/clang/libLLVM/../../../llvm/include/llvm/Transforms 
-I/net/sirius/temp/routie-build/6.6/src/gnu/usr.bin/clang/libLLVM/obj/../include/llvm/Mips 
-I/net/sirius/temp/routie-build/6.6/src/gnu/usr.bin/clang/libLLVM/../../../llvm/lib/Target/Mips 
-I/net/sirius/temp/routie-build/6.6/src/gnu/usr.bin/clang/libLLVM/obj/../include/llvm/Mips 
-I/net/sirius/temp/routie-build/6.6/src/gnu/usr.bin/clang/libLLVM/../../../llvm/lib/Target/Mips 
-I/net/sirius/temp/routie-build/6.6/src/gnu/usr.bin/clang/libLLVM/obj/../include/llvm/Mips 
-I/net/sirius/temp/routie-build/6.6/src/gnu/usr.bin/clang/libLLVM/../../../llvm/lib/Target/Mips 
-I/net/sirius/temp/routie-build/6.6/src/gnu/usr.bin/clang/libLLVM/obj/../include/llvm/Mips 
-I/net/sirius/temp/routie-build/6.6/src/gnu/usr.bin/clang/libLLVM/../../../llvm/lib/Target/Mips 
-I/net/sirius/temp/routie-build/6.6/src/gnu/usr.bin/clang/libLLVM/obj/../include/llvm/Mips 
-I/net/sirius/temp/routie-build/6.6/src/gnu/usr.bin/clang/libLLVM/../../../llvm/lib/Target/Mips 
-I/net/sirius/temp/routie-build/6.6/src/gnu/usr.bin/clang/libLLVM/obj/../include/llvm/Mips 
-I/net/sirius/temp/routie-build/6.6/src/gnu/usr.bin/clang/libLLVM/../../../llvm/lib/Target/Mips 
-I/net/sirius/temp/routie-build/6.6/src/gnu/usr.bin/clang/libLLVM/../../../llvm/include/llvm/Transforms 
-I/net/sirius/temp/routie-build/6.6/src/gnu/usr.bin/clang/libLLVM/../../../llvm/include/llvm/Transforms/IPO 
-I/net/sirius/temp/routie-build/6.6/src/gnu/usr.bin/clang/libLLVM/../../../llvm/include 
-I/net/sirius/temp/routie-build/6.6/src/gnu/usr.bin/clang/libLLVM/../include 
-I/net/sirius/temp/routie-build/6.6/src/gnu/usr.bin/clang/libLLVM/obj 
-I/net/sirius/temp/routie-build/6.6/src/gnu/usr.bin/clang/libLLVM/obj/../include 
-DNDEBUG -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS 
-D__STDC_FORMAT_MACROS -DLLVM_PREFIX="/usr" -DLLDB_DISABLE_PYTHON -c 
/net/sirius/temp/routie-build/6.6/src/gnu/usr.bin/clang/libLLVM/../../../llvm/lib/Target/AMDGPU/AMDGPUTargetMachine.cpp 
-o AMDGPUTargetMachine.o

c++: error: unable to execute command: Segmentation fault
c++: error: clang frontend command failed due to signal (use -v to see 
invocation)

OpenBSD clang version 8.0.1 (tags/RELEASE_801/final) (based on LLVM 8.0.1)
Target: mips64-unknown-openbsd6.6
Thread model: posix
InstalledDir: /usr/bin
c++: note: diagnostic msg: PLEASE submit a bug report to 
http://llvm.org/bugs/ and include the crash backtrace, preprocessed 
source, and associated run script.

c++: note: diagnostic msg:


PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
Preprocessed source(s) and associated run script(s) are located at:
c++: note: diagnostic msg: /tmp/AMDGPUTargetMachine-6052ab.cpp
c++: note: diagnostic msg: /tmp/AMDGPUTargetMachine-6052ab.sh
c++: note: diagnostic msg:


*** Error 254 in 
/net/sirius/temp/routie-build/6.6/src/gnu/usr.bin/clang/libLLVM 
(:67 'AMDGPUTargetMachine.o': @c++ -O2 -pipe -...)
*** Error 1 in /net/sirius/temp/routie-build/6.6/src/gnu/usr.bin/clang 
(:48 'all')
*** Error 1 in /net/sirius/temp/routie-build/6.6/src/gnu/usr.bin 
(:48 'all')
*** Error 1 in /net/sirius/temp/routie-build/6.6/src/gnu 
(:48 'all')

*** Error 1 in . (:48 'all')
*** Error 1 in . (Makefile:95 'do-build')
*** Error 1 in /usr/src (Makefile:74 'build')
routie#


Maybe the machine has too little memory?

routie$ swapctl -lk
Device  1K-blocks Used    Avail Capacity  Priority
/dev/sd0b  220770    35824   184946    16%    0
routie$
routie$ sysctl -a | grep physmem
hw.physmem=536870912
routie$


regards,
chris

Re: Skype alternatives for OpenBSD

[Stuart Longland]

On 7/11/19 4:23 am, Jan Stary wrote:
> On Nov 03 11:55:21, secli...@boxdan.com wrote:
>> Not sure about the original poster but I would be interested in any
>> end-to-end encrypted video/audio/chat programs that are available.
> 
> On this general purpose operating system,
> the following is in a base install:
> 
> aucat ... | ssh user@host 'aucat ...'
> video ... | ssh user@host 'video ...'
Latency and video-audio synchronisation might be a bit of a crap-shoot
with such a set-up.
-- 
Stuart Longland (aka Redhatter, VK4MSL)

I haven't lost my mind...
  ...it's backed up on a tape somewhere.

Re: random packet drops with syncookies/synproxy

[Markus Wernig]

Hi again

Nobody has answered, so I suppose nobody else has this problem :-)
That's good.

So just to make sure: Is anybody using syncookies and/or synproxy in
production in a similar setup?

Thx /markus


On 11/4/19 8:35 PM, Markus Wernig wrote:
> Hi all
> 
> After being hit by some synflood waves recently I enabled syncookies on
> our OBSD 6.6 i386 CARP fw pair:
> 
> set syncookies always
> 
> This stopped the state table from filling up. But after some hours pf
> started (randomly?) dropping legitimate connection attempts, both on
> external->internal (dst-natted) and on internal->internal (not natted)
> connections (TCP only, afaict).
> 
> Looking at pflog and the rule number that blocked the packet, it seems
> that the preceding "pass quick" rules matching the packets were ignored.
> 
> The packets that were dropped were the ACK ones, so the SYN-SYNACK seems
> to have taken place. The client then usually retransmitted the ACK,
> which kept being dropped for ca. 15-20 seconds, after which time it was
> suddenly accepted and the connection established. Many times also only
> the first ACK was dropped, and the first retransmit was accepted.
> 
> So I disabled syncookies and set the relevant ~5 external->internal
> rules to synproxy state.
> 
> With that, the same behaviour happened within a few minutes.
> 
> During that time pfctl -vsi showed the "synproxy" counter increasing by
> multiple thousands per second (sic), while the state table entries
> remained stable around 500 (their normal value).
> 
> So I disabled the synproxy state again, but reloading the rules with
> pfctl was not enough, I had to reboot both boxes to stop them from
> dropping legitimate connections. With both syncookies and synproxy
> disabled, the problem does not occur.
> 
> Is anybody aware of anything that could trigger this behaviour? Or have
> any hint where I could look further? I have all the log files if more
> info is needed.
> 
> thx /markus
> 
> (btw. the behaviour was the same on 6.5)
> 

Re: Tools for writers

[Roderick]

On Wed, 6 Nov 2019, Oliver Leaver-Smith wrote:


The use case I have is for a novel which should require less formatting
than a technical book, so I should be able to retrofit that after once
I have investigated the many tools mentioned in the thread.


Plain TeX would mean in that case a simple text file with few formatting
tags, for example for italics and boldface. Then you can generate
a postcript file with tex and dvips commands and print it, if you want.
Later you can perfectionate it.

To read the first pages of "The TeXBook" would be enough for the beginning,
and you find a pdf version googling for it.

nroff is interesting, because is a unix standard from the beginning
and (in the meantime only almost) everywhhere, but is more complicated
to learn, the source less readable, and the result not better.

Rodrigo

Re: Skype alternatives for OpenBSD

[Jan Stary]

On Nov 03 11:55:21, secli...@boxdan.com wrote:
> Not sure about the original poster but I would be interested in any
> end-to-end encrypted video/audio/chat programs that are available.

On this general purpose operating system,
the following is in a base install:

aucat ... | ssh user@host 'aucat ...'
video ... | ssh user@host 'video ...'

Re: Tools for writers

[Damien Thiriet]

Hi,


As an alternative to LaTeX, especially if you design the book,
you may give ConTeXt a chance. Just several elements of
comparison with LaTeX

Cons:

* quite hard learning-curve
* documentation is hard to find a the beginning. 
  The reference manual is not maintained any more. 
  Things are however better than three years ago: the ConTeXt excursion
  book has been updated. Official documentation is now split into
  manuals dealings with specific issues (tables, biblio, XML and so on).
* ConTeXt is a niche even inside the *TeX world.
* Publishers usually ask for LaTeX.
* You have to design your layout from scratch (no documentclass shiped,
  only paper format)


Pros:
* you don't need to upload packages, and check for incompabilities.
  I have been using it a lot for three years now, and never loaded any 
  third-part module.
* bibliography out of the box, which is great since I could'nt have
  biber working on OpenBSD.
* metapost graphics out of the box. MP graphics compile faster than TikZ
  since there are tightly integrated with base code (the user base is however 
  much smaller than TikZ)
* its key-value syntax is quite predictible, once you're used at it.
* you can have XML and EPUB output (default is PDF) 
* smaller base than LaTeX if you install it as a standalone (260M,
  mostly because of fonts). I could'nt manage to install the Mkiv standalone 
version
  (being too stupid to patch its install script), but Hans Hagen
  released a distribution of luametatex, the development version of ConTeXt, a
  few weeks ago and it is available for OpenBSD.
  http://www.pragma-ade.com/install.htm

  Troubles with pdf inclusions can be bypassed uploading
  those luametatex binaries after installation 
  http://dl.contextgarden.net/build/luametatex/amd64-openbsd6.6/luametatex

Regards,

Damien Thiriet

Re: unwindctl doesn't connect to unwind, error message: "unwindctl: connect: /var/run/unwind.sock: No such file or directory"

[Otto Moerbeek]

It appears there is a diff in snaps. Should be fixed soon.

-Otto

On Wed, Nov 06, 2019 at 04:41:42PM +0100, Felix Maschek wrote:

> Done so. But I'm not able to understand the trace. I have attached it.
> 
> Kind regards
> 
> Felix
> 
> On 2019-11-06 16:29, Otto Moerbeek wrote:
> > On Wed, Nov 06, 2019 at 04:16:10PM +0100, Felix Maschek wrote:
> > 
> > > Hi,
> > > 
> > > unwind is running and does talk to 9.9.9.9 (checked with DNS Leak Test -
> > > bash.ws ):
> > > 
> > >       vatrox$ ps -A | grep unwind
> > >           42668 ??  Ip   0:00.01 /sbin/unwind
> > >           42070 ??  IpU  0:03.27 unwind: resolver (unwind)
> > >           43163 ??  Ip   0:00.09 unwind: frontend (unwind)
> > >           59857 ??  Ip   0:00.01 unwind: captive portal (unwind)
> > >           72389 p1  R+/2 0:00.00 grep unwind
> > > 
> > > The socket is missing:
> > > 
> > >       vatrox$ ls /var/run
> > >           ConsoleKit  cron.sock   dev.db  ld.so.hints rc.d
> > > syslog.pid  utmp
> > >           apmdev  dbus    dmesg.boot  ntpd.sock smtpd.sock  user
> > Strange. Tge code is structured in such a way that failure to cerate the
> > socket is fatal.
> > 
> > Once thing to try:
> > 
> > run
> > ktrace -i rcctl start unwind
> > 
> > and then
> >   rcctl stop unwind
> > kdump > /tmp/d
> > 
> > amd inspect /tmp/d to find out what happended to the socket.
> > 
> > -Otto
> > 
> > > Kind regards
> > > 
> > > Felix
> > > 
> > > On 2019-11-06 16:08, Otto Moerbeek wrote:
> > > > On Wed, Nov 06, 2019 at 03:41:10PM +0100, Felix Maschek wrote:
> > > > 
> > > > > Hi,
> > > > > 
> > > > > I've used unwind for some weeks and observed a problem after 
> > > > > upgrading to
> > > > > last snapshot (after some weeks).
> > > > > 
> > > > > Calling unwindctl leads to the following error message:
> > > > > 
> > > > >    vatrox$ unwindctl status DoT
> > > > >    unwindctl: connect: /var/run/unwind.sock: No such file or 
> > > > > directory
> > > > > 
> > > > > My configuration (which still is functional):
> > > > > 
> > > > >    /etc/rc.conf.local:
> > > > > 
> > > > >        unwind_flags=""
> > > > > 
> > > > >    /etc/dhclient.conf:
> > > > > 
> > > > >        prepend domain-name-servers 127.0.0.1;
> > > > > 
> > > > >    /etc/unwind.conf:
> > > > > 
> > > > >        forwarder 9.9.9.9 port 853 authentication name 
> > > > > dns.quad9.net DoT
> > > > > 
> > > > > Any idea?
> > > > Is unwind running? Does /var/run/unwind.sock exist?
> > > > 
> > > > -Otto
> > > > 
> 

Re: Downgrade 6.6 to 6.5

[chohag]

Theo de Raadt writes:
> I have some sort of X1rev6 and I don't see the problem.
>
> The situation is you have the hardware, and you also have the sourcecode,
> and the repository to traverse investigate the problem.
>
> That sounds hard, until you give it a try.

To be fair, it *is* hard. You have to have some understanding of
how the magic rock you've blindly devoted yourself to works and how
to encant the magical prescriptions that instruct it, which require
learning such esoteric arts as "reading" and "thinking" and "logic".

These are not things which come easily to many. The fact that all
the required information is at everyone's fingertips and literally
begging for attention notwthstanding.

Matthew

Re: unwindctl doesn't connect to unwind, error message: "unwindctl: connect: /var/run/unwind.sock: No such file or directory"

[Felix Maschek]

Done so. But I'm not able to understand the trace. I have attached it.

Kind regards

Felix

On 2019-11-06 16:29, Otto Moerbeek wrote:

On Wed, Nov 06, 2019 at 04:16:10PM +0100, Felix Maschek wrote:


Hi,

unwind is running and does talk to 9.9.9.9 (checked with DNS Leak Test -
bash.ws ):

      vatrox$ ps -A | grep unwind
          42668 ??  Ip   0:00.01 /sbin/unwind
          42070 ??  IpU  0:03.27 unwind: resolver (unwind)
          43163 ??  Ip   0:00.09 unwind: frontend (unwind)
          59857 ??  Ip   0:00.01 unwind: captive portal (unwind)
          72389 p1  R+/2 0:00.00 grep unwind

The socket is missing:

      vatrox$ ls /var/run
          ConsoleKit  cron.sock   dev.db  ld.so.hints rc.d
syslog.pid  utmp
          apmdev  dbus    dmesg.boot  ntpd.sock smtpd.sock  user

Strange. Tge code is structured in such a way that failure to cerate the
socket is fatal.

Once thing to try:

run
ktrace -i rcctl start unwind

and then
  rcctl stop unwind
kdump > /tmp/d

amd inspect /tmp/d to find out what happended to the socket.

-Otto


Kind regards

Felix

On 2019-11-06 16:08, Otto Moerbeek wrote:

On Wed, Nov 06, 2019 at 03:41:10PM +0100, Felix Maschek wrote:


Hi,

I've used unwind for some weeks and observed a problem after upgrading to
last snapshot (after some weeks).

Calling unwindctl leads to the following error message:

       vatrox$ unwindctl status DoT
       unwindctl: connect: /var/run/unwind.sock: No such file or directory

My configuration (which still is functional):

       /etc/rc.conf.local:

           unwind_flags=""

       /etc/dhclient.conf:

           prepend domain-name-servers 127.0.0.1;

       /etc/unwind.conf:

           forwarder 9.9.9.9 port 853 authentication name dns.quad9.net DoT

Any idea?

Is unwind running? Does /var/run/unwind.sock exist?

-Otto



<>

Re: Downgrade 6.6 to 6.5

[Otto Moerbeek]

On Wed, Nov 06, 2019 at 09:06:52AM -0700, Theo de Raadt wrote:

> I have some sort of X1rev6 and I don't see the problem.

Same here. no fans out of control on my X1rev6.

-Otto
> 
> The situation is you have the hardware, and you also have the sourcecode,
> and the repository to traverse investigate the problem.
> 
> That sounds hard, until you give it a try.
> 
> Josh  wrote:
> 
> > Snapshot -current #427 did not solve the problem after all.
> > so after much testing with bios options, disabling the intel
> > acceleration and even the chrome "hardware acceleration", nothing
> > seems to stop the fan from spinning. It will take a good 5min for the
> > fan to stop when computer is idling (activity of 96-98% idling, using
> > top CS). If I do a zzz like after one minute of idling and wake it
> > right after, the fan just stops. CPU temp remains the same as before
> > the zzz.
> > 
> > Not sure what to do next, I believe this could be reproduced on any X1
> > 6G... Just install 6.6, log through xenodm, launch Chrome, heavy
> > programs to start the FAN spinning then idle the laptop and see how
> > long it takes for the fan to stop.
> > You should also be able to reproduce the other behaviour: when cpu
> > temp is 55-60degC and fan spinning, you can zzz and wake it right
> > away, fan remains stopped (as long as you don't do cpu intense tasks
> > upon awake)
> > 
> > would a "sendbug" be helpful?
> > 
> > 
> > On Sun, Nov 3, 2019 at 3:41 PM Josh  wrote:
> > >
> > > hi,
> > >
> > > I've upgraded from 6.5 to 6.6 on my X1 6G and since then, I am unable
> > > to find the reason(s) of the high fan spinning.
> > > Is there a procedure to downgrade to 6.5 or should I just reinstall
> > > from scratch?
> > >
> > > thank you
> > 
> 

Re: Downgrade 6.6 to 6.5

[Theo de Raadt]

I have some sort of X1rev6 and I don't see the problem.

The situation is you have the hardware, and you also have the sourcecode,
and the repository to traverse investigate the problem.

That sounds hard, until you give it a try.

Josh  wrote:

> Snapshot -current #427 did not solve the problem after all.
> so after much testing with bios options, disabling the intel
> acceleration and even the chrome "hardware acceleration", nothing
> seems to stop the fan from spinning. It will take a good 5min for the
> fan to stop when computer is idling (activity of 96-98% idling, using
> top CS). If I do a zzz like after one minute of idling and wake it
> right after, the fan just stops. CPU temp remains the same as before
> the zzz.
> 
> Not sure what to do next, I believe this could be reproduced on any X1
> 6G... Just install 6.6, log through xenodm, launch Chrome, heavy
> programs to start the FAN spinning then idle the laptop and see how
> long it takes for the fan to stop.
> You should also be able to reproduce the other behaviour: when cpu
> temp is 55-60degC and fan spinning, you can zzz and wake it right
> away, fan remains stopped (as long as you don't do cpu intense tasks
> upon awake)
> 
> would a "sendbug" be helpful?
> 
> 
> On Sun, Nov 3, 2019 at 3:41 PM Josh  wrote:
> >
> > hi,
> >
> > I've upgraded from 6.5 to 6.6 on my X1 6G and since then, I am unable
> > to find the reason(s) of the high fan spinning.
> > Is there a procedure to downgrade to 6.5 or should I just reinstall
> > from scratch?
> >
> > thank you
> 

Re: unwindctl doesn't connect to unwind, error message: "unwindctl: connect: /var/run/unwind.sock: No such file or directory"

[Otto Moerbeek]

On Wed, Nov 06, 2019 at 04:29:16PM +0100, Otto Moerbeek wrote:

> On Wed, Nov 06, 2019 at 04:16:10PM +0100, Felix Maschek wrote:
> 
> > Hi,
> > 
> > unwind is running and does talk to 9.9.9.9 (checked with DNS Leak Test -
> > bash.ws ):
> > 
> >     vatrox$ ps -A | grep unwind
> >         42668 ??  Ip   0:00.01 /sbin/unwind
> >         42070 ??  IpU  0:03.27 unwind: resolver (unwind)
> >         43163 ??  Ip   0:00.09 unwind: frontend (unwind)
> >         59857 ??  Ip   0:00.01 unwind: captive portal (unwind)
> >         72389 p1  R+/2 0:00.00 grep unwind
> > 
> > The socket is missing:
> > 
> >     vatrox$ ls /var/run
> >         ConsoleKit  cron.sock   dev.db  ld.so.hints rc.d   
> > syslog.pid  utmp
> >         apmdev  dbus    dmesg.boot  ntpd.sock smtpd.sock  user
> 
> Strange. Tge code is structured in such a way that failure to cerate the
> socket is fatal.
> 
> Once thing to try:
> 
> run 
>   ktrace -i rcctl start unwind 
> 
> and then
> rcctl stop unwind
>   kdump > /tmp/d
> 
> amd inspect /tmp/d to find out what happended to the socket.

Hmm that does not work.

stop unwind and do:

ktrace -i /sbin/unwind
ktrace -C
kdump > /tmp/d

Search for unwind.sock in /tmp/d

-Otto

Re: Tools for writers

[Oliver Leaver-Smith]

Thanks everyone for recommendations, I think I am just going to use VimOutliner 
for development and outlining. The use case I have is for a novel which should 
require less formatting than a technical book, so I should be able to retrofit 
that after once I have investigated the many tools mentioned in the thread. 

-ols
--
Oliver Leaver-Smith
+44(0)114 360 1337
TZ=Europe/London

Re: unwindctl doesn't connect to unwind, error message: "unwindctl: connect: /var/run/unwind.sock: No such file or directory"

[Otto Moerbeek]

On Wed, Nov 06, 2019 at 04:16:10PM +0100, Felix Maschek wrote:

> Hi,
> 
> unwind is running and does talk to 9.9.9.9 (checked with DNS Leak Test -
> bash.ws ):
> 
>     vatrox$ ps -A | grep unwind
>         42668 ??  Ip   0:00.01 /sbin/unwind
>         42070 ??  IpU  0:03.27 unwind: resolver (unwind)
>         43163 ??  Ip   0:00.09 unwind: frontend (unwind)
>         59857 ??  Ip   0:00.01 unwind: captive portal (unwind)
>         72389 p1  R+/2 0:00.00 grep unwind
> 
> The socket is missing:
> 
>     vatrox$ ls /var/run
>         ConsoleKit  cron.sock   dev.db  ld.so.hints rc.d   
> syslog.pid  utmp
>         apmdev  dbus    dmesg.boot  ntpd.sock smtpd.sock  user

Strange. Tge code is structured in such a way that failure to cerate the
socket is fatal.

Once thing to try:

run 
ktrace -i rcctl start unwind 

and then
rcctl stop unwind
kdump > /tmp/d

amd inspect /tmp/d to find out what happended to the socket.

-Otto

> 
> 
> Kind regards
> 
> Felix
> 
> On 2019-11-06 16:08, Otto Moerbeek wrote:
> > On Wed, Nov 06, 2019 at 03:41:10PM +0100, Felix Maschek wrote:
> > 
> > > Hi,
> > > 
> > > I've used unwind for some weeks and observed a problem after upgrading to
> > > last snapshot (after some weeks).
> > > 
> > > Calling unwindctl leads to the following error message:
> > > 
> > >      vatrox$ unwindctl status DoT
> > >      unwindctl: connect: /var/run/unwind.sock: No such file or directory
> > > 
> > > My configuration (which still is functional):
> > > 
> > >      /etc/rc.conf.local:
> > > 
> > >          unwind_flags=""
> > > 
> > >      /etc/dhclient.conf:
> > > 
> > >          prepend domain-name-servers 127.0.0.1;
> > > 
> > >      /etc/unwind.conf:
> > > 
> > >          forwarder 9.9.9.9 port 853 authentication name dns.quad9.net DoT
> > > 
> > > Any idea?
> > Is unwind running? Does /var/run/unwind.sock exist?
> > 
> > -Otto
> > 

Re: unwindctl doesn't connect to unwind, error message: "unwindctl: connect: /var/run/unwind.sock: No such file or directory"

[Felix Maschek]

Hi,

unwind is running and does talk to 9.9.9.9 (checked with DNS Leak Test - 
bash.ws ):


    vatrox$ ps -A | grep unwind
        42668 ??  Ip   0:00.01 /sbin/unwind
        42070 ??  IpU  0:03.27 unwind: resolver (unwind)
        43163 ??  Ip   0:00.09 unwind: frontend (unwind)
        59857 ??  Ip   0:00.01 unwind: captive portal (unwind)
        72389 p1  R+/2 0:00.00 grep unwind

The socket is missing:

    vatrox$ ls /var/run
        ConsoleKit  cron.sock   dev.db  ld.so.hints rc.d    
syslog.pid  utmp

        apmdev  dbus    dmesg.boot  ntpd.sock smtpd.sock  user


Kind regards

Felix

On 2019-11-06 16:08, Otto Moerbeek wrote:

On Wed, Nov 06, 2019 at 03:41:10PM +0100, Felix Maschek wrote:


Hi,

I've used unwind for some weeks and observed a problem after upgrading to
last snapshot (after some weeks).

Calling unwindctl leads to the following error message:

     vatrox$ unwindctl status DoT
     unwindctl: connect: /var/run/unwind.sock: No such file or directory

My configuration (which still is functional):

     /etc/rc.conf.local:

         unwind_flags=""

     /etc/dhclient.conf:

         prepend domain-name-servers 127.0.0.1;

     /etc/unwind.conf:

         forwarder 9.9.9.9 port 853 authentication name dns.quad9.net DoT

Any idea?

Is unwind running? Does /var/run/unwind.sock exist?

-Otto

Re: unwindctl doesn't connect to unwind, error message: "unwindctl: connect: /var/run/unwind.sock: No such file or directory"

[Otto Moerbeek]

On Wed, Nov 06, 2019 at 03:41:10PM +0100, Felix Maschek wrote:

> Hi,
> 
> I've used unwind for some weeks and observed a problem after upgrading to
> last snapshot (after some weeks).
> 
> Calling unwindctl leads to the following error message:
> 
>     vatrox$ unwindctl status DoT
>     unwindctl: connect: /var/run/unwind.sock: No such file or directory
> 
> My configuration (which still is functional):
> 
>     /etc/rc.conf.local:
> 
>         unwind_flags=""
> 
>     /etc/dhclient.conf:
> 
>         prepend domain-name-servers 127.0.0.1;
> 
>     /etc/unwind.conf:
> 
>         forwarder 9.9.9.9 port 853 authentication name dns.quad9.net DoT
> 
> Any idea?

Is unwind running? Does /var/run/unwind.sock exist?

-Otto

unwindctl doesn't connect to unwind, error message: "unwindctl: connect: /var/run/unwind.sock: No such file or directory"

[Felix Maschek]

Hi,

I've used unwind for some weeks and observed a problem after upgrading 
to last snapshot (after some weeks).


Calling unwindctl leads to the following error message:

    vatrox$ unwindctl status DoT
    unwindctl: connect: /var/run/unwind.sock: No such file or directory

My configuration (which still is functional):

    /etc/rc.conf.local:

        unwind_flags=""

    /etc/dhclient.conf:

        prepend domain-name-servers 127.0.0.1;

    /etc/unwind.conf:

        forwarder 9.9.9.9 port 853 authentication name dns.quad9.net DoT

Any idea?

Kind regards

Felix

>>>

OpenBSD 6.6-current (GENERIC.MP) #428: Tue Nov  5 13:08:03 MST 2019
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8255049728 (7872MB)
avail mem = 7992156160 (7621MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0x9cbfd000 (65 entries)
bios0: vendor LENOVO version "JBET47WW (1.12 )" date 03/10/2015
bios0: LENOVO 20BUS1KJ02
acpi0 at bios0: ACPI 5.0
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SLIC ASF! HPET ECDT APIC MCFG SSDT SSDT SSDT 
SSDT SSDT SSDT SSDT SSDT SSDT PCCT SSDT TCPA SSDT UEFI MSDM BATB FPDT UEFI

acpi0: wakeup devices LID_(S4) SLPB(S3) IGBE(S4) EXP2(S4) XHCI(S3) EHC1(S3)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpiec0 at acpi0
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz, 2195.21 MHz, 06-3d-04
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,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,MD_CLEAR,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 1 (application processor)
cpu1: Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz, 2194.93 MHz, 06-3d-04
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,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN

cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 1, core 0, package 0
cpu2 at mainbus0: apid 2 (application processor)
cpu2: Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz, 2194.94 MHz, 06-3d-04
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,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN

cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 0, core 1, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz, 2194.93 MHz, 06-3d-04
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,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,MD_CLEAR,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 2 pa 0xfec0, version 20, 40 pins
acpimcfg0 at acpi0
acpimcfg0: addr 0xf800, bus 0-63
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (PEG_)
acpiprt2 at acpi0: bus 2 (EXP1)
acpiprt3 at acpi0: bus 3 (EXP2)
acpiprt4 at acpi0: bus -1 (EXP3)
acpicpu0 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpicpu1 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpicpu2 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpicpu3 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS

acpipwrres0 at acpi0: PUBS, resource for XHCI, EHC1
acpipwrres1 at acpi0: NVP3, resource for PEG_
acpipwrres2 at acpi0: NVP2, resource for

Re: Downgrade 6.6 to 6.5

[Jay Hart]

Running the latest BIOS firmware???

Jay

> Snapshot -current #427 did not solve the problem after all.
> so after much testing with bios options, disabling the intel
> acceleration and even the chrome "hardware acceleration", nothing
> seems to stop the fan from spinning. It will take a good 5min for the
> fan to stop when computer is idling (activity of 96-98% idling, using
> top CS). If I do a zzz like after one minute of idling and wake it
> right after, the fan just stops. CPU temp remains the same as before
> the zzz.
>
> Not sure what to do next, I believe this could be reproduced on any X1
> 6G... Just install 6.6, log through xenodm, launch Chrome, heavy
> programs to start the FAN spinning then idle the laptop and see how
> long it takes for the fan to stop.
> You should also be able to reproduce the other behaviour: when cpu
> temp is 55-60degC and fan spinning, you can zzz and wake it right
> away, fan remains stopped (as long as you don't do cpu intense tasks
> upon awake)
>
> would a "sendbug" be helpful?
>
>
> On Sun, Nov 3, 2019 at 3:41 PM Josh  wrote:
>>
>> hi,
>>
>> I've upgraded from 6.5 to 6.6 on my X1 6G and since then, I am unable
>> to find the reason(s) of the high fan spinning.
>> Is there a procedure to downgrade to 6.5 or should I just reinstall
>> from scratch?
>>
>> thank you
>
>

Re: Tools for writers

[Yon]

On Tue, Nov 05, 2019 at 06:38:52PM -0500, Steve Litt wrote:
> > If you write documentation, just use the best format in the first
> > place.  If the project you are documenting allows checking in
> > documentation in mdoc(7) format, use that.
>
> TL/DR SUMMARY: mdoc(7) is cool, but based on an hour or so's research is
> insufficient for all but the simplest full length books.
>
> I've spent the last hour or so looking at man pages mandoc(1) and
> mdoc(7), and I currently don't see how a non-simple book could be
> authored in mdoc(7). First of all, I see no method of creating a header
> hierarchy like ... or \part ... \subparagraph . I'd suspect it
> could be done by nesting .Sh lines, but I couldn't see how that could
> be done.
>
> As far as I can tell, mdoc(7) has no way to declare arbitrary styles.
> If I want a style called "stories", as an author I should be able to use
> one, and worry about semantic to presentational conversion of the
> stories style to be something I make later (with CSS or LaTeX or
> whatever). Almost by definition, if I can't create new semantic styles,
> I'll need to use or reuse predefined ones, which introduces ambiguity
> and mixing of semantic and presentational.
>
> Kudos for provisions to make a bibliography, and a TOC in HTML output.
>
> mdoc(7) supported lists cover a wide variety of presentations, but as
> far as I can tell you can't make new kinds of lists based on the
> existing lists. For instance, I might have a list for people with
> vertical spacing very different from a list for concepts, and I see no
> way to do that in mdoc(7) without declaring that all people are done
> with one kind of mdoc(7) list, and all concepts are done with another.
> Another problem: If I initially do both people and concepts with a
> certain mdoc(7) list type, and then decide people should look
> different, I'd have to search out all the people, instead of changing
> one line of CSS or one line of LaTeX.
Declaring arbitrary styles and semantics while being able to
produce HTML/EPUB and LaTeX was the main point of frundis.
I'll therefore provide some small examples, so that you may
research more if you want.

For example, you can define semantic tags for each format:

.X mtag -f latex -t people -c emph
.X mtag -f xhtml,epub -t people -c em

and then using them like:

.Sm -t people Steve

which will be rendered as Steve in
html, and \emph{Steve} in LaTeX.

There are different kind of semantic tags, whether for
phrasing elements or block/environment elements.  The
language provides common semantic elements for novels (4
header levels, TOC, links, cross-references), but it lacks
more advanced functionality, like built-in bibliographies.

When built-in functionality is not enough, you can wrap
LaTeX and HTML code with macros.  For example, you can write
the following macro hr in a file macros.frundis:

.#de hr \" define macro hr
.P
.Bf -f xhtml \" when exporting to HTML

.Ef
.Bf -f latex \" when exporting to LaTeX
\erule{\etextwidth}{1pt}
.Ef
.P
.#. \" end of definition

Then you can use it in your main file:

.If macros.frundis \" include macro definitions
.hr

If this kind of extensibility sounds like enough for what
you need, you may have a look at the whole mdoc(7) man page
frundis_syntax(5):

https://bardinflor.perso.aquilenet.fr/frundis/frundis_syntax-5.html

That said, if your books are too technical, you may end up
needing to extend yourself the language too much. Or maybe
you'll hit some unexpected limitations that will probably
not disappear with time, as the language is feature complete
for its main intended usage.

Yon

Re: Downgrade 6.6 to 6.5

[Josh]

yep, 1.41

OpenBSD 6.6-current (GENERIC.MP) #427: Sat Nov  2 13:23:11 MDT 2019
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 16896442368 (16113MB)
avail mem = 16371654656 (15613MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x9f04a000 (63 entries)
bios0: vendor LENOVO version "N23ET66W (1.41 )" date 09/02/2019
bios0: LENOVO 20KHCTO1WW
acpi0 at bios0: ACPI 5.0
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SSDT UEFI SSDT SSDT HPET APIC MCFG ECDT SSDT
SSDT BOOT BATB SSDT SSDT SSDT LPIT WSMT SSDT SSDT SSDT DBGP DBG2 MSDM
DMAR NHLT ASF! FPDT UEFI
acpi0: wakeup devices GLAN(S4) XHC_(S3) XDCI(S4) HDAS(S4) RP01(S4)
PXSX(S4) RP02(S4) PXSX(S4) PXSX(S4) RP04(S4) PXSX(S4) RP05(S4)
PXSX(S4) RP06(S4) PXSX(S4) RP07(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 2399 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz, 1789.52 MHz, 06-8e-0a
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,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,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,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 24MHz
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) i7-8650U CPU @ 1.90GHz, 1789.04 MHz, 06-8e-0a
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,SMX,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,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 4 (application processor)
cpu2: Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz, 1788.48 MHz, 06-8e-0a
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,SMX,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,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 0, core 2, package 0
cpu3 at mainbus0: apid 6 (application processor)
cpu3: Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz, 1790.06 MHz, 06-8e-0a
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,SMX,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,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 0, core 3, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 120 pins
acpimcfg0 at acpi0
acpimcfg0: addr 0xf000, bus 0-127
acpiec0 at acpi0
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 2 (RP01)
acpiprt2 at acpi0: bus -1 (RP02)
acpiprt3 at acpi0: bus -1 (RP03)
acpiprt4 at acpi0: bus -1 (RP04)
acpiprt5 at acpi0: bus 4 (RP05)
acpiprt6 at acpi0: bus -1 (RP06)
acpiprt7 at acpi0: bus -1 (RP07)
acpiprt8 at acpi0: bus -1 (RP08)
acpiprt9 at acpi0: bus 5 (RP09)
acpiprt10 at acpi0: bus -1 (RP10)
acpiprt11 at acpi0: bus -1 (RP11)
acpiprt12 at acpi0: bus -1 (RP12)
acpiprt13 at acpi0: bus -1 (RP13)
acpiprt14 at acpi0: bus -1 (RP14)
acpiprt15 at acpi0: bus -1 (RP15)
acpiprt16 at acpi0: bus -1 (RP16)
acpiprt17 at acpi0: bus -1 (RP17)
acpiprt18 at acpi0: bus -1 (RP18)
acpiprt19 at acpi0: bus -1 (RP19)
acpiprt20 at acpi0: bus -1 (RP20)
acpiprt21 at acpi0: bus -1 (RP21)
acpiprt22 at acpi0: bus -1 (RP22)
acpiprt23 at acpi0: bus -1 (RP23)
acpiprt24 at acpi0: bus -1 (RP24)
acpicpu0 at acpi0: C3(200@1034 mwait.1@0x60), C2(200@151
mwait.1@0x33), C1(1000@1 mwait.1), PSS
ac

Re: Downgrade 6.6 to 6.5

[Josh]

Snapshot -current #427 did not solve the problem after all.
so after much testing with bios options, disabling the intel
acceleration and even the chrome "hardware acceleration", nothing
seems to stop the fan from spinning. It will take a good 5min for the
fan to stop when computer is idling (activity of 96-98% idling, using
top CS). If I do a zzz like after one minute of idling and wake it
right after, the fan just stops. CPU temp remains the same as before
the zzz.

Not sure what to do next, I believe this could be reproduced on any X1
6G... Just install 6.6, log through xenodm, launch Chrome, heavy
programs to start the FAN spinning then idle the laptop and see how
long it takes for the fan to stop.
You should also be able to reproduce the other behaviour: when cpu
temp is 55-60degC and fan spinning, you can zzz and wake it right
away, fan remains stopped (as long as you don't do cpu intense tasks
upon awake)

would a "sendbug" be helpful?


On Sun, Nov 3, 2019 at 3:41 PM Josh  wrote:
>
> hi,
>
> I've upgraded from 6.5 to 6.6 on my X1 6G and since then, I am unable
> to find the reason(s) of the high fan spinning.
> Is there a procedure to downgrade to 6.5 or should I just reinstall
> from scratch?
>
> thank you

Re: Tools for writers

[Yon]

Hi,

On Wed, Nov 06, 2019 at 08:43:18AM +0100, Ingo Schwarze wrote:
> Hi Steve,
> 
> Steve Litt wrote on Tue, Nov 05, 2019 at 06:38:52PM -0500:
> > On Tue, 5 Nov 2019 18:38:03 +0100 > Ingo Schwarze wrote:
> >> Andrew wrote on Sun, Nov 03, 2019 at 12:56:58PM +:
> 
> >> [ Pandoc ]
> >>> is one of the most useful tools I have ever used.  If you are
> >>> writing any sort of documentation then I *highly* recommend
> >>> checking it out  
> 
> >> I strongly oppose that point.  
> 
> Admittedly, this was a bit of a diversion because the OP asked about
> long, general-purpose texts like books - but all the same, it didn't
> want to let the statement "pandoc is recommended for *documentation*"
> go unchallenged.
In my opinion, most of the points you made in the OpenBSD
Journal apply for novels too, and probably even more so for
technical books, but I can only judge for the first.

The fact that markdown is not semantic, but essentially
presentational, makes it impossible to make formatting
changes to a whole semantic category after the fact (e.g.
plant name, song title, place name), and impossible to
automatically extract that information from the file for
various purposes.  A fully featured apropos(1) is not
required for novels, but it's handy to at least be able to
extract a list of names from a specific semantic category,
whether to check it's correct, or to display it somewhere
else (like an index). It's also handy when translating a
work, to compare the original and translated version on
specific points, often catching mistakes.

But maybe the worst consequence of the markdown pitfalls you
mention, is that it cannot provide any kind of syntax error
reporting.  Markup languages have different needs than
programming languages.  For example favouring warnings (like
you did for mandoc(1)) is generally better than fatal errors
(like often LaTeX).  But no warnings (like markdown) is
worse than both.  Some people seem to think syntax
highlighting is enough to avoid formatting mistakes, but you
cannot depend on it when reading a diff, for example.  And
anyways, it's still easy to overlook a small formatting
error.

In my opinion, most of mandoc(1) design philosophy is worth
considering for non-documentation long works: diff and
grep-friendly simple non-ambiguous syntax, good non-fatal
warnings, mostly semantic and fast.  All of this seems good
for any big project.  When designing frundis(1) for novels,
it's been my main inspiration, though it falls short on one
point: due to the unpredictable requirements of creative
works, it's been simpler (unavoidable?) to not make it fully
self-contained.  At least, new macros can abstract target
format specific parts and make it fully-contained per
project, which is still better than markdown.

For long technical books, I don't think there's still
anything approaching what mandoc(1) is for documentation.
LaTeX and groff are good, but not semantic enough (making
non-PDF exports tricky), have a quite fragile syntax at
times and, in my experience, are not great at error
reporting - which may be because of current tools instead of
the languages themselves, though.

Yon

Re: Tools for writers

[Marc Chantreux]

> With the exception of perlpod(1)/pod2man(1), most programs that

good to know as i'm really confortable with pod.

> page formatting.  scdoc(1) is not an exception; the output code
> quality is poor indeed
>  * stray .P before and after .SH
> ...

this list is really interesting. maybe it should be shared with
the scdoc project. it will not solve the problems but at least those
ones can be fixed.

> To summarize, there wasn't any need for yet another man(7)
> autogenerator, perlpod(1) already existed, and while most man(7)
> autogenerators are bad, this one may even be producing below-average
> quality.

my opinion is more blur: using a tool that works find is important but
i'm always happy when i can remove a usage of an interpreted
langage (even perl which was by far my prefered one before i started to use 
raku).

> Do not use it.

i wasn't even wanting to: this one was mostly a joke to tickle you then
it ends up to a really interesting and constructive answer. thanks a
lot.

marc

OpenBSD BFD support

[Vasco Matos]

Hi,


I see that a white paper was written in order to have BFD (Bidirectional
Forwarding Detection) implemented on OpenBSD.
However after reading the paper and try to implement it it just doesn't
work.
I already tried to reach the white paper writer (Peter Hessler) without
success. Does anyone know if this is an ongoing project?
>From the Changelog "https://www.openbsd.org/plusXX.html";
 page the only thing I can see is a
mention on the 6.5 version but it points to a blank page
(Reconnected bfd(4)  to the build after
updating for sounlock() api change.)



Thanks

Re: Tools for writers

[Ingo Schwarze]

Hi Marc,

Marc Chantreux wrote on Wed, Nov 06, 2019 at 08:42:28AM +0100:

> let me ruin your day: are you aware of scdoc?
> https://git.sr.ht/~sircmpwn/scdoc

Yes, i think i tripped over it before, once.

> i really appreciated reading about you opinion. thank you.

I think the basic idea is a thoroughly bad one:  targetting man(7)
as an output language is already a dubious choice.  On the one hand,
man(7) can be considered an ancient, obsolete language.  It was the
state of the art from 1979 to about 1990 and has now been obsolete
for almost three decades.

Admittedly, there are still unusual circumstances where you need it,
not listing them here.  But in that case, it can and should be written
by hand.  Yes, it is more difficult than mdoc(7) or perlpod(1) to
write, but not all *that* hard, so a wrapper language is not really
needed.

With the exception of perlpod(1)/pod2man(1), most programs that
autogenerate man(7) code produce low-quality output, so usually,
using a preprocessor is a bad idea because you get poor manual
page formatting.  scdoc(1) is not an exception; the output code
quality is poor indeed:

 * stray .P before and after .SH
 * incorrect usage of plain "-" in NAME line
 * weird ALL CAPS formatting for .SS
 * failure to use font macros, using font escapes instead
 * stray .P inside .RS/.RE
 * incorrect use of plain "-" for \(em
 * violation of "new sentence, new line"
 * missing double space after full stop
 * EXTREMELY poor formatting of bullet lists,
   totally failing to use .TP or .IP in nroff output mode,
   instead resorting to plain .nf
 * TERRIBLE gratuitions use of .ie n for lists with
   manual negative \h that doesn't even work reliably
   in a portable way; while it does work with groff(1),
   it doesn't with mandoc(1) or other formatters
 * relies on tbl(7) for tables, but without giving any instructions
   to the subsequent formatter to run the tbl(1) preprocessor;
   while that works with mandoc(1), it is not portable and fails
   by default even with groff(1)
 * produces UTF-8 characters embedded in man(7) code instead
   of properly encoding them as documented in groff_char(7) and
   mandoc_char(7); while that works with mandoc(1), it is not
   portable and fails by default even with groff(1)

There may be more problems with it, this list is just from one very
brief glance at the man(7) output generated from the scdoc.5.scd
manual page itself.

To summarize, there wasn't any need for yet another man(7)
autogenerator, perlpod(1) already existed, and while most man(7)
autogenerators are bad, this one may even be producing below-average
quality.

Besides, several of the points i made against Markdown appear to
apply to scdoc just as well (or rather, just as badly), in particular
context sensitivity/ambiguity, purely presentational markup and
lack of semantic markup, lack of language independence...

Do not use it.

Yours,
  Ingo