This bites many people sooner or later: you think you’ve turned sendmail off, but it still gets opened up on your system. The answer: sendmail_enable=”NONE”.
(It should support sendmail_enable=”NOPE”.)
This bites many people sooner or later: you think you’ve turned sendmail off, but it still gets opened up on your system. The answer: sendmail_enable=”NONE”.
(It should support sendmail_enable=”NOPE”.)
John Marino has written up an extensive how-to for slider, the history tool for Hammer filesystems, including screenshots.
For whatever reason, I’ve seen several people in the last week or so have mouse problems on install, and they were often solved by running moused. So, there’s your little reminder.
Matthew Dillon’s added a sshlockout utility, to temporarily block SSH traffic from repeated brute force SSH login attempts. It’s been mentioned before, but it’s in the system now. It’s been refashioned to work with pf.
John Marino has created something very useful: a graphical tool for Hammer file history. It’s called ‘Slider’, and it uses curses to work in a terminal. It shows historic versions of files and can restore those old versions as needed. This was already possible in Hammer, of course, but it required a sequence of commands that were not straight-forward. I’ve been slow enough posting it that version 2.0 is already out, offering a way to see files that no longer exist, but are still in history. (i.e. deleted some time ago) ‘Time Machine’ sounds like the best name, but that seems to be taken.
One way to keep file history on an very active Hammer disk from eating up all the space: more snapshots. This may seem counterproductive, but disk pruning eliminates historical data between snapshots, so you can keep older data at the cost of some temporal accuracy.
From a question about mixing in a SSD and a very slow disk: swapcache can make things better, though I suggest other crazy arrangements.
If you really, really want to make sure you aren’t pulling in any parts of X when installing dports, and you’re building from source, there’s a few options you can set to keep X11 off your system. You can even go farther.
Get ready for some reading.
It’s possible, if you are several releases (years) behind, to end up with a DragonFly system that can’t compile and install the current release, due to incremental changes over time. It’s rare, but it could happen now between, say, version 3.4 and 4.0. The usual solution would be to incrementally upgrade in order, which is a lot of building and updating. The alternative is the new installworld-force option from Matthew Dillon that forces a new set of binaries into place. Use as a last resort.
This page, Varialus et Anisoptera, set up by… I’m not sure of the real name but it’s ‘varialus’ on IRC – has a detailed description of the DragonFly install process and installation of MATE, plus extra notes. I always find these sorts of cheatsheets entertaining.
Predrag Punosevac posted his writeup of using LDAP and DragonFly, which I’m noting here for the next person that needs LDAP authentication.
If you are running DragonFly, and also using nginx, the so_reuseport option will give you a significant speed boost. I’ve mentioned it before, but not this directly.
It seems pkg 1.3.6 was slightly scrambled. If you happen to have built and installed it, John Marino has special instructions on how to update to 1.3.7. If you are on DragonFly 3.8, you can follow those instructions now, and if you are on 3.9, that repo should be ready for an update in the next few days.
You should perform a full world and kernel install if on master.
Several people (including me) have been getting bit by a problem: when performing an installworld with a changed kernel, the vn kernel module is loaded, but it was built by the previous kernel and may cause problems when it doesn’t match up.
To fix that, vn is now built in, instead of being a separate module. The rescue initrd (which is what is being mounted when it has this problem) is now installed via a ‘make rescue‘ command that can wait until a successful installworld and reboot.
If you have a DragonFly system with an iwn wireless chipset, and you are having trouble connecting and running in the 5Ghz part of the spectrum only, here’s a tip: the -ht switch may fix it.
While Matthew Dillon was testing the new up-to-256-processor support for DragonFly, he added a few sysctls, one of which helps qemu performance when emulating a lot of processors. I note it here in case it’s helpful to someone else.
A note for everyone: use Hammer default on a very busy filesystem, and you will eat a lot of disk space since all file changes are recorded. (I’ve done this to myself a few times.) Francois Tigeot has a list of tips on how to keep that from happening.
Are you running a Hammer filesystem on a low-memory system? You may get some warnings. It’s possible to tweak some settings to accommodate it, or just deal.