Daniel Barlow 🚴 @telent@mastodon.social

on which note, "what are you even doing with nixwrt, Daniel?"

Glad you asked. As of the day before yesterday approximately (sqrt sod-all) but I am trying to get back into it

I ordered a second gl-ar750 so I have a dev device as well as the one that holds the family's internet access together
I am randomly refactoring stuff to make it easier to build particular parts (e.g. the kernel) from the command line than currently. I sometimes find myself building the whole monolithic image and then using binwalk to extract the component of interest, which feels suboptimal
I am wondering if I can revive the qemu target and somehow make it useful (maybe it could have emulated ethernet with a tap device so I could write tests that talk to a pppoe server, or ... I dunno ... something)

Went to rebuild nixwrt on my usual build machine and it started by compiling readelf. I think this probably means I garbage-collected the #nix store since last time I built it and therefore must build the mips toolchain/world ab initio. This in turn implies it's time to go to bed

(Another data point consistent with the hypothesis: right now it's building gcc)

btw if anyone was wondering "have you actually switched to this account" the answer is "sort of". I check this account more often than mastodon.social, and I try to remember (not always successfully) to boost whatever I write so if appears on both, but I don't have microblog.pub running in what you might call a "production" config yet. Which is to say, it's running in a random docker container and has no backups.

https://github.com/openwrt/openwrt/blob/master/target/linux/ath79/dts/qca9531_glinet_gl-ar750.dts

Oh, hey, this is good news. Linux (in OpenWRT) now has device tree support for my home router. Really need to snag another one so that I can port #nixwrt to it without losing the internet.

@dan@terse.telent.net [dan@noetbook:~]$ strace emacs 2>&1 |grep connect connect(4, {sa_family=AF_UNIX, sun_path="/var/run/nscd/socket"}, 110) = 0 connect(4, {sa_family=AF_UNIX, sun_path="/var/run/nscd/socket"}, 110) = 0 connect(5, {sa_family=AF_UNIX, sun_path=@"/tmp/.X11-unix/X0"}, 20) = 0 connect(5, {sa_family=AF_UNIX, sun_path=@"/tmp/.X11-unix/X0"}, 20) = 0 connect(5, {sa_family=AF_UNIX, sun_path="/run/user/1000/:0"}, 20) = -1 ENOENT (No such file or directory) yeah, er, right ... what?

Hello world from over here (microblog.pub test instance)

Despite a number of new features brought to the table by #Ubuntu 19.10, the headlining feature is this: it just feels really fast, even compared to Ubuntu 19.04. That comes down to dramatic improvements in #GNOME 3.34, the desktop environment used on Ubuntu. And we finally have a wealth of information detailing exactly what those are.

https://www.forbes.com/sites/jasonevangelho/2019/10/25/wondering-why-ubuntu-1910-feel-so-much-faster-heres-your-answer/#55e6fe7b3f52