Search results

https://securityboulevard.com/2021/04/forescout-and-jsof-disclose-new-dns-vulnerabilities-impacting-millions-of-enterprise-and-consumer-devices/

Those days are not gone ;) Just spending my energy on other things ..

sysutils/ethname has really saved me from many headaches. It's lovely being able to do this:ethname_enable="YES" ethname_vlan0070_mac="00:50:56:88:e1:24" ifconfig_vlan0070="inet 172.16.12.44 netmask 255.255.255.0" And then see:# ifconfig vlan0070 vlan0070...

License to thrill: Ahead of v13.0, the FreeBSD team talks about Linux and the completed toolchain project that changes everything https://www-theregister-com.cdn.ampproject.org/c/s/www.theregister.com/AMP/2021/03/10/the_state_of_freebsd/

No, and there you go. TrueNAS is not FreeBSD, and any advice about TrueNAS should be answered by them. I'm sure they have power/energy settings somewhere, but they've made their own system, so they'll know best. --> https://www.truenas.com/community/tags/powerd/

Note: this is a FreeBSD-centric reply; on other derivates, YMMV! You can try powerd_enable="YES" powerd_flags="-a adaptive -b adaptive" in /etc/rc.conf and then run service powerd start. This should 'dial' the machine down to the lowest possible power usage, without responding to every event...

We have no association with the Mall (which appeares to be run by/on iXsystems nowadays). Suggestion: call. https://www.freebsdmall.com/cgi-bin/fm/company.html?id=w5eEBdov&mv_arg=mv_arg&mv_pc=2

The forums have no association with the mailing lists. However, on the list page: freebsd-www -- **OBSOLETE** FreeBSD Project Webmasters About freebsd-www **OBSOLETE** subscribe to freebsd-doc instead! This list will soon be retired. https://lists.freebsd.org/mailman/listinfo/freebsd-www

In other words, you forgot '-e' and maybe the counterpart '-d'.

https://coderwall.com/p/tlec0g/openssl-encrypted-tar-backups-for-unix-like-s

What I could find so far: https://sfconservancy.org/copyleft-compliance/principles.html FWIW.

A post on Heise Online (google-translated below) suggests this:

I will not deny that, in an era long long ago, I actually had something like this under my desk. A desk that endured much yelling because the tip of my shoe would hit that turbo button from time to time, making everything grind to a halt. Just not often enough to make it immediately clear why...

Someone pushed the 'Turbo' button on the hardware this time.

Article: https://www.phoronix.com/scan.php?page=article&item=freebsd-13-beta1 Straight to the benchmark graphs (scroll down): https://openbenchmarking.org/result/2102103-HA-FREEBSD0515&imw=1&sgm=1&imw=1

I will post this to the FreeBSD developers (private) mailing list. Not many developers actually use these forums, which are more admin/end-user orientated. You can also (and simultaneously) post this to the freebsd-drivers mailing list; see for this and possible other applicable lists...

rule 0/0 is usually the default block rule, in a ruleset that starts with e.g. block log all which is then followed by exceptions to this. You can always find those rule numbers with pfctl -sr -vv and you'll be able to cross-reference those with the output in /usr/sbin/tcpdump -l -s 0 -e -n -i...