Comment by Freaky | Hacker News Reader

Comment by Freaky | Hacker News Reader

Parent Full thread

> I have to make this org.freedesktop.consolekit.pkla file and add entries to it in order to get the restart and shutdown buttons in Xfce to work

These Just Worked for me. My only real annoyance with Xfce is that it's unresponsive to mouse clicks for the first few seconds after starting.

> I really, really appreciate Debian's branches. If you install Wheezy, you can get security updates for packages, but not get version bumps. With FreeBSD, you have to choose between "the packages made at release time", or "the absolute bleeding edge."

There are quarterly port branches now to give people more of a choice: https://lists.freebsd.org/pipermail/freebsd-ports-announce/2...

> encrypted swap

Be nice to see this on by default these days, but if you're not already using it: swapoff -a && $EDITOR /etc/fstab && plop ".eli" at the end of the swap device name && swapon -a. Done.

> I also really like pf a whole lot more than iptables

I just wish it were more actively maintained and kept at least vaguely in-sync with upstream. Makes me reluctant to switch from ipfw.

> These Just Worked for me. My only real annoyance with Xfce is that it's unresponsive to mouse clicks for the first few seconds after starting.

Under a regular user account? I even added my user to wheel and operator, and no go. I've helped a few people on forums.freebsd.org set up this pkla file, too.

> There are quarterly port branches now to give people more of a choice

The quarterly branches are definitely a step in the right direction, but still not really what I want. I want patches for Heartbleed and Shellshock, but without any software version number bumps. I know their team is much smaller so it's just not feasible, but it's definitely something that would be greatly appreciated.

> I just wish it were more actively maintained and kept at least vaguely in-sync with upstream.

Definitely. Is OpenBSD's MP-safe yet? I believe that's partly related to why FreeBSD's has ALTQ disabled (but it's hard to find good information on why that choice was made.)

> Under a regular user account?

Yep. Only special factors I can think of are VirtualBox guest additions and passphraseless sudo - though I don't recall any similar problems when I last had it on my laptop which had neither.

Also starting from console and not a display manager, because they're vile things that are almost as bad as splash/boot screens.

> I know their team is much smaller so it's just not feasible, but it's definitely something that would be greatly appreciated.

Very much so - the biggest thing I miss from the Debian world is unattended-upgrades. Maybe with some more commercial support..

> Is OpenBSD's MP-safe yet? I believe that's partly related to why FreeBSD's has ALTQ disabled

It's still under a big giant lock as far as I'm aware. They're also removing ALTQ in favour of a simpler framework: http://undeadly.org/cgi?action=article&sid=20140419151959

> I just wish [pf] were more actively maintained and kept at least vaguely in-sync with upstream.

As much as I would love to have the newest OpenBSD pf config syntax available in FreeBSD I do appreciate them not breaking my firewall config as part of an OS update.

Reply on news.ycombinator.com