Shakedown Social

SciPunkIn the movie Hackers (1995), a group of nerds hack into computer networks to outsmart corrupt authorities and uncover a conspiracy. The film features a mix of retro computing aesthetics, cyberpunk themes, and real-life cybersecurity concepts like sudo and root access. <a href="https://pixelfed.social/discover/tags/hackers?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#hackers</a> <a href="https://pixelfed.social/discover/tags/retro?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#retro</a> <a href="https://pixelfed.social/discover/tags/computing?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#computing</a> <a href="https://pixelfed.social/discover/tags/cybersecurity?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#cybersecurity</a> <a href="https://pixelfed.social/discover/tags/cyberpunk?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#cyberpunk</a> <a href="https://pixelfed.social/discover/tags/movies?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#movies</a> <a href="https://pixelfed.social/discover/tags/sudo?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#sudo</a> <a href="https://pixelfed.social/discover/tags/root?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#root</a> <a href="https://pixelfed.social/discover/tags/god?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#god</a> <a href="https://pixelfed.social/discover/tags/cyberspace?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#cyberspace</a> <a href="https://pixelfed.social/discover/tags/datasecurity?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#datasecurity</a> <a href="https://pixelfed.social/discover/tags/hacking?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#hacking</a> <a href="https://pixelfed.social/discover/tags/computers?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#computers</a> <a href="https://pixelfed.social/discover/tags/network?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#network</a> <a href="https://pixelfed.social/discover/tags/blackhat?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#blackhat</a> <a href="https://pixelfed.social/discover/tags/whitehat?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#whitehat</a> <a href="https://pixelfed.social/discover/tags/cyberpunkaesthetic?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#cyberpunkaesthetic</a> <a href="https://pixelfed.social/discover/tags/computers?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#computers</a> <a href="https://pixelfed.social/discover/tags/filesystem?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#filesystem</a> <a href="https://pixelfed.social/discover/tags/fisherstevens?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#fisherstevens</a> <a href="https://pixelfed.social/discover/tags/pennjillette?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#pennjillette</a>

argv minus oneI wanted to store some <a href="https://mastodon.sdf.org/tags/BorgBackup" class="mention hashtag" rel="nofollow noopener" target="_blank">#BorgBackup</a> archives on an <a href="https://mastodon.sdf.org/tags/exFAT" class="mention hashtag" rel="nofollow noopener" target="_blank">#exFAT</a> disk so that any operating system (not just <a href="https://mastodon.sdf.org/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a>) could easily read it, but Borg needs a journaling <a href="https://mastodon.sdf.org/tags/filesystem" class="mention hashtag" rel="nofollow noopener" target="_blank">#filesystem</a>. 😢In theory, there isn't any reason why journaling can't be implemented on FAT 🤔 but everybody probably doesn't consider it worth the effort.<a href="https://mastodon.sdf.org/tags/NTFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#NTFS</a> would work too, except some of the <a href="https://mastodon.sdf.org/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> machines I run Borg on are running Debian Stable, whose old kernel lacks the ntfs3 driver. 🤦‍♂️

Grumpy Old Techie 🕊️Things I like about FreeBSD: "You can tune a file system, but you cannot tune a fish."is still listed as a bug in the tunefs man page on FreeBSD 14.3 I first saw it more that 30 years ago on SunOS that was BSD based at the time.<a href="https://hostux.social/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeBSD</a> <a href="https://hostux.social/tags/filesystem" class="mention hashtag" rel="nofollow noopener" target="_blank">#filesystem</a> <a href="https://hostux.social/tags/unix" class="mention hashtag" rel="nofollow noopener" target="_blank">#unix</a> <a href="https://hostux.social/tags/sunos" class="mention hashtag" rel="nofollow noopener" target="_blank">#sunos</a>

