I love the power of curl combined with wttr.in

Giving this example for those of us who love to use true free services for our work / live flow

I've been using wttr for decade(s)

Read here for more examples.

https://github.com/chubin/wttr.in?tab=readme-ov-file

#wttr #weather #curl #opensource #free #POSIX #API #programming #bash #csh #ksh #sh #portable #freeBSD #BSD #Linux

On the positive side, I discovered today that #ionos finally allows vserver customers (compared to their cloud computing offering) to set reverse DNS records on #IPv6 addresses. This finally allows me to send email via IPv6 over them (besides the similarly configured netcup instance I additionally have and which provides this functionality since years).

I recently installed NetBSD for the first time, on a remote VPS. All was fine, I installed pkgin, got some packages installed, installed openssh-portable, got my firewall rules set and so on. Having used FreeBSD and OpenBSD before it was a little different, but not too different.

Then one day, or rather late at night I found I needed to install some X11 sets and fired up sysinst. It being late, I did not read everything very carefully, but quickly found "re-install sets", "custom installtion", and then the X11 sets at the bottom of the menu. I selected them and started the installation.

It took a little longer than expected, and I noticed it was reinstalling base for some reason. No worries I thought, I hadn't touched that in the few days the system had been running, so it shouldn't be a problem.

Then when everything was finished, I noticed things were not working as expected. I think I managed to kill the sshd listening daemon and couldn't start it again. Then I noticed /etc/rc.conf was blank, so I had no network configuration, no sshd startup, no nothing. It seems /etc had also been replaced with defaults.

So by my lonesome, I had quite quickly managed to make quite a mess of things. Fortunately I did not reboot as was my first intuition when I found things weren't working. Sshd from packages required another script which had been replaced, the original sshd I had set to listen on another port which wasn't allowed through current firewall rules and so on.

Sorry for the boring ending, but it was all fully recoverable from my one ssh connection that fortunately didn't drop. Got network configured again, got firewall set up and started, got correct sshd started and so on. Then reboot, and all was good. Thanks to good documentation and easy configuration.

And that is why I #RUNBSD
Even being completely new to #NetBSD it was easy to recover.

I've re-tried sysinst after the fact, and now see base, /etc and so on will be re-installed by default if you don't uncheck them, so now I know.

So this is where my peeps at!

Hello everyone, my name is Børge and I am happy to get back into the BSD world, though only for personal projects for now.

I was a sysadmin for a small telco a while ago and we used Solaris/SPARC and FreeBSD/i386 for our servers, while I tried my hand at OpenBSD for my personal server. The network was all Cisco at the beginning, with some Juniper equipment for peering at the end but I did not get any experience with those unfortunately. I do have a certificate in SS7 somewhere, the signaling protocol telcos use for voice calls, but have forgotten pretty much all of it.

These days work is "cloud everything", which all seems to be based on Linux-something.

Reminiscing of "the good, old days" I wondered if I could run a BSD server anywhere to tap into my sysadmin background a little, or if I would have to use some Linux distribution.

Searching for BSD hosting providers, I am very happy I discovered #OpenBSDAms which I use for OpenBSD hosting (obviously).

Then I came across #BoxyBSD where I was lucky enough to get a FreeBSD instance.

Last but not least I came across a cheap VPS provider where I could run NetBSD. I don't mention the provider because I'm not sure I can recommend them yet.

I've been on Mastodon a little while, mostly reading as there is so much of interest to find here, though also because I'm quite shy, but hope to maybe post something about what I do now and then.

I really like all the *BSDs, they just do things in a way that seems sensible to me, so being here feels a lot like coming home.

So that's me a little about me. #introduction

How are you?

#OpenBSD #FreeBSD #NetBSD #RUNBSD

#FreeBSD #Ports novice question:

When a commit is made to a port, for example in branch 2025Q3, the corresponding package is build automatically within a few days?

So if I've configured my system to use quarterly packages, I'll just have to wait and the effects of the commit will appear?

Politics is theater. The current show is off-off-off-off-off-Broadway.

#BSD #Unix #RUNBSD

Add the following to named.conf or named.conf.options

// BIND9 configuration
//
// TLS upstream servers
tls cloudflare-tls {
  remote-hostname "one.one.one.one";
  protocols { TLSv1.3; };
};
tls opendns-tls {
  remote-hostname "dns.opendns.com";
  protocols { TLSv1.3; };
};
tls dns-sb-tls {
  remote-hostname "dns.sb";
  protocols { TLSv1.2; TLSv1.3; };
};
options {
...
  forwarders port 853 {
     2620:119:35::35 tls "opendns-tls";
     2620:119:53::53 tls "opendns-tls";
     208.67.220.220 tls "opendns-tls;"
     208.67.222.222 tls "opendns-tls";
     2606:4700:4700::1001 tls "cloudflare-tls";
     2606:4700:4700::1111 tls "cloudflare-tls";
     1.1.1.1 tls "cloudflare-tls";
     1.0.0.1 tls "cloudflare-tls";
     2a09:: tls "dns-sb-tls";
     2a11:: tls "dns-sb-tls";
     185.222.222.222 tls "dns-sb-tls";
  };
  forward first;
};

Oh well, I've tried to install FreeBSD 14.3 on an old PC of mine, but after the first reboot, it would always get stuck on the POST screen and I also couldn't enter the BIOS, as long as the disk with FreeBSD on it was connected.

The installation from a USB drive itself went fine, but wouldn't boot no matter what. It's one of my first PCs with an AMD Athlon 64 3000+, an MSI K8T Neo2, 1 GiB DDR, a 80 GB Seagate ATA HDD and a ATI 9800. I suppose the Phoenix BIOS doesn't like FreeBSD's MBR?

Alt...

Screenshot of the POST screen of a MSI K8T Neo2 after getting stuck trying to boot FreeBSD.

Need another jail like that one?

see: bastille clone help

This lets you duplicate containers in seconds. Fast, efficient, exact.

#FreeBSD #BastilleBSD

And it's IPv6-only 🙂

#freebsd #ipv6 #ipv6only #lxde