Rimvydas Jasinskas created a loader.conf(5) hint that keeps various nata(4) devices from attaching during boot. This is super useful if it’s a device that screws up your boot process. and I think it’s also great if you get irritated having something in your dmesg every time about the device you never use, like a CDROM.
I say “one more” like I know when this saga will end. If you are using the devcpu-data port to update your processors, you’ll need to add
to your /etc/rc.conf, as Sepherosa Ziehau points out.
The regular maintenance scripts for HAMMER1 assume that it’s mounted at the time of cleanup. If you have them unmounted, they won’t go through that regular maintenance, but it’s easy enough to fix.
One side effect of Meltdown/Spectre are CPU microcode (firmware) updates. For future needs: sysutils/devcpu-data is the port that has the updates for Intel, and cpucontrol(8) is the program you run on DragonFly to add them.
I haven’t used this myself, yet, so I can’t tell you how necessary an immediate update could be – but you will probably want to use it soon.
Update: Newer CPUs might require this sizing change.
Note the non-profit link; that may be useful to you.
- BSD on New Hardware.
- BSDCAN2017 Interview with Peter Hessler, Reyk Floeter, and Henning Brauer. (video)
- Moving bacula-sd into a FreeBSD jail.
- As noted here in a comment, you can name a BSD non-profit as a recipient of the ‘commission’ from Amazon purchases. Doesn’t cost you anything, or at least Amazon keeps that part of their pricing opaque.
- OpenBSD Workstation Guide. More hardware detail than I expected… and I really like the key storage idea. (via)
- Scripts to run an OpenBSD mirror, rsync and verify. (via)
- Best BSD for PowerPC machine?
- The LLVM Memory Sanitizer support work in progress. On NetBSD. (via)
- Linux Professional Institute and BSD Certification Group Join Efforts. (via)
- Thinking of joining Mastodon? Try bsd.network!
- Which BSD systems are affected by new Intel cpu bug?
- Meltdown, aka “Dear Intel, you suck”
- Every day a bug is embargoed is actually two days. Looking at it that way, the 48 hours it took Matt Dillon to patch DragonFly turned into 367 days – and it was Google/Intel’s decision to have it that way. (via)
- MWL’s 2017 Wrap-Up. Ironically, systemd is a moneymaker for him.
Syscons now holds 10 screens back, not 4. Every few years, I really, really need that.
I just wasted an hour trying to figure out why xorg had strange output but no errors on this laptop, and it’s because I had i915_load=”YES” in /boot/loader.conf instead of i915_load=”YES” in /etc/rc.conf. I’m almost nearly sure I’ve mentioned that before, but if not: here you go.
(though if you never plan to run X, you can put it in loader.conf and everything will just work.)
(Title updated for a more correct sentence)
Noted from this commit: if you are routing over IPv6 directly to another address, the sysctl net.inet6.icmp6.nd6_onlink_ns_rfc4861 must be set to 1.
A writeup that may help someone in the future: if you decide you want to encrypt your /home directory, on DragonFly, this is how you do it.
If you are starting KDE on DragonFly, you’ll want to be sure dbus is started too. Mentioning it juuuuuust in case…
I installed a DragonFly snapshot on a Lenovo x220 last night. I went for a EFI install, even though the x220 has a “Legacy” option. When I booted, it looked like this:
It successfully booted, but once it hit the kernel load, it started printing to the top of the screen in that lovely repeating pattern you see.
Matthew Dillon helpfully pointed out that the DRM and i915 modules needed to be loaded. Hitting ‘9’ during the bootloader countdown got me to a prompt where I could type:
drm_load="YES" i915_load="YES"' kern.kms_console=1 menu
Which brought me back to the boot menu, but this time it loaded those additional modules to support the Intel video chipset – and it worked!
These lines can go in /boot/loader.conf for permanent use.
Update: accelerated X will need a different setup – see my later post.
Matthew Dillon’s been using a Kabylake NUC for a DragonFly workstation and it’s generally working out well. It’s tiny enough to lose on a desk, in my opinion. He added performance details and a screenshot. The Specific Configs page has his notes, recorded, too.
There’s a new facility in DragonFly: kcollect(8). It holds automatically-collected kernel data for about the last day, and can output to gnuplot. Note the automatic collection part; your system will always be able to tell you about weirdness – assuming that weirdness extends to one of the features kcollect tracks. Here’s some of the commits.