Slashdot Mirror

← Back to Stories (view on slashdot.org)

Ask Slashdot: Migrating a Router From Linux To *BSD?

Posted by timothy on from the hiring-a-new-traffic-cop dept.

An anonymous reader writes I'm in the camp that doesn't trust systemd. You can discuss the technical merits of all init solutions all you want, but if I wanted to run Windows NT I'd run Windows NT, not Linux. So I've decided to migrate my homebrew router/firewall/samba server to one of the BSDs. Question one is: which BSD? Question two: where's some good documentation regarding setting up a home router/firewall on your favorite BSD?
It's fine if the documentation is highly technical, I've written linux kernel drivers before :) (Got a question? You can Ask Slashdot, too.)

3 of 403 comments (clear)

  1. Re:pfsense by IMightB · · Score: 4, Interesting

    Love PfSense doubleplus from me as well. However, I don't understand the blatant systemd misrepresentation/hatred

  2. Two things by Richy_T · · Score: 5, Interesting

    1) Don't run your fileserver on your router/firewall. You're asking for problems.

    2) Not all Linuxes run Systemd (Yay Slackware). I have nothing against the BSDs and they are probably better for networking anyway.

    Personally I have Tomato on my firewall/router and use Slackware for my server needs. Serves me pretty well.

  3. BSD not likely to go systemd by unixisc · · Score: 3, Interesting

    Solaris uses SMF and OS-X uses launchd, as was discussed yesterday in the thread about the new networking features in systemd. If BSD leaves SysV and adapts something, it's more likely to be launchd, rather than systemd. Also, systemd is under GNU LGPL 2.1, and the BSD projects have tended to seek out BSDL alternatives wherever possible. Which is why launchd is more likely to be used than systemd