frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Show HN: SafeClaw – a way to manage multiple Claude Code instances in containers

https://github.com/ykdojo/safeclaw
1•ykdojo•2m ago•0 comments

The Future of the Global Open-Source AI Ecosystem: From DeepSeek to AI+

https://huggingface.co/blog/huggingface/one-year-since-the-deepseek-moment-blog-3
1•gmays•2m ago•0 comments

The Evolution of the Interface

https://www.asktog.com/columns/038MacUITrends.html
1•dhruv3006•4m ago•0 comments

Azure: Virtual network routing appliance overview

https://learn.microsoft.com/en-us/azure/virtual-network/virtual-network-routing-appliance-overview
1•mariuz•4m ago•0 comments

Seedance2 – multi-shot AI video generation

https://www.genstory.app/story-template/seedance2-ai-story-generator
1•RyanMu•7m ago•1 comments

Πfs – The Data-Free Filesystem

https://github.com/philipl/pifs
1•ravenical•11m ago•0 comments

Go-busybox: A sandboxable port of busybox for AI agents

https://github.com/rcarmo/go-busybox
2•rcarmo•12m ago•0 comments

Quantization-Aware Distillation for NVFP4 Inference Accuracy Recovery [pdf]

https://research.nvidia.com/labs/nemotron/files/NVFP4-QAD-Report.pdf
1•gmays•12m ago•0 comments

xAI Merger Poses Bigger Threat to OpenAI, Anthropic

https://www.bloomberg.com/news/newsletters/2026-02-03/musk-s-xai-merger-poses-bigger-threat-to-op...
1•andsoitis•13m ago•0 comments

Atlas Airborne (Boston Dynamics and RAI Institute) [video]

https://www.youtube.com/watch?v=UNorxwlZlFk
1•lysace•14m ago•0 comments

Zen Tools

http://postmake.io/zen-list
1•Malfunction92•16m ago•0 comments

Is the Detachment in the Room? – Agents, Cruelty, and Empathy

https://hailey.at/posts/3mear2n7v3k2r
1•carnevalem•16m ago•0 comments

The purpose of Continuous Integration is to fail

https://blog.nix-ci.com/post/2026-02-05_the-purpose-of-ci-is-to-fail
1•zdw•18m ago•0 comments

Apfelstrudel: Live coding music environment with AI agent chat

https://github.com/rcarmo/apfelstrudel
1•rcarmo•19m ago•0 comments

What Is Stoicism?

https://stoacentral.com/guides/what-is-stoicism
3•0xmattf•20m ago•0 comments

What happens when a neighborhood is built around a farm

https://grist.org/cities/what-happens-when-a-neighborhood-is-built-around-a-farm/
1•Brajeshwar•20m ago•0 comments

Every major galaxy is speeding away from the Milky Way, except one

https://www.livescience.com/space/cosmology/every-major-galaxy-is-speeding-away-from-the-milky-wa...
2•Brajeshwar•20m ago•0 comments

Extreme Inequality Presages the Revolt Against It

https://www.noemamag.com/extreme-inequality-presages-the-revolt-against-it/
2•Brajeshwar•20m ago•0 comments

There's no such thing as "tech" (Ten years later)

1•dtjb•21m ago•0 comments

What Really Killed Flash Player: A Six-Year Campaign of Deliberate Platform Work

https://medium.com/@aglaforge/what-really-killed-flash-player-a-six-year-campaign-of-deliberate-p...
1•jbegley•22m ago•0 comments

Ask HN: Anyone orchestrating multiple AI coding agents in parallel?

1•buildingwdavid•23m ago•0 comments

Show HN: Knowledge-Bank

https://github.com/gabrywu-public/knowledge-bank
1•gabrywu•29m ago•0 comments

Show HN: The Codeverse Hub Linux

https://github.com/TheCodeVerseHub/CodeVerseLinuxDistro
3•sinisterMage•30m ago•2 comments

Take a trip to Japan's Dododo Land, the most irritating place on Earth