Orhun Parmaksız 👾Found a handy CLI tool for Git >_🔍 **git-statuses** — Display the status of multiple Git repositories in a clear, tabular format.🌀 Scans directories recursively for Git repositories🦀 Written in Rust!⭐ GitHub: <a href="https://github.com/bircni/git-statuses" rel="nofollow noopener" translate="no" target="_blank">https://github.com/bircni/git-statuses</a><a href="https://fosstodon.org/tags/rustlang" class="mention hashtag" rel="nofollow noopener" target="_blank">#rustlang</a> <a href="https://fosstodon.org/tags/git" class="mention hashtag" rel="nofollow noopener" target="_blank">#git</a> <a href="https://fosstodon.org/tags/repository" class="mention hashtag" rel="nofollow noopener" target="_blank">#repository</a> <a href="https://fosstodon.org/tags/scan" class="mention hashtag" rel="nofollow noopener" target="_blank">#scan</a> <a href="https://fosstodon.org/tags/filesystem" class="mention hashtag" rel="nofollow noopener" target="_blank">#filesystem</a> <a href="https://fosstodon.org/tags/commandline" class="mention hashtag" rel="nofollow noopener" target="_blank">#commandline</a> <a href="https://fosstodon.org/tags/vcs" class="mention hashtag" rel="nofollow noopener" target="_blank">#vcs</a> <a href="https://fosstodon.org/tags/terminal" class="mention hashtag" rel="nofollow noopener" target="_blank">#terminal</a>

Ariadna VigoDon't forget that your filesystem is a database you can use as such. I've been writing a diary of sorts, where each entry is just a text file, with the current date as its filename.<a href="https://social.tchncs.de/tags/tips" class="mention hashtag" rel="nofollow noopener" target="_blank">#tips</a> <a href="https://social.tchncs.de/tags/filesystem" class="mention hashtag" rel="nofollow noopener" target="_blank">#filesystem</a> <a href="https://social.tchncs.de/tags/diary" class="mention hashtag" rel="nofollow noopener" target="_blank">#diary</a> <a href="https://social.tchncs.de/tags/sysadmin" class="mention hashtag" rel="nofollow noopener" target="_blank">#sysadmin</a>

Thorsten Leemhuis (acct. 1/4)"[…] 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" target="_blank">#XFS</a> initially reserves additional space for these files.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. […]"<a href="https://blogs.oracle.com/linux/post/du-vs-df-in-xfs" rel="nofollow noopener" translate="no" target="_blank">https://blogs.oracle.com/linux/post/du-vs-df-in-xfs</a><a href="https://hachyderm.io/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://hachyderm.io/tags/Kernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#Kernel</a> <a href="https://hachyderm.io/tags/LinuxKernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#LinuxKernel</a> <a href="https://hachyderm.io/tags/Filesystem" class="mention hashtag" rel="nofollow noopener" target="_blank">#Filesystem</a>

