Re: Tools for writers
I really like Markdown for actual writing, because its markup for logical structure is quite low-key and non-distracting, and (unlike *roff or LaTeX) it also reads pretty well in source form. Tables are fairly annoying, particularly if I later have to insert a column in mid table. Use whatever editor works best for you. I use Vim because when I switched from Emacs back in 1999 my wrist problems disappeared almost overnight, a consequence of replacing almost all of the multi-key combinations with single keystrokes. If not for the physiological consequences I would probably still be using Emacs, or an emacslike such as jed or mg. Frankly I think it’s a bit weird that so many people are using an editor with key mappings expressly designed for a (Space Cadet) keyboard that few people ever had even seen in real life, never mind actually used. But evidently people cope just fine. That’s good, I guess? John On Sun, Nov 3, 2019 at 02:07 Oliver Leaver-Smith wrote: > Hello, > > 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.) > > Mich appreciated > > ~ols > -- > Oliver Leaver-Smith > +44(0)114-360-1337 > TZ=Europe/London >
Re: Broadcom firmwares and nvram files
On Sun, Nov 03, 2019 at 12:08:08AM +0100, Stefano Enrico Mendola wrote: > Hi, > > my bad, I thought the grepped output was enough. > Here's the complete dmesg(8) output. = > OpenBSD 6.6 (GENERIC.MP) #372: Sat Oct 12 10:56:27 MDT 2019 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > real mem = 2056568832 (1961MB) > avail mem = 1981595648 (1889MB) > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.7 @ 0x7c31a010 (16 entries) > bios0: vendor American Megatrends Inc. version "X205TA.212" date > 09/04/2015 > bios0: ASUSTeK COMPUTER INC. X205TA > acpi0 at bios0: ACPI 5.0 > acpi0: sleep states S0 S5 > acpi0: tables DSDT FACP TCPA UEFI OEM0 DBG2 HPET LPIT APIC MCFG SSDT SSDT > SSDT SSDT FPDT SSDT SSDT SSDT SSDT TPM2 BGRT CSRT MSDM > acpi0: wakeup devices WLAN(S0) > acpihpet0 at acpi0: 14318179 Hz > acpimadt0 at acpi0 addr 0xfee0 > cpu0 at mainbus0: apid 0 (boot processor) > cpu0: Intel(R) Atom(TM) CPU Z3735F @ 1.33GHz, 1333.58 MHz, 06-37-08 > cpu0: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,TSC_ADJUST,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN > cpu0: 1MB 64b/line 16-way L2 cache > cpu0: smt 0, core 0, package 0 > mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges > cpu0: apic clock running at 83MHz > cpu0: mwait min=64, max=64, C-substates=0.2.0.0.0.0.3.3, IBE > cpu1 at mainbus0: apid 2 (application processor) > cpu1: Intel(R) Atom(TM) CPU Z3735F @ 1.33GHz, 1333.33 MHz, 06-37-08 > cpu1: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,TSC_ADJUST,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN > cpu1: 1MB 64b/line 16-way L2 cache > cpu1: smt 0, core 1, package 0 > cpu2 at mainbus0: apid 4 (application processor) > cpu2: Intel(R) Atom(TM) CPU Z3735F @ 1.33GHz, 1333.34 MHz, 06-37-08 > cpu2: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,TSC_ADJUST,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN > cpu2: 1MB 64b/line 16-way L2 cache > cpu2: smt 0, core 2, package 0 > cpu3 at mainbus0: apid 6 (application processor) > cpu3: Intel(R) Atom(TM) CPU Z3735F @ 1.33GHz, 1333.34 MHz, 06-37-08 > cpu3: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,TSC_ADJUST,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN > cpu3: 1MB 64b/line 16-way L2 cache > cpu3: smt 0, core 3, package 0 > ioapic0 at mainbus0: apid 8 pa 0xfec0, version 20, 87 pins, remapped > acpimcfg0 at acpi0 > acpimcfg0: addr 0xe000, bus 0-255 > acpiprt0 at acpi0: bus 0 (PCI0) > acpiec0 at acpi0: not present > acpicpu0 at acpi0: C3(10@1000 mwait.1@0x64), C2(10@500 mwait.1@0x51), > C1(1000@1 mwait.1), PSS > acpicpu1 at acpi0: C3(10@1000 mwait.1@0x64), C2(10@500 mwait.1@0x51), > C1(1000@1 mwait.1), PSS > acpicpu2 at acpi0: C3(10@1000 mwait.1@0x64), C2(10@500 mwait.1@0x51), > C1(1000@1 mwait.1), PSS > acpicpu3 at acpi0: C3(10@1000 mwait.1@0x64), C2(10@500 mwait.1@0x51), > C1(1000@1 mwait.1), PSS > acpipwrres0 at acpi0: PLPE > acpipwrres1 at acpi0: USBC, resource for XHC1, EHC1, OTG1 > acpipwrres2 at acpi0: CLK0, resource for CAM1 > acpipwrres3 at acpi0: CLK1, resource for CAM0 > acpipwrres4 at acpi0: P28X > acpipwrres5 at acpi0: P18X > acpipwrres6 at acpi0: P28P > acpipwrres7 at acpi0: P18P > acpipwrres8 at acpi0: P28T, resource for CAM0, CAM1 > acpipwrres9 at acpi0: P18T, resource for CAM0, CAM1 > acpipwrres10 at acpi0: P1XT > acpitz0 at acpi0: no critical temperature defined > "INT3396" at acpi0 not configured > bytgpio0 at acpi0: GPO2 uid 3 addr 0xfed0e000/0x1000 irq 50, 44 pins > bytgpio1 at acpi0: GPO0 uid 1 addr 0xfed0c000/0x1000 irq 49, 102 pins > dwiic0 at acpi0 I2C5 addr 0x90932000/0x1000 irq 36 > iic0 at dwiic0 > tipmic0 at iic0 addr 0x5e irq 67 > bytgpio2 at acpi0: GPO1 uid 2 addr 0xfed0d000/0x1000 irq 48, 28 pins > "80860F0A" at acpi0 not configured > dwiic1 at acpi0 I2C1 addr 0x9091a000/0x1000 irq 32 > iic1 at dwiic1 > ihidev0 at iic1 addr 0x68 irq 71, vendor 0xb05 product 0x8585, PDEC3393 > ihidev0: 9 report ids > ikbd0 at ihidev0 reportid 1: 8 variable keys, 6 key codes > wskbd0 at ikbd0 mux 1 > hid at ihidev0 repor
Re: Broadcom firmwares and nvram files
On Sun, Nov 03, 2019 at 10:05:38AM +0100, Patrick Wildt wrote: > On Sun, Nov 03, 2019 at 12:08:08AM +0100, Stefano Enrico Mendola wrote: > > Hi, > > > > my bad, I thought the grepped output was enough. > > Here's the complete dmesg(8) output. = > > OpenBSD 6.6 (GENERIC.MP) #372: Sat Oct 12 10:56:27 MDT 2019 > > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > real mem = 2056568832 (1961MB) > > avail mem = 1981595648 (1889MB) > > mpath0 at root > > scsibus0 at mpath0: 256 targets > > mainbus0 at root > > bios0 at mainbus0: SMBIOS rev. 2.7 @ 0x7c31a010 (16 entries) > > bios0: vendor American Megatrends Inc. version "X205TA.212" date > > 09/04/2015 > > bios0: ASUSTeK COMPUTER INC. X205TA > > acpi0 at bios0: ACPI 5.0 > > acpi0: sleep states S0 S5 > > acpi0: tables DSDT FACP TCPA UEFI OEM0 DBG2 HPET LPIT APIC MCFG SSDT SSDT > > SSDT SSDT FPDT SSDT SSDT SSDT SSDT TPM2 BGRT CSRT MSDM > > acpi0: wakeup devices WLAN(S0) > > acpihpet0 at acpi0: 14318179 Hz > > acpimadt0 at acpi0 addr 0xfee0 > > cpu0 at mainbus0: apid 0 (boot processor) > > cpu0: Intel(R) Atom(TM) CPU Z3735F @ 1.33GHz, 1333.58 MHz, 06-37-08 > > cpu0: > > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,TSC_ADJUST,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN > > cpu0: 1MB 64b/line 16-way L2 cache > > cpu0: smt 0, core 0, package 0 > > mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges > > cpu0: apic clock running at 83MHz > > cpu0: mwait min=64, max=64, C-substates=0.2.0.0.0.0.3.3, IBE > > cpu1 at mainbus0: apid 2 (application processor) > > cpu1: Intel(R) Atom(TM) CPU Z3735F @ 1.33GHz, 1333.33 MHz, 06-37-08 > > cpu1: > > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,TSC_ADJUST,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN > > cpu1: 1MB 64b/line 16-way L2 cache > > cpu1: smt 0, core 1, package 0 > > cpu2 at mainbus0: apid 4 (application processor) > > cpu2: Intel(R) Atom(TM) CPU Z3735F @ 1.33GHz, 1333.34 MHz, 06-37-08 > > cpu2: > > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,TSC_ADJUST,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN > > cpu2: 1MB 64b/line 16-way L2 cache > > cpu2: smt 0, core 2, package 0 > > cpu3 at mainbus0: apid 6 (application processor) > > cpu3: Intel(R) Atom(TM) CPU Z3735F @ 1.33GHz, 1333.34 MHz, 06-37-08 > > cpu3: > > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,TSC_ADJUST,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN > > cpu3: 1MB 64b/line 16-way L2 cache > > cpu3: smt 0, core 3, package 0 > > ioapic0 at mainbus0: apid 8 pa 0xfec0, version 20, 87 pins, remapped > > acpimcfg0 at acpi0 > > acpimcfg0: addr 0xe000, bus 0-255 > > acpiprt0 at acpi0: bus 0 (PCI0) > > acpiec0 at acpi0: not present > > acpicpu0 at acpi0: C3(10@1000 mwait.1@0x64), C2(10@500 mwait.1@0x51), > > C1(1000@1 mwait.1), PSS > > acpicpu1 at acpi0: C3(10@1000 mwait.1@0x64), C2(10@500 mwait.1@0x51), > > C1(1000@1 mwait.1), PSS > > acpicpu2 at acpi0: C3(10@1000 mwait.1@0x64), C2(10@500 mwait.1@0x51), > > C1(1000@1 mwait.1), PSS > > acpicpu3 at acpi0: C3(10@1000 mwait.1@0x64), C2(10@500 mwait.1@0x51), > > C1(1000@1 mwait.1), PSS > > acpipwrres0 at acpi0: PLPE > > acpipwrres1 at acpi0: USBC, resource for XHC1, EHC1, OTG1 > > acpipwrres2 at acpi0: CLK0, resource for CAM1 > > acpipwrres3 at acpi0: CLK1, resource for CAM0 > > acpipwrres4 at acpi0: P28X > > acpipwrres5 at acpi0: P18X > > acpipwrres6 at acpi0: P28P > > acpipwrres7 at acpi0: P18P > > acpipwrres8 at acpi0: P28T, resource for CAM0, CAM1 > > acpipwrres9 at acpi0: P18T, resource for CAM0, CAM1 > > acpipwrres10 at acpi0: P1XT > > acpitz0 at acpi0: no critical temperature defined > > "INT3396" at acpi0 not configured > > bytgpio0 at acpi0: GPO2 uid 3 addr 0xfed0e000/0x1000 irq 50, 44 pins > > bytgpio1 at acpi0: GPO0 uid 1 addr 0xfed0c000/0x1000 irq 49, 102 pins > > dwiic0 at acpi0 I2C5 addr 0x90932000/0x1000 irq 36 > > iic0 at dwiic0 > > tipmic0 at iic0 addr 0x5e irq 67 > > bytgpio2 at acpi0: GPO1 uid 2 addr 0xfed0d000/0x1000 irq 48, 28 pins > > "80860F0A" at acpi0 not configured > > dwiic1 at acpi0 I2C1 addr 0x9091a000/0x10
Re: Tools for writers
> documents, but for my use case, LibreOffice has treated me well. I primarily > use it for simple things like putting together invoices, writing articles, > rendering documents to PDF or postscript, and reading .docx files people > send me. > I'm sure there's a superior way to do all this, there is no such thing as a "superior way", there are way that fit your expectations: i wasn't trying to convince you to use anything else that please you but i really think toolchain that uses latex as core offers much more opportunity than a libreoffice ones and would like to mention it if it can help. regards > I have to collaborate with average people. I've thought about learning latex > and mandoc and all the fancy tools, but I've just never gotten around to it. I wasn't talking about mandoc but pandoc (https://pandoc.org/): you write most of the things just using markdown format and add latex instructions whenever you want. this way, you keep simple things simple but you keep the power of latex under the wood. regards marc
Re: Skype alternatives for OpenBSD
On Sun, Nov 03, 2019 at 04:51:48PM +1000, Stuart Longland wrote: Do you need any video conferencing software (i.e. the group running the online class is willing to switch to whatever you can get working?), or do you specifically need Skype? Not sure about the original poster but I would be interested in any end-to-end encrypted video/audio/chat programs that are available.
Re: Tools for writers
Hi, On Sun, Nov 03, 2019 at 02:29:02AM +0100, Ingo Schwarze wrote: > As long as you only *use* macro packages, groff is *much* > easier to use than LaTeX (not least because the quality of > documentation of groff is vastly superior to LaTeX, and LaTeX > documentation is so extremely huge and fragmented that it's > a terrible challenge to find anything you need). > > But once you start modifying macro packages or writing your own > macros, i.e. once you enter into real programming, then it turns > out LaTeX is easier to program than roff(7) because the syntax and > semantics of the low-level roff(7) language are, let's put it > politely, quite unusual and surprising in many details. I know > that because i did write a non-trivial LaTeX module and because i > do maintain one of the larger roff macro packages, upstream at > groff, and besides, i did implement considerable parts of the roff > language in /usr/src/usr.bin/mandoc/roff.c. I actually wrote a semantic markup language shamelessly inspired from mdoc(7) and with simplified roff-like syntax, called “gofrundis” (actual tool is spelled frundis(1)), but primarily intented for authoring novels. It exports to LaTeX, HTML/EPUB or groff mom, and is documented using mdoc(7). That said, even though the language has quite silently existed for several years, excluding me it still has only two regular users as far as I know. The consequence is that there's not a community providing extension packages for it: anything not covered by the core language frundis_syntax(5) requires you to write some code in LaTeX, HTML or roff/mom and wrap it with macros. It's somewhat extensible, and I used it to write a thesis and export afterwards to LaTeX, because I find the syntax and semantics simpler and more pleasant to use. But I'm not sure I would recommend such non standard use. Yon
Re: Courier-Imap no longer accepts ssl connections after update to -current
Theodore Wynnychenko wrote: > Hi (again): > > After updating to current yesterday, and then updating all the packages > (using "pkg_add -vui -Dsnap"), I can no longer connect to the ssl (993) port > of the courier-imap server running on the system. > > Prior to the update, ssl connections were working without an issue. > it's working fine for me with: $ ldd /usr/local/bin/couriertls | grep ssl 11ae13a38000 11ae13a9c000 rlib 01 0 /usr/lib/libssl.so.48.0 and OpenBSD 6.6-current (GENERIC.MP) #425: Fri Nov 1 23:49:35 MDT 2019 there is a libssl bump ongoing, maybe you should rebuild courier-imap from ports or wait for next packages. does "openssl s_client -connect 127.0.0.1:993" works as expected and show you the correct certificate ? > Now, when trying to connect, the client gets a "A secure connection to the > server cannot be established" message. > > On the server, I see the following in the log for each ssl connection > attempt: > > Nov 2 07:40:38 host imapd-ssl: ip=[:::127.0.0.1], couriertls: > /etc/ssl/private/imapd.pem: error:02FFF00D:system > library:func(4095):Permission denied > > Nov 2 07:40:38 host imapd-ssl: ip=[:::127.0.0.1], couriertls: > /etc/ssl/private/imapd.pem: error:20FFF002:BIO > routines:CRYPTO_internal:system lib > > The packages for courier currently installed are: > > pkg_info | grep courier > courier-authlib-0.69.1 authentication library for courier > courier-authlib-mysql-0.69.1mysql authentication module for > courier-authLib > courier-imap-5.0.8 imap server for maildir format mailboxes > courier-pop3-5.0.8 pop3 server for maildir format mailboxes > courier-unicode-2.1 courier unicode library > > I did not make any changes to the /etc/courier/imapd-ssl configuration file. > What was working for me before was: > cat imapd-ssl |grep -v ^$ | grep -v ^# > SSLPORT=993 > SSLADDRESS=0 > MAXDAEMONS=500 > MAXPERIP=100 > SSLPIDFILE=/var/run/courier/imapd-ssl.pid > SSLLOGGEROPTS="-name=imapd-ssl" > IMAPDSSLSTART=YES > IMAPDSTARTTLS=NO > IMAP_TLS_REQUIRED=0 > COURIERTLS=/usr/local/bin/couriertls > TLS_CERTFILE=/etc/ssl/private/imapd.pem > TLS_DHPARAMS=/etc/ssl/private/imapd.pem > TLS_TRUSTCERTS=/etc/ssl/CA/cacert.pem > TLS_VERIFYPEER=NONE > MAILDIRPATH=Maildir > > Anyway, I don't know what the error lines really mean. I am wondering if it > is something do with the "interface" between courier and the ssl libraries. > I have tried "exploring" the web on this over the last 24 hours, but have > been unable to find anything to point me in any direction. > > As this is an "internal" mail-server, I just re-enabled the non-ssl > connection, so I can still connect to my mail. > > But, I am wondering if there is anything that I could do to resolve this > ssl-connection issue. > > Thanks (again) > Ted > > >
*roff and page layout ? (Re: Tools for writers)
> the "print/texlive" port is how ridiculously large it is. because it comes with the whole distribution. i never tested but https://tectonic-typesetting.github.io/ seems to fix it by downloading stuff on demand. however, another problem with tex is performance. troff is blazing fast. however... > "textproc/groff" port (disclosure: which i maintain). The roff(7) > The "textproc/heirloom-doctools" port is a serious contender for a ... i tried nroff long time ago so i tried to create templates for memos and letters with layouts where: A is company logo and info B is for metainfo about the current letter C is the actual body ┌─┐┌─┐ │A││B│ └─┘└─┘ ┌┐ │ C │ └┘ ┌─┐┌─┐ │A││C│ │B││ │ │ ││ │ │ ││ │ └─┘└─┘ i tried both of those (you can achieve this with latex minipages) but i never made it work so i gave out. did i miss a fine didactic documentation about it ? regards marc ps: i think it was the plan9 troff, > documentation of groff is vastly superior to LaTeX, and LaTeX > documentation is so extremely huge and fragmented that it's > a terrible challenge to find anything you need). well ... i have to admit i tried harder with LaTeX but thanks to CTAN, i reached the point when i know what are the classes and packages i need (mostly article, book, beamer and tikz). there is no CTAN for troff and that's a missing part. > out LaTeX is easier to program than roff(7) because the syntax and > semantics of the low-level roff(7) language are, let's put it > politely, quite unusual and surprising in many details. i love the way you're saying that. is there a document to dive into it ? > groff, and besides, i did implement considerable parts of the roff > language in /usr/src/usr.bin/mandoc/roff.c. nice. thank you for mandoc! regards marc
Re: Skype alternatives for OpenBSD
Frank Beuth [2019-11-03 11:55:21 +0100]: > Not sure about the original poster but I would be interested in any > end-to-end encrypted video/audio/chat programs that are available. Matrix may be interesting https://matrix.org/ It has ETE chat, but I am not sure about audio/video. It is possible to host synapse on OpenBSD (I do it), but to be honest it feels rather cumbersome. Synapse is written in Python and is rather slow.[^1] There are some other incomplete implementations as well, I think of one them is written in C++. Unfortunately the most complete (reference) client is Riot, which—to my knowledge—can only be used in a browser in OpenBSD. There is also a weechat script, however. In general, to me, it doesn't feel like it's prime time for Matrix yet, but I guess it could work with some better implementations of both clients and servers. I would love to replace Messenger with it to talk with my friends (those willing to change). It also has briding capabilities, for example there is an IRC bridge which I got partially working (I can receive messages from IRC rooms, but I didn't manage to send anything yet). [^1]: On my homeserver I am unable to join to the official #matrix room hosted at matrix.org, trying seems to overload my server, it becomes unresponsive. -- Bertalan Z. Péter FB9B 34FE 3500 3977 92AE 4809 935C 3BEB 44C1 0F89 /"\ \ /ASCII Ribbon Campaign X against HTML email & proprietary attachments / \www.asciiribbon.org signature.asc Description: PGP signature
Re: OpenBSD and solid state disks
On 2019-11-02, Raymond, David wrote: > I recently installed OpenBSD on a Lenovo X1 Carbon with a solid state > drive and it works great. > > My question is whether OpenBSD addresses the special characteristics > of solid state drives, especially those having to do with longevity > and reliability. I can't find anything written on this. Linux has > certain means for addressing this issue, such as fstrim as well as > various kernel options. Is there anything I have missed with OpenBSD > on this subject? > > Dave Raymond > Trim doesn't seem hugely necessary with modern SSDs. We do regular bulk port builds on SSD machines (often 4+ times a week for i386/amd64) without anything special and they seem to cope ok. I think https://www.reddit.com/r/openbsd/comments/9h231o/comment/e6bw9ig is valid.
Re: Skype alternatives for OpenBSD
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 03/11/2019 10:55, Frank Beuth 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. Have a look at Tox. It might work out for you on a technical level. I don't use Tox. I got involved with the project's development and I left very quickly. Personally I don't even want to be a user if I can help it. This is my own personal issue. If you check it out I sincerely hope you have a better experience than I did. Sociotechnologically it is an important project and I hope it succeeds on that level in the long run. Andrew - -- OpenPGP key: EB28 0338 28B7 19DA DAB0 B193 D21D 996E 883B E5B9 -BEGIN PGP SIGNATURE- iQGzBAEBCgAdFiEE/ASxpcFcqIVqgGgxgfJdKbhCoRcFAl2+tisACgkQgfJdKbhC oRdBugv+P/BIwuNWxmC0kEDiQUWt/E6TjXDwToMch71w0VsWASzM9dUErBTBMOhM BsW2s4J+vbec9PWlBqKogPcU57OlqnzPQgqiBQiCfsf/405DpSIfQcC/U/ZNTG3W RBiWzXFRKzfO3hbRQq8G5Q+mPB9fOffmJLJDosTDdSiPefdPNuH6ClcTTpi98pEZ 67ZQhTAE1IZp6pB1t124LMAz50VRY7mfPYuZBqLCPzFmpflilB0qjWmoH0T9BgMa hFQl8Yd/Bv5ypDTH3n13SsR9uXBR1wGic5j0XmZbaKtygn2eGfZqKBwLCmt+Cfvm ESLP3lG89hK95KstxIRFbPoWhsp+zuMCooIXr62Ik/a0FqHLw8nj9HQCv4FnAoQY KObNvTXsoQec5ojDoRWfPtM+LtjQJ+pYD6xEMYT04OPTKg5/K+HyOaVwCcZFzqdI IpdnO8TeKjNA/qLDAd3z49xgzet+IJDKUYx380XJDSVENkZcz2FNsIrhghXny4lQ ZA0JuJhZ =QUzB -END PGP SIGNATURE-
Re: Courier-Imap no longer accepts ssl connections after update to -current
On 2019-11-02, Theodore Wynnychenko wrote: > Nov 2 07:40:38 host imapd-ssl: ip=[:::127.0.0.1], couriertls: > /etc/ssl/private/imapd.pem: error:02FFF00D:system > library:func(4095):Permission denied This suggests that the uid running Courier-Imap does not have permission to access /etc/ssl/private/imapd.pem.
Re: Tools for writers
Dear Marc, > I wasn't talking about mandoc but pandoc (https://pandoc.org/): you > write most of the things just using markdown format and add latex > instructions whenever you want. this way, you keep simple things simple > but you keep the power of latex under the wood. Does _pandoc_ work on OpenBSD now? Yours sincerely, Xianwen
Re: Tools for writers
On 03/11/2019 12:44, Xianwen Chen (陈贤文) wrote: Does _pandoc_ work on OpenBSD now? Pandoc doesn't work on OpenBSD? This is seriously a bit of a shock. It 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 on a platform where is does work. Andrew -- OpenPGP key: EB28 0338 28B7 19DA DAB0 B193 D21D 996E 883B E5B9
Re: Tools for writers
hello, > Does _pandoc_ work on OpenBSD now? i realized i haven't try on BSD as my desktop remains a linux for the moment. sorry i lost the focus because of this very appealing thread. regards marc
Re: Broadcom firmwares and nvram files
On Sun, Nov 03, 2019 at 10:06:18AM +0100, Patrick Wildt wrote:
> Obiously I missed the attachment.
Could this tool be put into base or ports / pkg_add?
> /*
> * Copyright (c) 2013 Broadcom Corporation
> *
> * Permission to use, copy, modify, and/or distribute this software for any
> * purpose with or without fee is hereby granted, provided that the above
> * copyright notice and this permission notice appear in all copies.
> *
> * THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
> * WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
> * MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY
> * SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
> * WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
> ACTION
> * OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN
> * CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
> */
>
> #include
> #include
> #include
> #include
> #include
> #include
> #include
> #include
> //#include
>
> #define BRCMF_FW_MAX_NVRAM_SIZE 64000
> #define BRCMF_FW_NVRAM_DEVPATH_LEN19 /* devpath0=pcie/1/4/ */
> #define BRCMF_FW_NVRAM_PCIEDEV_LEN10 /* pcie/1/4/ + \0 */
> #define BRCMF_FW_DEFAULT_BOARDREV "boardrev=0xff"
>
> enum nvram_parser_state {
> IDLE,
> KEY,
> VALUE,
> COMMENT,
> END
> };
>
> /**
> * struct nvram_parser - internal info for parser.
> *
> * @state: current parser state.
> * @data: input buffer being parsed.
> * @nvram: output buffer with parse result.
> * @nvram_len: lenght of parse result.
> * @line: current line.
> * @column: current column in line.
> * @pos: byte offset in input buffer.
> * @entry: start position of key,value entry.
> * @multi_dev_v1: detect pcie multi device v1 (compressed).
> * @multi_dev_v2: detect pcie multi device v2.
> * @boardrev_found: nvram contains boardrev information.
> */
> struct nvram_parser {
> enum nvram_parser_state state;
> char *data;
> char *nvram;
> uint32_t nvram_len;
> uint32_t line;
> uint32_t column;
> uint32_t pos;
> uint32_t entry;
> int multi_dev_v1;
> int multi_dev_v2;
> int boardrev_found;
> };
>
> /**
> * is_nvram_char() - check if char is a valid one for NVRAM entry
> *
> * It accepts all printable ASCII chars except for '#' which opens a comment.
> * Please note that ' ' (space) while accepted is not a valid key name char.
> */
> static int is_nvram_char(char c)
> {
> /* comment marker excluded */
> if (c == '#')
> return 0;
>
> /* key and value may have any other readable character */
> return (c >= 0x20 && c < 0x7f);
> }
>
> static int is_whitespace(char c)
> {
> return (c == ' ' || c == '\r' || c == '\n' || c == '\t');
> }
>
> static enum nvram_parser_state brcmf_nvram_handle_idle(struct nvram_parser
> *nvp)
> {
> char c;
>
> c = nvp->data[nvp->pos];
> if (c == '\n')
> return COMMENT;
> if (is_whitespace(c) || c == '\0')
> goto proceed;
> if (c == '#')
> return COMMENT;
> if (is_nvram_char(c)) {
> nvp->entry = nvp->pos;
> return KEY;
> }
> printf("warning: ln=%d:col=%d: ignoring invalid character\n",
> nvp->line, nvp->column);
> proceed:
> nvp->column++;
> nvp->pos++;
> return IDLE;
> }
>
> static enum nvram_parser_state brcmf_nvram_handle_key(struct nvram_parser
> *nvp)
> {
> enum nvram_parser_state st = nvp->state;
> char c;
>
> c = nvp->data[nvp->pos];
> if (c == '=') {
> /* ignore RAW1 by treating as comment */
> if (strncmp(&nvp->data[nvp->entry], "RAW1", 4) == 0)
> st = COMMENT;
> else
> st = VALUE;
> if (strncmp(&nvp->data[nvp->entry], "devpath", 7) == 0)
> nvp->multi_dev_v1 = 1;
> if (strncmp(&nvp->data[nvp->entry], "pcie/", 5) == 0)
> nvp->multi_dev_v2 = 1;
> if (strncmp(&nvp->data[nvp->entry], "boardrev", 8) == 0)
> nvp->boardrev_found = 1;
> } else if (!is_nvram_char(c) || c == ' ') {
> printf("warning: ln=%d:col=%d: '=' expected, skip invalid key
> entry\n",
> nvp->line, nvp->column);
> return COMMENT;
> }
>
> nvp->column++;
> nvp->pos++;
> return st;
> }
>
> static enum nvram_parser_state
> brcmf_nvram_handle_value(struct nvram_parser *nvp)
> {
> char c;
> char *skv;
> char *ekv;
> uint32_t cplen;
>
> c = nvp->data[nvp->pos];
> if (!is_nvram_char(c)) {
> /* key,value pair complete */
> ekv = &nvp->data[nvp->pos];
Re: Skype alternatives for OpenBSD
On Sat, Nov 02, 2019 at 02:47:16PM -0700, Jordan Geoghegan wrote: > Assuming Firefox or chromium on OpenBSD has WebRTC support (havent checked > in a while), talky.io should work. It's a free website that supports WebRTC > chats. I've used it in the past with great success. The www/nextcloud port with the 'Talk' add-on, and with telephony/turnserver, can be used to self-host a WebRTC server on OpenBSD.
Re: Skype alternatives for OpenBSD
> Sent: Sunday, November 03, 2019 at 7:51 AM > From: "Stuart Longland" > To: misc@openbsd.org > Subject: Re: Skype alternatives for OpenBSD > > On 3/11/19 7:35 am, Jonathan Drews wrote: > > Is there an alternative to Skype that runs on OpenBSD? I looked in > > http://openports.se/ > > and didn't see anything. I want to take online classes nad need a video > > conferencingsoftware > > Do you need any video conferencing software (i.e. the group running the > online class is willing to switch to whatever you can get working?), or > do you specifically need Skype? The woman offering the class uses Skype so I am probably going to have to use Windows. I have a laptop with Windows 10 but I hardly ever use it. Windows is a big step down in performance when compared to OpenBSD. I thought Skype used a protocol that allowed other clients to connect to it then I read the Wikipedia page on Skype. The technology is owned by Microsoft. > -- > Stuart Longland (aka Redhatter, VK4MSL) > > I haven't lost my mind... > ...it's backed up on a tape somewhere. > >
Re: Following current - pkg_add update forward depedencies don't match question
On 2019-11-02, Theodore Wynnychenko wrote: > I decided to just try updating gettext, so (this is the full output on that > system): Well, that's the problem. Partial updates work sometimes but they can't be relied upon, in particular won't work around some types of restructuring changes as happened to the gettext port. > After staring at this for a while, I started to wonder (because it had been > a while since I last updated...) if the fact that "gettext" is now listed as > "getttext-runtime" (I guess this is just a "flavor," right?, but the change > was something I noticed) could be an issue. Flavours are after the version number (mutt-1.12.2v3-gpgme: this is the "gpgme" flavour of mutt). gettext was split into multiple parts (runtime, tools, and libtextstyle) in separate packages and there is no more package just named "gettext". Say you have A+B installed and want to update them, both use gettext. A(old)+B(old) depend on gettext; A(new)+B(new) depend on gettext-runtime. gettext and gettext-runtime contain same files so can't be installed together. Therefore you can't update A(old) to A(new) without also updating B(old) to B(new). Not that this is necessary to know in this case - just remember that after updating base, you need to run pkg_add -u to update all packages. Maybe add -Dsnap if the conditions require it, and flags like -V/-i are ok, but the other pkg_add -D flags are for special cases only, usually just for ports developers. > I then looked at the pkg_info for one of the "don't match" packages on my > system, and compared them to the new/current packages. > > So, for a local problem package I saw (in the depend list): > @depend devel/gettext:gettext-*:gettext-0.19.8.1p3 > > When I looked at the -current package I saw: > @depend devel/gettext,-runtime:gettext-runtime-*:gettext-runtime-0.20.1p0 > > Now, I really have little idea of what this means, or what I am doing, but I > decided I would just manually "fix" the @depend line in my local > "/var/db/pkg/[package]/+CONTENTS" to the "new" line (with > "gettext-runtime-0.20.1p0" in it). That probably didn't cause any big problems in this case, but I just want to make sure that it's showing in the thread for the list archives: don't do that :-) > I did that for all the "don't match" conflict packages, then re-ran "pkg_add > -vui -Dsnap" (although, I now understand the need or lack thereof for > "-Dsnap" better - thanks) and the package update completed without any real > issues. Specifically, gettext and all the "don't match" packages were > updated to the -current packages available yesterday. > > As I said, I have little idea of what I am doing, but this (at least for the > last 30 hours) seems to have worked and the system appears to be "stable" > (and, once again, -current). I would suggest running pkg_check now for a sanity check of the package database.
Re: Skype alternatives for OpenBSD
Dear Mr. Drews, > The woman offering the class uses Skype so I am probably going to have to use > Windows. I have a laptop with > Skype usually runs well on Linux. It may run on FreeBSD too, although I have never looked into that. One trick that I use is to run Skype on my Android phone. Yours sincerely, Xianwen
Re: Skype alternatives for OpenBSD
>I thought Skype used a protocol that allowed other clients to connect >to it then I read the Wikipedia page on Skype. The technology is owned >by Microsoft. Many moons ago you could at least chat with other clients, but you also had to run Skype itself. It was more or less remote controlling the official client. This is maybe what you are remembering. -- Greetings, Florian Viehweger
Re: Tools for writers
Dear Mr. Chantreux, > i realized i haven't try on BSD as my desktop remains a linux for the > moment. sorry i lost the focus because of this very appealing thread. My substitute for _pandoc_ is the _org-mode_ of emacs, which is for some people also good for outlining etc. But I miss _pandoc_. Yours sincerely, Xianwen
Re: Following current - pkg_add update forward depedencies don't match question
> -Original Message- > From: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org] On Behalf > Of Stuart Henderson > Sent: Sunday, November 03, 2019 7:59 AM > To: misc@openbsd.org > Subject: Re: Following current - pkg_add update forward depedencies > don't match question > > On 2019-11-02, Theodore Wynnychenko wrote: > > I decided to just try updating gettext, so (this is the full output > on that > > system): > > Well, that's the problem. Partial updates work sometimes but they can't > be relied upon, in particular won't work around some types of > restructuring > changes as happened to the gettext port. > I tried running 'pkg_add -u' (not as a partial update) probably 5-10 times, always getting the same 'forward dependencies don't match' notice, and pkg_add ending with the notices: Couldn't find updates for ... gettext-0.19.8.1p3 ... (and all the other 'don't match' packages) Couldn't install gettext-runtime-0.20.1p0 ... (and all the other 'don't match' packages) > Flavours are after the version number (mutt-1.12.2v3-gpgme: this is the > "gpgme" flavour of mutt). > > gettext was split into multiple parts (runtime, tools, and > libtextstyle) > in separate packages and there is no more package just named "gettext". > Say you have A+B installed and want to update them, both use gettext. > A(old)+B(old) depend on gettext; A(new)+B(new) depend on gettext- > runtime. > gettext and gettext-runtime contain same files so can't be installed > together. Therefore you can't update A(old) to A(new) without also > updating B(old) to B(new). > In my case, pkg_add -u did not succeed regardless of whether or not it was a complete update. > > Now, I really have little idea of what this means, or what I am > doing, but I > > decided I would just manually "fix" the @depend line in my local > > "/var/db/pkg/[package]/+CONTENTS" to the "new" line (with > > "gettext-runtime-0.20.1p0" in it). > > That probably didn't cause any big problems in this case, but I just > want > to make sure that it's showing in the thread for the list archives: > don't > do that :-) > I agree that it did not seem like the best idea (a little knowledge is a dangerous thing). When I was thinking about it, I thought of deleting gettext (so that I could install gettext-runtime), but that seemed to lead to a lot of other required package deletions, and I was worried that something would break. I could not figure out how to get one package (in this case, getext) to be deleted, for just a few minutes, so that I could install gettext-runtime without being forced to accept the deletion of a bunch of other packages. Is there a way to do something like that? I could not find one. > I would suggest running pkg_check now for a sanity check of the package > database. > Did that immediately after the update - I guess I got something right :-) Thanks again Ted
Downgrade 6.6 to 6.5
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: ixl(4) Driver SR-IOV Physical Function Interface has jitter on OpenBSD 6.5 and 6.6
Hello, I managed to get another server and card with identical hardware and tested ixl4 on bare metal, there was no jitter or latency issues with ping times never rising above 0.5 ms so it looks like issue I orignally reported was something possibly with the PCI-E subsystem ( PCI-E bridge) and OpenBSDdrivers from the virtual machine (KVM Q35) are there other tests that I can run that would help diagnose the issue ? dmesg of baremetal server running OpenBSD below foobare# dmesg OpenBSD 6.6 (GENERIC.MP) #372: Sat Oct 12 10:56:27 MDT 2019 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 68619927552 (65441MB) avail mem = 66527576064 (63445MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xeb570 (172 entries) bios0: vendor Intel Corp. version "SE5C600.86B.02.06.0007.082420181029" date 08/24/2018 bios0: Intel Corporation S2600GZ acpi0 at bios0: ACPI 4.0 acpi0: sleep states S0 S1 S5 acpi0: tables DSDT FACP APIC SPMI FPDT MCFG WDDT SRAT SLIT MSCT HPET SSDT SSDT DMAR HEST BERT ERST EINJ SSDT SSDT SSDT acpi0: wakeup devices P0P1(S4) RP01(S5) PXSX(S4) RP02(S5) PXSX(S4) RP03(S5) PXSX(S4) RP04(S5) PXSX(S4) RP05(S4) PXSX(S4) RP06(S4) PXSX(S4) RP07(S4) PXSX(S4) RP08(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Xeon(R) CPU E5-2660 v2 @ 2.20GHz, 2195.00 MHz, 06-3e-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,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,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.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Xeon(R) CPU E5-2660 v2 @ 2.20GHz, 2194.73 MHz, 06-3e-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,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: Intel(R) Xeon(R) CPU E5-2660 v2 @ 2.20GHz, 2194.73 MHz, 06-3e-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,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,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) Xeon(R) CPU E5-2660 v2 @ 2.20GHz, 2194.74 MHz, 06-3e-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,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 0, core 3, package 0 cpu4 at mainbus0: apid 8 (application processor) cpu4: Intel(R) Xeon(R) CPU E5-2660 v2 @ 2.20GHz, 2194.73 MHz, 06-3e-04 cpu4: 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,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu4: 256KB 64b/line 8-way L2 cache cpu4: smt 0, core 4, package 0 cpu5 at mainbus0: apid 16 (application processor) cpu5: Intel(R) Xeon(R) CPU E5-2660 v2 @ 2.20GHz, 2194.73 MHz, 06-3e-04 cpu5: 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,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu5: 256KB 64b/line 8-way L2 cache cpu5: smt 0, core 8, package 0 cpu6 at mainbus0: apid 18 (a
Re: Following current - pkg_add update forward depedencies don't match question
I also found twice that removed (from ports permanently) packages I had installed would throw things into a loop that once caused me to run out of memory or things just kept looping. ^C followed by pkg_delete -i "the offending package" then resuming pkg_add -u made things much easier. Overall the pkg_ tools have been great and always improving. Thank you for the hard work! Overall, following -current locally and remotely has become so incredibly easy now that I am running -current everywhere and really happy! (and resuming work on porting because of it) Thanks again! Chris Bennett
Re: Tools for writers
On Sun, Nov 03, 2019 at 01:44:20PM +0100, Xianwen Chen (陈贤文) wrote: > Dear Marc, > > > I wasn't talking about mandoc but pandoc (https://pandoc.org/): you > > write most of the things just using markdown format and add latex > > instructions whenever you want. this way, you keep simple things simple > > but you keep the power of latex under the wood. > > Does _pandoc_ work on OpenBSD now? I have built Pandoc on OpenBSD a couple of times: latest was in 2017. However, it can be sensitive to the GHC version used, and I have not bulit it using Stack. There are people who report building it in 2018, after some tweaking. https://github.com/jgm/pandoc/issues/4940 > > Yours sincerely, > Xianwen > Sincerely
Re: Tools for writers
Dear Mr. Schwarze, > That said, the obvious answer for the OP is of course the > "textproc/groff" port (disclosure: which i maintain). The roff(7) > language and the troff programm is what people in the UNIX world > always used for writing books and journal articles, and it is very > much alive even after the roff language celebrated its 55th birthday > this year. I'm in the habit of using it to prepare slides for > conference talks (with textproc/gpresent), for example, and i'm not > the only only one. I am interested in giving _groff_ and _gpresent_ a try. I am seasoned LaTeX user. Is there a tutorial that you would recommend to someone like me? Two things that come to my mind that I am concerned with. First, how does groff manage bibliography and citations? Second, peer-reviewed journals usually require submissions to be in Word format or in LaTeX. Is there an easy way to convert a groff document to a Word document or LaTeX? Yours sincerely, Xianwen
Re: Downgrade 6.6 to 6.5
Hi, no and yes, I fear. Le November 3, 2019 2:41:33 PM UTC, Josh a écrit : >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 -- Envoyé de mon appareil Android avec Courriel Librem Mail. Veuillez excuser ma brièveté.
Re: Tools for writers
Hello, Xianwen Chen wrote on Sun, Nov 03, 2019 at 04:16:43PM +0100: > I am interested in giving _groff_ and _gpresent_ a try. I am seasoned > LaTeX user. Is there a tutorial that you would recommend to someone like > me? No, i'm not aware of tutorials (but i generally don't use tutorials, so maybe i missed them). But there is good reference documentation: https://www.gnu.org/software/groff/manual/html_node/ Gpresent is a macro package specifically for presentation slides. The documentation is in the groff_present(7) and presentps(1) manual pages in the textproc/gpresent package and in the groff_mm(7) manual page in the textproc/groff package. > Two things that come to my mind that I am concerned with. > > First, how does groff manage bibliography and citations? See the refer(1) utility in the textproc/groff package. > Second, peer-reviewed journals usually require submissions to be in Word > format or in LaTeX. Is there an easy way to convert a groff document to > a Word document or LaTeX? No, and there isn't even a complicated way either. If your publisher requires LaTeX, use LaTeX; it's really that simple... Yours, Ingo
Re: OpenBSD and solid state disks
On 2019-11-02 16:10, Raymond, David wrote: > I recently installed OpenBSD on a Lenovo X1 Carbon with a solid state > drive and it works great. yep. > My question is whether OpenBSD addresses the special characteristics > of solid state drives, especially those having to do with longevity > and reliability. Just Use them, and plan on replacing them when they need to be replaced, or at least demoting them to "when this fails, I won't cry" uses. In other words, treat them JUST LIKE EVERY OTHER DRIVE. If I hand you a five year old magnetic drive, would you put it in a mission critical application? Probably not. If you have five year old hardware in a mission critical application, you should be looking at replacement. Treat your SSDs exactly the same way, you will have no problems. Used very hard, SSDs last many years. Used like most people use a laptop, you will be replacing for other reasons (capacity, hw it is in is uselessly old, etc.) long before the drives wear out. The obsession with SSD write fatigue is silly. All drives can (and do) fail, you must have a plan to deal with that, and in my experience with SSDs, write fatigue is NOT the primary killer, it's just a predictable one. Nick.
Re: Tools for writers
> My substitute for _pandoc_ is the _org-mode_ of emacs, which is for some > people also good for outlining etc. if i quit using vim some day, it will be for something lightweight so i'll never run emacs, i guess. regards marc
Re: OpenBSD and solid state disks
On 11/2/19 4:10 PM, Raymond, David wrote: I recently installed OpenBSD on a Lenovo X1 Carbon with a solid state drive and it works great. My question is whether OpenBSD addresses the special characteristics of solid state drives, especially those having to do with longevity and reliability. I can't find anything written on this. Linux has certain means for addressing this issue, such as fstrim as well as various kernel options. Is there anything I have missed with OpenBSD on this subject? Dave Raymond Any modern drive will have write levelling. Check the rated number of writes for the drive. Run iostat for a week or two to determine average writes/time interval. Compare that against 10% of rated writes. When you get there, replace the drive. 500 TB is a good number for write endurance. Completely writing a 1TB drive every day gives you 50 days. Writing 100GB a day gives you 500 days... Do you write 20 DVDs a day? That's your answer. Geoff Steckel
Re: Tools for writers
Right. Thank you very much! Ingo Schwarze writes: > Hello, > > Xianwen Chen wrote on Sun, Nov 03, 2019 at 04:16:43PM +0100: > >> I am interested in giving _groff_ and _gpresent_ a try. I am seasoned >> LaTeX user. Is there a tutorial that you would recommend to someone like >> me? > > No, i'm not aware of tutorials (but i generally don't use tutorials, > so maybe i missed them). But there is good reference documentation: > > https://www.gnu.org/software/groff/manual/html_node/ > > Gpresent is a macro package specifically for presentation slides. > The documentation is in the groff_present(7) and presentps(1) > manual pages in the textproc/gpresent package and in the groff_mm(7) > manual page in the textproc/groff package. > >> Two things that come to my mind that I am concerned with. >> >> First, how does groff manage bibliography and citations? > > See the refer(1) utility in the textproc/groff package. > >> Second, peer-reviewed journals usually require submissions to be in Word >> format or in LaTeX. Is there an easy way to convert a groff document to >> a Word document or LaTeX? > > No, and there isn't even a complicated way either. If your publisher > requires LaTeX, use LaTeX; it's really that simple... > > Yours, > Ingo
Re: Tools for writers
On Sun, 3 Nov 2019, Ingo Schwarze wrote: And finally, the only thing that is seriously wrong with the "print/texlive" port is how ridiculously large it is. That is "texlive". Donald Knuths TeX/mf is exactly the opposite to bloat.
Re: Tools for writers
Here is an old system, written in FORTRAN and C, perhaps compiles in OpenBSD: http://www.tustep.uni-tuebingen.de/tustep_eng.html But I never used it and I am hyppy with TeX. Rodrigo
Re: Tools for writers
Xianwen Chen (陈贤文) [2019-11-03 13:44:20 +0100]: > Does _pandoc_ work on OpenBSD now? I can confirm that pandoc works on OpenBSD as I have built it a few months ago. However, it wasn't a painless procedure. I installed it via cabal, but you need a little workaround, since a W^X allowed partition is required for the build There are some articles online which I followed and created a cabal directory in /usr/local (which is wxallowed) and mounted it in my $HOME as ‘.cabal’ (as opposed to mounting /home as wxallowed). Regards, Bertalan -- Bertalan Z. Péter FB9B 34FE 3500 3977 92AE 4809 935C 3BEB 44C1 0F89 /"\ \ /ASCII Ribbon Campaign X against HTML email & proprietary attachments / \www.asciiribbon.org
Re: Skype alternatives for OpenBSD
On Sun, 3 Nov 2019, Jonathan Drews wrote: I thought Skype used a protocol that allowed other clients to connect to it then I read the Wikipedia page on Skype. The technology is owned by Microsoft. A standard is SIP. Then a solution would be something like: https://kb.asipto.com/kamailio:skype-like-service-in-less-than-one-hour
Re: Downgrade 6.6 to 6.5
On Sun, Nov 03, 2019 at 03:41:33PM +0100, 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 > Did you spend any time to send a report to maybe get your problem analyzed and fixed? -Otto
Re: Disable ftp in pkg_add syspatch sysupgrade
Hahaha Thanks Theo, that made me smile. But you have answered my question perfectly, albeit in a round about way. Indeed it doesn’t matter what it is called, and would be clearer with a generic name, as we got caught out by a program calling another program with colliding name. For example, Having ‘pkg_add’ call a program named ‘ftp’ to perform http and https downloads. But where errors in the ftp subprocess are printed by the pkg_add process, making it seem like pkg_add was failing on an ftp protocol request, rather than the ‘ftp’ client process failing (while doing an http call).. So I think it was pretty fair for us to end up scratching our heads ;) Thanks, Andy. Sent from a teeny tiny keyboard, so please excuse typos > On 30 Oct 2019, at 15:54, Theo de Raadt wrote: > > Andrew Lemin wrote: > >> To me this seems unusual (was expecting 'curl' or 'wget' etc to avoid code >> duplication) and confusing? What do you think? > > curl is not in openbsd > > wget is not in openbsd > > Maybe we should rename our downloading software to lemin, which is > obviously a randomly chosen name with some obscure acronym we'll invent > to back the name, being a name noone recognizes we can probably avoid > assumptions as to what it does, whether it does ftp, or http, or https, > or who knows what. Of course such a strange name would also lead people > to not discovering it, and make them install some monster software > package off the internet with another strange name. > > In summary I think it's turning into a shitty world with selection by > meme. > >
Re: Disable ftp in pkg_add syspatch sysupgrade
For completeness, I discovered I was having issues with downloading the sources for the sysupgrade command on my edge firewall also! So it was not limited to internet servers as first thought. Since upgrading the 6.6 (had to run sysupgrade 4 times to get it to complete the downloads), the issues seems to have been resolved and now all packages are installing first time every time.. So I am not sure if this is just me or a 6.5 issue. Most likely the former ;) Kind regards, Andy. Sent from a teeny tiny keyboard, so please excuse typos > On 31 Oct 2019, at 01:47, Stuart Henderson wrote: > >> On 2019-10-30, Andrew Lemin wrote: >> - But throws errors when I try and use flavours which is critical for >> installing python for example (NB; This is a different error to before, >> where I was getting 'timeout' instead of 'Invalid argument'); >> [HOME]root@testbsd1:/local#pkg_add python%2 py-pip python%3 py3-pip >> py3-setuptools >> quirks-3.124 signed on 2019-10-16T20:27:45Z >> http://mirror.bytemark.co.uk/pub/OpenBSD/6.5/packages/amd64/py3-setuptools-40.0.0v0.tgz: >> ftp: Receiving HTTP reply: Invalid argument >> signify: gzheader truncated >> Couldn't install py3-setuptools-40.0.0v0 > > Odd. Can you try replicating on 6.6? > > Does "pkg_add py-pip py3-pip py3-setuptools" (i.e. allow pkg_add to > find the dependencies by itself) work? > >
Re: Tools for writers
Dear Mr. Péter, Thank you! > I installed it via cabal, but you need a little workaround, since a W^X > allowed partition is required for the build There are some articles > online which I followed and created a cabal directory in /usr/local > (which is wxallowed) and mounted it in my $HOME as ‘.cabal’ (as opposed > to mounting /home as wxallowed). I may try it later! Great tips! Yours sincerely, Xianwen
Re: OpenBSD and solid state disks
Thanks for the insight on SSDs -- sounds like there is not much of an issue with modern drives. Dave Raymond On 11/3/19, gwes wrote: > On 11/2/19 4:10 PM, Raymond, David wrote: >> I recently installed OpenBSD on a Lenovo X1 Carbon with a solid state >> drive and it works great. >> >> My question is whether OpenBSD addresses the special characteristics >> of solid state drives, especially those having to do with longevity >> and reliability. I can't find anything written on this. Linux has >> certain means for addressing this issue, such as fstrim as well as >> various kernel options. Is there anything I have missed with OpenBSD >> on this subject? >> >> Dave Raymond >> > Any modern drive will have write levelling. Check the rated number > of writes for the drive. Run iostat for a week or two to determine > average writes/time interval. Compare that against 10% of rated > writes. When you get there, replace the drive. > > 500 TB is a good number for write endurance. > Completely writing a 1TB drive every day gives you 50 days. > Writing 100GB a day gives you 500 days... > Do you write 20 DVDs a day? That's your answer. > > Geoff Steckel > > -- David J. Raymond david.raym...@nmt.edu http://physics.nmt.edu/~raymond
Re: Downgrade 6.6 to 6.5
I had the fan problem on an X1 5G running linux, but a bios upgrade solved it. Dave Raymond On 11/3/19, 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 > > -- David J. Raymond david.raym...@nmt.edu http://physics.nmt.edu/~raymond
Re: Broadcom firmwares and nvram files
Hi Patrick,
Thanks a lot for your answer. You told me exactly what I was looking for.
I've generated a 32bit EFI grub image and placed it inside an archiso
bootable image,
booted from Arch Linux, grabbed the EFI var, came back to my OpenBSD
installation,
compiled the program you attached and after generating the nvram file
everything works like a charm.
I think I'll write a post on my blog to have a quick reference for the
next times.
Many thanks for your time.
Best Regards
Stefano Sent: Sunday, November 03, 2019 at 2:06 PM
From: "Stefan Sperling"
To: "Patrick Wildt"
Cc: "Stefano Enrico Mendola" , "Brad Smith"
, misc@openbsd.org
Subject: Re: Broadcom firmwares and nvram filesOn Sun, Nov 03, 2019 at
10:06:18AM +0100, Patrick Wildt wrote:
> Obiously I missed the attachment.
Could this tool be put into base or ports / pkg_add?
> /*
> * Copyright (c) 2013 Broadcom Corporation
> *
> * Permission to use, copy, modify, and/or distribute this software for
any
> * purpose with or without fee is hereby granted, provided that the
above
> * copyright notice and this permission notice appear in all copies.
> *
> * THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL
WARRANTIES
> * WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
> * MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE
FOR ANY
> * SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
> * WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
ACTION
> * OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR
IN
> * CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
> */
>
> #include
> #include
> #include
> #include
> #include
> #include
> #include
> #include
> //#include
>
> #define BRCMF_FW_MAX_NVRAM_SIZE 64000
> #define BRCMF_FW_NVRAM_DEVPATH_LEN 19 /* devpath0=pcie/1/4/ */
> #define BRCMF_FW_NVRAM_PCIEDEV_LEN 10 /* pcie/1/4/ + \0 */
> #define BRCMF_FW_DEFAULT_BOARDREV "boardrev=0xff"
>
> enum nvram_parser_state {
> IDLE,
> KEY,
> VALUE,
> COMMENT,
> END
> };
>
> /**
> * struct nvram_parser - internal info for parser.
> *
> * @state: current parser state.
> * @data: input buffer being parsed.
> * @nvram: output buffer with parse result.
> * @nvram_len: lenght of parse result.
> * @line: current line.
> * @column: current column in line.
> * @pos: byte offset in input buffer.
> * @entry: start position of key,value entry.
> * @multi_dev_v1: detect pcie multi device v1 (compressed).
> * @multi_dev_v2: detect pcie multi device v2.
> * @boardrev_found: nvram contains boardrev information.
> */
> struct nvram_parser {
> enum nvram_parser_state state;
> char *data;
> char *nvram;
> uint32_t nvram_len;
> uint32_t line;
> uint32_t column;
> uint32_t pos;
> uint32_t entry;
> int multi_dev_v1;
> int multi_dev_v2;
> int boardrev_found;
> };
>
> /**
> * is_nvram_char() - check if char is a valid one for NVRAM entry
> *
> * It accepts all printable ASCII chars except for '#' which opens a
comment.
> * Please note that ' ' (space) while accepted is not a valid key name
char.
> */
> static int is_nvram_char(char c)
> {
> /* comment marker excluded */
> if (c == '#')
> return 0;
>
> /* key and value may have any other readable character */
> return (c >= 0x20 && c < 0x7f);
> }
>
> static int is_whitespace(char c)
> {
> return (c == ' ' || c == '\r' || c == '\n' || c == '\t');
> }
>
> static enum nvram_parser_state brcmf_nvram_handle_idle(struct
nvram_parser *nvp)
> {
> char c;
>
> c = nvp->data[nvp->pos];
> if (c == '\n')
> return COMMENT;
> if (is_whitespace(c) || c == '\0')
> goto proceed;
> if (c == '#')
> return COMMENT;
> if (is_nvram_char(c)) {
> nvp->entry = nvp->pos;
> return KEY;
> }
> printf("warning: ln=%d:col=%d: ignoring invalid character\n",
> nvp->line, nvp->column);
> proceed:
> nvp->column++;
> nvp->pos++;
> return IDLE;
> }
>
> static enum nvram_parser_state brcmf_nvram_handle_key(struct
nvram_parser *nvp)
> {
> enum nvram_parser_state st = nvp->state;
> char c;
>
> c = nvp->data[nvp->pos];
> if (c == '=') {
> /* ignore RAW1 by treating as comment */
> if (strncmp(&nvp->data[nvp->entry], "RAW1", 4) == 0)
> st = COMMENT;
> else
> st = VALUE;
> if (strncmp(&nvp->data[nvp->entry], "devpath", 7) == 0)
> nvp->multi_dev_v1 = 1;
> if (strncmp(&nvp->data[nvp->entry], "pcie/", 5) == 0)
> nvp->multi_dev_v2 = 1;
> if (strncmp(&nvp->data[nvp->entry], "boardrev", 8) == 0)
> nvp->boardrev_found = 1;
> } else if (!is_nvram_char(c) || c == ' ') {
> printf("warning: ln=%d:col=%d: '=' expected, skip invalid key entry\n",
> nvp->line, nvp->column);
> return COMMENT;
> }
>
> nvp->column++;
> nvp->pos++;
> return st;
> }
>
> static enum nvram_parser_state
> brcmf_nvram_handle_value(struct nvram_parser *nvp)
> {
> char c;
> char *skv;
> char *ekv;
> uint32_t cplen;
>
> c = nvp->data[nvp->pos];
> if (!is_nvram_char(c)) {
> /* key,value pair complete */
> ekv = &nvp->data[nvp->pos];
> skv = &nvp->data[nvp->entry];
> cplen = ekv - skv;
> if (nvp->nvram_len + cplen + 1 >= BRC
Re: Tools for writers
Maybe have a look at Asciidoctor[1]. It's a plain text markup language and fast parser/converter with ruby as its sole dependency. The language is easy to write, very easy to read and doesn't get in your way. It's similar to Markdown but much more potent, well-rounded and extensible if necessary. It was born as a replacement for reStructeredText and is very well suited for writing technical documentation or books. I use it specifically because I can just write a plain text document and worry about output formatting and everything else later, all while having the confidence that the output formatting will be doable with reasonable effort. In the beginning of trying it out, I used the firefox plugin from the same project which converts documents on the fly into HTML to get a sense of what the output will look like. (Asciidoctor is not to be confused with Asciidoc, which is the predecessor project but seems abandoned.) Fred [1]: https://asciidoctor.org Am 2019-11-02 16:00, schrieb Oliver Leaver-Smith: Hello, 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.) Mich appreciated ~ols -- Oliver Leaver-Smith +44(0)114-360-1337 TZ=Europe/London
Re: Skype alternatives for OpenBSD
On 3/11/19 11:27 pm, Jonathan Drews wrote: > The woman offering the class uses Skype so I am probably going to have to use > Windows. I have a laptop with Windows 10 but I hardly ever use it. Windows is > a big step down in performance when compared to OpenBSD. > I thought Skype used a protocol that allowed other clients to connect to it > then I read the Wikipedia page on Skype. The technology is owned by Microsoft. Yeah, Skype uses its own proprietary protocol. Not sure if there's ever been an effort to reverse engineer it. Skype was a start-up company originally, which was then bought by eBay, then later sold to Microsoft. There was clients for Linux, MacOS X and Windows years ago, not sure what their status is today. I haven't touched Skype myself since 2012, last time I did was on MacOS X 10.6. I hear there's a WebRTC version. If the browsers available for OpenBSD are capable of this too, that might be your best bet, otherwise you're more-or-less snookered: you'll have to run Skype either in a VM, alternate OS on the same computer (dual-boot), or install it on a separate computer. -- Stuart Longland (aka Redhatter, VK4MSL) I haven't lost my mind... ...it's backed up on a tape somewhere.
Re: OpenBSD and solid state disks
On 4/11/19 8:13 am, Raymond, David wrote: > Thanks for the insight on SSDs -- sounds like there is not much of an > issue with modern drives. Well, you're at the mercy of the SSD firmware to "do the right thing" and move the data around to ensure even wear levelling. Most do. The fact that you see SSDs on the consumer market that have 3 and 5 year warranties on them (the 2TB Samsung in my laptop at home had a 10 year warranty), suggests the manufacturers are either highly confident their product will last (or at least confident their disclaimers will let them off the hook). In the last few years I've had a couple of SD cards wear out, and one Intel 240GB SSD fail prematurely (it had a 3 year warranty, was about 12 months old at the time). I had some fun initially claiming the warranty of the Intel as they wanted a report from their Windows-only tool (hopefully their engineering team have seen fit to produce a stand-alone bootable version). I was able to provide reports from `smartctl` on Linux. After I pointed out that I didn't have Windows on this machine (and that if I did, it would have gone up in smoke with the SSD failing), they accepted this and replaced the faulty drive without further issues. Like any storage technology, SSDs are not infallible. Back up the data you wish to keep regularly, and test your back-ups. -- Stuart Longland (aka Redhatter, VK4MSL) I haven't lost my mind... ...it's backed up on a tape somewhere.
Re: Courier-Imap no longer accepts ssl connections after update to -current
Yes, it is (was) a permission issue. > -Original Message- > From: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org] On Behalf > Of Giovanni Bechis > Sent: Sunday, November 03, 2019 5:22 AM > To: misc@openbsd.org > Subject: Re: Courier-Imap no longer accepts ssl connections after > update to -current > > Theodore Wynnychenko wrote: > > Hi (again): > > > > After updating to current yesterday, and then updating all the > packages > > (using "pkg_add -vui -Dsnap"), I can no longer connect to the ssl > (993) port > > of the courier-imap server running on the system. > > > > Prior to the update, ssl connections were working without an issue. > > > it's working fine for me with: > $ ldd /usr/local/bin/couriertls | grep ssl > 11ae13a38000 11ae13a9c000 rlib 01 0 > /usr/lib/libssl.so.48.0 > and > OpenBSD 6.6-current (GENERIC.MP) #425: Fri Nov 1 23:49:35 MDT 2019 > I updated this AM to be sure: OpenBSD 6.6-current (GENERIC.MP) #427: Sat Nov 2 13:23:11 MDT 2019 # ldd /usr/local/bin/couriertls | grep ssl 113249966000 1132499ca000 rlib 01 0 /usr/lib/libssl.so.48.1 But, I kept getting the error and no connection: # openssl s_client -connect 127.0.0.1:993 CONNECTED(0003) 11102104709736:error:140040E5:SSL routines:CONNECT_CR_SRVR_HELLO:ssl handshake failure:/usr/src/lib/libssl/ssl_pkt.c:585: I then compared to prior (6.5) working courier package with the -current one. When I compared /usr/local/libexec/imapd-ssl.rc (and pop3d-ssl.rc), I noticed the addition of: > 56a62 > -user=_courier \ So, it seems that before the last update, couriertls ran as root, and now it runs as _courier. I completely understand the desire to drop root. But, in my case, my private cert was in /etc/ssl/private. drwx-- 2 root wheel 512B Nov 2 14:00 private and: -rw--- 1 root wheel 6.2K Dec 17 2016 imapd.pem So, this was the issue for me. I did not want to disrupt the structure of my ssl private keys too much, so I just made a second "private" directory for courier. drwx-- 2 _courier _courier 512B Nov 3 17:17 private-courier Put a copy of the file there. -rw--- 1 _courier _courier 6.2K Nov 3 17:09 imapd.pem And updated the /etc/imap-ssl configuration: TLS_CERTFILE=/etc/ssl/private-courier/imapd.pem TLS_DHPARAMS=/etc/ssl/private-courier/imapd.pem This fixed my issue (did the same for the pop3-ssl configuration). I reviewed my notes from when I installed this (back around 5.5-5.6 - I did not realize I was following -current for so long), and did not see a note that couriertls required the private key to be non-root readable. Also, the current README/config file does not inform that the cert file must now be readable by _courier, it only indicates that it "must not be world-readable." I am posting this here in case someone else runs into a similar issue. Thanks again for pointing me in the right direction. Ted
Re: OpenBSD 6.6 amd64 iavf(4) iavf / SR-iov 40G NIC lots of Jitter
Hello, from bare metal testing the ixl driver didn't have any jitter, but when IXL card it was passed through with SR-IOV on a KVM virtual machine there was jitter, so i'm thinking the issue is in the virtual machines handling of the PCI-PCI bridge I'm assuming based on the above test the iavf driver is not at fault but probably some thing in PCI between OpenBSD Guest running on the KVM Q35 Machine. Ill open a separate email thread about KVM Guests and support for Virtio / virtual hardware in OpenBSD Thanks On Tue, 22 Oct 2019 at 09:32, Tom Smyth wrote: > > Hi, > I ran another test with virtio net drivers on the same Q35 type vm guest in > KVM > and the pings were a lot more stable. > > > --- 10.4.24.1 ping statistics --- > 1000 packets transmitted, 1000 packets received, 0.0% packet loss > round-trip min/avg/max/std-dev = 0.223/0.394/3.766/0.172 ms > > pcidump > openbsd66# pcidump > Domain /dev/pci0: > 0:0:0: Intel 82G33 Host > 0:1:0: Bochs VGA > 0:26:0: Intel 82801I USB > 0:26:1: Intel 82801I USB > 0:26:2: Intel 82801I USB > 0:26:7: Intel 82801I USB > 0:27:0: Intel 82801I HD Audio > 0:28:0: Red Hat unknown > 0:28:1: Red Hat unknown > 0:28:2: Red Hat unknown > 0:28:3: Red Hat unknown > 0:29:0: Intel 82801I USB > 0:29:1: Intel 82801I USB > 0:29:2: Intel 82801I USB > 0:29:7: Intel 82801I USB > 0:30:0: Intel 82801BA Hub-to-PCI > 0:31:0: Intel 82801IB LPC > 0:31:2: Intel 82801I AHCI > 0:31:3: Intel 82801I SMBus > 5:1:0: Red Hat Qemu PCI-PCI > 5:2:0: Red Hat Qemu PCI-PCI > 5:3:0: Red Hat Qemu PCI-PCI > 5:4:0: Red Hat Qemu PCI-PCI > 6:7:0: Intel 82801I AHCI > 6:18:0: Qumranet Virtio Network > > dmesg > openbsd66# dmesg > OpenBSD 6.6 (GENERIC) #353: Sat Oct 12 10:45:56 MDT 2019 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC > real mem = 4278050816 (4079MB) > avail mem = 4135776256 (3944MB) > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xf5900 (10 entries) > bios0: vendor SeaBIOS version "rel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org" > date 04/01/2014 > bios0: QEMU Standard PC (Q35 + ICH9, 2009) > acpi0 at bios0: ACPI 3.0 > acpi0: sleep states S3 S4 S5 > acpi0: tables DSDT FACP APIC SSDT HPET MCFG > acpi0: wakeup devices > acpitimer0 at acpi0: 3579545 Hz, 24 bits > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > cpu0 at mainbus0: apid 0 (boot processor) > cpu0: Intel(R) Xeon(R) CPU E5-2660 v2 @ 2.20GHz, 91.04 MHz, 06-3e-04 > cpu0: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SS,HTT,SSE3,PCLMUL,SSSE3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,FSGSBASE,TSC_ADJUST,SMEP,ERMS,UMIP,MD_CLEAR,IBRS,IBPB,STIBP,SSBD,ARAT,XSAVEOPT,MELTDOWN > cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB > 64b/line 16-way L2 cache > cpu0: ITLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped > cpu0: DTLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped > cpu0: smt 0, core 0, package 0 > mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges > cpu0: apic clock running at 1000MHz > ioapic0 at mainbus0: apid 0 pa 0xfec0, version 20, 24 pins > acpihpet0 at acpi0: 1 Hz > acpimcfg0 at acpi0 > acpimcfg0: addr 0xb000, bus 0-255 > acpiprt0 at acpi0: bus 0 (PCI0) > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _STA method > no _ST
KVM Q35 Virtual Machines , SR-IOV PCI-E Bridges and OpenBSD jitter on attached network
Hello, Has anyone seen jitter from 0.5ms to 500ms on PCI-E attached (SR-IOV) Physical function / virtual function Network interfaces on OpenBSD Machines running on a KVM Virtual machine type (Q35) ? any tips for diagnosing what is causing the jitter ? I have ruled out the driver Ixl by comparing physical / bare metal performance vs performance when the physical function of the nic is passed through to the KVM Q35 guest I have also ruled out the hypervisor as centos Guest VMs running with the same hardware don't suffer from the jitter issue -- Kindest regards, Tom Smyth.
Re: Tools for writers
On 2019-11-02 18:29, Ingo Schwarze wrote: Hi Jordan, Jordan Geoghegan wrote on Sat, Nov 02, 2019 at 05:44:23PM -0700: I've thought about learning latex and mandoc and all the fancy tools, but I've just never gotten around to it. Actually, both mandoc(1) and mdoc(7) are off-topic in this thread. You cannot use either for writing a book, neither the mdoc(7) language nor the mandoc(1) program supports any of the important features. Woops, I got pandoc and mandoc confused. That said, the obvious answer for the OP is of course the "textproc/groff" port (disclosure: which i maintain). The roff(7) language and the troff programm is what people in the UNIX world always used for writing books and journal articles, and it is very much alive even after the roff language celebrated its 55th birthday this year. I'm in the habit of using it to prepare slides for conference talks (with textproc/gpresent), for example, and i'm not the only only one. [snip] As long as you only *use* macro packages, groff is *much* easier to use than LaTeX (not least because the quality of documentation of groff is vastly superior to LaTeX, and LaTeX documentation is so extremely huge and fragmented that it's a terrible challenge to find anything you need). [snip] Most certainly, it is *much* easier to get good typography out of groff or LaTeX (no matter which one) than out of LibreOffice or any similar abomination. Yours, Ingo Thanks for the recommendation Ingo, I'm going to test out groff for a writing project I have coming up. Cheers, Jordan
Re: Changes to VLAN and promiscuous mode in 6.6
Hey,
This should be fixed in current as of r1.199 of src/sys/net/if_vlan.c
Sorry for the inconvenience.
Cheers,
dlg
> On 29 Oct 2019, at 19:49, Zé Loff wrote:
>
>
> Hi all
>
> Some changes in VLAN-related code went into 6.6 and I think some of them
> changed the way the parent interface gets into promiscuous mode. Let me
> try to explain...
>
> Our ISP provides internet and VoIP over two separate VLANs (100 and 101,
> respectively). Our external firewall has two physical interfaces re0,
> and re1, and also does the filtering and NATing for internet, but VoIP
> traffic is transparently forwarded to the VoIP phone. So it's something
> like this:
>
> GPON -> re0 -+--> vlan100 -> (PF/NAT) -> vlan90 -+-> re1 -> A switch
> \-> vlan1010 -> bridge1 -> vlan1011 -/
>
> The VoIP phone connected to the switch, which does all the appropriate
> tagging and untagging. re0 and re1 have no IP addresses, neither do the
> vlan1010, vlan1011 and bridge1 virtual interfaces. The VoIP phone gets
> configured by DHCP, and gets its address (and etc) from the ISP. All
> interfaces are up, and correctly configured (ifconfigs below). This
> worked fine up until the 6.6 upgrade.
>
> Now, if things are left alone, the phone fails to get DHCP replies.
> This can be checked by running "tcpdump -i re1 vlan 101", which clearly
> shows the DHCP requests coming from the phone, but getting no replies.
> Exactly the same is seen on vlan1011 and vlan1010 (i.e. on both sides of
> the bridge1): DHCP requests but no replies. If tcpdump is run on re0
> ("tcpdump -i re0 vlan 101") then the interface goes into promiscuous
> mode and the DHCP replies start flowing from the ISP and the phone
> finally gets configured. Crucially, if the "-p" flag is added to
> tcpdump (i.e. not putting the if in promiscuous mode), DHCP fails.
>
> Is this behaviour intended and, if so, can re0 be configured to stay in
> promiscuous mode without having to do something silly as tcpdump'ing
> into /dev/null?
>
> Thanks in advance
> Zé
>
> --
>
> # ifconfig -A
> lo0: flags=8049 mtu 32768
>index 5 priority 0 llprio 3
>groups: lo
>inet6 ::1 prefixlen 128
>inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5
>inet 127.0.0.1 netmask 0xff00
> re0: flags=8b43 mtu
> 1500
>lladdr 00:0d:b9:3c:b0:e8
>index 1 priority 0 llprio 3
>media: Ethernet autoselect (1000baseT full-duplex,master)
>status: active
> re1: flags=8843 mtu 9100
>lladdr 00:0d:b9:3c:b0:e9
>index 2 priority 0 llprio 3
>media: Ethernet autoselect (1000baseT full-duplex,rxpause,txpause)
>status: active
> re2: flags=8802 mtu 1500
>lladdr 00:0d:b9:3c:b0:ea
>index 3 priority 0 llprio 3
>media: Ethernet autoselect (10baseT half-duplex)
>status: no carrier
> enc0: flags=0<>
>index 4 priority 0 llprio 3
>groups: enc
>status: active
> bridge1: flags=41
>index 6 llprio 3
>groups: bridge
>priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp
>vlan1011 flags=3
>port 11 ifpriority 0 ifcost 0
>vlan1010 flags=3
>port 10 ifpriority 0 ifcost 0
>Addresses (max cache: 100, timeout: 240):
>00:00:5e:00:01:c9 vlan1010 1 flags=0<>
>80:5e:c0:12:3f:80 vlan1011 1 flags=0<>
> vlan100: flags=808843 mtu
> 1500
>lladdr 00:0d:b9:3c:b0:e8
>description: WAN
>index 9 priority 0 llprio 3
>encap: vnetid 100 parent re0 txprio packet rxprio outer
>groups: vlan egress
>media: Ethernet autoselect (1000baseT full-duplex,master)
>status: active
>inet 148.69.164.57 netmask 0xfc00 broadcast 148.69.167.255
>inet 148.69.143.1 netmask 0xfffc broadcast 148.69.143.3
> vlan1010: flags=8943 mtu 1500
>lladdr 00:0d:b9:3c:b0:e8
>description: VoIP WAN
>index 10 priority 0 llprio 3
>encap: vnetid 101 parent re0 txprio packet rxprio outer
>groups: vlan
>media: Ethernet autoselect (1000baseT full-duplex,master)
>status: active
> vlan1011: flags=8943 mtu 1500
>lladdr 00:0d:b9:3c:b0:e9
>description: VoIP DMZ
>index 11 priority 0 llprio 3
>encap: vnetid 101 parent re1 txprio packet rxprio outer
>groups: vlan
>media: Ethernet autoselect (1000baseT full-duplex,rxpause,txpause)
>status: active
> vlan90: flags=8843 mtu 9000
>lladdr 00:0d:b9:3c:b0:e9
>description: DMZ
>index 14 priority 0 llprio 3
>encap: vnetid 90 parent re1 txprio packet rxprio outer
>groups: vlan
>media: Ethernet autoselect (1000baseT full-duplex,rxpause,txpause)
>status: active
>inet 10.17.16.1 netmask 0xfe00 broadcast 10.17.17.255
> pflog0: flags=141 mtu 33136
>index 15 priority 0 llprio 3
>groups: pflogDear sirs
>
>
> #
Re: Skype alternatives for OpenBSD
On 2019-11-03 05:15, Stefan Sperling wrote: On Sat, Nov 02, 2019 at 02:47:16PM -0700, Jordan Geoghegan wrote: Assuming Firefox or chromium on OpenBSD has WebRTC support (havent checked in a while), talky.io should work. It's a free website that supports WebRTC chats. I've used it in the past with great success. The www/nextcloud port with the 'Talk' add-on, and with telephony/turnserver, can be used to self-host a WebRTC server on OpenBSD. That's really cool, thanks for mentioning that. I'm going to go try setting up a Nextcloud WebRTC server now :p
dmesg OBSD 6.6 - only a few bugs
I had to perform an upgrade from the 6.6 CD after the 6.5 version stopped booting. Everything is now back to work. Here is the fresh dmesg. The only imperfection is : "Tearfree" X.org configuration is required whereas it wasn't on my previous OBSD install. YouTube videos are also very twitchy and seem to be heavy on the system resources, which used not to be the case. I use xfce4-desktop on an independently assembled Linux laptop. Sylvain S OpenBSD 6.6 (GENERIC) #353: Sat Oct 12 10:45:56 MDT 2019 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC real mem = 8461582336 (8069MB) avail mem = 8192516096 (7812MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xda571018 (40 entries) bios0: vendor American Megatrends Inc. version "4.6.5" date 11/11/2013 bios0: CLEVO CO. W240EU/W250EUQ/W270EUQ acpi0 at bios0: ACPI 5.0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT MCFG SSDT HPET SSDT SSDT SSDT BGRT acpi0: wakeup devices P0P1(S4) USB1(S3) USB2(S3) USB3(S3) USB4(S3) USB5(S3) USB6(S3) USB7(S3) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) PXSX(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i3-3130M CPU @ 2.60GHz, 2594.48 MHz, 06-3a-09 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,XSAVE,AVX,F16C,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,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.1.2, IBE cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 acpimcfg0: addr 0xf800, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (RP01) acpiprt2 at acpi0: bus -1 (RP02) acpiprt3 at acpi0: bus 2 (RP03) acpiprt4 at acpi0: bus 3 (RP04) acpiec0 at acpi0 acpicpu0 at acpi0: C3(200@87 mwait.1@0x30), C2(500@59 mwait.1@0x10), C1(1000@1 mwait.1), PSS acpitz0 at acpi0: critical temperature is 120 degC acpipci0 at acpi0 PCI0: 0x0010 0x0011 0x acpicmos0 at acpi0 acpibtn0 at acpi0: PWRB acpibtn1 at acpi0: SLPB acpibtn2 at acpi0: LID0 acpiac0 at acpi0: AC unit online acpibat0 at acpi0: BAT0 model "BAT" serial 0001 type LION oem "NOTEBOOK" "PNP0C14" at acpi0 not configured acpivideo0 at acpi0: GFX0 acpivout0 at acpivideo0: LCD0 cpu0: using VERW MDS workaround (except on vmm entry) cpu0: Enhanced SpeedStep 2594 MHz: speeds: 2600, 2500, 2400, 2300, 2200, 2100, 2000, 1900, 1800, 1700, 1600, 1500, 1400, 1300, 1200 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel Core 3G Host" rev 0x09 inteldrm0 at pci0 dev 2 function 0 "Intel HD Graphics 4000" rev 0x09 drm0 at inteldrm0 inteldrm0: msi xhci0 at pci0 dev 20 function 0 "Intel 7 Series xHCI" rev 0x04: msi, xHCI 1.0 usb0 at xhci0: USB revision 3.0 uhub0 at usb0 configuration 1 interface 0 "Intel xHCI root hub" rev 3.00/1.00 addr 1 "Intel 7 Series MEI" rev 0x04 at pci0 dev 22 function 0 not configured ehci0 at pci0 dev 26 function 0 "Intel 7 Series USB" rev 0x04: apic 2 int 16 usb1 at ehci0: USB revision 2.0 uhub1 at usb1 configuration 1 interface 0 "Intel EHCI root hub" rev 2.00/1.00 addr 1 azalia0 at pci0 dev 27 function 0 "Intel 7 Series HD Audio" rev 0x04: msi azalia0: codecs: VIA/0x8446, Intel/0x2806, using VIA/0x8446 audio0 at azalia0 ppb0 at pci0 dev 28 function 0 "Intel 7 Series PCIE" rev 0xc4: msi pci1 at ppb0 bus 1 ppb1 at pci0 dev 28 function 2 "Intel 7 Series PCIE" rev 0xc4: msi pci2 at ppb1 bus 2 iwn0 at pci2 dev 0 function 0 "Intel Centrino Wireless-N 2230" rev 0xc4: msi, MIMO 2T2R, BGN, address 00:c2:c6:02:95:ea ppb2 at pci0 dev 28 function 3 "Intel 7 Series PCIE" rev 0xc4: msi pci3 at ppb2 bus 3 rtsx0 at pci3 dev 0 function 0 "Realtek RTL8411 Card Reader" rev 0x01: msi sdmmc0 at rtsx0: 4-bit, dma re0 at pci3 dev 0 function 2 "Realtek 8168" rev 0x0a: RTL8411 (0x4880), msi, address 00:90:f5:e2:e0:c3 rgephy0 at re0 phy 7: RTL8169S/8110S/8211 PHY, rev. 5 ehci1 at pci0 dev 29 function 0 "Intel 7 Series USB" rev 0x04: apic 2 int 23 usb2 at ehci1: USB revision 2.0 uhub2 at usb2 configuration 1 interface 0 "Intel EHCI root hub" rev 2.00/1.00 addr 1 pcib0 at pci0 dev 31 function 0 "Intel HM76 LPC" rev 0x04 ahci0 at pci0 dev 31 function 2 "Intel 7 Series AHCI" rev 0x04: msi, AHCI 1.3 ahci0: port 0: 6.0Gb/s ahci0: port 2: 1.5Gb/s scsibus1 at ahci0: 32 targets sd0 at scsibus1 targ 0 lun 0: naa.5002538d415ff087 sd0: 238475MB, 512 bytes/sector, 488
Re: Tools for writers
On Sat, 2 Nov 2019 20:07:39 +0100 Antoine Jacoutot wrote: > On Sat, Nov 02, 2019 at 03:04:34PM -0400, STeve Andre' wrote: > > > > > > On 2019-11-02 11:00, Oliver Leaver-Smith wrote: > > > Hello, > > > > > > 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.) > > > > > > Mich appreciated > > > > > > ~ols > > > -- > > > Oliver Leaver-Smith > > > +44(0)114-360-1337 > > > TZ=Europe/London > > > > > > > /usr/bin/vi > > You obviously never wrote a book. > At least not with the requirements OP asked for. I know what you mean and you're right to a degree, but I'm currently writing a couple of books with AsciiDoctor edited in Vim. And I use VimOutliner for outlining. I'll try to remember and let you know when I actually finish one of the books. SteveT Steve Litt November 2019 featured book: Manager's Guide to Technical Troubleshooting Second edition http://www.troubleshooters.com/mgr
Re: Tools for writers
On Sun, 3 Nov 2019 18:50:56 + (UTC) Roderick wrote: > Here is an old system, written in FORTRAN and C, perhaps compiles in > OpenBSD: > > http://www.tustep.uni-tuebingen.de/tustep_eng.html > > But I never used it and I am hyppy with TeX. > > Rodrigo > I'm not sure, but I think if you write with a certain subset of TeX, it would be fairly easy to write a program to convert it to XHTML5, from which you can pretty easily create ePubs. Plain TeX as made by Knuth is indeed simple for all simple things, and doable for more complicated things. SteveT Steve Litt November 2019 featured book: Manager's Guide to Technical Troubleshooting Second edition http://www.troubleshooters.com/mgr
Re: Tools for writers
On Sat, 2 Nov 2019 15:16:22 -0400 STeve Andre' wrote: > On 2019-11-02 15:07, Antoine Jacoutot wrote: > > On Sat, Nov 02, 2019 at 03:04:34PM -0400, STeve Andre' wrote: > >> > >> > >> On 2019-11-02 11:00, Oliver Leaver-Smith wrote: > >>> Hello, > >>> > >>> 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.) > >>> > >>> Mich appreciated > >>> > >>>~ols > >>> -- > >>> Oliver Leaver-Smith > >>> +44(0)114-360-1337 > >>> TZ=Europe/London > >>> > >> > >> /usr/bin/vi > > > > You obviously never wrote a book. > > At least not with the requirements OP asked for. > > > Actually, I am, right now. I've found that "formatting" is an > annoyance, when writing material. Get it written, *then* worry > about how it looks. I've done this for more than 40 years when > creating documents, reports and such for work. So after writing the whole thing, you're going to go back and insert some sorts of codes for backstory paragraphs, emphasis, dialog, and various other styles? How are you going to get word-wrap right? I know it's possible with novels, but it takes some pretty good writing skills to do so. And I'll go out on a limb and say it's impossible with a technical book. SteveT Steve Litt November 2019 featured book: Manager's Guide to Technical Troubleshooting Second edition http://www.troubleshooters.com/mgr
Re: Downgrade 6.6 to 6.5
I did not sent a bug report per say. Just this: http://openbsd-archive.7691.n7.nabble.com/Fan-spinning-constantly-on-Lenovo-X1C-and-6-6-td375687.html I upgraded to -current #427 and it seems to be better. I will spend more time with it before I draw any conclusions. thanks On Sun, Nov 3, 2019 at 8:52 PM Otto Moerbeek wrote: > > On Sun, Nov 03, 2019 at 03:41:33PM +0100, 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 > > > > Did you spend any time to send a report to maybe get your problem > analyzed and fixed? > > -Otto
