Foskett Services

If you think that was bad, just listen to what Theo de Raadt had to say. "NFSv4 is a gigantic joke on everyone....NFSv4 is not on our roadmap. It is a ridiculous bloated protocol which they keep adding crap to. In about a decade the people who actually start auditing it are going to see all the mistakes that it hides. "The design process followed by the NFSv4 team members matches the methodology taken by the IPV6 people. (As in, once a mistake is made, and 4 people are running the test code, it is a fact on the ground and cannot be changed again.) The result is an unrefined piece of trash." https://blog.fosketts.net/2015/02/03/vsphere-6-nfs-41-finally/

It's a reasonable way to live your life, but it's worth noting that most WiFi smart bulbs and switches can be liberated with a not-unreasonable amount of effort: https://blog.fosketts.net/2020/05/29/liberate-wi-fi-smart-bulbs-and-sw… Personally I benefit from being able to control the type of light and change it over the course of the day, and I've found a couple of uses for automatic switches which improve my life as well. Point being, these things at least can be liberated from the IoT, where we all know what the S stands for.

In the past I'd loved zfs and I still love it's physical volume management ability and it's concept of pooled storage however after years I choose to ditch it. A more informative post on that topic is this https://blog.fosketts.net/2017/07/10/zfs-best-filesystem-now/

Related, and similarly awesome: SGI screen fonts: https://njr.sabi.net/2015/11/01/sgi-screen-fonts-converted-for-os-x/ DEC VT220 font: http://blog.fosketts.net/2015/10/06/the-best-mac-os-x-terminal-font-gl… (related blog post as canonical site appears to be down)

I found a USB-C -> HDMI -> DVI-D -> monitor works for that situation. But the HDMI adapter matters. Some Dell adapters we had laying around the office are what worked for me here, but it was flakey (plug in multiple times - plug in multiple monitors in the correct order). If your monitor supports Displayport then that is the route you want to use. The MBP 2016 supports USB-C displayport alternate mode, and quality cables exist. This is pretty much bulletproof if it's an option to you. https://www.amazon.com/gp/product/B01EZH7CKO/ are the cables I bought since they were available next-day, but Monoprice also makes a quality cable. http://blog.fosketts.net/2016/10/30/2016-macbook-pro-usb-cthunderbolt-… is also a great resource to get started, if you haven't seen it yet.

In case you enjoy that terminal font[1] as much as I do, you can download it here: http://sensi.org/%7Esvo/glasstty/Glass_TTY_VT220.ttf [1] http://blog.fosketts.net/2015/10/06/the-best-mac-os-x-terminal-font-gl…

> The 787 didn't even exist when the GPS time last rolled over, so it's quite unusual to see it have this problem It's not as unusual as you'd think: https://blog.fosketts.net/2019/04/06/gps-time-rollover-failures-keep-h… There you see a nice summary of the problem and an example a Mercedes car from, if I understood, 2008 experiencing the same type of problems. Also discussed on HN: https://news.ycombinator.com/item?id=19593227 It's like having a Y2K bug software and saying "but that software didn't exist before 1900." It doesn't matter when the "epochs" are, it's just about what the design covered or didn't. I've personally fixed the trading software which failed to correctly implement the correct rollover of the decades (i.e. the transition from year 9 to year 0 in the names), not to mention Y2K. It was simply tested before only "in the same decade." It's definitely a failure in the development process, for the software that is supposed to work in some bigger time frame, and not only shortly.

Your milage may vary, but this was my source: https://blog.fosketts.net/2009/08/30/64bit-snow-leopard-kernel/

Only removed from the tegras, not the gaming cards. But yeah if you were doing OBS streaming on your jetson, then the newer hardware won't have NVENC. Normally I'd say "but nobody is doing that" but someone (was) indeed doing exactly that, lol. https://blog.fosketts.net/2020/09/10/introducing-rabbit-i-bought-a-clo… As mentioned it's probably a ton more relevant to embedded and robotics/computer-vision use-cases, which NVIDIA is really trying to push for (automotive etc). So it's still a surprising change and will be a pain for some people.

It's kind of this: https://blog.fosketts.net/2012/02/21/cubix-ers-blade-server-system/ but for Raspberry Pi's and Nvidia Jetsons.

Nice! The list of six items is a more concise read than https://blog.fosketts.net/2016/10/29/total-nightmare-usb-c-thunderbolt… , which also raised some concerns about the profound differentness of many identical looking cables.