xoron :verified:File encryption with a browser.I've been exploring the <a href="https://infosec.exchange/tags/WebCryptoAPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebCryptoAPI</a> and I'm impressed!When combined with the <a href="https://infosec.exchange/tags/FileSystemAPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#FileSystemAPI</a>, it offers a seemingly secure way to <a href="https://infosec.exchange/tags/encrypt" class="mention hashtag" rel="nofollow noopener" target="_blank">#encrypt</a> and <a href="https://infosec.exchange/tags/store" class="mention hashtag" rel="nofollow noopener" target="_blank">#store</a> files directly on your device. Think <a href="https://infosec.exchange/tags/localstorage" class="mention hashtag" rel="nofollow noopener" target="_blank">#localstorage</a>, but with <a href="https://infosec.exchange/tags/encryption" class="mention hashtag" rel="nofollow noopener" target="_blank">#encryption</a>!I know <a href="https://infosec.exchange/tags/webapps" class="mention hashtag" rel="nofollow noopener" target="_blank">#webapps</a> can have <a href="https://infosec.exchange/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#security</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" target="_blank">#OpenSourced</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" target="_blank">#selfhosted</a> on <a href="https://infosec.exchange/tags/GitHubPages" class="mention hashtag" rel="nofollow noopener" target="_blank">#GitHubPages</a>.Live Demo: <a href="https://dim.positive-intentions.com/?path=/story/usefs--encrypted-demo" rel="nofollow noopener" translate="no" target="_blank">https://dim.positive-intentions.com/?path=/story/usefs--encrypted-demo</a>Demo Code: <a href="https://github.com/positive-intentions/dim/blob/staging/src/stories/05-Hooks-useFS.stories.js" rel="nofollow noopener" translate="no" target="_blank">https://github.com/positive-intentions/dim/blob/staging/src/stories/05-Hooks-useFS.stories.js</a>Hook Code: <a href="https://github.com/positive-intentions/dim/blob/staging/src/hooks/useFS.js" rel="nofollow noopener" translate="no" target="_blank">https://github.com/positive-intentions/dim/blob/staging/src/hooks/useFS.js</a>IMPORTANT NOTES (PLEASE READ!): * This is NOT a product. It's for <a href="https://infosec.exchange/tags/testing" class="mention hashtag" rel="nofollow noopener" target="_blank">#testing</a> and <a href="https://infosec.exchange/tags/demonstration" class="mention hashtag" rel="nofollow noopener" target="_blank">#demonstration</a> purposes only. * It has NOT been reviewed or audited. Do NOT use for sensitive data. * The "password encryption" currently uses a hardcoded password. This is for demonstration, not security. * This is NOT meant to replace robust solutions like <a href="https://infosec.exchange/tags/VeraCrypt" class="mention hashtag" rel="nofollow noopener" target="_blank">#VeraCrypt</a>. It's just a <a href="https://infosec.exchange/tags/proofofconcept" class="mention hashtag" rel="nofollow noopener" target="_blank">#proofofconcept</a> to show what's possible with <a href="https://infosec.exchange/tags/browser" class="mention hashtag" rel="nofollow noopener" target="_blank">#browser</a> <a href="https://infosec.exchange/tags/APIs" class="mention hashtag" rel="nofollow noopener" target="_blank">#APIs</a>.<a href="https://infosec.exchange/tags/Encryption" class="mention hashtag" rel="nofollow noopener" target="_blank">#Encryption</a> <a href="https://infosec.exchange/tags/Cryptography" class="mention hashtag" rel="nofollow noopener" target="_blank">#Cryptography</a> <a href="https://infosec.exchange/tags/JavaScript" class="mention hashtag" rel="nofollow noopener" target="_blank">#JavaScript</a> <a href="https://infosec.exchange/tags/Frontend" class="mention hashtag" rel="nofollow noopener" target="_blank">#Frontend</a> <a href="https://infosec.exchange/tags/Privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#Privacy</a> <a href="https://infosec.exchange/tags/Security" class="mention hashtag" rel="nofollow noopener" target="_blank">#Security</a> <a href="https://infosec.exchange/tags/WebDevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebDevelopment</a> <a href="https://infosec.exchange/tags/Coding" class="mention hashtag" rel="nofollow noopener" target="_blank">#Coding</a> <a href="https://infosec.exchange/tags/Developer" class="mention hashtag" rel="nofollow noopener" target="_blank">#Developer</a> <a href="https://infosec.exchange/tags/Tech" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tech</a> <a href="https://infosec.exchange/tags/FOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#FOSS</a> <a href="https://infosec.exchange/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a> <a href="https://infosec.exchange/tags/GitHub" class="mention hashtag" rel="nofollow noopener" target="_blank">#GitHub</a> <a href="https://infosec.exchange/tags/MastodonDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#MastodonDev</a> <a href="https://infosec.exchange/tags/Programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#Programming</a> <a href="https://infosec.exchange/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebStandards</a> <a href="https://infosec.exchange/tags/FileSystem" class="mention hashtag" rel="nofollow noopener" target="_blank">#FileSystem</a> <a href="https://infosec.exchange/tags/WebAPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebAPI</a> <a href="https://infosec.exchange/tags/ProofOfConcept" class="mention hashtag" rel="nofollow noopener" target="_blank">#ProofOfConcept</a>

Jonathan MatthewsFolks who know "rsync -F" because they already use it -- am I right in thinking that it adds these behaviours to a sync:- recursively look for .rsync-filter files in every directory in the copy source, including the top-level- apply the filters they each contain to the directory and subdirectories rooted at the same level that each file was found- exclude those .rsync-filter files from being copied to the destination Is that right? <a href="https://fosstodon.org/tags/rsync" class="mention hashtag" rel="nofollow noopener" target="_blank">#rsync</a> <a href="https://fosstodon.org/tags/sync" class="mention hashtag" rel="nofollow noopener" target="_blank">#sync</a> <a href="https://fosstodon.org/tags/data" class="mention hashtag" rel="nofollow noopener" target="_blank">#data</a> <a href="https://fosstodon.org/tags/sysadmin" class="mention hashtag" rel="nofollow noopener" target="_blank">#sysadmin</a> <a href="https://fosstodon.org/tags/filesystem" class="mention hashtag" rel="nofollow noopener" target="_blank">#filesystem</a> <a href="https://fosstodon.org/tags/filesystems" class="mention hashtag" rel="nofollow noopener" target="_blank">#filesystems</a>

