Thanks for reading so closely and providing great feedback!
You are totally right on problems 1 and 2 being swapped.
For problem #5, you caught me taking too large a logical leap and making some assumptions there. Turns out the issue is just that cowsay special cases directories called `bin` (and thus treats directories called `sbin` differently)[0].
I just pushed an update to the post correcting both of these.
Thanks for pointing out `package.provided`. It does look like it could be a reasonable way to do this, but I'm not sure how exactly I'd be able to atomically swap GNU coreutils for uutils coreutils using that method?
I think I'd need to add `sys-apps/coreutils` to `package.provided`, then install uutils coreutils while telling Portage to ignore file collisions (because I'd be overwriting GNU coreutils binaries). However, that would have hidden the fact that I would have also been overwriting binaries from other packages (for example `hostname`, which is provided by `sys-apps/net-tools` in Gentoo).
For anyone interested in trying out ladder logic, I run a web app that includes a ladder logic simulator in the browser. There is a small set of lessons too.
Sorry it’s desktop only for now. I never got around to figuring out how to make the drag and drop interface work well on mobile screens, although I’d love to.
I was using ldd to investigate how nix handles dynamic linking and I was seeing some output I didn't understand. Others were asking about this on stackoverflow[0] but I wasn't able to find any explanation. After a little digging I realized what I was missing: ldd doesn't run the dynamic linker requested by the program (in its elf headers), rather it uses the "standard" dynamic linker in your environment.
Thanks for sharing! I built a similar tool (also in Rust) which allows tracing system and library calls, and could be used for this purpose. I wanted to expose the functionality both as a library and CLI, but for now I’ve only published documentation on using the CLI.
I was using I2C for the first time, as part of a brushess ESC project, and had to learn the hard way that internal (to the mcu) pull-up resistors would not work at any reasonable (for my needs) communication speed.
This post compares the performance of the circuit using the internal pull-up resistors against external 1kohm resistors, including plots showing the improved signal quality.
> Normally Luke would group the same functions together but since I don’t have debugging symbols I had to eyeball nearby addresses to guess if it’s the same place.
I really enjoyed this article, but I do have a question about this part. Why would a single function be listed at mutliple addresses?
I wrote this blog post after spending some time troubleshooting a linux process which seemed to be getting stalled, to capture a few one-liners that I found to be really useful for gathering initial informatoin about the problem.
I'm no expert on these things, so I'd appreciate any feedback on these techniques, or other alternatives!
I’ve never used Tridactyl, but I switched from vim vixen to qutebrowser and found the full browser allows a much deeper vim integration and customization than a plugin ever could.
I’d highly recommend checking out qutebrowser if you are interested in this type of thing.
The article is about an internal employee group raising concerns that the leadership team decided in favor of hosting the episodes. I’d guess the group would have similar opinions about the Eminem songs.
I could see this data being used by Facebook to argue that they are providing $n per week of value to each user, based on that being the price users demand in exchange for not using Facebook.
Of course loss aversion being what it is, humans will ask for more money in exchange for losing access to something than they ever would have paid to gain access to that thing.
You are totally right on problems 1 and 2 being swapped.
For problem #5, you caught me taking too large a logical leap and making some assumptions there. Turns out the issue is just that cowsay special cases directories called `bin` (and thus treats directories called `sbin` differently)[0].
I just pushed an update to the post correcting both of these.
[0]: https://github.com/cowsay-org/cowsay/blob/d8c459357cc2047235...