https://soranews24.com/2026/02/07/take-a-trip-to-japans-dododo-land-the-most-irritating-place-on-...
2•zdw•30m ago•0 comments

British drivers over 70 to face eye tests every three years

https://www.bbc.com/news/articles/c205nxy0p31o
42•bookofjoe•30m ago•13 comments

BookTalk: A Reading Companion That Captures Your Voice

https://github.com/bramses/BookTalk
1•_bramses•31m ago•0 comments

Is AI "good" yet? – tracking HN's sentiment on AI coding

https://www.is-ai-good-yet.com/#home
3•ilyaizen•32m ago•1 comments

Show HN: Amdb – Tree-sitter based memory for AI agents (Rust)

https://github.com/BETAER-08/amdb
1•try_betaer•33m ago•0 comments

OpenClaw Partners with VirusTotal for Skill Security

https://openclaw.ai/blog/virustotal-partnership
2•anhxuan•33m ago•0 comments

Show HN: Seedance 2.0 Release

https://seedancy2.com/
2•funnycoding•33m ago•0 comments
Open in hackernews

Finding a Successor to the FHS

https://lwn.net/SubscriberLink/1032947/67e23ce1a3f9f129/
46•firexcy•5mo ago

Comments

hulitu•5mo ago
> Last year, postmarketOS core developer Pablo Correa Gomez and a few others started an effort to move the FHS work under the freedesktop.org banner and create 4.0 of the standard

No. freedesktop.org is the place where standards go to die and CADT development takes place.

i80and•5mo ago
A little surprised that the linked systemd file-hierarchy(7) manpage makes no mention of /opt
creatonez•5mo ago
/opt/ is just a dumping ground for crap nobody can find a better location for
curt15•5mo ago
Where else would ./install-3rdparty-software.sh write to? Should it spray files all over /usr?
creatonez•5mo ago
It shouldn't do anything until the user has told it where the files should end up. It's an unpackaged program, there is no sane place to put it that doesn't have a high chance of conflicting with something else.
kelnos•5mo ago
That's only due to a lack of standardization. I think a default install to a vendor-specific directory under /opt is a sane place to put it, and there's a very low chance that would conflict with something else.

But sure, absolutely, an installer should prompt the user for an install location, and I think a default under /opt is probably among the best defaults possible, if we consider installing outside $HOME to be reasonable.

MisterTea•5mo ago
Honestly there should be no install-bs.sh and you just bind everything into the file tree as needed. At least that is how it works on Plan 9 which simplifies a lot of things like path which is just '/bin.'
JdeBP•5mo ago
You won't find it in the hier(7) manual pages on BSDs, either.

* https://man.openbsd.org/hier

* https://man.netbsd.org/hier.7

* https://man.freebsd.org/cgi/man.cgi?query=hier&sektion=7

* https://man.dragonflybsd.org/?command=hier&section=7

There was a long time when the Linux world held /opt in disfavour, because officially it required either a stock market ticker name or some other corporate identity to make a subdirectory legitimate. You can still see traces of this in the Solaris descendant operating systems, where pkginfo(5) talks about package names using corporate stock ticker names.

* https://illumos.org/man/5/pkginfo

/opt/SUNW* used to be a very familiar thing to a lot of people.

Maybe enough time has passed for anti-corporate memory to fade. Maybe there's enough corporate backing in the Linux world now to resurrect the idea regardless.