OSTechNixUnderstanding the Linux /usr Merge <a href="https://floss.social/tags/filesystem" class="mention hashtag" rel="nofollow noopener" target="_blank">#filesystem</a> <a href="https://floss.social/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> <a href="https://floss.social/tags/unix" class="mention hashtag" rel="nofollow noopener" target="_blank">#unix</a> <a href="https://floss.social/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#opensource</a> <a href="https://ostechnix.com/understanding-linux-usr-merge/" rel="nofollow noopener" translate="no" target="_blank">https://ostechnix.com/understanding-linux-usr-merge/</a>

Thorsten Leemhuis (acct. 1/4)Highlights from the main <a href="https://hachyderm.io/tags/erofs" class="mention hashtag" rel="nofollow noopener" target="_blank">#erofs</a> merge for <a href="https://hachyderm.io/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> 6.16 (<a href="https://git.kernel.org/torvalds/c/79b98edf918e8146047e08817e2a42937428be02" rel="nofollow noopener" translate="no" target="_blank">https://git.kernel.org/torvalds/c/79b98edf918e8146047e08817e2a42937428be02</a>):* a `fsoffset` mount option is introduced for file-backed mounts to specify the filesystem offset in order to adapt customized container formats.* Intel QAT hardware accelerators are supported to improve DEFLATE decompression performance.<a href="https://hachyderm.io/tags/kernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#kernel</a> <a href="https://hachyderm.io/tags/LinuxKernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#LinuxKernel</a> <a href="https://hachyderm.io/tags/Linux616" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux616</a> <a href="https://hachyderm.io/tags/filesystem" class="mention hashtag" rel="nofollow noopener" target="_blank">#filesystem</a>

Thorsten Leemhuis (acct. 1/4)Highlights from the main <a href="https://hachyderm.io/tags/XFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#XFS</a> merge for <a href="https://hachyderm.io/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> 6.16 (<a href="https://git.kernel.org/torvalds/c/f83fcb87f824b0bfbf1200590cc80f05e66488a7" rel="nofollow noopener" translate="no" target="_blank">https://git.kernel.org/torvalds/c/f83fcb87f824b0bfbf1200590cc80f05e66488a7</a>): - Atomic writes for XFS - Remove experimental warnings for pNFS, scrub and parent pointers<a href="https://hachyderm.io/tags/kernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#kernel</a> <a href="https://hachyderm.io/tags/LinuxKernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#LinuxKernel</a> <a href="https://hachyderm.io/tags/Linux616" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux616</a> <a href="https://hachyderm.io/tags/Filesystem" class="mention hashtag" rel="nofollow noopener" target="_blank">#Filesystem</a>

Thorsten Leemhuis (acct. 1/4)Highlights from the main <a href="https://hachyderm.io/tags/bcachefs" class="mention hashtag" rel="nofollow noopener" target="_blank">#bcachefs</a> merge for <a href="https://hachyderm.io/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> 6.16: <a href="https://git.kernel.org/torvalds/c/522544fc71c27b4b432386c7919f71ecc79a3bfb" rel="nofollow noopener" translate="no" target="_blank">https://git.kernel.org/torvalds/c/522544fc71c27b4b432386c7919f71ecc79a3bfb</a>- Incompatible features may now be enabled at runtime, via "opts/version_upgrade" in sysfs.- Various changes to support deployable disk images- Major error message improvements for btree node reads, data reads, and elsewhere.- New option, 'rebalance_on_ac_only'.- Repair/self healing: - We can now kick off recovery passes and run them in the background if we detect errors. - Performance: - Faster snapshot deletion - Faster device removal - We're now coalescing redundant accounting updates prior to transaction commit, taking some pressure off the journal. - Stack usage improvements: All allocator state has been moved off the stack<a href="https://hachyderm.io/tags/kernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#kernel</a> <a href="https://hachyderm.io/tags/LinuxKernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#LinuxKernel</a> <a href="https://hachyderm.io/tags/Linux616" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux616</a> <a href="https://hachyderm.io/tags/Filesystem" class="mention hashtag" rel="nofollow noopener" target="_blank">#Filesystem</a>

