482 karma · joined March 9, 2011
[ my public key: https://keybase.io/steev; my proof: https://keybase.io/steev/sigs/PGtiLgG_OUADsWHjZzy8Lv0b8v5dGABfLaGfx2jcEjw ]
I would notice because it sat on my computer desk.
To be clear, I don't think it was nefarious that it would, just that I realized I wasn't using it as much as I thought I would and decided to unplug it.
The WiFi device itself is handled by the kernel's brcmfmac driver, and there is the usual firmware (also requires a .txt file) or you can use something like nexmon, which tweeks the firmware (and a patched driver to use it) for using monitor mode, injection and a few other misc things people have done with the firmware.
I say that as both a Gentoo and Kali ARM dev
I'm not saying that to downplay the RPI - the community it has around it is great, but long gone are the days of trying to get Linux running on a random arm board. And I should know, I have over 100 different arm machines at my place.
I have no idea if it has changed, as I gave up trying to get things fixed.
The one issue I still have with systemd is the way it handles the kernel's command line.
I work with Chromebooks a lot, using software that isn't ChromeOS. The cool thing is that they can use FIT images so you can load multile kernels and device tree bindings into one image. So I can use the same sdcard on the Acer tegra Chromebook, Samsung's Chromebook, as well as the ASUS Flip Chromebook. However, to boot from sdcard you have to enable developer mode. When you enable developer mode, it adds a flag to the kernel command line "debug" - systemd sees that and thinks you want systemd in debug mode (wat?) Unfortunately there is no way to override this. I've tried passing the log level as info, which sort of works, until journalctl starts, and IT parses the debug flag in the command line and ignores the flag that sets the log level to info.
No amount of explaining this helped and I (and many others who have had various issues) gave up on trying to help make systemd better.
The only workaround to this is to stop using 1 sdcard amongst all of my Chromebooks and use individual sdcards per machine that uses a u-boot built for each Chromebook that does not pass the debug flag.
I like systemd and many of it's features are helpful, but when you run into issues, it's almost always an uphill battle to fix them, even when you provide a patch.
Sure an alternative would be great but the point of the article is to get up and running with the pi-hole software so they went with the fastest install.
If you make the claims, it's on you to provide the proof, not on us to go out and search and find or not find it.
It's a subset mostly for mobile.
http://www.advanceautowire.com/mgbgtv8/ is just one that I know of. Though I only know because when I was younger, my parents had MGs, sadly my siblings all got one for graduation and I didn't. They figured I would want the computer more.
I do wish they would at least put out a 10.3.4 to fix the security issues, but I understand not putting the resources into a phone from 2012; I'm happy to at least have gotten 10.3.3 considering my Nexus 5 stopped getting updates last year and it was release in 2013.
I love my MotoX 2013, but it never got updates (Sprint model, Sprint blamed Motorola, Motorola blamed Sprint); it's succeptible to Stagefright so I can't use it anymore. And it will never receive an update for it.
As much as we use our phones and as much personal information is on them, security updates should be first and foremost.
Yes, AOSP exists for some devices, but 9 times out of 10, something breaks when using it.
When Android moves to a new way of doing audio or video, drivers stop working, and some people try to come up with shims, but as others point out. The developer of it gets a new phone and the project dies.
My Nexus 5 (November 2013) hasn't gotten a security update since October 2016. My iPhone 5 (September 2012) just got an update to 10.3.3 in July.
Android devices are notorious for being slow to get updates, if you ever get them at all.
Yeah it can be cheaper to get an Android device, and I have quite a few, but they simply aren't up to the same standards that iPhones are.
I'll probably buy the Pixel as well. The more I use ChromeOS, the more I realize how much time I waste on other crap that doesn't really help me get done what I want to do. And using ChromiumOS, there is the "dev_install" command which will set up a Gentoo chroot in /usr/local, that points to the machine that you built it on, and if you're running the devserver, you can run emerge pkgname, it will shoot it off to the server to build it, and once it's done compiling, installs in the chroot. There is also gmerge which will install ChromiumOS packages for you (e.g. A new version of the browser or maybe a newer kernel, without rebuilding everything) OR you can build a new image, hit up the Help page in settings and it will generate a diff on the server and update the entire install to the latest image. It's really an interesting setup, and I really like it.
Everything goes through gerrit, so you can even help out with version bumps and or patches fairly easily. The documentation is really good, and if you happen to hang out on IRC, the ChromiumOS developers are extremely helpful when something isn't clear, and even update the documentation for clarity.