Incidentally, that’s another illustration that retrofitting namespaces in an ambient-authority monolithic kernel is tricky.
This is in contrast with the Hurd, where per-process views are an inherent part of the design.
Incidentally, that’s another illustration that retrofitting namespaces in an ambient-authority monolithic kernel is tricky.
This is in contrast with the Hurd, where per-process views are an inherent part of the design.
Recommendation is now to disable network namespaces to mitigate vulnerabilities due to their interaction with unprivileged user namespaces:
https://www.openwall.com/lists/oss-security/2024/04/14/1
That’s a sad outcome.
The folks at arte.tv have put geolocation gates that prevent access over #Tor, but at least they have a sense of humor.
@clacke Speaking of which, the story of “UTC” is fun:
https://en.wikipedia.org/wiki/UTC#Etymology
Today it's been 10 years since the first #GNU #Guix commit! 🎂
Some of the 600+ people who made it possible wrote their story:
👉 https://guix.gnu.org/en/blog/2022/10-years-of-stories-behind-guix/
🎉 🥳 👏 #FreeSoftware #Guix10Years
@ekaitz_zarraga @Ninjatrappeur In general I’d recommend records: they’re disjoint types (so you get type checking and can’t put in a value for a nonexistent field) and they’re fast. There’s destructuring via ‘match’ (or ‘match-record’ in Guix).
Dear imperialist friend, this character is not any more “special” than those you’d find in Зеленський or احمد بن بلة.
The #GNU #Shepherd 0.9.0 is out!
👉 https://lists.gnu.org/archive/html/guix-devel/2022-04/msg00089.html
Improved logging, on-demand service startup à la inetd and systemd, concurrency through Fibers. Running on your #Guix System machine anytime now!
#Shepherd: systemd-style socket activation ✅
Now to try all that out on #Guix System and Guix Home services.
@AbbieNormal Yeah, it’ll provide better logging, possibly faster startup, and services started on demand—e.g., sshd actually started only when a client connects.
The #GNU #Shepherd finally getting concurrency via #Fibers!
https://lists.gnu.org/archive/html/guix-devel/2022-03/threads.html
Now with preliminary inetd-style service support, hopefully soon with systemd-style socket activation.
Concurrent programming with Fibers in #Guile is delightful!
@clacke @ekaitz_zarraga Yes, https://hpc.guix.info/blog/2018/01/pre-built-binaries-vs-performance/ talks about “fat binaries” and function multi-versioning, which are like you describe.
@clacke @ekaitz_zarraga True! The difference I think is that Gentoo makes reproducibility and provenance tracking harder because of that.
@ekaitz_zarraga I suspect the new instructions mostly come from extensions, in particular SIMD extensions since ~2000 (remember MMX? :-)).
They trickle in slowly as people update their hardware and software.
See also: https://hpc.guix.info/blog/2022/01/tuning-packages-for-a-cpu-micro-architecture/
TIL (in a talk on RISC-V) that, since 1978, the x86 ISA got three new instructions *per month*.
We've just published the Guix-HPC annual report!
👉 https://hpc.guix.info/blog/2022/02/guix-hpc-activity-report-2021/
See how we support #ReproducibleResearch workflows, from core #Guix work to #SoftwareHeritage support to #Jupyter integration and more.
Reason I mention this is that while hunting a bug involving Python in a relocatable pack produced by ‘guix pack’, we found that Python provides ‘os.path.normpath’, which is documented as doing the “wrong” thing—that is, “lexical” dot-dot resolution instead of what POSIX expects:
https://docs.python.org/3.11/library/os.path.html#os.path.normpath
@CodingItWrong I don’t know of any language-specific curated repo: they all seem to favor rapid growth and developer-friendliness over user-friendliness. Traditional free distros are curated, though.
Non-copyleft licenses are the norm in Rust. Nothing prevents you from choosing a copyleft license, but making that choice “excludes” you from the Rust community and there’s a strong incentive to follow the norm (e.g., see how Sequoia recently dropped its weak copyleft license.)
@CodingItWrong It excludes you in the sense that other Rust developers will say they “can’t” use your code because it has the “wrong” license.
It’s just social pressure, nobody is formally excluding anyone of course.
#Rust seems to have grown an individualist community, with all its tiny packages hosted in a non-curated repo, with its rejection of copyleft, and with its disregard of #FreeSoftware “community standards” developed by distro folks over the years.
I feel that introducing Rust right into once collectively-developed code bases at the core of GNU/Linux will have unpredictable and detrimental effects.
Chirp! is a social network. It runs on GNU social, version 2.0.1-beta0, available under the GNU Affero General Public License.
All Chirp! content and data are available under the Creative Commons Attribution 3.0 license.