Thorsten Leemhuis (acct. 1/4)"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" target="_blank">#Btrfs</a> changes merged for <a href="https://hachyderm.io/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> 6.16:<a href="https://git.kernel.org/torvalds/c/5e82ed5ca4b510e0ff53af1e12e94e6aa1fe5a93" rel="nofollow noopener" translate="no" target="_blank">https://git.kernel.org/torvalds/c/5e82ed5ca4b510e0ff53af1e12e94e6aa1fe5a93</a>A few highlights:Performance: - extent buffer conversion to xarray gains throughput and runtime improvements on metadata heavy operations doing writeback (sample test shows +50% throughput, -33% runtime) - extent io tree cleanups lead to performance improvements by avoiding unnecessary searches or repeated searches - more efficient extent unpinning when committing transaction (estimated run time improvement 3-5%) User visible changes: - remove standalone mount option 'nologreplay', deprecated in 5.9, replacement is 'rescue=nologreplay' - in scrub, update reporting, add back device stats message after detected errors (accidentally removed during recent refactoring) Core: - convert extent buffer radix tree to xarray - continued preparations for large folios<a href="https://hachyderm.io/tags/kernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#kernel</a> <a href="https://hachyderm.io/tags/LinuxKernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#LinuxKernel</a> <a href="https://hachyderm.io/tags/Linux616" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux616</a> <a href="https://hachyderm.io/tags/Filesystem" class="mention hashtag" rel="nofollow noopener" target="_blank">#Filesystem</a>

AptiviLinux 6.16 will see more btrfs improvementsThe 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.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).”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.You can find more about this pull request by clicking on the below button: <a class="" href="https://lore.kernel.org/lkml/cover.1747826882.git.dsterba@suse.com/T/#u" rel="nofollow noopener" target="_blank">Learn more</a> <a href="https://www.freepik.com/free-photo/happy-female-student-sitting-bench-using-laptop-outdoors_4530166.htm" rel="nofollow noopener" target="_blank">Cover image credit.</a><a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/btrfs/" target="_blank">#Btrfs</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/filesystem/" target="_blank">#Filesystem</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/linux/" target="_blank">#Linux</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/linux-kernel/" target="_blank">#LinuxKernel</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/news/" target="_blank">#news</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/tech/" target="_blank">#Tech</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/technology/" target="_blank">#Technology</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/update/" target="_blank">#update</a>

argv minus one<a href="https://fosstodon.org/@xceptn" class="u-url mention" rel="nofollow noopener" target="_blank">@xceptn</a> 🤔 Could this perhaps be fixed with a new API?Like, a new system call that checks if string A contains substring B, with whatever case-folding algorithm is in effect for folder C.<a href="https://mastodon.sdf.org/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://mastodon.sdf.org/tags/FileSystem" class="mention hashtag" rel="nofollow noopener" target="_blank">#FileSystem</a> <a href="https://social.kernel.org/users/torvalds" class="u-url mention" rel="nofollow noopener" target="_blank">@torvalds</a>

Karsten SchmidtJust added some new diagrams to describe the internals of the <a href="https://thi.ng/block-fs" rel="nofollow noopener" translate="no" target="_blank">https://thi.ng/block-fs</a> block storage & filesystem (incl. some examples) and also added/updated CLI tooling docs...<a href="https://mastodon.thi.ng/tags/ThingUmbrella" class="mention hashtag" rel="nofollow noopener" target="_blank">#ThingUmbrella</a> <a href="https://mastodon.thi.ng/tags/BlockStorage" class="mention hashtag" rel="nofollow noopener" target="_blank">#BlockStorage</a> <a href="https://mastodon.thi.ng/tags/FileSystem" class="mention hashtag" rel="nofollow noopener" target="_blank">#FileSystem</a> <a href="https://mastodon.thi.ng/tags/TypeScript" class="mention hashtag" rel="nofollow noopener" target="_blank">#TypeScript</a> <a href="https://mastodon.thi.ng/tags/JavaScript" class="mention hashtag" rel="nofollow noopener" target="_blank">#JavaScript</a> <a href="https://mastodon.thi.ng/tags/Documentation" class="mention hashtag" rel="nofollow noopener" target="_blank">#Documentation</a> <a href="https://mastodon.thi.ng/tags/Diagram" class="mention hashtag" rel="nofollow noopener" target="_blank">#Diagram</a>

