Posts by JdeBP@tty0.social
(DIR) Post #B4HRy3C6DHdJKrl65Q by JdeBP@tty0.social
0 likes, 0 repeats
@josevnz Looks complex. (-:C shell:% printf '%s\n' $pathZ shell:% printf '%q\n' "$path[@]"#UnixShells #CShell #ZShell #zsh #csh
(DIR) Post #B4daepWhyjNyVdQVgO by JdeBP@tty0.social
1 likes, 0 repeats
@alanc Service management, as I mentioned, began as the domain of the much older Service Access Facility, which comes from #Unix S5R4 in 1988.The #Illumos manual page for the sacadm command (for one) is dated 1992, and the Illumos #ServiceAccessFacility dates back to the days of #Solaris 2.The use of sacadm/pmadm/ttyadm/nlsadmin in Illumos et al. is the same now as it was when Æleen Frisch wrote about them for Solaris 2 in xyr book in 1995.http://jdebp.info/FGA/unix-service-access-facility.html@Radio_Azureus
(DIR) Post #B4daepnixSzrMPO6Cm by JdeBP@tty0.social
1 likes, 0 repeats
On that subject: I can now give @cks one of the most delayed and useless responses to a mailing list question, ever.https://omnios.org/ml-archive/2014-February/002358.htmlChanging the BPS setting for a terminal service in #OmniOS is done with ttyadm(8). Use the -l option to pick the desired chain of speed settings from ttydefs.https://man.omnios.org/man8/ttyadmCreate an entry with sttydefs(8) if necessary that has "115200" in the stty flags and that chains to the next slower speed.https://man.omnios.org/man8/sttydefs@alanc @Radio_Azureus
(DIR) Post #B6gXu7EVHcRELPAaJs by JdeBP@tty0.social
1 likes, 0 repeats
@ska An additional fun factor is that wildcards in #djbdns by design don't work like wildcards in BIND. The difference was much discussed a quarter of a century ago.So any bug reports that assume that wildcards in djbdns databases are supposed to behave like they do in BIND's 'zone' files need to be checked for proper foundation.And with RFC 4592 an even greater divergence then happened.#djbwares #DNS #shibari
(DIR) Post #B6hRPg4fHyRorId9dY by JdeBP@tty0.social
0 likes, 0 repeats
@ska I hope not, if working like #djbdns is the goal.RFC4592 has a tree-structure model of domain name existence that prevents wildcards from working in some cases in a way that the djbdns table-structure model does not prevent.Using the RFC4592 example:When one does an MX lookup for _telnet._tcp.example. or ghost.*.example. it returns a non-empty record set because of the @ wildcard at *.example. .In the RFC4592 model, the *.example. wildcard does not get applied.#DomainNameSystem
(DIR) Post #B6hRYE4Imd4ebeXLea by JdeBP@tty0.social
0 likes, 0 repeats
@ska It probably would be possible, but it was genuinely a design decision by Bernstein to make wildcards work that way. There were several mailing list discussions.https://marc.info/?l=djbdns&m=104636747625737&w=2In this case, working like #djbdns means taking unmodified cdb files and providing the same responses from those data; which is what your WWW page currently says is the #shibari goal.If taking unmodified data files and giving non-tinydns behaviour instead is the goal, then that WWW page misleads.
(DIR) Post #B6hRYEKxmgOxRKKeci by JdeBP@tty0.social
1 likes, 0 repeats
@ska Anyway, who the Hell is this community that thinks that the original #djbdns is the be-all and end-all?Let me know, and I'll show them #djbwares, where I've got a whole long list of things that have been improved, from IPv6 support through a non-hexdump way of doing SRV records to not letting ANY queries be amplification attack puppets.http://jdebp.info/Softwares/djbwares/guide/changes.html
(DIR) Post #B6hWTFntP57yJMJHii by JdeBP@tty0.social
0 likes, 0 repeats
@ska That rather depends from the claim that something that was deliberately designed, and is documented as working that way, even *is* a bug. Bernstein did design to make things less suprisingly odd than 'zone' files.Because this was and is unintuitive. I was one of the people who sometimes explained to users that there were implied interior nodes that stopped wildcards from working. As well as the other ways that BIND wildcarding didn't work like MaraDNS, Microsoft DNS, and #djbdns.
(DIR) Post #B6hZ7MJYodfhznNEaO by JdeBP@tty0.social
0 likes, 0 repeats
@ska Sugar for AAAA records was done in 2025 by me. Felix von Leitner did it differently 25 years earlier, but I didn't like that it required two parallel toolsets and sets of record types. My way, it's just an IPv6 address in the same '+' records.That's been available for a *long* time.#djbdns #djbwares
(DIR) Post #B7tuEdXyZGNugkqVfM by JdeBP@tty0.social
0 likes, 0 repeats
@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
(DIR) Post #B7tuEe5IZN2WM6R7bc by JdeBP@tty0.social
0 likes, 0 repeats
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/116834743954481512I am tempted to just quickly knock one together and put it into the #nosh toolset.RT: https://tty0.social/users/JdeBP/statuses/116834743954481512
(DIR) Post #B7tuEeY0qc0Zn9s3MW by JdeBP@tty0.social
0 likes, 0 repeats
@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
(DIR) Post #B7tuEewpMLrF27Ts2a by JdeBP@tty0.social
1 likes, 0 repeats
@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
(DIR) Post #B8Apz8QuzTwUB58x7o by JdeBP@tty0.social
0 likes, 0 repeats
@wolf480pl @cks Nah. With per-user service management it is far more likely to be D-Bus. It could be a D-Bus service failing, or not present, or not starting properly; or even a problem with the per-user broker.Crank up your D-Bus monitor.#systemd
(DIR) Post #B8C3XkLm11l2BQX07M by JdeBP@tty0.social
0 likes, 0 repeats
@cks You should have this:https://manpages.ubuntu.com/manpages/resolute/man1/dbus-monitor.1.htmlIf it cannot connect, in a session for the relevant user, without tweaking the DBUS_SESSION_BUS_ADDRESS environment variable, or at all, then that might well be the problem. (-:@wolf480pl #systemd #DesktopBus