Re: Tools for writers
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 agree with the majority of people here, use a text editor you are comfortable with. I use nvi, I've tryed a lot, but I always go back to nvi. Remember that the version in base doesn't have unicode support. One that almost got me was the new fork of nedit: https://sourceforge.net/projects/xnedit/ My advise is to think about your layout, how people are going to read your work, and then "mark" that layout in a plain text file, using spaces, labels, etc. Write freely, without being distracted by strange lines and your text being transformed while you are typing it, lags... oh man, I don't know why people like those monstrosities, but a lot of people love them so maybe something is wrong with me!. Use key bindings to search for words, translations, synonymous, local dictionaries, whatever. Use the tools your OS already have. Then, at the end, choose a formatter that fits you, or the one that your publisher ask you for, if any. I prefer troff than TeX/LaTeX. In my opinion, the latter has become a chaos. The last time I used it (more than a decade ago) it was still compiled by a generator of C code from pascal sources, and then the "distribution" grew from it like that story about alien plants from Creepshow. If you have to use it, I remember one distribution on Plan9, kerTeX IIRC, it was in unix also, way more compact. I prefer heirloom troff. Very small, very easy to use fonts and non English hyphenation and it feels more unix to me, I suppose it is just a matter of taste. The last time I was in the groff mailing list (they shared it nicely with heirloom troff users) they were working on a macro "mom" to make life easier to writers. I prefer using troff directly, but you can give it a try, it should be mature now. Make a script that creates an input for your formatter from your plain file, using your labels, spaces, etc, so if you need to use another formatter, you don't have to touch your work, just make another script. Just an advise. I enjoyed this book back at the time. Now is not only open, but you have also the groff source, so you can see how is the book itself developed. I think that you can pick a lot of good ideas from it, and it shows you how to use and combine the tools you already have, that is, the unix philosophy. https://www.oreilly.com/openbook/utp/ P.S. I read someone recommending lilypond for typesetting music. The output is beautiful, and if you are familiar with lisp you'll be familiar with its guts. But I prefer these: This is a new version of RISC OS pms: https://sourceforge.net/p/philip-s-music-writer/ I discovered this some time ago by chance, and now I have to make a choice: http://www.Arkkra.com/ Both of them are small C programs, almost no dependencies, beautiful output and easy input syntax. Regards, adr
Re: Tools for writers
On Sat, Nov 02, 2019 at 03:00:28PM +, 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 I am not sure what is your ability to learn tools - no offence, but some people want to have it as WYSIWIG, period, and I am mostly ok about it (as long as they also do their cleaning). However, my unholy opinion is, if you plan for your words to be readable with the least problem say, twenty years from now, then you should stick with text based formats for, er, text and learn few tools that can process such format. So, - LaTeX for writing a book It is possible to have parts of a text in various files, which can be included into main file - various ways of developing plot, etc. It is possible to have many versions of same book, including chapters into them as separate files. And so on. I am not sure if a writer actually needs this much flexibility, but a lot is possible if you would like to mess with different ways to organize a book. - Emacs for editor This part is tricky, but I definitely prefer Emacs. Some prefer Vim and I agree it is very fine editor, but myself, I go with Emacs. I stay away from anything web based, browser based and Javascript based. All of those look like ticking bombs to me. When they go (not an unlikely event, IMHO) those depending on them are left to freeze. Or they will be dying a death of thousand worms loaded from some far away countries in their just-updated JS library. - Org mode for plot/characters and stuff Org mode is kind of program running inside Emacs (not really, but do I want to delve into talking about Lisp, loadable code and programmable editors). Or, it is a way to have one's own personal wiki in a file, without the need for web server and whatnot. Very handy, if you ask me. All those are tools and require some learning. In my case, I read a tutorial built into Emacs (say, an hour of reading + learning to press right keys), I read some chapters from Leslie Lamport book on LaTeX (say, maybe few hours of trying stuff inside Emacs and producing documents with it). As of Org-mode, I caught some basics and started going, then caught some more and there is still 98% or more to learn, but as I do not have to, I just use what I know and keep going. There are few more tools which might be useful for above case. - pandoc for converting from LaTeX to ODT (i.e. Open Office) - I have not used it but some people say it works - version control - whatever is easier, I have just set my own org-mode based "wiki" into RCS. RCS is amongst the oldest such system still in use, but I did not wanted to mess with other things, for a while. Now, if I make a mistake, press wrong key combo and delete half of my wiki, I might have better chance to recover from this error. There are many version control systems to choose from, I think most will work locally on your computer without prematurely exposing the book to the outside world. This email was written in Emacs, BTW. I get easy formatting for free. Of course, tools have quirks. I think so. I got used to them and forgot, so I am unable to say more about this. So maybe the learning experience will not be peachy rosy for you at first, but I would say positives prevail over time. HTH -- Regards, Tomasz Rola -- ** A C programmer asked whether computer had Buddha's nature. ** ** As the answer, master did "rm -rif" on the programmer's home** ** directory. And then the C programmer became enlightened... ** ** ** ** Tomasz Rola mailto:tomasz_r...@bigfoot.com **
Re: Tools for writers
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) > For writing you need a text editor. I like nvi 1.79 /usr/bin/vi due to its predictability as I agree that Vim sucks http://www.galexander.org/vim_sucks.html nvi is in the base :-) Unfortunately yacc was "depreciated" on Linux in favor of bison so good luck compiling nvi. I have never been able to pull that one on Red Hat 7. Now typesetting is whole another story. In old good times a writter will bring her/his manuscript to a publishing company where qualified individuals would apply typographic rules, enforce standards, and do graphics design before sending things to the typesetter. IMHO letterpress is still the gold standard and nothing comes close to it. However people moved to phototype first and digital to cut the cost. Cutting cost came with the price. Quality sucks but I guess if you have never had a letterpress book in your hands you will not know it. I am guessing you want a computerized solution but you are not a typesetter nor designer and you need some assistance to impose format on the text. Essentially you have two classes of solutions. 1. You will need to use some kind logical markup and enter the mixture of text and commands. In this case typography is embedded into the source file. 2. You want some super clever program to do typesetting for you. You are in luck my friend. If you chose solution one all four typesetting systems in existence are ported and can be found in OpenBSD ports. I am listing them in the chronological order. a. Troff (Please see GNU Troff aka. Groff from the ports) b. TeX (LaTeX is just a set of macros but you can also use key-value driven ConTeXt) c. Lout d. To typeset music use LilyPond. If you chose second option there is only one solution I am aware of. It is Brian K. Reid Scribe. Brian used to work here at Carnegie Mellon University many years before my time. After failing to make millions he essentially left his code to his assistant and my good friend/co-worker Dale Moore who still has a working copy. I am not sure if we can get Scribe to the ports three but for private use should be Ok. I can check with Dale on Monday. > > 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 am not sure what you have found out but I will tell you a little secret. No matter what you chose these days your publisher if you have one will convert your document into XML as it is the most convenient format for electronic safekeeping. Just to complete this little write up. I am not oblivious to GUI word processors (which typically store things in Rich Text Format (RTF), a Microsoft take onto the TeX). The only problem with them is that they don't change the fact that people who don't know typographic rules can't become experts on typography just because they can drug text with the mouse and click left and right. That is why I personally use LaTeX (typography built in packages) instead of key-value driven ConTeXt. If you must use word processor you are again in luck with OpenBSD. OpenBSD still has the first open source office suite in its ports tree (Siag) and while I still use SIAG spreadsheet my exposure to Pathetic Writer (PW) is only rudimentary. I heard a good things about Ted from people who like RTF Finally I have tried a numerous lightweight markup languages but only found txt2tags to be useful. Keep in mind that using txt2tags+htmldoc to produce pdf document will produce horrible document as there is no line breaking algorithm equivalent of famous TeX algorithm. Getting nicer output from txt2tags will inevitable lead to embedding so much LaTeX code into your txt2tags that you will start wondering why are you using txt2tags to begin with. Cheers, Predrag Cheers, Predrag > Mich appreciated > > ~ols > -- > Oliver Leaver-Smith > +44(0)114-360-1337 > TZ=Europe/London
Re: Tools for writers
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. 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. The "textproc/heirloom-doctools" port is a serious contender for a top-quality typesetting system (though not recommended as a manual page viewer). In some finer points of typography, it is better than groff; for example, it supports paragraph-at-once filling. But admittedly, groff is more actively maintained, so unless you know exactly why you prefer Heirloom troff, i'd suggest you try groff first. And finally, the only thing that is seriously wrong with the "print/texlive" port is how ridiculously large it is. All the same, i used it often to write journal articles, letters, invoices, and the like, and still use it now and then. 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. 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
Re: Tools for writers
On 2019-11-02 15:54, Marc Chantreux wrote: hello, You can't go wrong with LibreOffice. I've written thousands of pages over the years with it. It may be too "heavy" for some, but for me, if I'm doing something too complex for vi or mousepad, I just fire up LibreOffice. to me there is no such thing that is too complex for the unix documentation toolchain that you can achieve with libreoffice. i feel the other way around: libreoffice is always a bad choice: * when i need a rich good looking document in which you can easily add graphical material of very different nature (music cheets, chemical or math formula, gantt graph, ...), then [your editor of choice] + pandoc + git + latex + tikz + gnuplot + graphviz + m4 is really the best thing i found * if you need interactivity and animation (which isn't my case): the web is there (i personally use pandoc + pug + livescript (to be replaced by elm) + stylus) the only one case where libreoffice is the good choice is if you mind the learning curve but writting a book is a long process, pay the bill at first to be more peaceful later seems to be a good deal to me. regards. marc Fair enough, I have no issue with using the various unix tools for making 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, but I'm lazy and I like some of the more mundane features of LibreOffice like being able to render a document to postscript and then print to the printer I have specified in my /etc/printcap file as well as .docx format support for when 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.
Re: Broadcom firmwares and nvram files
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 reportid 3 not configured hid at ihidev0 reportid 4 not configured hid at ihidev0 reportid 6 not configured hid at ihidev0 reportid 9 not configured "INT33BD" at acpi0 not configured acpibat0 at acpi0: BATC model "SR Real Battery" serial 123456789 type
Re: Tools for writers
hello, > You can't go wrong with LibreOffice. I've written thousands of pages over > the years with it. It may be too "heavy" for some, but for me, if I'm doing > something too complex for vi or mousepad, I just fire up LibreOffice. to me there is no such thing that is too complex for the unix documentation toolchain that you can achieve with libreoffice. i feel the other way around: libreoffice is always a bad choice: * when i need a rich good looking document in which you can easily add graphical material of very different nature (music cheets, chemical or math formula, gantt graph, ...), then [your editor of choice] + pandoc + git + latex + tikz + gnuplot + graphviz + m4 is really the best thing i found * if you need interactivity and animation (which isn't my case): the web is there (i personally use pandoc + pug + livescript (to be replaced by elm) + stylus) the only one case where libreoffice is the good choice is if you mind the learning curve but writting a book is a long process, pay the bill at first to be more peaceful later seems to be a good deal to me. regards. marc
Broadcom firmwares and nvram files
Hi Folks, A friend of mine gave me an Asus X250TA to use as a low-power home server. I don't want to waste any of the two USB2 ports for an USB-Ethernet adaptor, but I'd like to use the integrated wifi module instead. After launching fw_update(1) using an USB tethered connection, the firmware gets installed, but it's apparently lacking a .nvram file. Here's the error I'm getting: $ dmesg | grep brcmbwfm0: failed loadfirmware of file brcmfmac43340-sdio.nvram The nvram(4) man page is not even that helpful in this case. I don't think the OpenBSD philosophy is to throw partially working firmwares in the repos, so I think the problem could be related to something else, but I have no clue what this something else could be. Also, the firmware repository does not contain any .nvram file, which makes me doubteven more that the problem is related to something partially supported. Any ideas? Best regards Stefano
dmesg of OpenBSD 6.6 (GENERIC.MP) on 'Thinkpad R60e (type 9461)'
[not subscribed, please Cc, thanks.]
> OpenBSD 6.6 (GENERIC.MP) #304: Sat Oct 12 11:18:21 MDT 2019
> dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP
> real mem = 3219472384 (3070MB)
> avail mem = 3145039872 (2999MB)
> mpath0 at root
> scsibus0 at mpath0: 256 targets
> mainbus0 at root
> bios0 at mainbus0: date 10/13/06, BIOS32 rev. 0 @ 0xfd690, SMBIOS rev. 2.4 @
> 0xe0010 (68 entries)
> bios0: vendor LENOVO version "7CETB5WW (2.05 )" date 10/13/2006
> bios0: LENOVO 9461DXG
> acpi0 at bios0: ACPI 3.0
> acpi0: sleep states S0 S3 S4 S5
> acpi0: tables DSDT FACP SSDT ECDT TCPA APIC MCFG HPET BOOT SSDT SSDT SSDT SSDT
> acpi0: wakeup devices LID_(S3) SLPB(S3) EXP0(S4) EXP1(S4) EXP2(S4) EXP3(S4)
> PCI1(S4) USB0(S3) USB1(S3) USB2(S3) USB7(S3) HDEF(S4)
> acpitimer0 at acpi0: 3579545 Hz, 24 bits
> acpiec0 at acpi0
> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: Intel(R) Core(TM)2 CPU T5600 @ 1.83GHz ("GenuineIntel" 686-class) 1.83
> GHz, 06-0f-06
> cpu0:
> FPU,V86,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,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,LONG,LAHF,PERF,SENSOR,MELTDOWN
> mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
> cpu0: apic clock running at 166MHz
> cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2, IBE
> cpu1 at mainbus0: apid 1 (application processor)
> cpu1: Intel(R) Core(TM)2 CPU T5600 @ 1.83GHz ("GenuineIntel" 686-class) 1.83
> GHz, 06-0f-06
> cpu1:
> FPU,V86,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,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,LONG,LAHF,PERF,SENSOR,MELTDOWN
> ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins, remapped
> acpimcfg0 at acpi0
> acpimcfg0: addr 0xf000, bus 0-63
> acpihpet0 at acpi0: 14318179 Hz
> acpiprt0 at acpi0: bus 0 (PCI0)
> acpiprt1 at acpi0: bus 1 (AGP_)
> acpiprt2 at acpi0: bus 2 (EXP0)
> acpiprt3 at acpi0: bus 3 (EXP1)
> acpiprt4 at acpi0: bus 4 (EXP2)
> acpiprt5 at acpi0: bus 12 (EXP3)
> acpiprt6 at acpi0: bus 21 (PCI1)
> acpicpu0 at acpi0: !C3(250@17 mwait.3@0x20), !C2(500@1 mwait.1@0x10),
> C1(1000@1 mwait.1), PSS
> acpicpu1 at acpi0: !C3(250@17 mwait.3@0x20), !C2(500@1 mwait.1@0x10),
> C1(1000@1 mwait.1), PSS
> acpipwrres0 at acpi0: PUBS, resource for USB0, USB2, USB7
> acpitz0 at acpi0: critical temperature is 127 degC
> acpitz1 at acpi0: critical temperature is 100 degC
> acpibtn0 at acpi0: LID_
> acpibtn1 at acpi0: SLPB
> "PNP0A08" at acpi0 not configured
> acpicmos0 at acpi0
> acpibat0 at acpi0: BAT0 model "92P1139" serial 5142 type LION oem "Panasonic"
> acpiac0 at acpi0: AC unit online
> acpithinkpad0 at acpi0
> acpidock0 at acpi0: GDCK not docked (0)
> acpivideo0 at acpi0: VID_
> acpivout0 at acpivideo0: LCD0
> acpivideo1 at acpi0: VID_
> acpivout at acpivideo1 not configured
> bios0: ROM list: 0xc/0xfc00 0xd/0x1600 0xd1800/0x1000 0xdc000/0x4000!
> 0xe/0x1!
> cpu0: Enhanced SpeedStep 1829 MHz: speeds: 1833, 1333, 1000 MHz
> pci0 at mainbus0 bus 0: configuration mode 1 (bios)
> pchb0 at pci0 dev 0 function 0 "Intel 82945GM Host" rev 0x03
> ppb0 at pci0 dev 1 function 0 "Intel 82945GM PCIE" rev 0x03: apic 1 int 16
> pci1 at ppb0 bus 1
> radeondrm0 at pci1 dev 0 function 0 "ATI Radeon Mobility X1400" rev 0x00
> drm0 at radeondrm0
> radeondrm0: apic 1 int 16
> azalia0 at pci0 dev 27 function 0 "Intel 82801GB HD Audio" rev 0x02: msi
> azalia0: codecs: Analog Devices AD1981HD, Conexant/0x2bfa, using Analog
> Devices AD1981HD
> audio0 at azalia0
> ppb1 at pci0 dev 28 function 0 "Intel 82801GB PCIE" rev 0x02: apic 1 int 20
> pci2 at ppb1 bus 2
> bge0 at pci2 dev 0 function 0 "Broadcom BCM5751M" rev 0x21, BCM5750 C1
> (0x4201): msi, address XX:CE:NS:OR:ED:XX
> brgphy0 at bge0 phy 1: BCM5750 10/100/1000baseT PHY, rev. 0
> ppb2 at pci0 dev 28 function 1 "Intel 82801GB PCIE" rev 0x02: apic 1 int 21
> pci3 at ppb2 bus 3
> ath0 at pci3 dev 0 function 0 "Atheros AR5212" rev 0x01: apic 1 int 17
> ath0: AR5424 10.3 phy 6.1 rf5424 10.2 eeprom 5.3, WOR2W, address
> XX:CE:NS:OR:ED:XX
> ppb3 at pci0 dev 28 function 2 "Intel 82801GB PCIE" rev 0x02: apic 1 int 22
> pci4 at ppb3 bus 4
> ppb4 at pci0 dev 28 function 3 "Intel 82801GB PCIE" rev 0x02: apic 1 int 23
> pci5 at ppb4 bus 12
> uhci0 at pci0 dev 29 function 0 "Intel 82801GB USB" rev 0x02: apic 1 int 16
> uhci1 at pci0 dev 29 function 1 "Intel 82801GB USB" rev 0x02: apic 1 int 17
> uhci2 at pci0 dev 29 function 2 "Intel 82801GB USB" rev 0x02: apic 1 int 18
> uhci3 at pci0 dev 29 function 3 "Intel 82801GB USB" rev 0x02: apic 1 int 19
> ehci0 at pci0 dev 29 function 7 "Intel 82801GB USB" rev 0x02: apic 1 int 19
> usb0 at ehci0: USB revision 2.0
> uhub0 at usb0 configuration 1 interface 0 "Intel EHCI root hub" rev 2.00/1.00
> addr 1
> ppb5 at pci0 dev 30 function 0 "Intel 82801BAM Hub-to-PCI" rev 0xe2
> pci6 at
dmesg of OpenBSD 6.6 (GENERIC) on 'Thinkpad R60e (type 9461)'
[not subscribed, please Cc, thanks.]
> OpenBSD 6.6 (GENERIC) #298: Sat Oct 12 11:06:10 MDT 2019
> dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
> real mem = 3219472384 (3070MB)
> avail mem = 3145138176 (2999MB)
> mpath0 at root
> scsibus0 at mpath0: 256 targets
> mainbus0 at root
> bios0 at mainbus0: date 10/13/06, BIOS32 rev. 0 @ 0xfd690, SMBIOS rev. 2.4 @
> 0xe0010 (68 entries)
> bios0: vendor LENOVO version "7CETB5WW (2.05 )" date 10/13/2006
> bios0: LENOVO 9461DXG
> acpi0 at bios0: ACPI 3.0
> acpi0: sleep states S0 S3 S4 S5
> acpi0: tables DSDT FACP SSDT ECDT TCPA APIC MCFG HPET BOOT SSDT SSDT SSDT SSDT
> acpi0: wakeup devices LID_(S3) SLPB(S3) EXP0(S4) EXP1(S4) EXP2(S4) EXP3(S4)
> PCI1(S4) USB0(S3) USB1(S3) USB2(S3) USB7(S3) HDEF(S4)
> acpitimer0 at acpi0: 3579545 Hz, 24 bits
> acpiec0 at acpi0
> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: Intel(R) Core(TM)2 CPU T5600 @ 1.83GHz ("GenuineIntel" 686-class) 1.83
> GHz, 06-0f-06
> cpu0:
> FPU,V86,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,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,LONG,LAHF,PERF,SENSOR,MELTDOWN
> mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
> cpu0: apic clock running at 166MHz
> cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2, IBE
> cpu at mainbus0: not configured
> ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins, remapped
> acpimcfg0 at acpi0
> acpimcfg0: addr 0xf000, bus 0-63
> acpihpet0 at acpi0: 14318179 Hz
> acpiprt0 at acpi0: bus 0 (PCI0)
> acpiprt1 at acpi0: bus 1 (AGP_)
> acpiprt2 at acpi0: bus 2 (EXP0)
> acpiprt3 at acpi0: bus 3 (EXP1)
> acpiprt4 at acpi0: bus 4 (EXP2)
> acpiprt5 at acpi0: bus 12 (EXP3)
> acpiprt6 at acpi0: bus 21 (PCI1)
> acpicpu0 at acpi0: !C3(250@17 mwait.3@0x20), !C2(500@1 mwait.1@0x10),
> C1(1000@1 mwait.1), PSS
> acpipwrres0 at acpi0: PUBS, resource for USB0, USB2, USB7
> acpitz0 at acpi0: critical temperature is 127 degC
> acpitz1 at acpi0: critical temperature is 100 degC
> acpibtn0 at acpi0: LID_
> acpibtn1 at acpi0: SLPB
> "PNP0A08" at acpi0 not configured
> acpicmos0 at acpi0
> acpibat0 at acpi0: BAT0 model "92P1139" serial 5142 type LION oem "Panasonic"
> acpiac0 at acpi0: AC unit online
> acpithinkpad0 at acpi0
> acpidock0 at acpi0: GDCK not docked (0)
> acpivideo0 at acpi0: VID_
> acpivout0 at acpivideo0: LCD0
> acpivideo1 at acpi0: VID_
> acpivout at acpivideo1 not configured
> bios0: ROM list: 0xc/0xfc00 0xd/0x1600 0xd1800/0x1000 0xdc000/0x4000!
> 0xe/0x1!
> cpu0: Enhanced SpeedStep 1829 MHz: speeds: 1833, 1333, 1000 MHz
> pci0 at mainbus0 bus 0: configuration mode 1 (bios)
> pchb0 at pci0 dev 0 function 0 "Intel 82945GM Host" rev 0x03
> ppb0 at pci0 dev 1 function 0 "Intel 82945GM PCIE" rev 0x03: apic 1 int 16
> pci1 at ppb0 bus 1
> radeondrm0 at pci1 dev 0 function 0 "ATI Radeon Mobility X1400" rev 0x00
> drm0 at radeondrm0
> radeondrm0: apic 1 int 16
> azalia0 at pci0 dev 27 function 0 "Intel 82801GB HD Audio" rev 0x02: msi
> azalia0: codecs: Analog Devices AD1981HD, Conexant/0x2bfa, using Analog
> Devices AD1981HD
> audio0 at azalia0
> ppb1 at pci0 dev 28 function 0 "Intel 82801GB PCIE" rev 0x02: apic 1 int 20
> pci2 at ppb1 bus 2
> bge0 at pci2 dev 0 function 0 "Broadcom BCM5751M" rev 0x21, BCM5750 C1
> (0x4201): msi, address XX:CE:NS:OR:ED:XX
> brgphy0 at bge0 phy 1: BCM5750 10/100/1000baseT PHY, rev. 0
> ppb2 at pci0 dev 28 function 1 "Intel 82801GB PCIE" rev 0x02: apic 1 int 21
> pci3 at ppb2 bus 3
> ath0 at pci3 dev 0 function 0 "Atheros AR5212" rev 0x01: apic 1 int 17
> ath0: AR5424 10.3 phy 6.1 rf5424 10.2 eeprom 5.3, WOR2W, address
> XX:CE:NS:OR:ED:XX
> ppb3 at pci0 dev 28 function 2 "Intel 82801GB PCIE" rev 0x02: apic 1 int 22
> pci4 at ppb3 bus 4
> ppb4 at pci0 dev 28 function 3 "Intel 82801GB PCIE" rev 0x02: apic 1 int 23
> pci5 at ppb4 bus 12
> uhci0 at pci0 dev 29 function 0 "Intel 82801GB USB" rev 0x02: apic 1 int 16
> uhci1 at pci0 dev 29 function 1 "Intel 82801GB USB" rev 0x02: apic 1 int 17
> uhci2 at pci0 dev 29 function 2 "Intel 82801GB USB" rev 0x02: apic 1 int 18
> uhci3 at pci0 dev 29 function 3 "Intel 82801GB USB" rev 0x02: apic 1 int 19
> ehci0 at pci0 dev 29 function 7 "Intel 82801GB USB" rev 0x02: apic 1 int 19
> usb0 at ehci0: USB revision 2.0
> uhub0 at usb0 configuration 1 interface 0 "Intel EHCI root hub" rev 2.00/1.00
> addr 1
> ppb5 at pci0 dev 30 function 0 "Intel 82801BAM Hub-to-PCI" rev 0xe2
> pci6 at ppb5 bus 21
> cbb0 at pci6 dev 0 function 0 "TI PCIXX12 CardBus" rev 0x00: apic 1 int 16
> "TI PCIXX12 FireWire" rev 0x00 at pci6 dev 0 function 1 not configured
> cardslot0 at cbb0 slot 0 flags 0
> cardbus0 at cardslot0: bus 22 device 0 cacheline 0x8, lattimer 0xb0
> pcmcia0 at cardslot0
> ichpcib0 at pci0 dev 31 function 0 "Intel 82801GBM LPC" rev 0x02: PM disabled
> pciide0 at pci0 dev 31 function 1 "Intel 82801GB IDE" rev 0x02: DMA,
Thinkpad R40 varia (1)
[not subscribed, please Cc, thanks.] Me's retiring the R40 in its current capacity, so let me wind up a couple of things: There was nothing wrong with the CMOS battery; the seller gave me the impression that the machine had been used recently, but menow suspects that quite not to be the case, hence me confusion. The general battery, which is an original, still lasts about an hour despite its age. Mefound this out 'cause at one point it got unplugged by accident, by a family member, shortly after a call from nature ensured me momentary absence. In the midst of the summer heat, the hdd got sick and had to be replaced with a spare, which is now also breaking down (granted, both hdds are about equally old...). It appears characteristic even of the 'new' R60e to be inadequate at cooling the hdd; merecommends a cooling pad when not underway. (A metal desk may also be effective as a workaround, but one does not always have that luxury.) The USB sockets continue to provide power when the machine is otherwise off; given the above, this is a good thing(tm). While lacking any of the 'windoze' or menu keys, the card keys have been useful to provide me with 24 virtual terminals (courtesy of me own wscons(4) patches; see tech@). Menever got the ipw(4) to work, but the seller (who ran windoze...) warned me of that before the sale, so mefigures it's a hardware problem. The R40 will now be used for odds and ends only, but it has certainly served me well. --zeurkous. -- Friggin' Machines!
Re: Tools for writers
You might try lyx. This is a front end for latex. You can write without worrying about formatting and come back to that later. Also, when you do the formatting, you don't have to worry about niggling details as in word and its clones. Just declare chapters, sections, etc. Lyx is an OpenBSD package. Dave Raymond On 11/2/19, Jordan Geoghegan wrote: > > On 2019-11-02 13:18, Chris Bennett wrote: >> On Sat, Nov 02, 2019 at 03:16:22PM -0400, STeve Andre' wrote: >>> >>> On 2019-11-02 15:07, Antoine Jacoutot wrote: 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. >>> >>> --STeve Andre' >>> >>> >> Actually the OP said that not necessarily the same application. >> I have to agree that writing the content and doing the formatting to be >> two separate processes. I write in a furious stream of conciousness. >> Looking at the formatting, etc. just impedes my work. >> Spout out the thoughts. Then review content. Then work on formatting and >> editing content. >> >> /bin/ed >> >> Then do the delicate work of editing and formatting after the creative >> stream ends. Or creativity may be lost. Forever. Over seeing some >> misspelled word or wrong punctuation. >> >> Two or three different tools. Since there are really about three >> processes being done that are quite different. For me, multitasking >> sucks. >> >> But, please, what is good for formatting? I don't have an answer for >> that myself. I am considering writing as a new direction for myself. >> Getting old sucks. >> >> Chris Bennett >> > > You can't go wrong with LibreOffice. I've written thousands of pages > over the years with it. It may be too "heavy" for some, but for me, if > I'm doing something too complex for vi or mousepad, I just fire up > LibreOffice. > > -- David J. Raymond david.raym...@nmt.edu http://physics.nmt.edu/~raymond
Re: Tools for writers
On 2019-11-02 13:18, Chris Bennett wrote: On Sat, Nov 02, 2019 at 03:16:22PM -0400, STeve Andre' wrote: On 2019-11-02 15:07, Antoine Jacoutot wrote: 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. --STeve Andre' Actually the OP said that not necessarily the same application. I have to agree that writing the content and doing the formatting to be two separate processes. I write in a furious stream of conciousness. Looking at the formatting, etc. just impedes my work. Spout out the thoughts. Then review content. Then work on formatting and editing content. /bin/ed Then do the delicate work of editing and formatting after the creative stream ends. Or creativity may be lost. Forever. Over seeing some misspelled word or wrong punctuation. Two or three different tools. Since there are really about three processes being done that are quite different. For me, multitasking sucks. But, please, what is good for formatting? I don't have an answer for that myself. I am considering writing as a new direction for myself. Getting old sucks. Chris Bennett You can't go wrong with LibreOffice. I've written thousands of pages over the years with it. It may be too "heavy" for some, but for me, if I'm doing something too complex for vi or mousepad, I just fire up LibreOffice.
Re: Skype alternatives for OpenBSD
On Sat, Nov 02, 2019 at 10:35:36PM +0100, 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. --Kind regards,Jonathan It depends what you need for your online classes. Regular video should "just work". For anything else (real video conferencing), use something else; interactive real time audio / video is crap; it doesn't work in the real world. -- Antoine
Re: Skype alternatives for OpenBSD
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. On 2019-11-02 14:35, 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. --Kind regards,Jonathan
Skype alternatives for OpenBSD
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. --Kind regards,Jonathan
dmesg of OpenBSD 6.6 (RAMDISK_CD) on 'Thinkpad R60e (type 9461)'
[not subscribed, please Cc, thanks.]
> OpenBSD 6.6 (RAMDISK_CD) #294: Sat Oct 12 11:29:03 MDT 2019
> dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/RAMDISK_CD
> real mem = 3219439616 (3070MB)
> avail mem = 3151642624 (3005MB)
> mainbus0 at root
> bios0 at mainbus0: date 10/13/06, BIOS32 rev. 0 @ 0xfd690, SMBIOS rev. 2.4 @
> 0xe0010 (68 entries)
> bios0: vendor LENOVO version "7CETB5WW (2.05 )" date 10/13/2006
> bios0: LENOVO 9461DXG
> acpi0 at bios0: ACPI 3.0
> acpi0: tables DSDT FACP SSDT ECDT TCPA APIC MCFG HPET BOOT SSDT SSDT SSDT SSDT
> acpiec0 at acpi0
> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: Intel(R) Core(TM)2 CPU T5600 @ 1.83GHz ("GenuineIntel" 686-class) 1.83
> GHz, 06-0f-06
> cpu0:
> FPU,V86,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,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,LONG,LAHF,PERF,SENSOR,MELTDOWN
> cpu0: apic clock running at 166MHz
> cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2, IBE
> cpu at mainbus0: not configured
> ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins, remapped
> acpiprt0 at acpi0: bus 0 (PCI0)
> acpiprt1 at acpi0: bus 1 (AGP_)
> acpiprt2 at acpi0: bus 2 (EXP0)
> acpiprt3 at acpi0: bus 3 (EXP1)
> acpiprt4 at acpi0: bus 4 (EXP2)
> acpiprt5 at acpi0: bus 12 (EXP3)
> acpiprt6 at acpi0: bus 21 (PCI1)
> acpicpu at acpi0 not configured
> acpipwrres at acpi0 not configured
> acpitz at acpi0 not configured
> acpitz at acpi0 not configured
> "PNP0C0D" at acpi0 not configured
> "PNP0C0E" at acpi0 not configured
> "PNP0A08" at acpi0 not configured
> acpicmos0 at acpi0
> "PNP0C0A" at acpi0 not configured
> "ACPI0003" at acpi0 not configured
> "IBM0068" at acpi0 not configured
> bios0: ROM list: 0xc/0xfc00 0xd/0x1600 0xd1800/0x1000 0xdc000/0x4000!
> 0xe/0x1!
> pci0 at mainbus0 bus 0: configuration mode 1 (bios)
> pchb0 at pci0 dev 0 function 0 "Intel 82945GM Host" rev 0x03
> ppb0 at pci0 dev 1 function 0 "Intel 82945GM PCIE" rev 0x03: apic 1 int 16
> pci1 at ppb0 bus 1
> vga1 at pci1 dev 0 function 0 "ATI Radeon Mobility X1400" rev 0x00
> wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
> "Intel 82801GB HD Audio" rev 0x02 at pci0 dev 27 function 0 not configured
> ppb1 at pci0 dev 28 function 0 "Intel 82801GB PCIE" rev 0x02: apic 1 int 20
> pci2 at ppb1 bus 2
> bge0 at pci2 dev 0 function 0 "Broadcom BCM5751M" rev 0x21, BCM5750 C1
> (0x4201): msi, address XX:CE:NS:OR:ED:XX
> brgphy0 at bge0 phy 1: BCM5750 10/100/1000baseT PHY, rev. 0
> ppb2 at pci0 dev 28 function 1 "Intel 82801GB PCIE" rev 0x02: apic 1 int 21
> pci3 at ppb2 bus 3
> ath0 at pci3 dev 0 function 0 "Atheros AR5212" rev 0x01: apic 1 int 17
> ath0: AR5424 10.3 phy 6.1 rf5424 10.2 eeprom 5.3, WOR2W, address
> XX:CE:NS:OR:ED:XX
> ppb3 at pci0 dev 28 function 2 "Intel 82801GB PCIE" rev 0x02: apic 1 int 22
> pci4 at ppb3 bus 4
> ppb4 at pci0 dev 28 function 3 "Intel 82801GB PCIE" rev 0x02: apic 1 int 23
> pci5 at ppb4 bus 12
> uhci0 at pci0 dev 29 function 0 "Intel 82801GB USB" rev 0x02: apic 1 int 16
> uhci1 at pci0 dev 29 function 1 "Intel 82801GB USB" rev 0x02: apic 1 int 17
> uhci2 at pci0 dev 29 function 2 "Intel 82801GB USB" rev 0x02: apic 1 int 18
> uhci3 at pci0 dev 29 function 3 "Intel 82801GB USB" rev 0x02: apic 1 int 19
> ehci0 at pci0 dev 29 function 7 "Intel 82801GB USB" rev 0x02: apic 1 int 19
> usb0 at ehci0: USB revision 2.0
> uhub0 at usb0 configuration 1 interface 0 "Intel EHCI root hub" rev 2.00/1.00
> addr 1
> ppb5 at pci0 dev 30 function 0 "Intel 82801BAM Hub-to-PCI" rev 0xe2
> pci6 at ppb5 bus 21
> cbb0 at pci6 dev 0 function 0 "TI PCIXX12 CardBus" rev 0x00: apic 1 int 16
> "TI PCIXX12 FireWire" rev 0x00 at pci6 dev 0 function 1 not configured
> cardslot0 at cbb0 slot 0 flags 0
> cardbus0 at cardslot0: bus 22 device 0 cacheline 0x8, lattimer 0xb0
> pcmcia0 at cardslot0
> pcib0 at pci0 dev 31 function 0 "Intel 82801GBM LPC" rev 0x02
> pciide0 at pci0 dev 31 function 1 "Intel 82801GB IDE" rev 0x02: DMA, channel
> 0 configured to compatibility, channel 1 configured to compatibility
> atapiscsi0 at pciide0 channel 0 drive 0
> scsibus0 at atapiscsi0: 2 targets
> cd0 at scsibus0 targ 0 lun 0: removable
> cd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2
> pciide0: channel 1 ignored (disabled)
> ahci0 at pci0 dev 31 function 2 "Intel 82801GBM AHCI" rev 0x02: msi, AHCI 1.1
> ahci0: port 0: 1.5Gb/s
> scsibus1 at ahci0: 32 targets
> sd0 at scsibus1 targ 0 lun 0:
> naa.CENSOREDCENSORED
> sd0: 305245MB, 512 bytes/sector, 625142448 sectors
> "Intel 82801GB SMBus" rev 0x02 at pci0 dev 31 function 3 not configured
> usb1 at uhci0: USB revision 1.0
> uhub1 at usb1 configuration 1 interface 0 "Intel UHCI root hub" rev 1.00/1.00
> addr 1
> usb2 at uhci1: USB revision 1.0
> uhub2 at usb2 configuration 1 interface 0 "Intel UHCI root hub" rev 1.00/1.00
> addr 1
> usb3 at uhci2: USB revision 1.0
> uhub3 at
Re: Tools for writers
>>> On 2 Nov 2019, at 19:17, 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: /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. >> >> --STeve Andre' > > I’m inclined to agree with you STeve. For the “writing words in a document” > part, nothing beats a distraction-free experience that vi provides. For > avoidance of doubt, my query was more around supporting the writing process > (outlining, character development) and the formatting (like you say, an after > thought most often) > > ~ols > -- > Oliver Leaver-Smith > +44(0)114-360-1337 > TZ=Europe/London
Re: OpenBSD and solid state disks
[...] > 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? I'm certainly not one to reply to this question on the raw metal/filesystem level, but I can assure you that I have used OpenBSD on SSDs (in different computers) for several years by now without noticing any of the scares that circulate about SSDs (those seem to be mainly filesystem corruption and/or significant slowdown). Some of the concerns may simply go back to early generations of SSD drives. I recall that tedu@ discussed SSDs and these matters on his flak blog previously that may contain more details and possibly reassurance for you. Mounting with softdep seems to be advisable. I'm happy to be complemented or corrected by someone with more in-depth knowledge of the low-level aspects of SSDs.
Re: Tools for writers
On Sat, Nov 02, 2019 at 03:16:22PM -0400, STeve Andre' wrote: > > > On 2019-11-02 15:07, Antoine Jacoutot wrote: > > 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. > > --STeve Andre' > > Actually the OP said that not necessarily the same application. I have to agree that writing the content and doing the formatting to be two separate processes. I write in a furious stream of conciousness. Looking at the formatting, etc. just impedes my work. Spout out the thoughts. Then review content. Then work on formatting and editing content. /bin/ed Then do the delicate work of editing and formatting after the creative stream ends. Or creativity may be lost. Forever. Over seeing some misspelled word or wrong punctuation. Two or three different tools. Since there are really about three processes being done that are quite different. For me, multitasking sucks. But, please, what is good for formatting? I don't have an answer for that myself. I am considering writing as a new direction for myself. Getting old sucks. Chris Bennett
OpenBSD and solid state disks
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 -- David J. Raymond david.raym...@nmt.edu http://physics.nmt.edu/~raymond
Re: Tools for writers
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. --STeve Andre'
Re: Tools for writers
> 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) > Hi, Not sure for plot and characters. I would recommend txt2tags [1], txtproc/txt2tags in ports. There is also a more up-to-date version written in python3 (2], both works fine. It can convert txt2tags syntax in different formats, such as html or tex (useful to get nice PDF). The most interesting imho are : - ``postproc`` and ``preproc`` instruction. Sort of ``#define`` in C or ``\newcommand`` in LaTeX. Very useful. - ``include``. Also available in LaTeX. Have a look at [3] for an example. One might do markdown + sed + Makefile for the same result. Using txt2tags, I wrote a ≈350 pages book in PDF [4] and maintain it for a little more than two years now, very happy with txt2tags. If txt2tags is not enough, then LaTeX is great, but requires to learn a lot more to use it correctly. Regards. [1]: https://txt2tags.org/ [2]: https://github.com/jendrikseipp/txt2tags [3]: https://framagit.org/prx/auto-hebergement-openbsd/blob/master/src/auto-hebergement-openbsd.t2t [4]: https://ybad.name/ah/ -- prx
Re: Tools for writers
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. -- Antoine
Re: Tools for writers
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
new rust-libtls crates
Hi, a bit off-topic, but a Rust-LibreSSL crossover: It seems that many people have written Rust crates for libtls. And most (or all) of them haven't been updated for years. I talked to the owner of libtls and libtls-sys and he assigned ownership of his libtls crates to me. Yesterday I published a complete and API-incompatible rewrite of the crates, under the ISC license. I'm trying to find a compromise between a close adaption of the libtls API and a modern Rust way to implement such an API. https://crates.io/crates/libtls I'm working on additional code for async I/O with tokio and/or async/await. Async client/server already works but I'm tweaking the code to a) clean it up and b) adjust it to the future with the new "futures" API ;) Why libtls? Because it is a sane TLS API with secure defaults. I trust the decisions of the LibreSSL developers and libtls provides some the best defaults. The code works on OpenBSD and Linux. Many distributions such as Ubuntu don't seem to provide LibreSSL packages, so the very nice libtls API is not available for them. My crate tries to download, build, and link LibreSSL statically if it is not found. (I wonder if anyone has ever looked into packaging just libtls for Ubuntu/Debian independently. This would even help portability of our OpenBSD daemons.) Reyk
Re: Tools for writers
Mr. Hansteen what are your thoughts on Texlive? On Sat, Nov 2, 2019 at 9:16 AM Peter Nicolai Mathias Hansteen < pe...@bsdly.net> 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. > > — > Peter N. M. Hansteen, member of the first RFC 1149 implementation team > http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/ > "Remember to set the evil bit on all malicious network traffic" > delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds. > > > > >
Re: Tools for writers
> 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. — Peter N. M. Hansteen, member of the first RFC 1149 implementation team http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/ "Remember to set the evil bit on all malicious network traffic" delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
Tools for writers
For me OpenOffice works and of Focus Writer. I “won” NaNoWriMo using focus writer. On Saturday, November 2, 2019, 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 >
Tools for writers
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: Redraw of terminal change in 6.6?
On Sat, Nov 02, 2019 at 08:32:50AM +0100, Mischa wrote: > Hi All, > > Not sure if this is on my side, setting, or if something has changed with > tmux or top redrawing of the terminal. > I am using tmux, over mosh, on one of my jump hosts to connect to other > hosts. In some of the windows I have a remote top -C running. > When I am attaching the tmux session on a smaller display, for example my > phone, the output of top is fine. > > However when I connect back with a larger display the output of top is > completely garbled. It does recover line by line when processes jump to a > different “rank”. > > Below are two screenshots with roughly 5 minutes between them. > Anything I can test? Change? Do? > > Thanx!! > > Mischa > Hi, Same issue here since upgrading from 6.5 to 6.6. I don't use mosh, but connect via SSH to a remote machine and attaching to tmux running irssi. It is attached to a shared session. The first attached resolution/window size is bigger. Maybe it is fixed already: https://cvsweb.openbsd.org/src/usr.bin/tmux/server-client.c rev 1.296 -- Kind regards, Hiltjo
Courier-Imap no longer accepts ssl connections after update to -current
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. 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
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: Saturday, November 02, 2019 4:12 AM > To: misc@openbsd.org > Subject: Re: Following current - pkg_add update forward depedencies > don't match question > > On 2019-11-01, Theodore Wynnychenko wrote: > > Hello > > > > I just updated a system to current the other day. > > > > OpenBSD 6.6 GENERIC.MP#411 amd64 > > > > The last time I updated was probably 2-3 months ago. > > > > Anyway, when I went to updated packages (also following > current/snapshots), > > I got a number of "forward dependencies - don't match" notices and > the > > packages don't update. > > What command are you running to update? > > The "don't match" are expected but (at least with "pkg_add -u" without > restricting to a subset of packages) it shouldn't stop packages from > updating anyway. > > Can you show the pkg_add command line you're using and complete output? > i.e. run it under script(1) and send the typescript. > > This doesn't match "probably 2-3 months ago", php 5.6 and the > associated > pecl packages were removed before 6.5, and php-7.1.27 was from > somewhere > between 6.4 and 6.5. Not that this matters in itself, an update over > that time period would still be expected to work, but if you're > going to be updating infrequently you should definitely stick to > releases+syspatch rather than -current. > Sorry, it was probably longer than "2-3 months." Life got in the way. I should do better going forward, and I understand that going "back" to release from current can be problematic. In any case, I wanted to describe my "experience" with this issue. I will try to be brief. Yesterday afternoon, I noticed that the timestamps for packages had updated. So, I tried again (on another system where "breaking" is less consequential). I decided to just try updating gettext, so (this is the full output on that system): # PKG_PATH=https://ftp.openbsd.org/pub/OpenBSD/snapshots/packages/amd64/ pkg_add -u -Dsnap gettext quirks-3.184 signed on 2019-11-01T17:28:51Z .libs1-gettext-0.19.4p0+gettext-0.19.8.1p3->gettext-runtime-0.20.1p0 forward dependencies: | Dependencies of python-2.7.16 on gettext-* don't match | Dependencies of python-3.6.8p0 on gettext-* don't match | Dependencies of libidn-1.35 on gettext-* don't match | Dependencies of glib2-2.58.3p8 on gettext-* don't match | Dependencies of wget-1.20.2 on gettext-* don't match | Dependencies of libpsl-0.20.2 on gettext-* don't match | Dependencies of libgpg-error-1.36 on gettext-* don't match | Dependencies of monitoring-plugins-2.2p7 on gettext-* don't match Merging python-2.7.16->2.7.16p1 (ok) NOT MERGING: can't find update for [python-3.6.8p0] (ok) Merging libidn-1.35->1.35p0 (ok) Merging glib2-2.58.3p8->2.60.7 (ok) Merging wget-1.20.2->1.20.3p1 (ok) Merging libpsl-0.20.2->0.20.2p0 (ok) Merging libgpg-error-1.36->1.36p0 (ok) Merging monitoring-plugins-2.2p7->2.2p8 (ok) Proceed with update anyway ? [y/N/a] y Detected loop, merging sets ok | python-3.7.5 | .libs1-gettext-0.19.4p0+gettext-0.19.8.1p3+glib2-2.58.3p8+libgpg-error-1.36+ libidn-1.35+libpsl-0.20.2+monitoring-plugins-2.2p7+python-2.7.16+wget-1.20.2 ->gettext-runtime-0.20.1p0+glib2-2.60.7+libgpg-error-1.36p0+libidn-1.35p0+li bpsl-0.20.2p0+monitoring-plugins-2.2p8+python-2.7.16p1+wget-1.20.3p1 [python-3.6.8p0].libs-glib2-2.56.1+.libs-libidn-1.34+.libs-libpsl-0.7.1p1+.l ibs1-gettext-0.19.4p0+gettext-0.19.8.1p3+glib2-2.58.3p8+libgpg-error-1.36+li bidn-1.35+libpsl-0.20.2+monitoring-plugins-2.2p7+python-2.7.16+wget-1.20.2-> gettext-runtime-0.20.1p0+glib2-2.60.7+libgpg-error-1.36p0+libidn-1.35p0+libp sl-0.20.2p0+monitoring-plugins-2.2p8+python-2.7.16p1+python-3.7.5+wget-1.20. 3p1 forward dependencies: | Dependencies of python-3.6.8p0 on gettext-* don't match Proceed with update anyway ? [y/N/a] y Can't install [python-3.6.8p0].libs-glib2-2.56.1+.libs-libidn-1.34+.libs-libpsl-0.7.1p1+.l ibs1-gettext-0.19.4p0+gettext-0.19.8.1p3+glib2-2.58.3p8+libgpg-error-1.36+li bidn-1.35+libpsl-0.20.2+monitoring-plugins-2.2p7+python-2.7.16+wget-1.20.2-> gettext-runtime-0.20.1p0+glib2-2.60.7+libgpg-error-1.36p0+libidn-1.35p0+libp sl-0.20.2p0+monitoring-plugins-2.2p8+python-2.7.16p1+python-3.7.5+wget-1.20. 3p1: can't resolve gettext-* Couldn't find updates for .libs-glib2-2.56.1 .libs-libidn-1.34 .libs-libpsl-0.7.1p1 .libs1-gettext-0.19.4p0 gettext-0.19.8.1p3 glib2-2.58.3p8 libgpg-error-1.36 libidn-1.35 libpsl-0.20.2 monitoring-plugins-2.2p7 python-2.7.16 wget-1.20.2 Couldn't install gettext-runtime-0.20.1p0 glib2-2.60.7 libgpg-error-1.36p0 libidn-1.35p0 libpsl-0.20.2p0 monitoring-plugins-2.2p8 python-2.7.16p1 python-3.7.5 wget-1.20.3p1 -- 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"
Re: rspamd stop rc script doesn't work in OpenBSD 6.6
On 2019-10-29, List wrote: > I think what causes the problem is rspamd which uses JITs. These JITS > break W^X. If you enable rspamd etc on boot by (rcctl enable ...). And > reboot.. This is incorrect. rspamd uses luajit (on arches where it's available), but it is not a requirement that every JIT compiler makes W+X mappings - in particular luajit *does* work with W^X.
Re: Following current - pkg_add update forward depedencies don't match question
On 2019/11/02 05:04, Chris Bennett wrote: > On Sat, Nov 02, 2019 at 09:24:05AM -, Stuart Henderson wrote: > > On 2019-11-01, Chris Bennett wrote: > > > NO. You need to use pkg_add -u -Dsnap. > > > > Normally when pkg_add doesn't have a full path to the package directory > > (e.g. PKG_PATH=http://mirror/pub/OpenBSD/6.6/packages/amd64/) > > it constructs it from a hostname in PKG_PATH or a partial path in > > /etc/installurl. To do that it has to add e.g. 6.6/packages/amd64 > > to the partial path. > > > > It decides whether to use 6.6/ (or other version number) or snapshots/ > > based on whether the current version is a snapshot or not (from the > > "sysctl kern.version" output). > > > > All that -Dsnap does is say "use snapshots/ even if this looks like > > it's a release (no suffix after "6.6"). You only ever need it if you're > > a) running snapshota and b) are in the brief period in the run-up to > > release where the version number has no suffix. > > > > > Occasionally you might need to use sysupgrade -s. That happened to me > > > from one -current to another. > > > > sysupgrade -s is sysupgrade's equivalent to pkg_add -Dsnap. So again you > > would only ever need it directly in the run-up to release. > > > > > > This happened to me with a snapshot from before -release and getting a > snapshot right after -release. Perhaps this should be mentioned in man > sysupgrade(8)? The error message ftp something was not intuitive. > sysupgrade -s is logical and reasonable, but wasn't at all obvious from > the error message. I have had the same error message when a connection > was a problem. > In any case, I was able to fix the problem. > > Thanks, > Chris Bennett > > The error message is better now (post-6.6) though there is still some room for improvement (can't currently move from "6.6-beta" to "6.6" via sysupgrade without hacking the script slightly). Getting the amount of documentation right is a bit of a balancing act, it could be written in more explicit detail, but it makes the doc more complex for something which is only needed over a ~10 day period.
Re: Following current - pkg_add update forward depedencies don't match question
On Sat, Nov 02, 2019 at 09:24:05AM -, Stuart Henderson wrote: > On 2019-11-01, Chris Bennett wrote: > > NO. You need to use pkg_add -u -Dsnap. > > Normally when pkg_add doesn't have a full path to the package directory > (e.g. PKG_PATH=http://mirror/pub/OpenBSD/6.6/packages/amd64/) > it constructs it from a hostname in PKG_PATH or a partial path in > /etc/installurl. To do that it has to add e.g. 6.6/packages/amd64 > to the partial path. > > It decides whether to use 6.6/ (or other version number) or snapshots/ > based on whether the current version is a snapshot or not (from the > "sysctl kern.version" output). > > All that -Dsnap does is say "use snapshots/ even if this looks like > it's a release (no suffix after "6.6"). You only ever need it if you're > a) running snapshota and b) are in the brief period in the run-up to > release where the version number has no suffix. > > > Occasionally you might need to use sysupgrade -s. That happened to me > > from one -current to another. > > sysupgrade -s is sysupgrade's equivalent to pkg_add -Dsnap. So again you > would only ever need it directly in the run-up to release. > > This happened to me with a snapshot from before -release and getting a snapshot right after -release. Perhaps this should be mentioned in man sysupgrade(8)? The error message ftp something was not intuitive. sysupgrade -s is logical and reasonable, but wasn't at all obvious from the error message. I have had the same error message when a connection was a problem. In any case, I was able to fix the problem. Thanks, Chris Bennett
Re: Following current - pkg_add update forward depedencies don't match question
On 2019-11-01, Chris Bennett wrote: > NO. You need to use pkg_add -u -Dsnap. Normally when pkg_add doesn't have a full path to the package directory (e.g. PKG_PATH=http://mirror/pub/OpenBSD/6.6/packages/amd64/) it constructs it from a hostname in PKG_PATH or a partial path in /etc/installurl. To do that it has to add e.g. 6.6/packages/amd64 to the partial path. It decides whether to use 6.6/ (or other version number) or snapshots/ based on whether the current version is a snapshot or not (from the "sysctl kern.version" output). All that -Dsnap does is say "use snapshots/ even if this looks like it's a release (no suffix after "6.6"). You only ever need it if you're a) running snapshota and b) are in the brief period in the run-up to release where the version number has no suffix. > Occasionally you might need to use sysupgrade -s. That happened to me > from one -current to another. sysupgrade -s is sysupgrade's equivalent to pkg_add -Dsnap. So again you would only ever need it directly in the run-up to release.
Re: Following current - pkg_add update forward depedencies don't match question
On 2019-11-01, Theodore Wynnychenko wrote: > Hello > > I just updated a system to current the other day. > > OpenBSD 6.6 GENERIC.MP#411 amd64 > > The last time I updated was probably 2-3 months ago. > > Anyway, when I went to updated packages (also following current/snapshots), > I got a number of "forward dependencies - don't match" notices and the > packages don't update. What command are you running to update? The "don't match" are expected but (at least with "pkg_add -u" without restricting to a subset of packages) it shouldn't stop packages from updating anyway. Can you show the pkg_add command line you're using and complete output? i.e. run it under script(1) and send the typescript. > For example: > > gettext-0.19.8.1p3->gettext-runtime-0.20.1p0 forward dependencies: >| Dependencies of php-apache-7.1.27p0 on gettext-* don't match >| Dependencies of gnupg-1.4.23p1 on gettext-* don't match >| Dependencies of glib2-2.58.3p8 on gettext-* don't match >| Dependencies of courier-imap-4.18.2p0 on gettext-* don't match >| Dependencies of e2fsprogs-1.42.12p4 on gettext-* don't match >| Dependencies of libgpg-error-1.36 on gettext-* don't match >| Dependencies of python-3.6.8p0 on gettext-* don't match >| Dependencies of samba-4.8.9 on gettext-* don't match >| Dependencies of gdbm-1.16 on gettext-* don't match >| Dependencies of popt-1.16p1 on gettext-* don't match >| Dependencies of aspell-0.60.6.1p8 on gettext-* don't match >| Dependencies of libpsl-0.20.2 on gettext-* don't match >| Dependencies of wget-1.20.2 on gettext-* don't match >| Dependencies of php-7.1.27 on gettext-* don't match >| Dependencies of libidn-1.35 on gettext-* don't match >| Dependencies of monitoring-plugins-2.2p7 on gettext-* don't match >| Dependencies of python-2.7.16 on gettext-* don't match >| Dependencies of courier-authlib-0.68.0p4 on gettext-* don't match >| Dependencies of fetchmail-6.3.26p2 on gettext-* don't match >| Dependencies of pecl56-pecl_http-2.5.6p3 on gettext-* don't match >| Dependencies of p11-kit-0.23.15p0 on gettext-* don't match This doesn't match "probably 2-3 months ago", php 5.6 and the associated pecl packages were removed before 6.5, and php-7.1.27 was from somewhere between 6.4 and 6.5. Not that this matters in itself, an update over that time period would still be expected to work, but if you're going to be updating infrequently you should definitely stick to releases+syspatch rather than -current. > Or (another example), with similar notices about forward dependencies not > matching: > # pkg_info | grep php-7 > php-7.1.27 server-side HTML-embedded scripting language > > And the mirror shows: > php-7.1.32.tgz > > I see that I can "force" the update with "pkg_add -u -D updatedepends". > > It seems like this should be safe to do, but it's not something I have done > before. > > While my system isn't "production" for a large multi-national, I do use it > as a file server and stuff, and it is working right now, and I don't want to > make it not work. > > So, before I did this, I was wondering if there was anything I should > consider/do to address this issue, other than just "forcing" the update? > > I guess, when at its core, I don't really completely understand what the > notice means, and how and why it happened. It means that you have a group of packages that all depend on a specific version of another package, so all must be updated in a single set rather than individually.
Re: LDAP tls: handshake failure
Hi Pedrag,
On Sat, 02 Nov 2019 05:45:08 +0100,
Predrag Punosevac wrote:
>
> Martijn van Duren wrote:
>
> > On 10/24/19 2:25 PM, Claudio Jeker wrote:
> > >
> > > OK claudio@
> > >
> > I'll commit this soon-ish based on claudio's OK, but if at all
> > possible I would like to ask the people affected by this to test this
> > and see if this solves their problem.
>
> I did this on the pair of LDAP servers atlas and titan to make sure I
> can reproduce results.
>
> atlas# uname -a
> OpenBSD atlas.int.autonlab.org 6.6 GENERIC.MP#0 amd64
> atlas# syspatch -l
> 001_bpf
> 002_ber
> 003_bgpd
> atlas# rcctl restart ldapd
> ldapd(ok)
> ldapd(ok)
> atlas# ldapvi -ZZ
> ldap_start_tls_s: Protocol error (2)
>
>
> # Getting source code
>
> atlas# cvs -qd anon...@anoncvs.ca.openbsd.org:/cvs checkout -rOPENBSD_6_6 -P
> src
> atlas# cvs -q up -Pd -rOPENBSD_6_6
>
> atlas# make clean
> atlas# make obj
> atlas# make
> atlas# make install
>
> #atlas rcctl restart ldapd
> ldapd(ok)
> ldapd(ok)
> atlas# ldapvi -ZZ
> ldap_start_tls_s: Protocol error (2)
>
> Upon close inspection I see that cvs is pulling the revision 1.31.2.1
>
> https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/usr.sbin/ldapd/ldape.c?r1=1.33
> which is the same as the binary patch I already installed.
>
>
> Manually fetching revision 1.33 which I am guessing is going to current.
> and rebuilding the daemon
>
> ldapvi -ZZ
>
> is now sucessful.
>
> So for me personally version 1.33 of ldape.c works. This is the
> difference between 1.31.2.1 which can be obtained as a binary patch and
> the version 1.33
>
> atlas# diff ldape.c.v.1.31.2.1 ldape.c.v.1.33
> 1c1
> < /*$OpenBSD: ldape.c,v 1.31.2.1 2019/10/27 20:05:13 tb Exp $ */
> ---
> > /*$OpenBSD: ldape.c,v 1.33 2019/10/26 17:52:55 martijn Exp $ */
> 301d300
> < struct ber_element *ext_val = NULL;
> 310c309
> < if (ober_scanf_elements(req->op, "{se", , _val) != 0)
> ---
> > if (ober_scanf_elements(req->op, "{s", ) != 0)
> 314c313
> < req->op = ext_val;
> ---
> > req->op = req->op->be_sub->be_next;
the patch is only in -current / snapshots, but not in -stable
Best regards
Robert
