HN user

steevdave

482 karma

Gentoo Linux developer since 2005. Currently working with ARM embedded machines, doing mostly kernel work, though I spend a lot of time packaging up software as well.

[ my public key: https://keybase.io/steev; my proof: https://keybase.io/steev/sigs/PGtiLgG_OUADsWHjZzy8Lv0b8v5dGABfLaGfx2jcEjw ]

Posts0
Comments147
View on HN
No posts found.

My experience with my Google home before I unplugged it is that it would randomly kick on - even in relative silence, unless the clack of a keyboard and maybe a fan whir could be misheard as "okay Google"

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.

wpa_supplicant just does the heavy lifting of connecting to the WiFi network.

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.

Raspberry Pi 4 7 years ago

Are you sure? I've worked with a myriad of ARM devices, and I would say that despite their small size, Hardkernel are one of the most responsive companies when I have had issues.

I say that as both a Gentoo and Kali ARM dev

Just about every other board out there is just as plug and play as the RPI.

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.

The lack of contributors has a lot to do with Lennart's (apologies if I misspelled his name) attitude early on in systemd's development.

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.

Maybe they added it after you read it, but when I read the post they specifically mention it's bad and provide a link to read more on why it's bad.

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.

Anything iPhone 5 or lower will not - 10.3.3 fixed one of the issues, but 2 more exist.

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.

It takes only one slip up to screw your security. One targeted attack that you don't notice because you're in a rush.

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 got my first computer job this way - I offered to work for free for the first two weeks, if it didn't work out, they got free labor for two weeks. They hired me by the third day. This was back in 2002 or so though, and I was still at home with my parents. Nowadays I could not make such an offer.

There is an ebuild for it already, although it is in an overlay on github. Probably needs cleaned up but as I don't want to install QT on the laptop I'm using, I haven't looked too much at the ebuild, just noticed a few minor issues with it (no noting that it's a prebuilt binary and to not warn for the QA issues as a result) and not using the unpacker eclass off the top of my head.

Thanks for the quick response. I'll try to find some time to look into this. I know Chromium links to libudev for input device support so that it can do things like gestures, but I don't know that LightTable supports (will support?) them. It may be possible to do away with that linking but I may have to dig into the chromium code to do it.

I'm not near any machines of mine that aren't Chromebooks. Does anyone know if the libudev.so.0 stuff is fixed? I don't see any mention of it in the change log, but I was really hoping they would have a fix for those of us not on Ubuntu so we don't have to symlink the new libudev.so.1 to so.0 just to use light table (yes other hacks exist, this was the most prevalent one...)

I have two Chromebooks. One with 3G, that runs the stable ChromeOS, and the other wifi only, runs ChromiumOS, latest ToT, mostly because I'm working on getting ChromiumOS to run on our hardware, so it's a bit easy to compare and contrast when things are working and when they aren't. It's dead simple to boot off an sdcard or USB stick. The Chrome/Chromium did a REALLY good job at making the information available.

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.

I used to work for a content filtering company. Yes child porn exists, and it's one of your worst days when these sites start popping up in what you're reviewing, no, we can't send the links to others to "prove" it exists. I no longer work there and I'm glad I don't have days like that anymore.

Well typically the driver is written by the manufacturer or, more commonly, someone who DID want access to those features. What may be useless to you, or I, may be immensely useful to someone else.

I'd be interested in it, developer mode gives access to vim and ssh, which is all I need to do my job (embedded kernel development). ChromeOS is quite decent on its own, and since it's ChromeOS it would have flash and their PDF reader on it. The only real complaint there is that their PDF reader doesn't support indexes and I usually have PDFs that are 2-5k pages so scrolling is a pain.