How to Avoid require_once Path Confusion
Relative paths break when scripts run from new locations.
#Filesystem
Local-Only File Encryption with JavaScript.
I've been exploring the #WebCryptoAPI and I'm impressed!
When combined with the #FileSystemAPI, it offers a seemingly secure way to #encrypt and #store files directly on your device. Think #localstorage, but with #encryption!
I know #webapps can have #security vulnerabilities since the code is served over the web, so I've #OpenSourced my demo! You can check it out, and it should even work if #selfhosted on #GitHubPages.
Live Demo: https://dim.positive-intentions.com/?path=/story/usefs--encrypted-demo
Demo Code: https://github.com/positive-intentions/dim/blob/staging/src/stories/05-Hooks-useFS.stories.js
About the Dim framework:
https://positive-intentions.com/docs/category/dim
IMPORTANT NOTES (PLEASE READ!):
* This is NOT a product. It's for #testing and #demonstration 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 #VeraCrypt. It's just a #proofofconcept to show what's possible with #browser #APIs.
#Encryption #Cryptography #JavaScript #Frontend #Privacy #Security #WebDevelopment #Coding #Developer #Tech #FOSS #OpenSource #GitHub #MastodonDev #Programming #WebStandards #FileSystem #WebAPI #ProofOfConcept
Another question for Unix experts - this is a hexdump of a SunOS 4.0.1 install disk for Sun 386i systems. Does anyone recognise the file format? It looks like some sort of file system dump, but I don't think it's a variant of BSD dump(8).
The first fields seem to be (in ASCII) Access permissions, uid, and gid (and later the file/dir name).
I wrote a new blog post on my idea for a new filesystem hierarchy for Linux. Its just a toy, so don't take it too seriously. I do want to update it over time to adapt to issues and logical inconsistencies (I still can't decide where to put persist). The chances of anything coming of this are near zero, so just have fun thinking of what could be.
https://blog.ofstars.red/posts/filesystem-layout-ng/
#Linux #Filesystem #FilesystemHierarchy #FilesystemHierarchyStandard #UNIX #UNIXLike
Hue для домашнего Hadoop: Docker, CSRF и неочевидные грабли
Пятая статья цикла о построении CDC-пайплайна с нуля. HDFS и Hive работают, но управлять ими через консоль неудобно. Сегодня поднимаем веб-интерфейс Hue и разбираемся, почему в 2026 году сборка из исходников требует Python 2.7.
How to Prevent file_put_contents From Clobbering Logs
Without FILE_APPEND, each write overwrites.
@mms Let's build a #filesystem out of this. No real files, everything is inferred. No #backups needed. No drives needed. Instantly transfers to new devices. Ultimate leverage over users. Easily embeds ads everywhere. Infinite market cap. We better be quick though, I hear Microsoft is working on ads for ReFS v4!
One of my first encounters with the Beautiful BSD Operating Systems was on a machine that Loves Pepper.
It was configured to do one task and do that one task well. The machine was a file server configured to serve diverse clients with speed agility and redundancy. The machine which loved to be called ChiliBox had space for just a couple of hard drives HDDs. That meant that if you want it true redundancy, you had to connect external hard drives
Those enclosures could also be provided by the hardware vendor
The ChiliBox was a fun toy to play with
It served my clients well for a number of years where all that was needed was to swap out hard drives which were worn without losing any data the only patience the client needed to have, is to make the resilvering of the new HDD complete itself.
#BSD #freeBSD #UNIX #ChiliBox #Server #filesystem #Raid #Raid5 #technology #OpenSource
Quote from Hammer2 page
Because HAMMER2 is a block copy-on-write filesystem, the "atime" field is not supported and will typically just reflect local system in-memory caches or mtime.
The radix tree is dynamic in that each entry can dynamically control how many bits it chops off. This allows small files to be contained in just one or two levels regardless of the block seek positions. The depth of the radix tree is increased as needed via a splitting mechanism, and will also be recombined if it grows smaller. All block references are 64-bit aligned-byte-indexed references and thus portable regardless of physical sector size changes between underlying block devices.
Inodes are 1KB of which 512 bytes are used for the top-level radix tree OR 512 bytes of data. Any file less than or equal to 512 bytes stores its data directly in the inode. Files up to 256KB can be accommodated with direct inode block references.
Directory entries are hashed (semi-sorted hash algorithm), and directly embedded in the radix table's blockref structure for maximum performance. Files with very long filenames will contain a dataref, otherwise filenames are embedded in the directory entry itself. Because directory entries are hashed, seeking and lookups are able to use a radix search and no linear scan of the directory is needed.
The inode and directory entry structure is extremely well suited for any file size or directory size, from tiny to huge.
Because of the block-copy-on-write nature of the filesystem, the filesystem is able to create a snapshot trivially simply by copying the volume header's root block table (4 blockref entries). The directory topology actually starts with a SUPERROOT, and volume ROOTs are directory entries under the SUPERROOT. Though the entries are actually special-cased a bit and actually part of the root inode for each filesystem root. And since physical freeing of space is handled via a bulk meta-data scan, destroying a snapshot or volume can be done simply by wiping the inode and ignoring everything under it... the next bulkfree scan will reclaim any reclaimable space. Similarly with file deletions... the top-level data blockrefs can simply be removed. The inode can simply be removed from the radix tree.
Performance is very good. HAMMER2 uses a variable-sized block in powers of two, starting at 1KB, up to 64KB, for the last block of the file (straddling EOF). All earlier blocks in the file, if any, use 64KB blocks. The freemap is organized by domain to cluster various meta-data types together. Indirect blocks can be one of two sizes: 16KB or 64KB, allowing medium-sized files and directories to be optimally allocated. In addition, file data compression of a logical block can result in a smaller physical block. The physical layer always does 64KB I/O and can cluster the I/O on top of that.
https://www.dragonflybsd.org/hammer/
#filesystem #programming #BSD #dragonflyBSD #freeBSD #OpenSource #technology #no #FSK
Additional Reference Material
HAMMER2 Design v6 (08-Dec-2018)
#filesystem #programming #BSD #dragonflyBSD #freeBSD #OpenSource #technology #no #FSK
The amazing DragonFlyBSD has the fantastic
Hammer2 filesystem:
* Block copy-on-write filesystem
* Instant recovery on mount
* Instant snapshots
* Mounted snapshots are writable
* Automatic snapshotting can be enabled at the system level via periodic scripts
* Default Periodic also does daily bulk pass on the meta-data to free space
* Automatic compression (controllable on directory recursion and per-file basis)
* Automatic de-duplication
* Future master/slave mechanism
* Utilizes a dynamic radix tree
* 64-bit hardlink counter
* 2^63 logical file size limit
* Recursive check codes to detect corruption
* Any number of pseudo-filesystem volumes for each physical hammer2 disk image (also used by snapshots).
https://www.dragonflybsd.org/hammer/
#filesystem #programming #BSD #dragonflyBSD #freeBSD #OpenSource #technology #no #FSK
Coooooooool !! Reproducible XFS filesystem .
#linuxadmin #xfs #filesystem #opensource
https://video.fosdem.org/2026/ua2114/RAUUL9-reproducible-xfs-images.av1.webm
Coooooooool !! Reproducible XFS filesystem .
#linuxadmin #xfs #filesystem #opensource
https://video.fosdem.org/2026/ua2114/RAUUL9-reproducible-xfs-images.av1.webm
The recording of my #fosdem talk is now available!
https://fosdem.org/2026/schedule/event/RAUUL9-reproducible-xfs-images/
Peeking into /proc: turning live Linux data into evidence: https://andreafortuna.org/2026/01/19/proc-filesystem
#aurorastore
Files
https://play.google.com/store/apps/details?id=com.marc.files
Why use 3rd party file manager when there is inbuilt manager in ur android. Available on aurora store #android #freedom #filesystem
💾 The File Count Challenge 🔎
Have you ever wondered how many PDFs, images, videos, or particular kind of files you have on your device? It is the time to find out.
I am hereby proud to officially launch a Fedi-wide file count challenge, in exclusive partnership with the 2025-27 class of @xpub 👾
💁 How to participate
- Go to your main device (not mobile)
- Open the terminal
- Run
find . | grep '.pdf$' -c(on Windows:gci -r | where Name -match '\.pdf$') - Repeat the previous command, replacing “
pdf” with any file format you are interested in sharing. We suggest:jpg,mp3, andpng. 🔆 Bonus:html,js,ttf,odt,svg - Take a screenshot of the output
- Share the screenshot on the Fediverse, using the #fileCountChallenge hashtag (please, copy-paste the actual text from the terminal in the image description/alt text)
- Add your (user)name and results to the scoreboard
- 🆒 Bonus: share the story explaining why you have so many/little files for one format.
🏆 Awards
There is a secret prize for the three people who have the most PDFs, JPEGs, and HTMLs. More info to follow.
Boost, share, fork… Do whatever you want, but please have fun while doing it.
I willl keep writing updates. Yaaaaaaay ⌨️⌨️⌨️⌨️⌨️⌨️⌨️⌨️⌨️⌨️⌨️⌨️⌨️⌨️⌨️⌨️⌨️
#fileCountChallenge #fileCount #XPUB #challenge #terminal #Linux #cmd #CLI #find #grep #filesystem #file #files
Peeking into /proc: turning live Linux data into evidence: https://andreafortuna.org/2026/01/19/proc-filesystem
How to tell where a file or folder is
https://fed.brid.gy/r/https://eclecticlight.co/2026/01/23/how-to-tell-where-a-file-or-folder-is/
Client Info
Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst