Here’s a detailed writeup from Aaron LI on how to get a DragonFly system onto an IPv6 network.
Update: He also supplied an example pf ruleset that solved some IPv6 throughput problems for his VPS.
Pulled from a longer thread: x.x.1 update instructions for DragonFly.
Probably old hat to most readers, but I like to see this documented, and the hw.ncpu ‘trick’ is nice.
I finally used up my overflow links.
The new look on undeadly.org sure is nice.
I was reminded of this thanks to the Google Calendar entry: SemiBUG is having their monthly meeting tomorrow night (the 22nd, in case that’s tonight by the time you read this), and it’s one of my favorite formats – a series of lightning talks with 2 slides, 5 minutes.
A new episode of garbage has heaved forth, with an interview of Patrick Wildt from the recent Toronto hackathon.
This is overflow from last week’s overflow.
I think I managed to avoid any theme this week.
Questions are this week’s accidental theme.
If you are running DragonFly on a Ryzen CPU, this commit will fix (work around?) a hardware bug. I have not looked at how other operating systems may be addressing it, but it may be interesting to contrast.
I should have linked this yesterday: a description of kcollect and its uses from Matthew Dillon, complete with example graph of a very busy machine.
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.