Recent searches

No recent searches

Search options

Only available when logged in.
toad.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Mastodon server operated by David Troy, a tech pioneer and investigative journalist addressing threats to democracy. Thoughtful participation and discussion welcome.

Administered by:

Server stats:

214
active users

toad.social: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.4.1

#composefs

0 posts0 participants0 posts today
Timothée Ravier<p>We are bringing UKI and strong boot integrity guarantees with composefs to Bootable Containers. We demonstrated our latest progress on that front at DevConf.cz 2025: <a href="https://pretalx.devconf.info/devconf-cz-2025/talk/739KGC/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">pretalx.devconf.info/devconf-c</span><span class="invisible">z-2025/talk/739KGC/</span></a></p><p><a href="https://floss.social/tags/Fedora" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Fedora</span></a> <a href="https://floss.social/tags/BootableContainers" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BootableContainers</span></a> <a href="https://floss.social/tags/bootc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>bootc</span></a> <a href="https://floss.social/tags/UKI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UKI</span></a> <a href="https://floss.social/tags/composefs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>composefs</span></a></p>
Alex L 🕊 🇵🇸<p>WOW I didn't realize I am already using <a href="https://mastodon.social/tags/Bootc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Bootc</span></a> and <a href="https://mastodon.social/tags/ComposeFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ComposeFS</span></a> on my system.</p><p>Thanks <a href="https://mastodon.social/tags/uBlue" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>uBlue</span></a> <a href="https://mastodon.social/tags/AuroraLinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AuroraLinux</span></a> </p><p>Now let's check the status of <a href="https://mastodon.social/tags/Podman" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Podman</span></a> + ComposeFS...</p>
Alejandro Baez<p><span class="h-card" translate="no"><a href="https://snabelen.no/@hopland" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>hopland</span></a></span> this so much. 😅</p><p>It takes the whole layering approach to the next level with something like <a href="https://fosstodon.org/tags/composefs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>composefs</span></a>. Something that will be a real contender to <a href="https://fosstodon.org/tags/nix" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>nix</span></a> current design. All without necessarily require to reinvent the tool you use to packer either. Getting that repeatedly and reproducible struct from the normal built artifact. 🤯</p>
Thor A. Hopland<p>If you are a maintainer of <a href="https://snabelen.no/tags/nix" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>nix</span></a>, <a href="https://snabelen.no/tags/nixpkgs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>nixpkgs</span></a> or <a href="https://snabelen.no/tags/nixos" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>nixos</span></a>: listen up.</p><p>You've got about 2 years or so being a serious contender, until someone like <a href="https://snabelen.no/tags/lix" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>lix</span></a> or even <a href="https://snabelen.no/tags/ostree" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ostree</span></a> with <a href="https://snabelen.no/tags/ComposeFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ComposeFS</span></a> comes in and eats your lunch.</p><p>Part and parcel of that is the community, the language, the security of knowing that there is culpability and responsibility.</p><p>Linus Torvalds had to walk it off because an entire foundation told him to. If the nix "community" is beyond this, why give <a href="https://snabelen.no/tags/DeterminateSystems" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DeterminateSystems</span></a> contracts?</p>
Alex L 🕊 🇵🇸<p><span class="h-card" translate="no"><a href="https://fosstodon.org/@zeab" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>zeab</span></a></span> </p><p><a href="https://mastodon.social/tags/Podman" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Podman</span></a> is already one step further with <a href="https://mastodon.social/tags/Bootc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Bootc</span></a> and soon one more with <a href="https://mastodon.social/tags/ComposeFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ComposeFS</span></a> ;-)</p>
Alex L 🕊 🇵🇸<p><span class="h-card" translate="no"><a href="https://mastodon.social/@fidel" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>fidel</span></a></span> <span class="h-card" translate="no"><a href="https://fosstodon.org/@XeroLinux" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>XeroLinux</span></a></span> </p><p>Finally, since OSTree and Podman will support <a href="https://mastodon.social/tags/ComposeFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ComposeFS</span></a> we will have deduplicated storage between different containers and the host OS. And maybe even Flatpak since it already uses OSTree.</p><p>If hypothetically a distro uses its packages to build images for OSTree, Flatpak and containers we would have the max deduplication, resulting in a reimplementation of a traditional distro. </p><p>[...]</p>
Alex L 🕊 🇵🇸<p><span class="h-card" translate="no"><a href="https://emacs.ch/@ramin_hal9001" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>ramin_hal9001</span></a></span> </p><p>You may want to reconsider <a href="https://mastodon.social/tags/Flatpak" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Flatpak</span></a> if in the future <a href="https://mastodon.social/tags/ComposeFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ComposeFS</span></a> will allow shared storage between the OS, Flatpak apps and <a href="https://mastodon.social/tags/Podman" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Podman</span></a> containers:</p><p><a href="https://mastodon.social/@alxlg/112000758150683850" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">mastodon.social/@alxlg/1120007</span><span class="invisible">58150683850</span></a></p><p>Of course if you are happy with <a href="https://mastodon.social/tags/Guix" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Guix</span></a> keep using it, but Flatpak is not stupid, there is nothing that offers the same functionalities.</p>
Alex L 🕊 🇵🇸<p><span class="h-card" translate="no"><a href="https://social.sciences.re/@zimoun" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>zimoun</span></a></span> <span class="h-card" translate="no"><a href="https://rstats.me/@adamhsparks" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>adamhsparks</span></a></span> </p><p>In my opinion, <a href="https://mastodon.social/tags/Guix" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Guix</span></a> is an overkill for anything except computer science research. I think an approach that has better chances to succeed is reusing the OCI ecosystem and in particular using <a href="https://mastodon.social/tags/ComposeFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ComposeFS</span></a> for a per-file deduplication, that is important for large datasets. The missing piece for me it's a package manager for knowledge i.e. that links papers, datasets, source code for both calculations and documents (LaTeX, <a href="https://mastodon.social/tags/Typst" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Typst</span></a> etc) in a graph of dependencies, citations etc.</p>
Alex L 🕊 🇵🇸<p><span class="h-card" translate="no"><a href="https://framapiaf.org/@Bristow_69" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>Bristow_69</span></a></span> <span class="h-card" translate="no"><a href="https://tutut.delire.party/@flore" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>flore</span></a></span> </p><p>Let's say Flatpak uses a bit more storage and memory when apps are not perfectly aligned to each others, but at least run them with no need to integrate everything in a single graph of packages.</p><p>There is duplication between the OS and Flatpak and it may be solved in the future with <a href="https://mastodon.social/tags/ComposeFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ComposeFS</span></a>, but if you use distros like Fedora Atomic flavours or OpenSUSE MicroOS you can reduce that duplication a lot.</p><p>2/2</p>
TrendingLive feeds
About