Posted on

In Other BSDs for 2019/01/19

Overflow from the past two weeks. I’ll have my email and tab backlog cleared next week.

Posted on

Cleanly adding sysctl entries on DragonFly

If you’d like to set a particular sysctl(8), you enter it into /etc/sysctl.conf. A common mistake is to copy the command line and put “sysctl foo=bar” in sysctl.conf instead of “foo=bar”. This used to cause a warning, but it still bit people, as it would cause a long stream of error messages during boot – with no clear reason, as the kernel tried to understand the command. Now, that typo is handled automatically.

Posted on

Power notes, booting notes

Two links I yoinked from conversation in EFNet #dragonflybsd: there’s a “powersave” power management page on dragonflybsd.org that for some reason wasn’t linked in the main documentation page. I fixed that, and you may want to look at it and change your mwait settings, or look at the corepower(4) module. (From ivadasz’s comments; thanks!)

There’s also an older page on DragonFly and grub2 that may be interesting to anyone looking to boot. (From aly’s comments; thanks!)

Posted on

Lazy Reading for 2019/01/13

Unofficial theme this week: me commenting on almost every link.

Posted on

In Other BSDs for 2019/01/12

Literally the first 45 minutes of me picking from saved links is all it took for this week.

Your BSD smug linksfor the week: I saw these two posts in my RSS feed, one right after the other: “Get ready to patch your Linux systems with systemd, 3x new CVEs out there as of yesterday. These enable any user to escalate to root.” and “Windows 10 Bsod on three different machines after updates. On was new out of box. Any ideas? ”

Posted on

Lazy Reading for 2019/01/06

Unofficial theme: DOOM

Posted on

In Other BSDs for 2019/01/05

I like when I can get Net, Free, and Open items all in the same week.

Posted on

File deprecation and DragonFly upgrades

On your next DragonFly upgrade, watch the end of your ‘make upgrade’ output. You may have some deprecated files, especially if your system has been upgraded through several releases. 

= You have 11 now deprecated files.
= Once you are sure that none of your third party (ports or local) 
= software are still using them, rerun with REMOVE_DEPRECATED set.

The now-deprecated files will be listed just before this warning. They aren’t removed automatically in case there’s installed software still linking to them. If you are running only dports software, and are up to date with all of it, you are probably fine to remove these files:

make -DREMOVE_DEPRECATED upgrade

If you have software you compiled yourself some time ago, it may have linked to these old files. One way to search for that would be to use find to find all executable files that are in particular directories, and then use ldd to see what shared libraries are used by each executable:

find /usr/local/bin /usr/local/sbin -type f -perm +a+x -print -exec ldd {} \;

… and then grep for the names of the deprecated files. You’ll get a bunch of “not a dynamic executable” errors when you do this because it’s a rough example I did for this post, but you can always pipe the stdout of the command to a file and review later. If you do turn up any executables linked to the deprecated files – recompile!

(If you have a better find string or strategy, please comment.)

Posted on

Lazy Reading for 2018/12/30

Last of the year!

Posted on

In Other BSDs for 2018/12/29

A big reading week. Enjoy!