News for hackers. Stuff that matters.
Re:Debian developer revisits FreeBSD after 20 years (2015) by yaseer on Saturday February 17, 2018 @09:43AM (#16400854)
Who here uses FreeBSD in production, and what use-cases do they find it better than Linux for?
Re:Debian developer revisits FreeBSD after 20 years (2015) by drewg123 on Saturday February 17, 2018 @10:38AM (#16401116)
We use it at Netflix for our Open Connect CDN.

In general, the FreeBSD performance is far better for our workload (we have served up to 100Gb/s from a single-socket CDN node). In fact, I'm sitting here reading HN while watching a single-socket E5-2697A machine ramp up past 92Gb/s for a 100% TLS workload.

Re:Debian developer revisits FreeBSD after 20 years (2015) by 2trill2spill on Saturday February 17, 2018 @10:45AM (#16401145)
I hate to nag you. But whats the status of TLS sendfile? That feature is a great example of what FreeBSD can do, unfortunately it's still closed source.
Re:Debian developer revisits FreeBSD after 20 years (2015) by drewg123 on Saturday February 17, 2018 @03:43PM (#16402582)
Yes, sorry. We keep getting busy doing other things. I'm actually working on getting it upstream now. I was testing some "before upstreaming" cleanups to make sure I didn't break anything :)
Re:Debian developer revisits FreeBSD after 20 years (2015) by geofft on Saturday February 17, 2018 @11:35AM (#16401386)
Can I ask you what your network hardware is and how customized your kernel is (i.e., are you patching the network stack at all or running some vendor-customized drivers, or is it all in mainline)?
Re:Debian developer revisits FreeBSD after 20 years (2015) by drewg123 on Saturday February 17, 2018 @03:46PM (#16402595)
We use fairly standard Mellanox and Chelsio 100GbE NICs. Except for TLS sendfile and our vectorized mbufs, most of the patches that we've been running have actually been to the VM system. Thankfully, due in large part to the recent efforts to scale the VM system upstream, a lot of our hacks are going away.

We've got a blog detailing a lot of our work here: https://medium.com/netflix-techblog/serving-100-gbps-from-an...

Re:Debian developer revisits FreeBSD after 20 years (2015) by rsync on Saturday February 17, 2018 @04:30PM (#16402826)
"Who here uses FreeBSD in production, and what use-cases do they find it better than Linux for?"

rsync.net[1] is based solely on FreeBSD.

Our cloud storage platform is based on ZFS so it's a natural choice as ZFS is a supported and mature filesystem on FreeBSD.

[1] As always, email for details about the "HN Discount".

Re:Debian developer revisits FreeBSD after 20 years (2015) by Timothycquinn on Saturday February 17, 2018 @10:51AM (#16401171)
I use FreeBSD on my FreeNAS in Production. Makes an awesome box to have in a Small business network for all NAS services, backups and also lightweight virtualization for backend scripting and services. I could not recommend FreeBSD via FreeNAS more for these purposes. It just plain works. Almost all configurations can be done via Web GUI and rarely needs touching the root OS via commandline.
Re:Debian developer revisits FreeBSD after 20 years (2015) by xiljin on Saturday February 17, 2018 @03:13PM (#16402469)
We use FreeBSD in production (SaaS accounting/payroll app) as a load balancing proxy/web server (Nginx) and outgoing mail server (OpenSMTPD) because it's a stable, proven OS with sane defaults. Thanks to OpenBSD, we get an awesome firewall (PF) and dead simple OpenSMTPD mail server (total config is around 25 lines which gives us DKIM signing and PKI with no additional software).

At home, FreeBSD is used as a HTPC (Kodi), file server and backup box (it acts like a Time Machine for our Macs via netatalk and for Linux we use rsnapshot over NFS).

Re:Debian developer revisits FreeBSD after 20 years (2015) by titanix2 on Saturday February 17, 2018 @10:44AM (#16401141)
The PlayStation use an OS based on FreeBSD. The licensing is the big differenciating factor I guess.
Re:Debian developer revisits FreeBSD after 20 years (2015) by vetinari on Saturday February 17, 2018 @11:34AM (#16401383)
Panasonic uses FreeBSD in their TVs. Others don't, Samsung or LG for example use Linux. They don't seem to have a problem with licensing.
Re:Debian developer revisits FreeBSD after 20 years (2015) by HugoDaniel on Saturday February 17, 2018 @09:46AM (#16400868)
I use it. My use case is:

1. After properly setting it up, do sporadic updates when necessary without worrying that the whole thing falls appart.

Much better than Linux ;)

Re:Debian developer revisits FreeBSD after 20 years (2015) by krylon on Saturday February 17, 2018 @12:19PM (#16401607)
> After properly setting it up, do sporadic updates when necessary without worrying that the whole thing falls appart.

Do not get me wrong, I love that about FreeBSD as well. But a good GNU/Linux distro can do that, too, say, Debian or CentOS. All of the free Unix-like systems are light years ahead of Windows in terms of not spontaneously mutating and breaking things.

I always bite my tongue when people say they like Windows because it "just works", because Windows just as often "just stops" working for no discernible reason. And troubleshooting on Windows is so much more difficult, that surprisingly often, the "solution" is to wipe the system and reinstall everything.

Re:Debian developer revisits FreeBSD after 20 years (2015) by terminalcommand on Saturday February 17, 2018 @01:55PM (#16402077)
With the latest updates to Windows 10, Win has been working stable lately.

The things I hate are:

- The anti malware service executable eating a lot of CPU

- Terrible, terrible terminal emulation even with the improved powershell window

- The crazy amount of committed memory. Even if you have 16-32 gigs of RAM, the OS still writes pagefiles to disk.

I used to hate that I couldn't customize the Desktop Environment to suit my needs. But with custom Autohotkey scripts it seems to me that sky is the limit.

The windows subsystem for linux is buggy, nevertheless it is usable and helps a great deal. Most gnu software for example Gnuapl compile and work OTB.

I've only witnessed one blue screen of death in the last month.

I should also note that I'm using an 8th gen desktop machine I've built with minimal hardware. Even with Spectre/meltdown patches I didn't experience any trouble.

Re:Debian developer revisits FreeBSD after 20 years (2015) by krylon on Saturday February 17, 2018 @02:21PM (#16402225)
I only use Windows at work, where I also used to be the helpdesk guy. These days I spend most of my time programming, so I am somewhat out of the loop lately.

BSOD-wise, Windows has been very stable for a very long time[1]. I am not a fan of Windows, but Windows crashing is a very rare event, and when it happens, in my experience the cause is either a) faulty hardware, b) buggy device drivers or c) crappy AV software mucking around in kernel space (over the last three years, almost all the Windows bluescreens I saw were due to crappy AV software). My work laptop has BSOD'd on me maybe once or twice in three years - and I am one of those people that rarely shutdown or reboot their systems. At the end of the (work) day, I put my laptop to sleep, and only reboot it when an update requires it or when it misbehaves very badly. So I am pushing the system pretty hard.

I did not have much contact with Windows 10, yet, though. My work laptop runs Windows 7, and between Windows 2000 and 8.1, Windows 7 is the one I like best, so I am sticking with it for as long as I can. WSL sounds nice, though. And I heard Windows 10 finally got a native, builtin ssh client.

> Even if you have 16-32 gigs of RAM, the OS still writes pagefiles to disk.

This one has always struck me as odd about Windows. Linux or *BSD, given enough memory, will not swap at all until you push them. Windows seems to do it "proactively". I suppose it gets less annoying with an SSD, but my work laptop has a slow 5400rpm HDD.

[1] I once saw a Windows NT 4.0 Server with six years of uptime. Personally, I shudder at the thought of a server that has not gotten any updates in years, but if that is not a concern, Windows is absolutely capable of accumulating that kind of uptime.

Re:Debian developer revisits FreeBSD after 20 years (2015) by oblio on Saturday February 17, 2018 @02:19PM (#16402215)
You can set Windows Defender to not proactively scan.
Re:Debian developer revisits FreeBSD after 20 years (2015) by acdha on Saturday February 17, 2018 @09:57AM (#16400924)
What Linux distribution were you using – something like Gentoo?
Re:Debian developer revisits FreeBSD after 20 years (2015) by HugoDaniel on Saturday February 17, 2018 @10:25AM (#16401060)
I used a few in my past life as a bad sysadmin. Mostly Ubuntu Server's. Some Fedora's, some CentOS's, some Arch Linux. I never did try Gentoo in production servers though.

And through the years I learned to dislike their hive-mind approach to problems with half-baked crippled solutions that get approved and merged to production because some untouchable dev/guru/mastermind decided that he alone was a significant sample of all linux users:

- Forget about extending and improving ifconfig. Lets change everything and create a new command, afterall ifconfig is not that important,.

- Forget about your system dir layout. Lets change it and mix everything up into /

- Oops that kernel update completly screwed iptables...

- Oops that kernel update somehow introduced packet loops in the network

- Today I learned that I/O DoS is.

- wtf systemd ? Now i have to read up on this new sh*t that they are pushing down my throat. Oh wait there is no documentation.

- Don't get me started on filesystems...

Anyhow, I find Unix systems very hard to manage and maintain, i mean we do have all these devops tools to automatically manage configs and programatically setup machines in a coherent way. Linux just likes to show more than others that it exists, and does it in very inappropriate ways.

Re:Debian developer revisits FreeBSD after 20 years (2015) by vetinari on Saturday February 17, 2018 @11:32AM (#16401365)
> Forget about your system dir layout. Lets change it and mix everything up into /

Actually, everything is put into /usr, in / you have just symlinks. And there's a reason for that.

> wtf systemd ? Now i have to read up on this new sh*t that they are pushing down my throat. Oh wait there is no documentation.

One would say, that after 8 years you would be able to find the documentation. It has manpages too.

Re:Debian developer revisits FreeBSD after 20 years (2015) by Drdrdrq on Sunday February 18, 2018 @03:58AM (#16405115)
Also, while I still oppose systemd (because it's a monolith, because it reinvents logging and because... it comes from the people behind DBus :) I must admit that lately I prefer writing systemd units to making nohup workarounds. I never did grok init.d scripts and from what I've seen neither did lots of other people. So that's a big plus in my book.
Re:Debian developer revisits FreeBSD after 20 years (2015) by acdha on Sunday February 18, 2018 @09:25AM (#16406195)
I’m not in love with everything about systemd but I’ve noticed that about 90% of the attacks sound to an experienced sysadmin more like the person making the claim has never encountered/ understood the need for that particular feature. Many people will talking lovingly about SysV init without any mention of the many things people did to hack around limitations or the downtime suffered because they didn’t.

(Yeah, it’s not perfect but the rough parts can be improved and I’m looking forward to standardization meaning we never talk about daemonization, automatic restarts, or logging again)

Re:Debian developer revisits FreeBSD after 20 years (2015) by JdeBP on Tuesday February 20, 2018 @02:55AM (#16418571)
You have constructed the classic fallacious dichotomy between van Smoorenburg init and systemd.

* http://uselessd.darknedgy.net/ProSystemdAntiSystemd/