I personally would have preferred to see some actually MTBF or MTTF data. (https://blog.fosketts.net/2011/07/06/defining-failure-mttr-mttf-mtbf/)

There's industry-wide confusion related to the USB-C plug USB-C != USB 3.1 https://www.extremetech.com/computing/197145-reversible-usb-type-c-fin… USB-C != Thunderbolt 3 http://blog.fosketts.net/2016/10/29/total-nightmare-usb-c-thunderbolt-…

Right, and that's exactly what I'm referring to. See this article that got a lot of attention: http://blog.fosketts.net/2016/10/29/total-nightmare-usb-c-thunderbolt-… Or just look at the USB-C cables sold by Apple. There should be standardized icons on the cable denoting what the cable is capable of doing.

One single cable or one single port? I thought the problem with the USB Type-C port was that there is a myriad of different USB C cables that "fit" into the port but each cable has different capabilities and thus your device may only work with a certain USB C cable. http://blog.fosketts.net/2016/10/29/total-nightmare-usb-c-thunderbolt-…

That's more USB-C than Apple. http://blog.fosketts.net/2016/10/29/total-nightmare-usb-c-thunderbolt-…

Not sure why your comment was down voted - http://blog.fosketts.net/2016/10/29/total-nightmare-usb-c-thunderbolt-…

HP machines to be specific. http://blog.fosketts.net/2011/06/06/datacenter-equipment-apple/

If you're on Mac just create a sparse encrypted DMG using Disk Utility, put it into Dropbox, bam you're done. http://blog.fosketts.net/2011/07/05/mac-dropbox-encrypted-volume/ I prefer applications to focus on one thing and do it very well, and leave other orthogonal functionality to other applications or the OS to then do the other parts very well. In this respect Quiver is well designed, I tip my hat to the author.

http://pondini.org/TM/Works3.html - seems like it. I'm not sure it'd survive Dropbox - maybe a Mac user can chime in here? Edit: It seems perfect: http://blog.fosketts.net/2011/07/05/mac-dropbox-encrypted-volume/ The closest for Linux would be ecryptfs, but I'm not sure if it splits images up.

The short answer is no. The slightly longer answer is Hell NO! Just knowing Steve's personality of "total control of the Stack" is enough to discount this. Plus, the pictures of their massive new data center http://blog.fosketts.net/2011/06/06/datacenter-equipment-apple/ do no make it sound so.

> Close that car hood citizen, there are secrets in there, don't make me taze you. Auto makers originally tried to prevent car owners from servicing their own cars or taking them to third parties to be serviced. It took a legal struggle and legislation to enshrine the rights of ownership that car owners take for granted. Or at least took for granted. A new legal struggle is turning around the right to repair modern cars that make extensive use of processors and proprietary software. http://blog.fosketts.net/2010/07/29/walled-gardens-gilded-cages-repair…

I thought the same thing when I saw both names mentioned. My understanding is CIFS is an older dialect of SMB that some servers/clients can still fall back on. Here's some key text from an article on the subject [0]: > Most people, when they use either SMB or CIFS, are talking about the same exact thing. The two are interchangeable not only in a discussion but also in application – i.e., a client speaking CIFS can talk to a server speaking SMB and vice versa. Why? Because CIFS is a form of SMB. > 1.) The CIFS implementation of SMB is rarely used these days. Under the covers, most modern storage systems no longer use CIFS, they use SMB 2 or SMB 3. In the Windows world, SMB 2 has been the standard as of Windows Vista (2006) and SMB 3 is part of Windows 8 and Windows Server 2012. > 2.) CIFS has a negative connotation amongst pedants. SMB 2 and SMB 3 are massive upgrades over the CIFS dialect, and storage architects who are near and dear to file sharing protocols don’t appreciate the misnomer. It’s kind of like calling an executive assistant a secretary. [0] https://www.varonis.com/blog/cifs-vs-smb/ [1] https://blog.fosketts.net/2012/02/16/cifs-smb/ (related)

I couldn't understand why. I found this article echoing your experiences: http://blog.fosketts.net/2016/11/26/beware-usb-c-hdmi-adapters-flaky-2… Note that it ends saying "The Good News: DisplayPort Works I purchased a couple of USB-C to DisplayPort adapters from Monoprice and am pleased to report that they both work just fine. As hoped, these simple adapters natively and passively attach Alternate Mode DisplayPort from the MacBook Pro’s integrated AMD GPU through the Intel Thunderbolt controller and connect perfectly with the monitors I’ve tried." I then Googled "active displayport hdmi converter" (to find one with a little chip inside, that actively really outputs true HDMI.) I found this page: https://www.startech.com/eu/m/AV/Displayport-Converters/DisplayPort-to… Which says "Connect an HDMI® monitor to a DisplayPort® Video Source". Since it's active, the Mac should see it as a DisplayPort device. The device then takes that signal and outputs HDMI. So while the resolution might not be perfect, I would expect this combination to work and let you connect your Mac to any HDMI device, period. Since it sounds like you have this problem a lot, if you did end up buying that device I'd be keen to know if it worked! (email in my profile.) Thanks.

There's a lot of misinformation and half-truths in this article. To pick one example, the filesystem: yes, we're sadly not using ZFS but that's in all likelihood due to licensing restrictions, not because Apple thinks HFS+ doesn't need replacing. What Apple has done is introduce CoreStorage, a "storage virtualisation system" (see link below), which beyond allowing new features to be added now (e.g. full disk encryption), will presumably allow easier migration to a new filesystem in future. And this was added in Lion. http://blog.fosketts.net/2011/08/04/mac-osx-lion-corestorage-volume-ma… As a self-described power user, I've found 10.8 to be a nice upgrade on 10.7 and worlds better than 10.6. That's not to say there aren't issues -- there are many, as there are with any OS -- but Apple currently isn't showing any sign of slowing down, with many of the issues I've experienced having been fixed in 10.8, while any power user is quite capable of disabling new consumer-facing features that don't benefit them (e.g. Launchpad, iCloud). Edit: reading further, there's a better example -- the author's criticism of Fusion Drives. I quote "Bottom line: Fusion as-is and as supplied by Apple is OK (maybe, hard to say for sure in multi-drive systems). Other than that, messing around carries some ugly risks." Not only are Apple's Fusion drives a new technology (and it's a relatively pioneering one at that, at least in the consumer space -- they're not HDDs with an SSD cache, but…