<stenur>
Hey pedja. Wrong channel, sorry, me and IRC. That is FreeBSD, like 7 some say, but back to 4 is possible.
<stenur>
Like "run, as an example, binaries built on FreeBSD 4.11-RELEASE, on a much newer RELEASE"
<pedja>
that's an interesting exercise
<stenur>
Ie it is about the binary compatibility layers of FreeBSD.
<pedja>
what's the state of their Linux-compat layer these days?
<stenur>
Oh. I did run a program compiled statically on Linux around say maybe 2001 until about 2018 (but daily until 2009) via those binary compatibility layers.
<stenur>
That i do not know. They now have a Linuxulator or how it is called..
<stenur>
Yeah that is its name. "We currently claim compatibility with Linux 3.2.0 in 12-STABLE and 4.4.0 in 14-CURRENT. "
<stenur>
I do not really run FreeBSD no more but in virtual machines under Linux. Linux is now doing all the work.
<pedja>
importing drm graphics stack from Linux, iirc, was some dark magic hackery :)
SiFuh has quit [Remote host closed the connection]
<stenur>
Am on my way to listen to all lounges and chills from 15-20 years ago again, tracked in a file -rw-r----- 1 steffen steffen 3325 Aug 27 17:22 /home/steffen/src/.PEDJA
<pedja>
I think fbsd-11 was the last I made VM out of
<stenur>
Already listened/worked a lot, and that "Balkan Pissbox!" will not escape me.
<stenur>
12.2 is max at the moment.
<pedja>
these days, I have 5+ Leap/TW VM's for experiments :)
<pedja>
selinux and stuff like that
<stenur>
Sounds SuSE thing. Uh, selinux.
<pedja>
not (open)SUSE thing officially yet, apparmor is the default/used atm
<stenur>
I only use VMs for OS testing. Aka program portability. Otherwise i slowly hack more boxing scripts with unshare(1) / overlayfs etc.
<pedja>
so reinventing containers :)?
<stenur>
Yes, stupidly work intensive ones.
<pedja>
you might like podman/buildah/skopeo
<pedja>
(run/build/inspect) containers tools
<stenur>
nonono. I like it that way. It is really easy, and i can adjust a template. I do not need that. The irssi proxy master on the VM sits in such a box and the bytes you will see soon passed through it. :)
<pedja>
ah, nice
<stenur>
Yeah. status is actually via pid file, i have integrated that in my net-qos.sh script which does firewall and daemon stuff, and it uses start-stop-daemon to startup the "container", so we do have a PID to track.
<pedja>
interesting. podman has something similar, it can create service file for container, so systemd can control it
<stenur>
oh no please no systemd. I am thinking about writing a reaper module that uses prctl(2) PR_SET_CHILD_SUBREAPER, like that we could start all the stuff and should become informed whenever a child dies.
<stenur>
I think that is one of the things that systemd uses, and i _always_ get angry when i see that all the other software login etc whatever do not make use of it. This (and in my case: only this) is what makes systemd fly.
<stenur>
Imho.
<stenur>
Ok for an admin such one-service-file-syntax with all the plenty of possibilities is surely gigantic.
SiFuh has joined #crux
ivandi1 has quit [Quit: WeeChat 3.2.1]
ivandi has joined #crux
pedja has quit [Ping timeout: 245 seconds]
Moth has joined #crux
<cruxbot>
[contrib.git/3.6]: seatd: service file now uses start-stop-daemon
frinnst_ has quit [Remote host closed the connection]
frinnst has quit [Ping timeout: 260 seconds]
groovy2shoes has quit [Remote host closed the connection]