shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

250
active users

#filesystem

2 posts2 participants0 posts today
Thorsten Leemhuis (acct. 1/4)<p>"[…] we observed that the df command shows higher space utilization compared to du when many small files are copied. Over time, the outputs of both df and du converge. This happens because <a href="https://hachyderm.io/tags/XFS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>XFS</span></a> initially reserves additional space for these files.</p><p>The feature that causes this behavior is Dynamic Speculative End of File (EOF) Preallocation. This feature allows files to dynamically reserve more space to prevent fragmentation in case the file is grown later on. This blog post explores what this feature is, how it works, and how it can be beneficial for certain use cases. […]"</p><p><a href="https://blogs.oracle.com/linux/post/du-vs-df-in-xfs" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">blogs.oracle.com/linux/post/du</span><span class="invisible">-vs-df-in-xfs</span></a></p><p><a href="https://hachyderm.io/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Linux</span></a> <a href="https://hachyderm.io/tags/Kernel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Kernel</span></a> <a href="https://hachyderm.io/tags/LinuxKernel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>LinuxKernel</span></a> <a href="https://hachyderm.io/tags/Filesystem" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Filesystem</span></a></p>
xoron :verified:<p>File encryption with a browser.</p><p>I've been exploring the <a href="https://infosec.exchange/tags/WebCryptoAPI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>WebCryptoAPI</span></a> and I'm impressed!</p><p>When combined with the <a href="https://infosec.exchange/tags/FileSystemAPI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>FileSystemAPI</span></a>, it offers a seemingly secure way to <a href="https://infosec.exchange/tags/encrypt" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>encrypt</span></a> and <a href="https://infosec.exchange/tags/store" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>store</span></a> files directly on your device. Think <a href="https://infosec.exchange/tags/localstorage" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>localstorage</span></a>, but with <a href="https://infosec.exchange/tags/encryption" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>encryption</span></a>!</p><p>I know <a href="https://infosec.exchange/tags/webapps" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>webapps</span></a> can have <a href="https://infosec.exchange/tags/security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>security</span></a> vulnerabilities since the code is served over the web, so I've <a href="https://infosec.exchange/tags/OpenSourced" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenSourced</span></a> my demo! You can check it out, and it should even work if <a href="https://infosec.exchange/tags/selfhosted" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>selfhosted</span></a> on <a href="https://infosec.exchange/tags/GitHubPages" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GitHubPages</span></a>.</p><p>Live Demo: <a href="https://dim.positive-intentions.com/?path=/story/usefs--encrypted-demo" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">dim.positive-intentions.com/?p</span><span class="invisible">ath=/story/usefs--encrypted-demo</span></a></p><p>Demo Code: <a href="https://github.com/positive-intentions/dim/blob/staging/src/stories/05-Hooks-useFS.stories.js" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/positive-intentions</span><span class="invisible">/dim/blob/staging/src/stories/05-Hooks-useFS.stories.js</span></a></p><p>Hook Code: <a href="https://github.com/positive-intentions/dim/blob/staging/src/hooks/useFS.js" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/positive-intentions</span><span class="invisible">/dim/blob/staging/src/hooks/useFS.js</span></a></p><p>IMPORTANT NOTES (PLEASE READ!):<br> * This is NOT a product. It's for <a href="https://infosec.exchange/tags/testing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>testing</span></a> and <a href="https://infosec.exchange/tags/demonstration" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>demonstration</span></a> purposes only.<br> * It has NOT been reviewed or audited. Do NOT use for sensitive data.<br> * The "password encryption" currently uses a hardcoded password. This is for demonstration, not security.<br> * This is NOT meant to replace robust solutions like <a href="https://infosec.exchange/tags/VeraCrypt" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>VeraCrypt</span></a>. It's just a <a href="https://infosec.exchange/tags/proofofconcept" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>proofofconcept</span></a> to show what's possible with <a href="https://infosec.exchange/tags/browser" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>browser</span></a> <a href="https://infosec.exchange/tags/APIs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>APIs</span></a>.</p><p><a href="https://infosec.exchange/tags/Encryption" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Encryption</span></a> <a href="https://infosec.exchange/tags/Cryptography" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Cryptography</span></a> <a href="https://infosec.exchange/tags/JavaScript" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>JavaScript</span></a> <a href="https://infosec.exchange/tags/Frontend" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Frontend</span></a> <a href="https://infosec.exchange/tags/Privacy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Privacy</span></a> <a href="https://infosec.exchange/tags/Security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Security</span></a> <a href="https://infosec.exchange/tags/WebDevelopment" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>WebDevelopment</span></a> <a href="https://infosec.exchange/tags/Coding" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Coding</span></a> <a href="https://infosec.exchange/tags/Developer" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Developer</span></a> <a href="https://infosec.exchange/tags/Tech" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Tech</span></a> <a href="https://infosec.exchange/tags/FOSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>FOSS</span></a> <a href="https://infosec.exchange/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenSource</span></a> <a href="https://infosec.exchange/tags/GitHub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GitHub</span></a> <a href="https://infosec.exchange/tags/MastodonDev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>MastodonDev</span></a> <a href="https://infosec.exchange/tags/Programming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Programming</span></a> <a href="https://infosec.exchange/tags/WebStandards" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>WebStandards</span></a> <a href="https://infosec.exchange/tags/FileSystem" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>FileSystem</span></a> <a href="https://infosec.exchange/tags/WebAPI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>WebAPI</span></a> <a href="https://infosec.exchange/tags/ProofOfConcept" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ProofOfConcept</span></a></p>
Jonathan Matthews<p>Folks who know "rsync -F" because they already use it -- am I right in thinking that it adds these behaviours to a sync:</p><p>- recursively look for .rsync-filter files in every directory in the copy source, including the top-level</p><p>- apply the filters they each contain to the directory and subdirectories rooted at the same level that each file was found</p><p>- exclude those .rsync-filter files from being copied to the destination </p><p>Is that right? <a href="https://fosstodon.org/tags/rsync" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>rsync</span></a> <a href="https://fosstodon.org/tags/sync" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>sync</span></a> <a href="https://fosstodon.org/tags/data" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>data</span></a> <a href="https://fosstodon.org/tags/sysadmin" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>sysadmin</span></a> <a href="https://fosstodon.org/tags/filesystem" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>filesystem</span></a> <a href="https://fosstodon.org/tags/filesystems" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>filesystems</span></a></p>
OSTechNix<p>Understanding the Linux /usr Merge <a href="https://floss.social/tags/filesystem" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>filesystem</span></a> <a href="https://floss.social/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>linux</span></a> <a href="https://floss.social/tags/unix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>unix</span></a> <a href="https://floss.social/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>opensource</span></a> <br><a href="https://ostechnix.com/understanding-linux-usr-merge/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">ostechnix.com/understanding-li</span><span class="invisible">nux-usr-merge/</span></a></p>
Thorsten Leemhuis (acct. 1/4)<p>Highlights from the main <a href="https://hachyderm.io/tags/erofs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>erofs</span></a> merge for <a href="https://hachyderm.io/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Linux</span></a> 6.16 (<a href="https://git.kernel.org/torvalds/c/79b98edf918e8146047e08817e2a42937428be02" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">git.kernel.org/torvalds/c/79b9</span><span class="invisible">8edf918e8146047e08817e2a42937428be02</span></a>):</p><p>* a `fsoffset` mount option is introduced for file-backed mounts to specify the filesystem offset in order to adapt customized container formats.</p><p>* Intel QAT hardware accelerators are supported to improve DEFLATE decompression performance.</p><p><a href="https://hachyderm.io/tags/kernel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>kernel</span></a> <a href="https://hachyderm.io/tags/LinuxKernel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>LinuxKernel</span></a> <a href="https://hachyderm.io/tags/Linux616" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Linux616</span></a> <a href="https://hachyderm.io/tags/filesystem" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>filesystem</span></a></p>
Thorsten Leemhuis (acct. 1/4)<p>Highlights from the main <a href="https://hachyderm.io/tags/XFS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>XFS</span></a> merge for <a href="https://hachyderm.io/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Linux</span></a> 6.16 (<a href="https://git.kernel.org/torvalds/c/f83fcb87f824b0bfbf1200590cc80f05e66488a7" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">git.kernel.org/torvalds/c/f83f</span><span class="invisible">cb87f824b0bfbf1200590cc80f05e66488a7</span></a>):</p><p> - Atomic writes for XFS</p><p> - Remove experimental warnings for pNFS, scrub and parent pointers</p><p><a href="https://hachyderm.io/tags/kernel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>kernel</span></a> <a href="https://hachyderm.io/tags/LinuxKernel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>LinuxKernel</span></a> <a href="https://hachyderm.io/tags/Linux616" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Linux616</span></a> <a href="https://hachyderm.io/tags/Filesystem" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Filesystem</span></a></p>
Thorsten Leemhuis (acct. 1/4)<p>Highlights from the main <a href="https://hachyderm.io/tags/bcachefs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>bcachefs</span></a> merge for <a href="https://hachyderm.io/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Linux</span></a> 6.16: <a href="https://git.kernel.org/torvalds/c/522544fc71c27b4b432386c7919f71ecc79a3bfb" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">git.kernel.org/torvalds/c/5225</span><span class="invisible">44fc71c27b4b432386c7919f71ecc79a3bfb</span></a></p><p>- Incompatible features may now be enabled at runtime, via "opts/version_upgrade" in sysfs.</p><p>- Various changes to support deployable disk images</p><p>- Major error message improvements for btree node reads, data reads, and elsewhere.</p><p>- New option, 'rebalance_on_ac_only'.</p><p>- Repair/self healing:</p><p> - We can now kick off recovery passes and run them in the background if we detect errors. </p><p>- Performance:</p><p> - Faster snapshot deletion<br> <br> - Faster device removal<br> <br> - We're now coalescing redundant accounting updates prior to transaction commit, taking some pressure off the journal.<br> <br> - Stack usage improvements: All allocator state has been moved off the stack</p><p><a href="https://hachyderm.io/tags/kernel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>kernel</span></a> <a href="https://hachyderm.io/tags/LinuxKernel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>LinuxKernel</span></a> <a href="https://hachyderm.io/tags/Linux616" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Linux616</span></a> <a href="https://hachyderm.io/tags/Filesystem" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Filesystem</span></a></p>
Thorsten Leemhuis (acct. 1/4)<p>"some performance improvements and one minor mount option update" are among the main <a href="https://hachyderm.io/tags/Btrfs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Btrfs</span></a> changes merged for <a href="https://hachyderm.io/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Linux</span></a> 6.16:</p><p><a href="https://git.kernel.org/torvalds/c/5e82ed5ca4b510e0ff53af1e12e94e6aa1fe5a93" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">git.kernel.org/torvalds/c/5e82</span><span class="invisible">ed5ca4b510e0ff53af1e12e94e6aa1fe5a93</span></a></p><p>A few highlights:</p><p>Performance:<br> <br>- extent buffer conversion to xarray gains throughput and runtime improvements on metadata heavy operations doing writeback (sample test shows +50% throughput, -33% runtime)<br> <br>- extent io tree cleanups lead to performance improvements by avoiding unnecessary searches or repeated searches<br> <br>- more efficient extent unpinning when committing transaction (estimated run time improvement 3-5%)<br> <br>User visible changes:<br> <br>- remove standalone mount option 'nologreplay', deprecated in 5.9, replacement is 'rescue=nologreplay'<br> <br>- in scrub, update reporting, add back device stats message after detected errors (accidentally removed during recent refactoring)<br> <br>Core:<br> <br>- convert extent buffer radix tree to xarray<br> <br>- continued preparations for large folios</p><p><a href="https://hachyderm.io/tags/kernel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>kernel</span></a> <a href="https://hachyderm.io/tags/LinuxKernel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>LinuxKernel</span></a> <a href="https://hachyderm.io/tags/Linux616" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Linux616</span></a> <a href="https://hachyderm.io/tags/Filesystem" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Filesystem</span></a></p>
Aptivi<p><strong>Linux 6.16 will see more btrfs&nbsp;improvements</strong></p><p>The btrfs filesystem in Linux 6.16 has undergone many improvements that make its performance faster than before. It has already been improved across Linux releases, but the upcoming version of Linux sees even more improvements to this filesystem. Any system that uses this filesystem can now benefit from those improvements.</p><p>The buffer conversion work underwent some throughput and runtime improvements for metadata heavy operations, backed by several commits in a pull request made to the 6.16 branch, such as “extent buffer conversion to xarray gains throughput and runtime improvements on metadata heavy operations doing writeback (sample test shows +50% throughput, -33% runtime).”</p><p>The tree cleanups have been improved to avoid repeated or unnecessary searches. This improves the I/O performance, should any operation rely on tree cleanups. As for committing transactions, the extent unpinning action has become more efficient than before, yielding a 3-5% performance improvement in runtime.</p><p>You can find more about this pull request by clicking on the below button:</p> <a class="" href="https://lore.kernel.org/lkml/cover.1747826882.git.dsterba@suse.com/T/#u" rel="nofollow noopener noreferrer" target="_blank">Learn more</a> <p><a href="https://www.freepik.com/free-photo/happy-female-student-sitting-bench-using-laptop-outdoors_4530166.htm" rel="nofollow noopener noreferrer" target="_blank">Cover image credit.</a></p><p><span></span></p><p><a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/btrfs/" target="_blank">#Btrfs</a> <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/filesystem/" target="_blank">#Filesystem</a> <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/linux/" target="_blank">#Linux</a> <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/linux-kernel/" target="_blank">#LinuxKernel</a> <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/news/" target="_blank">#news</a> <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/tech/" target="_blank">#Tech</a> <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/technology/" target="_blank">#Technology</a> <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/update/" target="_blank">#update</a></p>
argv minus one<p><span class="h-card"><a href="https://fosstodon.org/@xceptn" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>xceptn</span></a></span> </p><p>🤔 Could this perhaps be fixed with a new API?</p><p>Like, a new system call that checks if string A contains substring B, with whatever case-folding algorithm is in effect for folder C.</p><p><a href="https://mastodon.sdf.org/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Linux</span></a> <a href="https://mastodon.sdf.org/tags/FileSystem" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>FileSystem</span></a> <span class="h-card"><a href="https://social.kernel.org/users/torvalds" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>torvalds</span></a></span></p>
Karsten Schmidt<p>Just added some new diagrams to describe the internals of the <a href="https://thi.ng/block-fs" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">thi.ng/block-fs</span><span class="invisible"></span></a> block storage &amp; filesystem (incl. some examples) and also added/updated CLI tooling docs...</p><p><a href="https://mastodon.thi.ng/tags/ThingUmbrella" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ThingUmbrella</span></a> <a href="https://mastodon.thi.ng/tags/BlockStorage" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BlockStorage</span></a> <a href="https://mastodon.thi.ng/tags/FileSystem" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>FileSystem</span></a> <a href="https://mastodon.thi.ng/tags/TypeScript" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TypeScript</span></a> <a href="https://mastodon.thi.ng/tags/JavaScript" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>JavaScript</span></a> <a href="https://mastodon.thi.ng/tags/Documentation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Documentation</span></a> <a href="https://mastodon.thi.ng/tags/Diagram" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Diagram</span></a></p>
Michael<p>I have found that all of the "solutions" I've looked at are just locking you into some more specific ecosystem, so went back to the revolutionary idea of using the <a href="https://mastodon.social/tags/filesystem" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>filesystem</span></a> I have my photos and videos in a folder structure on my laptop by year, trip.</p><p>I don't auto backup from my <a href="https://mastodon.social/tags/iPhone" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>iPhone</span></a> or <a href="https://mastodon.social/tags/Sonya6700" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Sonya6700</span></a> anymore, that really just synced a load of cruft I had to delete, or pay to store. I move photos I want to my laptop, where I adjust and edit them in <a href="https://mastodon.social/tags/darktable" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>darktable</span></a> / <a href="https://mastodon.social/tags/rawtherapee" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>rawtherapee</span></a> / <a href="https://mastodon.social/tags/digikam" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>digikam</span></a> </p><p>🧵 2/4</p>
Karsten Schmidt<p><a href="https://mastodon.thi.ng/tags/ReleaseWednesday" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ReleaseWednesday</span></a> Just pushed a new version of <a href="https://thi.ng/block-fs" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">thi.ng/block-fs</span><span class="invisible"></span></a>, now with additional multi-command CLI tooling to convert &amp; bundle a local file system tree into a single block-based binary blob (e.g. for bundling assets, or distributing a virtual filesystem as part of a web app, or for snapshot testing, or as bridge for WASM interop etc.)</p><p>Also new, the main API now includes a `.readAsObjectURL()` method to wrap files as URLs to binary blobs with associated MIME types, thereby making it trivial to use the virtual filesystem for sourcing stored images and other assets for direct use in the browser...</p><p>(Ps. For more context see other recent announcement: <a href="https://mastodon.thi.ng/@toxi/114264980961483146" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">mastodon.thi.ng/@toxi/11426498</span><span class="invisible">0961483146</span></a>)</p><p><a href="https://mastodon.thi.ng/tags/ThingUmbrella" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ThingUmbrella</span></a> <a href="https://mastodon.thi.ng/tags/BlockStorage" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BlockStorage</span></a> <a href="https://mastodon.thi.ng/tags/FileSystem" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>FileSystem</span></a> <a href="https://mastodon.thi.ng/tags/BlockFS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BlockFS</span></a> <a href="https://mastodon.thi.ng/tags/VirtualFS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>VirtualFS</span></a> <a href="https://mastodon.thi.ng/tags/CLI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CLI</span></a> <a href="https://mastodon.thi.ng/tags/TypeScript" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TypeScript</span></a> <a href="https://mastodon.thi.ng/tags/JavaScript" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>JavaScript</span></a> <a href="https://mastodon.thi.ng/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenSource</span></a></p>
Karsten Schmidt<p><a href="https://mastodon.thi.ng/tags/ThingUmbrella" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ThingUmbrella</span></a> <a href="https://mastodon.thi.ng/tags/ReleaseTuesday" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ReleaseTuesday</span></a>... New package (initial alpha release):</p><p><a href="https://thi.ng/block-fs" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">thi.ng/block-fs</span><span class="invisible"></span></a> provides highly customizable &amp; extensible block-based storage with an optional hierarchical filesystem layer. This is useful everywhere you might need virtual filesystem, though the storage providers can also be used without the filesystem layer (e.g. for <a href="https://mastodon.thi.ng/tags/Forth" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Forth</span></a>-style block data/editors).</p><p>The default configuration provides:</p><p>- arbitrarily nested directories<br>- filenames (UTF-8) of max. 31 bytes per directory level<br>- max. 32 owner IDs<br>- file locking<br>- creation/modification timestamps (64 bit)<br>- efficient append writes</p><p>Currently included storage providers: TypedArray-based in-memory and host filesystem based file storage (one block per file). More are planned (e.g. IndexedDB, remote endpoint)... </p><p>The readme is currently still lacking various diagrams to illustrate the filesystem internals. I will add those ASAP...</p><p><a href="https://mastodon.thi.ng/tags/ThingUmbrella" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ThingUmbrella</span></a> <a href="https://mastodon.thi.ng/tags/FileSystem" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>FileSystem</span></a> <a href="https://mastodon.thi.ng/tags/VirtualFS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>VirtualFS</span></a> <a href="https://mastodon.thi.ng/tags/BlockStorage" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BlockStorage</span></a></p>
Brad Linder<p>The latest Windows Insider preview builds add support for the ReFS file system, with support for disk partitions up to 35 petabytes. There's no support for bootable ReFS media or removable storage though. <a href="https://fosstodon.org/tags/Windows" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Windows</span></a> <a href="https://fosstodon.org/tags/Microsoft" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Microsoft</span></a> <a href="https://fosstodon.org/tags/ReFS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ReFS</span></a> <a href="https://fosstodon.org/tags/Filesystem" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Filesystem</span></a> <a href="https://www.tomshardware.com/software/windows/new-advanced-filesystem-format-option-found-in-windows-11-preview-build-refs-supports-up-to-35-petabytes" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">tomshardware.com/software/wind</span><span class="invisible">ows/new-advanced-filesystem-format-option-found-in-windows-11-preview-build-refs-supports-up-to-35-petabytes</span></a></p>
ocean :blobcat:<p>What’s your recommended <a href="https://mastodon.social/tags/filesystem" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>filesystem</span></a> for <a href="https://mastodon.social/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>linux</span></a> desktops and Linux <a href="https://mastodon.social/tags/servers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>servers</span></a> ?</p>
Khurram Wadee ✅<p>I managed to create an <a href="https://mastodon.org.uk/tags/encrypted" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>encrypted</span></a> <a href="https://mastodon.org.uk/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Linux</span></a> <a href="https://mastodon.org.uk/tags/Filesystem" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Filesystem</span></a> on a <a href="https://mastodon.org.uk/tags/USBStick" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>USBStick</span></a>. The reason I wanted this is that I want to back up some directories, which contain secure information and also <a href="https://mastodon.org.uk/tags/NTFS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>NTFS</span></a>, the one that comes on most drives, doesn’t know how to handle <a href="https://mastodon.org.uk/tags/SymbolicLinks" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SymbolicLinks</span></a> properly. I don’t need or want to share the stick with any non-Linux machines.</p><p><a href="https://mastodon.org.uk/tags/GNU" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GNU</span></a> <a href="https://mastodon.org.uk/tags/FreeSoftware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>FreeSoftware</span></a> <a href="https://mastodon.org.uk/tags/LUKS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>LUKS</span></a></p>
IT News<p>Make a Secret File Stash In The Slack Space - Disk space is allocated in clusters of a certain size. When a file is written to d... - <a href="https://hackaday.com/2025/02/10/make-a-secret-file-stash-in-the-slack-space/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">hackaday.com/2025/02/10/make-a</span><span class="invisible">-secret-file-stash-in-the-slack-space/</span></a> <a href="https://schleuss.online/tags/softwarehacks" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>softwarehacks</span></a> <a href="https://schleuss.online/tags/linuxhacks" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>linuxhacks</span></a> <a href="https://schleuss.online/tags/filesystem" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>filesystem</span></a> <a href="https://schleuss.online/tags/slackspace" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>slackspace</span></a> <a href="https://schleuss.online/tags/cluster" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cluster</span></a> <a href="https://schleuss.online/tags/secret" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>secret</span></a></p>
OSTechNix<p>Understanding the Linux /proc Filesystem: A Beginners Guide <a href="https://floss.social/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Linux</span></a> <a href="https://floss.social/tags/Proc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Proc</span></a> <a href="https://floss.social/tags/Filesystem" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Filesystem</span></a> <a href="https://floss.social/tags/Linuxcommands" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Linuxcommands</span></a> <a href="https://floss.social/tags/Linuxbasics" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Linuxbasics</span></a> <a href="https://floss.social/tags/Linuxhowto" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Linuxhowto</span></a> <br><a href="https://ostechnix.com/linux-proc-filesystem/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">ostechnix.com/linux-proc-files</span><span class="invisible">ystem/</span></a></p>
Different Than<p>In old cowboy <a href="https://infosec.exchange/tags/books" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>books</span></a> I read as a kid there were people who had lots of <a href="https://infosec.exchange/tags/skills" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>skills</span></a>--saddling horses, caring for livestock, fixing fences, maintaining tools, cooking on the trail, harnessing oxen, repairing wagons and barrels, etc. They were always in demand and someone always needed what they were doing.</p><p>I think people who understand file systems, network protocols, a couple of coding languages, graphics, etc. are kind of like that, now.</p><p><a href="https://infosec.exchange/tags/tech" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>tech</span></a> <a href="https://infosec.exchange/tags/useful" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>useful</span></a> <a href="https://infosec.exchange/tags/polymath" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>polymath</span></a> <a href="https://infosec.exchange/tags/modern" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>modern</span></a> <a href="https://infosec.exchange/tags/filesystem" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>filesystem</span></a> <a href="https://infosec.exchange/tags/coding" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>coding</span></a> <a href="https://infosec.exchange/tags/networking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>networking</span></a> <a href="https://infosec.exchange/tags/network" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>network</span></a></p>