MichaelI 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" target="_blank">#filesystem</a> I have my photos and videos in a folder structure on my laptop by year, trip.I don't auto backup from my <a href="https://mastodon.social/tags/iPhone" class="mention hashtag" rel="nofollow noopener" target="_blank">#iPhone</a> or <a href="https://mastodon.social/tags/Sonya6700" class="mention hashtag" rel="nofollow noopener" target="_blank">#Sonya6700</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" target="_blank">#darktable</a> / <a href="https://mastodon.social/tags/rawtherapee" class="mention hashtag" rel="nofollow noopener" target="_blank">#rawtherapee</a> / <a href="https://mastodon.social/tags/digikam" class="mention hashtag" rel="nofollow noopener" target="_blank">#digikam</a> 🧵 2/4

Karsten Schmidt<a href="https://mastodon.thi.ng/tags/ReleaseWednesday" class="mention hashtag" rel="nofollow noopener" target="_blank">#ReleaseWednesday</a> Just pushed a new version of <a href="https://thi.ng/block-fs" rel="nofollow noopener" translate="no" target="_blank">https://thi.ng/block-fs</a>, now with additional multi-command CLI tooling to convert & 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.)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...(Ps. For more context see other recent announcement: <a href="https://mastodon.thi.ng/@toxi/114264980961483146" rel="nofollow noopener" translate="no" target="_blank">https://mastodon.thi.ng/@toxi/114264980961483146</a>)<a href="https://mastodon.thi.ng/tags/ThingUmbrella" class="mention hashtag" rel="nofollow noopener" target="_blank">#ThingUmbrella</a> <a href="https://mastodon.thi.ng/tags/BlockStorage" class="mention hashtag" rel="nofollow noopener" target="_blank">#BlockStorage</a> <a href="https://mastodon.thi.ng/tags/FileSystem" class="mention hashtag" rel="nofollow noopener" target="_blank">#FileSystem</a> <a href="https://mastodon.thi.ng/tags/BlockFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#BlockFS</a> <a href="https://mastodon.thi.ng/tags/VirtualFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#VirtualFS</a> <a href="https://mastodon.thi.ng/tags/CLI" class="mention hashtag" rel="nofollow noopener" target="_blank">#CLI</a> <a href="https://mastodon.thi.ng/tags/TypeScript" class="mention hashtag" rel="nofollow noopener" target="_blank">#TypeScript</a> <a href="https://mastodon.thi.ng/tags/JavaScript" class="mention hashtag" rel="nofollow noopener" target="_blank">#JavaScript</a> <a href="https://mastodon.thi.ng/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a>

Karsten Schmidt<a href="https://mastodon.thi.ng/tags/ThingUmbrella" class="mention hashtag" rel="nofollow noopener" target="_blank">#ThingUmbrella</a> <a href="https://mastodon.thi.ng/tags/ReleaseTuesday" class="mention hashtag" rel="nofollow noopener" target="_blank">#ReleaseTuesday</a>... New package (initial alpha release):<a href="https://thi.ng/block-fs" rel="nofollow noopener" translate="no" target="_blank">https://thi.ng/block-fs</a> provides highly customizable & 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" target="_blank">#Forth</a>-style block data/editors).The default configuration provides:- arbitrarily nested directories - filenames (UTF-8) of max. 31 bytes per directory level - max. 32 owner IDs - file locking - creation/modification timestamps (64 bit) - efficient append writesCurrently 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)... The readme is currently still lacking various diagrams to illustrate the filesystem internals. I will add those ASAP...<a href="https://mastodon.thi.ng/tags/ThingUmbrella" class="mention hashtag" rel="nofollow noopener" target="_blank">#ThingUmbrella</a> <a href="https://mastodon.thi.ng/tags/FileSystem" class="mention hashtag" rel="nofollow noopener" target="_blank">#FileSystem</a> <a href="https://mastodon.thi.ng/tags/VirtualFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#VirtualFS</a> <a href="https://mastodon.thi.ng/tags/BlockStorage" class="mention hashtag" rel="nofollow noopener" target="_blank">#BlockStorage</a>

Brad LinderThe 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" target="_blank">#Windows</a> <a href="https://fosstodon.org/tags/Microsoft" class="mention hashtag" rel="nofollow noopener" target="_blank">#Microsoft</a> <a href="https://fosstodon.org/tags/ReFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#ReFS</a> <a href="https://fosstodon.org/tags/Filesystem" class="mention hashtag" rel="nofollow noopener" target="_blank">#Filesystem</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" translate="no" target="_blank">https://www.tomshardware.com/software/windows/new-advanced-filesystem-format-option-found-in-windows-11-preview-build-refs-supports-up-to-35-petabytes</a>

Recent searches

Search options

Administered by:

Server stats:

#filesystem