#nosh — Public Fediverse posts

I'm not the only person to provide a full off-line browsable HTML guide to my softwares in the box, also. (-:

In case anyone else hits it: The version of xgettext in #NetBSD 10.1 is old enough (0.16) that it breaks the #WatanabeShell build. You need the one that is in pkgsrc (0.22).

#UnixShells #nosh

@seuros

Does /dev/coreboot-console change at runtime? I added a service for it to the #nosh collection, analogous to the collection's dmesg service that spits out /dev/dmesg.boot, which was the work of about 10 minutes; but I'm wondering whether it's even worth it.

#coreboot #FreeBSD

@iaruffell

Looking at the blurb afresh, I see that it still uses the login program to login.

That isn't necessary nowadays. One thing that I later added to the toolset was a replacement program that assumed that one had at least a 1970s video terminal with a repositionable cursor, and draws a full-screen TUI with the user/password prompts as text entry fields.

http://jdebp.info/Softwares/nosh/guide/commands/login-envuidgid.xml

I assume that the old paper terminal login style works better for the #brltty case, though.

#nosh

@iaruffell

For what it's worth, I've long since been providing a terminal emulator, that runs on both #FreeBSD and #NetBSD, that can also optionally provide a Linux-format vcsa file, a format that #brltty already understands and can read.

http://jdebp.info/Softwares/nosh/brltty.html

http://jdebp.info/Softwares/nosh/guide/commands/console-terminal-emulator.xml

I wrote up that blurb in 2014, and it still does that today, although I did in 2015 make vcsa file generation a non-default option, as there's also a better full Unicode display file available.

#nosh

@cks

That could very well be your problem. Something is waiting for #DesktopBus, and it's taking its time for the per-user broker to come up.

D-Bus is a bit fragile. I had to go through all of this stuff for per-user service management with the #nosh toolset, and there are many ways in which the D-Bus mechanisms can break.

A few ways were because originally the design was that the first client forked the broker process. Not good when the client's resource limited.

@wolf480pl
#systemd

@rl_dane

It's food for thought, too. All this fuss made about cat, repeated to this day in some quarters, and of the three things explicitly pointed out as wrong with what Berkeley did, only a tool to do one of them, vis(1), was ever written in 43 years.

The ironic cherry on top is that the only operating systems that come with vis out of the box are the BSDs.

#Unix #TextProcessing #nosh #cat #vis #linenumber #sqz

@rl_dane

The 'cat -v considered harmful folks' (Kernighan and Pike) invented vis(1).

> The preferred approach in this case is a separate program that deals with non-printable characters. We called ours vis […] because its job is to make things visible.

I suspect that they would approve of sqz(1) likewise abstracted from cat -s, because they also said

> cat isn’t […] for compressing multiple blank lines […] it’s for concatenating files.

#vis #sqz #cat #Unix #TextProcessing #nosh

@rl_dane

Well since vis(1) came about because of cat -v, it seems that there should be a sqz(1) because of cat -s .

#Unix #TextProcessing #nosh

As you can see, @rl_dane has me wondering whether anyone has ever written a sqz(1) #Unix #TextProcessing tool, to go alongside vis(1).

https://tty0.social/@JdeBP/116834743954481512

I am tempted to just quickly knock one together and put it into the #nosh toolset.

@rl_dane

When you view manual pages on a video terminal, the -s ('squeeze') option to the final $PAGER in the pipeline does this. You'll be surprised at how many blank lines there really are in manuals.

less, (BSD) more, most, and (my) console-tty37-viewer all have this option.

Given that, it's an of course moment, with a nod to the people who think that this should no more be a part of cat than vis(1) is, that cat has a squeeze option too.

#Unix #TextProcessing #nosh

Since I was visiting the 'daemontools' account on #GitHub, I took a look at what the people who mistakenly thought that it was someone actually involved, have done.

Not much, fortunately.

One wheel reinvention that didn't even look at Bruce Guenter's daemontools-encore.

Only one thing worth following up on, in 13 years:

https://github.com/daemontools/daemontools/issues/8

The bugfix will be in #djbwares version 13 when it comes out. As noted, neither @ska's nor my #nosh reimplementations have this bug.

#daemontools

@david_chisnall

dnscache, as you can see from that manual, needs both TCP and UDP listening sockets, so there's a TCP tool. The service ./run script for the DNS server chains through both tools.

There are also the three different kinds of AF_LOCAL listener tools.

http://jdebp.info/Softwares/nosh/guide/commands.html#UCSPIChainLoading

@BastilleBSD
#nosh

@BastilleBSD

Yes, there exist #FreeBSD tools that can set up the socket and the environment variable. I wrote one such tool years ago, and have been running a DNS server that accepts pre-created listening sockets and itself runs wholly unprivileged for almost as long.

