Search results

Indeed. Thanks to the recent changes you don't even have to build uwsgi from ports now to use it with Python 3.6. Just pkg install uwsgi-py36 will do.

[i] is a BBCode for writing text in italic, so you might have to wrap the code in tags. This will hopefully show up correctly: while true do st1 = `sysctl kern.cp_times` st1.chomp! vals1 = st1.split(/ /); vals1.shift sleep 1 st2 = `sysctl kern.cp_times` st2.chomp! vals2 =...

Only on FreeBSD >= 11.0. On older versions it's still just /usr/bin:/bin

You did it the right way, however whatever comes after the @ must be an exact match for a username, so @tobik@ for tobik@ or @Nicola Mingotti for Nicola Mingotti

You can checkout top sources directly (< 1 MB): svnlite co https://svn.freebsd.org/base/head/contrib/top svnlite co https://svn.freebsd.org/base/head/usr.bin/top usr.bin-top

Since both of them clone wlan0, they cannot work if wlan0 already exists... So do a ifconfig wlan0 destroy first.

I don't think that's true. exec signal

No, portmaster uses the install target of the port in that case and it doesn't create an intermediary package. It just creates a package manifest and registers the port installation with the package database (see pkg-register). There is no compression step and no *.txz is being created.

I don't know. Probably it will. Only one way to find out...

Something like ifconfig wlan0 create wlandev bwn0 wlanaddr [ethernet mac address] up or ifconfig wlan0 create wlandev bwn0 ether [ethernet mac address] up should work.

Why not? Whatever you set on wlan0 should be passed through to the NIC.

That's normal. Just use wlan0 to address the wireless card.

Of course Emacs can do this too if you enable cua-selection-mode ;-)

Of course it does. Whatever advice we can give applies to FreeBSD but might not apply to TrueOS. TrueOS has FF58 in their ports tree fork (https://github.com/trueos/freebsd-ports) and surely it can be built from that on TrueOS...

SCFB uses the EFI framebuffer and is independent of driver support in FreeBSD itself. So yes it supports the Kabylake chipset.

Being afraid to do proper package updates is not a good sign. :( libdl.so.1 is provided (as a filter for libc.so.7) on 12.0-CURRENT to ease porting of applications that insist on linking with -ldl. If you're actually running 12.0-CURRENT then it's either 6 months out of date or you're building...

lsof uses internal kernel data structures and the sources in /usr/src need to match the kernel you're running. Is this the case? Judging by the stable/17.7 branch and commit 14a0f7db3 this appears to be OPNsense, maybe ask on their forums instead. Whatever advice we can give might not apply to...

sound's conversion layer should take care of that already and convert to a sample format that the soundcard can handle. I'm not sure why you would have to run sndiod unless you've explicitly enabled bitperfect mode or something.

If you mean using packages from pkg.FreeBSD.org for build dependencies then the answer is no.