#inetd — Public Fediverse posts

@wolf480pl Brings #inetd to my mind.

@rust_discussions in contrast to what the article claims, socket activation wasn't pioneered by Apple's #launchd, but much earlier in 1986 by #inetd as part of BSD 4.3.

I wanted to jump up on the AI-powered-dev-assistant bandwagon, so I installed TabbyML into neovim and then ended up in a small rathole trying to get systemd to act like inetd. Details on my blog at https://place.org/~pj/blog/using-systemd-as-user-level-inetd.html

#TabbyML #neovim #systemd #inetd

I wanted to jump up on the AI-powered-dev-assistant bandwagon, so I installed TabbyML into neovim and then ended up in a small rathole trying to get systemd to act like inetd. Details on my blog at https://place.org/~pj/blog/using-systemd-as-user-level-inetd.html

#TabbyML #neovim #systemd #inetd

#openbsd #sh #magic @prahou @ParadeGrotesque @solene sorry, does anyone know why enabling #inetd in /etc/rc.conf.local and commenting in #ntalkd in /etc/inetd.conf and starting inetd isn't sufficient to #talk(1) ? #write(1) to the #tty(1) works.

I've been obsessed with #C recently. Been reading lots of the #GNULibC manual, and just admiring what a feature
complete library it is (I always thaught you didn't get much of a stdlib with C for some odd reason, but of
course #Posix).

Came across the section on #inetd, so I decided to write my own as a learning experience. Obviously inetd today has
security issues, but it's a good way to learn about sockets, parsing config files, and a bunch of other posix stuff.