Search results

Interesting. Has been working for me without this step.

Maybe the hardware is dying? It is elderly, after all.

This would be a fun git-bisect project if I had the HW... Maybe QEMU Tulip emulation would work?

That does sound like a bug. I don't have the hardware so I can't try to reproduce it. What version of Freebsd is this under?

There was an unofficial port, but no more: https://forums.freebsd.org/threads/disaster-strikes-seamonkey-removed-from-ports-tree.71335/post-637689 It reportedly works under Linux emulation.

They definitely were because I remember being angry about slides 45 and 46, where the bullet points at the top of the slide absolutely contradict the actual data presented in the slide And Look at the data, and you'll see the Forum way outperforms all those alternative means of communications...

I use it on Mac, and the default engine is Duckduckgo. It's OK.

The Hans Reiser lesson?

Yeah, my bad. Still a whole lot more work than the simple flavorized approach baaz implemented, and still way more friction to someone that just wants to try out Xlibre without spending a bunch of time on it.

So then anything you want to run under Xlibre has to be aware of these mangled names? How's that simpler than FLAVORS?

A MITM attack for my encrypted traffic? Hard pass. https://www.paloaltonetworks.com/cyberpedia/what-is-a-next-generation-firewall-ngfw

I always run my firewalls on bare metal. Virtualization adds a layer than can have problems. For an enterprise setup, I'd look at two machines and carp interfaces. Test by powering each off by unplugging the power cable. Make sure the network hiccup is minimal if noticeable, and that the...

I just built 4 and kept them around in an array of structures: #include <sys/types.h> #include <sys/sysctl.h> #include <FL/Fl.H> #include <FL/Fl_Window.H> #include "Fl_Gauge.H" struct cbdata { char* sysctl_name; Fl_Gauge* gauge; }; void gaugecb(void* p_data) { int t_dK; //Default is...

I have only a rudimentary understanding of how the ports framework operates, but FWIW I'm convinced the FLAVORS version is the way to go right now.

This is somewhat off topic. I beg your forgiveness in advance. If you're writing something new from scratch, why not look at libtls? It was specifically designed to avoid the pitfalls and weirdness of Openssl. Note that using libtls does not force you to switch to Libressl. There's...

To expand on what Covacat and Alain have said, the "dev.aibs.0.%desc" sysctl returns the description of the aibs sensor at index 0. From the man page: This is going to be a string of characters of some arbitrary length and sysctlbyname needs a place to put them. In the code above buf is the...

Here's a 4-gauge version. It didn't turn out as nicely as I had hoped. Again unzip the sources somewhere and compile them like this: c++ -o fltk_temp $(fltk-config --cxxflags) Fl_Gauge.cxx fltk_temp.cpp $(fltk-config --ldflags) And run it like this: ./fltk_temp

Figured out a screenshot solution that doesn't drag in too many dependencies. Here's the CPU gauge from this post, and the demo from the ancient sources. I'm having fun so I'll probably try a 4-CPU version sometime today.

It looks like you use just a naked Fl_Box when you want to display a text value. I found this code in the ancient trove: Fl_Box *yzone=new Fl_Box(20,370,200,20,"Yellow Zone Info"); yzone->label("Inside the Red Line Area"); yzone->label("Outside of the Red Line Area"); Didn't try it, 'cause I...

Fl_Output is a weird read-only version of Fl_Input that looks like it'll accept user input, but does not. I really prefer the Fl_Gauge thing I found even though the code is ancient and grungy. I think it looks sweet.