FreeBSD Unix on Dell Precision M4800
I installed FreeBSD 10.3 on the laptop I recently acquired and almost eveything worked out of the box. The gigabit ethernet and wi-fi coards worked fine and by setting the BIOS to discrete graphics only, the nVidia Quadro was recognized.

I installed the binary driver from nVidia, because they support FreeBSD because they're awesome like that. The nvidia-xconfig(1) program was useful to streamline the process of getting X.org to use the Quadro.

There were a few things that did need some tewaking though. First there's the sound card. Because the quadro supports HDMI (in addition to VGA and DisplayPort), it includes an HDA-compliant sound card. This card is recognized before the primary HDA-compliant sound card in the machine, the one that's actually connected to the speakers.

I did some research and there were some suggestions about using sysctl(8) to control soundcard GPIO pins to connect the nVidia sound device to the speackers but what ultimately worked was using sysctl(8) to change the default primary sound device to the dedicated card. There were a few ways to make this happen but the one I found that actually worked was to place sysctl(8) command lines in /etc/rc.local.

First I found the device I wanted as the default:

mforde@gaz:~> cat /dev/sndstat 
Installed devices:
pcm0:  (play) default
pcm1:  (play)
pcm2:  (play) 
pcm3:  (play)

Device pcm2 was the one I wanted so I added the following lines to /etc/rc.local

sysctl hw.snd.default_unit=2
sysctl hw.snd.default_auto=2

Now when boot completes pcm2 is set to my default and sound "just works" and sndstat shows pcm2 as the default.

I found ACPI support has some weirdness as ACPI support often does. What I found was that Suspend works from console, but resume doesn't... HOWEVER After I start X ACPI suspend and resume work just fine. Normally I prefer to boot into a console and only start X if I really need it, but because I want suspend and resume to work "by default" I've enabled X to start at boot by allowing the xdm console in /etc/ttys.

But this had one last issue. See, when manually starting X, I added the -dpi 143 option to get graphics and text to be appropriately sized for my screen. XDM needed to know about this.

This probably wasn't the best place to do it, but I edited /usr/local/lib/X11/xdm/XServers and modified the call to X(7) to add the -dpi 143 option. Now when Xdm loads at start up, the DPI is set correctly.

The function keys for adjusting the screen brightness don't work; however, xbacklight(1) works just fine. Similarly the volume keys don't work but I can adjust the volume quite easily with aumix(1).

I've submitted my dmesg output to NYCBUG's dmesgd repository.

I suppose I've posted this for two reasons. The first is so I have a record of how I eventually got these little things working in case I have to do it again. The second is in case anyone has similar issues with their hardware; if they happen to stumble upon this, it might give them some hints.

[/unix] [permanent link]

X11 Mouse Cursor Themes
Starting after installimg the binary nvidia drivers on both my laptop (Quadro K1100M) and my workstation (GeForce GT 630) Blackbox was defaulting to a mouse cursor that was suboptimal, a black, notched triangle.

The settings in the Xresources for the mouse cursor theme are honored by XDM at the graphical log in, but when Blackbox or Fluxbox start, the cursor would change to the black notched triangle. TWM honors the settings in Xresources, but TWM is just a little too minimalist, even for me.

But there's a simple fix!

Create a file in your home directory (if it doesn't already exist) .icons/default/index.theme. In this file, add the following lines:

[Icon Theme]
Inherits = polarblue

where polarblue is the name of the X11 mouse cursor theme you wish to use. FreeBSD installs many of the X11 cursor sets into /usr/local/lib/X11/icons/, your Unix flavor may be different. In theory, you can also install new themes of your choosing into ~/.icons/ and use those without the need for any elevated privileges.

Additionally, there's the option of creating a .Xdefaults file in the home directory and adding the line

Xcursor.theme: polarblue

Again, where polarblue is the name of theme you want to use.

[/unix] [permanent link]

Google blocks browsers
Netmeister has an interesting blurb about experience with Google blocking various UserAgents.

From the posting:

For example, perl's LWP::UserAgent sets the agent string per default to
"libwww-perl/#.#". Google apparently doesn't like that and will not
return results to you. Setting it to something like "Mozilla/5.0 (X11;
U; NetBSD i386; en-US; rv:1.8.1.3)" would work.

Interestingly, they appear to whitelist agents, rather than blacklisting
them.

What was that about not being evil?

[/musings] [permanent link]

Take back your privacy
Recent surveys have found that 76% of [the most visited] websites in the world cotain trackers from google and 24% contain trackers from facebook. This has been reported by CNBC, PC World, The Verge, Fortune, and Breitbart.

Almost anywhere you go on the internet, they are following you, building a profile on you, and selling that information, your information, to the highest bidder. Even if you don't have a user account for google or facebook "services," they've built a profile of you using this surreptitiously collected data.

It turns out there are some steps one can take to prevent these companies from following you wherever you go. It's not perfect, but it helps a lot. First, don't use Chrome. Second, install ad-blocker plugins for your browser. Third, use your firewall.

It turns out Google and Facebook are large enough that they have their own Autonomous Systems (AS) composed of numerous subnets. Google owns AS 15169, while Facebook owns AS 32934. Using a little bit of shell, it's relatively easy to look up all the subnets owned by these companies.

whois -h whois.radb.net -- '-i origin AS32934' | grep "^route:" | awk '{print $2;}'
whois -h whois.radb.net -- '-i origin AS15169' | grep "^route:" | awk '{print $2;}'

That's a lot of subnets. Because I have different operating systems on different computers and still want to block traffic to and from all those IP addresses, I've written some simple scripts to add rules to various firewalls. I have scripts for IPFW on FreeBSD, IPTables on Linux, and the Windows Firewall that should work from XP SP3 through Windows 10. I've only tested it on Windows 7 and Windows 10, and it worked in those.

All of these scripts can be found in this directory. The IPFW and IPTables scripts are self-contained. For the Windows command shell batch files, the *ips.txt files are also needed.

I have to say, the internet looks very different with these firewall rules in place. There are noticeably fewer advertisements and pages load faster. Embedded YouTube videos and Instagram photos don't appear. Sometimes the frame disappears, sometimes you get a "failed to connect" page appearing in a frame in the middle of a page. (Yes, these rules block YouTube and Instagram; they are owned by google and facebook and reside in the subnets owned by those companies.) On a relatively rare occasion, I come across a site using some sort of javascript or css or something hosted by a machine in one of those ASs and that will be blocked. Sometimes the site handles that gracefully, sometimes it stops being functional. A small price to take back your life.

Update: Twitter has trackers on a decent amount of sites out there too, so I've added scripts to block Twitter's AS 13414 as well. Those scripts are in the same directories as the others.

[/musings] [permanent link]

5K Run for Charity
I have entered the 2008 Lincoln Tunnel Challenge to help raise money for the Special Olympics. I would appreciate it if every one could make a donation, no matter the amount.

You can make a donation by visiting http://www.kintera.org/faf/r.asp?t=4&i=259467&u=259467-208197882&e=1594945751. Any and every donation is appreciated.

Thank you.

[/musings] [permanent link]