JdeBP

This is specifically for the command-line and system tools stuff, including #nosh and #djbwares.

For anything else, including general computer programming, the non-politics account is @JdeBP and the politics account is @JdeBP. #senryu and #SlowLife tasks are at @JdeBP.

Last Notes

2026-05-23 07:03:31 GMT

- reply

@nprofile…qxrs
It's a shame that #Slackware is like every other Linux distribution and only packages #nvi and not #nvi2.
Nonetheless, you might want to cross-reference what you have against the nvi2 version of the manual, which expanded the descriptions of and clarified some existing things.
https://man.freebsd.org/cgi/man.cgi?query=nvi
https://man.dragonflybsd.org/?command=nvi
#vi #elvis

2026-05-14 00:24:26 GMT

I decided to make that list anyway.
http://jdebp.info/FGA/vi-family.html
#vi #VIM #NeoVIM #viless #neatvi #nextvi #nvi #elvis #STEVIE

2025-07-29 15:33:17 GMT

- reply

@nprofile…v27x @nprofile…tum0
I think that you possibly hadn't noticed before because it wasn't NetBSD; but now I've ported all three of #redo, #djbwares, and #nosh to NetBSD (testing on a non-amd64 architecture, no less!), as you've probably seen over the past few months. So now there's a system for building #NetBSD packages alongside Debian's, FreeBSD's, and OpenBSD's.

2025-07-29 15:00:43 GMT

- reply

@nprofile…v27x @nprofile…tum0
It has always been capable of building its own packages, by the way. (And since it's slashpackage, one can by design just package/compile it self-contained and not do the subsequent packaging step.)
https://jdebp.uk/FGA/slashpackage.html#OSPackaging
It's not a Debian thing. Quite the opposite. For a long time no-one packaged any of this at all, so I made packages for people myself. Even now, no-one at all packages djbwares and there is only one that packages nosh.
#redo

2025-07-29 14:45:52 GMT

- reply

@nprofile…v27x @nprofile…tum0
I'm curious how knowledge of the 1.5 source archive even reached any packagers.
That was not listed on the WWW pages at all but only on a GOPHER site that's explicitly for people to get bonus content such as access to in-development source, and comes with an explicit warning in the GOPHER menu.
The published source archives listed on the WWW, as well as the GitHub snapshot, were still at 1.4. I had only just ticked them over to 1.5 when I sent that nudge out. (-:
#redo

2025-07-26 13:19:39 GMT

Dear #NetBSD people:
pkg_create(1) takes files with its -f, -B, and -b options. But there is zero documentation anywhere for what is supposed to be in the latter two.
Please document this, preferably on that manual page alongside where the contents of the first file are documented.
#pkgsrc

2025-07-26 03:39:55 GMT

@nprofile…tum0
You're the only name in the log. (-:
https://git.parabola.nu/abslibre.git/tree/pcr/jdebp-redo
I'm just giving the packagers (those that I know about and are easily contactable, at any rate) a tap on the shoulder before the rest of the world explicitly learns that #redo 1.5 is up.
https://jdebp.uk/Softwares/redo/
(Po-Chuan Hsieh of #FreeBSD is still using a URL that has not worked since Brexit. 17 million people voted that I should not have my domain name. (-:)
@nprofile…v27x
#djbwares 10 is next.

2025-06-07 07:13:56 GMT

As implied, the #NetBSD port of #nosh, #redo, and #djbwares is pretty much done.
NetBSD doesn't make it as easy to switch between process 1 programs as FreeBSD does, so the system manager is not tested. But many of the other tools from tai64nlocal, cyclog, and setterm; through login-envuidgid and envdir; to the service manager and console-tty37-viewer; have now been used in earnest.
There are known missing bits in #ifconfig and list-process-table. And UVT realizers are not tested at all yet.

2025-05-14 20:53:41 GMT

- reply

@nprofile…0zny @nprofile…t4qe
In this quest for a BSD GUI desktop, have you checked out Midnight BSD and Ghost BSD?
#MidnightBSD #GhostBSD

2025-05-05 14:40:45 GMT

- reply

@nprofile…t4qe
There isn't a knob for turning sixel on/off in the port, so it's unlikely to be down to solely the way that it was built.
#FreeBSD #fastfetch

2025-04-26 16:56:09 GMT

- reply

@nprofile…t4qe @nprofile…xwsy
What could #sixel support specifically entail that could be impacted by pledge()? #xterm is still only drawing pixels into pixmaps, sixel mode or otherwise.
Unwillingness to turn on a new (since 2013) not-very-well-tested-until-recently feature, almost certainly. NetBSD delayed turning it on until 2020. (Debian went straight for turning it on in 2013, by contrast.) But I don't see how pledge() would have had any hand in the decision.
#OpenBSD

2024-11-19 01:27:45 GMT

- reply

@nprofile…seqg @nprofile…272y
That says that it moved to https://github.com/opsengine/cpulimit 12 years ago.
That said, if portability is not a concern, adjusting the max bandwidth of the cpu controllers of a dedicated control group for Chrome processes is the better approach.
#cpulimit #linux #cgroups