Post Abde8LzXSCGDiIZqIC by Anniiii@gts.ferreo.dev
 (DIR) More posts by Anniiii@gts.ferreo.dev
 (DIR) Post #AbdcJgS1Wi5SRcAwnA by stefano@mastodon.bsd.cafe
       2023-11-09T18:14:26Z
       
       0 likes, 0 repeats
       
       Oh, I need a clean space to test software y!'No problem: 'bastille create -B jail42 13.2-RELEASE 0.0.0.0 bridge0', followed by 'bastille console jail42' - and here I am. No overhead, no extra layers, no problems! #FreeBSD #BastilleBSD #SystemAdministration #NoFussComputing
       
 (DIR) Post #AbddHCwmLnDoJYwc1w by Anniiii@gts.ferreo.dev
       2023-11-09T18:24:19Z
       
       0 likes, 0 repeats
       
       @stefano "jail42", so you're just numbering your jails? Interesting approach, do you then have some associated document stored somewhere documenting what the seperate jails actually are? Personally I just go with naming the jail with the software its primarily running (and adding the purpose afterwards if I for some reason need multiple jails with that software).
       
 (DIR) Post #AbddZaeQxRup2n83hw by stefano@mastodon.bsd.cafe
       2023-11-09T18:28:31Z
       
       0 likes, 0 repeats
       
       @Anniiii no, the jail had a name but I didn't want to post it as it was stupid. Generally speaking, I name the jail considering their task. For example, those are (some of the) BSD Cafe jails: bsdcelastic  Up     192.168.123.36   -                bsdcelastic  13.2-RELEASE-p5  /usr/local/bastille/jails/bsdcelastic/root bsdcmas01    Up     192.168.123.33   -                bsdcmas01    13.2-RELEASE-p5  /usr/local/bastille/jails/bsdcmas01/root bsdcmat      Up     192.168.123.38   -                bsdcmat      13.2-RELEASE-p5  /usr/local/bastille/jails/bsdcmat/root bsdcmflux    Up     192.168.123.37   -                bsdcmflux    13.2-RELEASE-p5  /usr/local/bastille/jails/bsdcmflux/root bsdcpgres01  Up     192.168.123.32   -                bsdcpgres01  13.2-RELEASE-p5  /usr/local/bastille/jails/bsdcpgres01/root bsdcredis01  Up     192.168.123.35   -                bsdcredis01  13.2-RELEASE-p5  /usr/local/bastille/jails/bsdcredis01/root
       
 (DIR) Post #Abde8LzXSCGDiIZqIC by Anniiii@gts.ferreo.dev
       2023-11-09T18:33:56Z
       
       0 likes, 0 repeats
       
       @stefano Ah I see, good this seems more organized haha Was a bit worried for a second, since as a programmer I can certainly attest to some people coming up with truly horrific naming for things.
       
 (DIR) Post #AbdeHqlOPjv1kzUMW8 by stefano@mastodon.bsd.cafe
       2023-11-09T18:36:32Z
       
       0 likes, 0 repeats
       
       @Anniiii I know - variable names can be terrible 🙂
       
 (DIR) Post #AbdfczDcGyua12Kg40 by Anniiii@gts.ferreo.dev
       2023-11-09T18:50:40Z
       
       0 likes, 0 repeats
       
       @stefano yes, one letter variable names or even x1, x2, x3, ..., functions that are a non-standard abbreviation that I'm sure made sense to the author a few years ago but now are too cryptic to decipher, even seen a function `void iso14755(const void* arg)` (so it takes something but without saying what and does something without giving me any new value back and if I want to know any more I get to read a ISO standard or the implementation)