Maybe /opt/RHT* is the shape of things to come. (-:

I've never over the years seen the systemd people advocate for /opt, though.

WhyNotHugo•5mo ago
/opt is used for manually-installed software. Packages should never place files there, so it falls out-of-scope for file-hierarchy(7) or hier(7).
curt15•5mo ago
>there's far less emphasis on creating native distribution packages for third-party software in 2025. Flatpaks, Snaps, and AppImage packages seem more popular with desktop-application developers these days. A lot of server-side software is now expected to be deployed as a container—or a group of containers run in Kubernetes—rather than installed as a package.

Are CLI tools or low-level, privileged software (e.g. anything that requires root) also distributed using flatpak or snap these days?

creatonez•5mo ago
Ubuntu distributes some system daemons and even the kernel image as Snaps. The Ubuntu Server interactive installer nags you to look at a list of server software (such as nginx) to install using Snap.

Flatpak hasn't really taken the same path, it doesn't have much utility for anything other than desktop apps.

bonzini•5mo ago
There is toolbox, see https://github.com/containers/toolbox.
creatonez•5mo ago
Toolbox and Distrobox are not based on Flatpak, though. They're more just nicely packaged docker-like container tools, targeted for development use cases.
JdeBP•5mo ago
There's an awful lot of back and forth in the comments there over whether it should be a specification that defines its requirements in terms of whatever systemd programs happen to do, or whether it should be a specification with its own concrete basis that systemd is held to like everything else.
kelnos•5mo ago
It should be neither. It should be a set of rules that most people can agree on. If some of that is what systemd does, that's fine. If there are things that systemd does that most people don't agree on, something else should end up in the standard, and systemd should conform to it.

The problem is that systemd evokes some pretty visceral negative reactions in people. I still have mixed feelings about it, but, by and large, I encounter minimal real-world issues with it. Just because systemd has decided to do something that violates the older FHS3/4 standards, doesn't automatically make it a bad thing. Maybe what they're doing is a better way. Maybe not.

WhyNotHugo•5mo ago
The irony is that systemd doesn't really follow what it prescribes in file-hierarchy(7), and expects some files in the "wrong" place. Other software has (obviously) followed suit, so now we're in a world where software follows the conventions that systemd _implements_ to maintain compatibility, rather than what it _documents_.

The most obvious example that comes to mind is /usr/lib/os-release, which file-hierarchy(7) indicates should actually be in /usr/share/os-release.

kkfx•5mo ago
Honestly? We need not a successor of FHS but of filesystems, who are intimately tied package managers and installers. Zfs timidly start the change, with IPS (Image Package System) and BE (Boot Environments, as zfs clones), and we need to go much beyond that instead of wasting resources keeping up an '80s model like some do from btrfs to stratis.

We need:

- query-able storage, because search&narrow is the current way of accessing information and collecting/transcluding data is the way to go;

- easy storage management, the "rampant layer violation" of zfs we really need;

- integration of such storage to the software stack, from the OS to single packages, it's a nonsense having to "spread" archives in a taxonomy to deploy them or downloading archives to be unpacked as well for updates when we have send-able filesystems (zfs send of snapthots) and binary diff (from a snapshot "tagged version" of a fs-package to another, sent over internet).

Unfortunately we need operation people together with devs and nowadays operation is nearly disappeared. Devs alone can't understand what we need, they can't go beyond their desktops in a mass large enough to avoid a positive evolution.

ElectricalUnion•5mo ago
> - easy storage management, the "rampant layer violation" of zfs we really need;

Except in zfs you have to think if you really want that device in that pool or that vdev. I use btrfs, slow and kinda unsafe, specifically because you just specify raid1c2/raid1c3/raid1c4 and it kind of survives c-1 dead disks (until you run out of disk space and everything goes to flames).

> - integration of such storage to the software stack, from the OS to single packages, it's a nonsense having to "spread" archives in a taxonomy to deploy them or downloading archives to be unpacked as well for updates when we have send-able filesystems (zfs send of snapthots) and binary diff (from a snapshot "tagged version" of a fs-package to another, sent over internet).

We (kinda, for some very generous definitions of) have that in composefs? But I still sense even with that, you still want some resemblance of sanity in your indivual layers.

spauldo•5mo ago
Who is "we?" I certainly don't need those things. If you need to add a bunch of complexity for your use case then feel free, but for most of us it's unnecessary.
LargoLasskhyfv•5mo ago
Go Gobo! FHS is loco! ( https://gobolinux.org/at_a_glance.html )

https://jdebp.uk/FGA/slashpackage.html or some derivative would be OK, too.