The dependency map of the program you're running states which one takes precedence and gets mapped (overlay-mounted, to be more precise) to /System/Index/bin.

So, a dependency map that contains "Foo = 1.0" would cause Foo/1.0/bin/uninstall.sh to be the one mapped to /System/Index/bin.

What a beautiful book cover. The chapters remind me of several algorithms available on SAGA GIS to handle digital elevation models, like lake filling and finding flow direction. Kudos to the authors, this is a nice resource to learn more about the topic.

Samsung's SmartSSD comes with a Xilinx FPGA accelerator that can be used to execute code without having to move data outside the device. And their open source SDK includes domain-specific routines including databases.

See https://xilinx.github.io/Vitis_Libraries/ for details on their software stack.

Hi! It isn't derived from any other distro; it's built from scratch using its own file system arrangement. The most recent release comes with GoboLinux' own init system, although we have been running some experiments with systemd as well.

Thanks. What's the name of the init system ? Any reason not to use Void's runit ? Any reason to switch to systemd ? (I am truly unopinionated on init systems,not trying to start a flame war, juste curious)

I liked the integration with binfmt_misc! There are several different approaches to bundle data files with a single executable, as the author probably knows it. My favorite one is AppImage. Even though, I've also looked into using alternative approaches to software distribution in the recent past, and ended up creating an extra section in the ELF file to store ancillary data. `objcopy --add-section <params> --set-section-flags <params>` appends the payload to the executable, and libelf can be used at some later point to retrieve the data back. Works like a charm, as long as you don't let `strip` remove unneeded sections from that executable file.

I loved the paper! The technique its authors present is more elaborated, though: they mix different sounds extracted from nature, such as birds and wind, and allow mixing different streams to create something pleasant to a sysadmin's ears. I liked this paragraph in special:

"Due to copyright limitations on existing natural sound collections, Prof. Couch has spent many hours with a Telinga parabolic nature microphone and Sony DAT or digital minidisc recorder in search of the perfect bird."

Thanks for sharing this paper!

This is really cool! It just occurred to me that the same approach would work to identify non-sequential reads from applications that access data from disk/tape. Thanks a lot for sharing this project with us :-)

Excellent point regarding their Wiki. Gentoo's wiki is a great resource, too. What I like the most is that both have distro-agnostic information that apply elsewhere.

I run GoboLinux on all machines I own. The distro provides an infrastructure for experimenting with different ideas at the filesystem and package management layers, which are activities aligned with my personal interests. I've been a core developer since its early days for a reason :)

The problems are associated with the fact it's a niche, research-oriented distro: due to the lack of man-power, one often needs to write compilation recipes for several programs (and potentially having to patch them) before being able to build and run them. Many things that are taken for granted when you run a major distro are not there.

Despite the limitations, I always have a hell of a good time developing and using the distro; it's been 18 years so far. We also have a small community of people who identify themselves with the distro's proposals and who are comfortable enough to live with its limitations. Many of them became active recipe contributors over the years.

The alternative Linux distribution is back with a new major release. The project, which is known for using a completely different filesystem hierarchy, comes with its own desktop extensions and even a fancy procedurally-generated wallpaper.