Tell any naysayers that it can be done. (-:

http://jdebp.info/Softwares/nosh/guide/commands/udp-socket-listen.xml

http://jdebp.info/Softwares/djbwares/guide/commands/dnscache.xml

#dnscache #nosh #AdGuardHome

@cks @drscriptt

By the way: It's DEC Private Mode 67 (a.k.a. DECBKM) for controlling Backspace, and DEC Private Mode 1037 for Delete.

Not every terminal emulator understands these. But they're understood by things as wide ranging as hterm and mintty.

I copied these from #DECVTs and XTerm in my terminal emulator, and my #setterm has options for generating both DECSM/DECRM mode switches.

http://jdebp.info/Softwares/nosh/guide/commands/setterm.xml

#nosh #TerminalEmulators

@ermo

Given that you've built this package from source, run

sh bsd/nosh-bundles/post-install

pkg has sh source the scripts, so sh doesn't know to print line numbers in the error messages. If you tell sh to run the script from file it will, which will help narrow down which of the ~1100 lines it is.

You don't need to run the script as the superuser to get sh to find this particular error. Ignore all of the permissions errors that will come out, though. (-:

#nosh

@ermo

Confusing. The only package with a post-install script that uses redo is nosh-run-system-manager. That does have a declared dependency upon redo in its +MANIFEST.

In any case, the unterminated quoted string error would not be the result of a missing redo utility. That's a script syntax error, not a command going wrong error. sh unfortunately doesn't report such a syntax error here.

#nosh

@ermo

Important note 1C does address how one goes back to the old system.

The pre-deinstall script for the nosh-run-system-manager package (on FreeBSD) makes that very modification persistently in /boot/loader.conf , so just uninstalling that package is also a way back.

(On Debian Linux, the mechanism is a symbolic link; and again, installing and deinstalling the package persistently switches the #nosh system manager in and out.)

#SystemManager

@ermo

Excellent.

Yes, the latest released versions are supposed to be a version behind the actual development source. I freeze the source, do a binaries release, and start a new development version.

So #redo latest binary release is 1.5, and #nosh is 1.41.

#djbwares is at version 12, with version 13 under development. I must have forgotten to update the WWW page.

@cks

I suspect that this has changed over the years. Kay Sievers's original proposal in 2010 indeed had the active device as the last one. But Lennart Poettering writing in 2012, after things had settled down amongst the kernel developers, wrote that the active device was the first one. I vaguely remember inspecting the code that constructed the string to check, at the time. I'll try to remember to have another look.

https://0pointer.de/blog/projects/serial-console.html

#Linux #console #vt #manual #nosh

@cks

I write a console(4) and a vt(4) manual page for #Linux, too, as there is a larger gap there, Linux doco not having a vt(4) page as #FreeBSD does.

http://jdebp.info/Softwares/nosh/guide/commands/linux-console.xml

http://jdebp.info/Softwares/nosh/guide/commands/linux-vt.xml

#console #vt #manual #nosh

@cks

I wrote a console(4) manual page some years ago, to fill in a gap.

http://jdebp.info/Softwares/nosh/guide/commands/freebsd-console.xml

#FreeBSD #console #manual #nosh

New Mediterranean, Middle Eastern restaurant now open at Easton | Nosh

Shawerma Bite, which specializes in Mediterranean and Middle Eastern food, opened Jan. 2 at 4100 Worth Ave. in Columbus at Easton Town Center. Housed in the space that previously was Dragon Donut…
#dining #cooking #diet #food #mediterranean #MediterraneanDiet #MediterraneanFood #Mediterranean #mediterraneanfood #nosh
https://www.diningandcooking.com/2471822/new-mediterranean-middle-eastern-restaurant-now-open-at-easton-nosh/

New Mediterranean, Middle Eastern restaurant now open at Easton | Nosh

Shawerma Bite, which specializes in Mediterranean and Middle Eastern food, opened Jan. 2 at 4100 Worth Ave. in Columbus at Easton Town Center. Housed in the space that previously was Dragon Donuts before it closed in August 2024,…
#dining #cooking #diet #food #MediterraneanFood #Mediterranean #mediterraneanfood #nosh
https://www.diningandcooking.com/2471822/new-mediterranean-middle-eastern-restaurant-now-open-at-easton-nosh/

In light of recent reports I thought about adding AF_VSOCK support (if that is meaningful) to the #nosh toolset's #ifconfig .

It turns out that there's no vsock device on my Debian development machine.

I do not have the time at the moment to look into this more thoroughly.

I knew that there was #HJKL navigation and #WASD navigation, and some of the full-screen utilities in the #nosh toolset support both.

I read that there's also QAOP, which alas contradicts the conventional use of 'q' that those utilities already have, and ESDF which alas overlaps WASD.

One cannot be all things to all people, and it seems excessive to make this configurable somehow when they're only limited-use bonuses over just using the normal arrow keys.

#ComputerGaming #ComputerKeyboards

@lymenzies

If you want a FreeBSD-like ifconfig on Linux-based operating systems, I made one. I needed the same syntax across both.

http://jdebp.info/Softwares/nosh/

http://jdebp.info/Softwares/nosh/guide/commands/ifconfig.xml

#ifconfig #FreeBSD #nosh

@developing_agent @mcc @ariadne

Even simply separately packaging binaries and hooks *today* would avoid the problem whereby the systemd-all-in-one package always installs all possible runtime hooks, some of which try to spin up systemd-logind, and systemd itself, by various surprising back-routes.

http://jdebp.info/Softwares/nosh/guide/services/systemd-logind.html

Gerrit Pape had packaged runit-run and runit-init separately from runit, and this was the model to follow.

@ska
#nosh #runit

Just for fun I created a Shavian QWERTY keyboard map for #FreeBSD.

The hard part turned out to be that I had to work from pictures of layout diagrams, and tiny ones at that, cross-referencing them by eye against a Unicode chart. No-one has a text list of what Shavian alphabet characters go with what keys.

I named it gb-shaw, of course.

#ShavianAlphabet #nosh #uservt #KeyboardLayouts

@freezr

If you like the FreeBSD syntax, I have an ifconfig that is closer to FreeBSD syntax than the net-tools one is.

In fact, that was its raison d'être. It brought (most of) the FreeBSD syntax to Debian so that I could auto-translate /etc/network/interfaces into FreeBSD-like setup that used ifconfig.

http://jdebp.info/Softwares/nosh/guide/commands/ifconfig.xml

http://jdebp.info/Softwares/nosh/guide/networking.html

#FreeBSD #ifconfig #nosh