So, now that #Emacs v29 has #SQLite support built-in, are we likely to see a new #mail #storage backend aiming to solve the problems @danluu highlighted about a decade ago with #filesystems and #email (https://danluu.com/file-consistency/)?
#emacs #sqlite #mail #storage #filesystems #email
ReiserFS is now “obsolete” in the Linux kernel and should be gone by 2025 - Enlarge / An Alameda County couple watches as investigators prepare to ... - https://arstechnica.com/?p=1964740 #filesystems #filesystem #hansreiser #reiserfs #biz #linux #tech #zfs
#zfs #tech #linux #biz #reiserfs #hansreiser #filesystem #filesystems
Ars Technica: ReiserFS is now “obsolete” in the Linux kernel and should be gone by 2025 https://arstechnica.com/?p=1964740 #Tech #arstechnica #IT #Technology #filesystems #filesystem #HansReiser #ReiserFS #Biz&IT #Linux #Tech #ZFS
#Tech #arstechnica #it #technology #filesystems #filesystem #hansreiser #reiserfs #biz #Linux #zfs
@avolkov @noracodes Such automagic boilerplate generation also hides away a bunch of details that prevents students from actually understanding what's happening.
Ask them to create a new project from scratch.
Of course the fact it's so finicky in the first place itself highlights a problem with #Java.
Also #filesystems were a mistake but that's a whole other rant of mine (#transactional filesystems would've been vaguely acceptable).
#transactional #java #filesystems
I am finally quitting using #Windows on my main machine, the motherfucker totally corrupted my #btrfs data partition while trying to install #GTAV and #lossless albums onto it. The part started "locking" itself down, started to get cheskum errors and now im about to lose about 100gb on music, roms and games because of corporate garbage. This could be also a #usererror that could've been prevented if windows made things easier for alternative #filesystems but they want market for themselves.
#filesystems #usererror #lossless #gtav #btrfs #windows
We have embarked on a complex, continuous, and not always linear operation—to migrate, where possible, the majority of our servers from #Linux to #FreeBSD. Here's why.
https://it-notes.dragas.net/2022/01/24/why-were-migrating-many-of-our-servers-from-linux-to-freebsd/
#SysAdmin #OSS #ItNotes #OperatingSystems #SysAdmin #ServerMigration #Stability #JailsVsContainers #FileSystems #ZFS #BootProcedure #NetworkStack #Performance #SystemAnalysis #BhyveVsKVM #OpenSource #Bhyve #KVM
#linux #freebsd #sysadmin #oss #itnotes #operatingsystems #servermigration #stability #jailsvscontainers #filesystems #zfs #bootprocedure #networkstack #performance #systemanalysis #bhyvevskvm #opensource #bhyve #kvm
@koakuma You know, this is yet another reason I think #fossil (which uses #SQLite) did it better than #git.
#Filesystems lack the transactionality of #databases necessary to maintain consistency, and so doing anything important on a filesystem is simply foolish.
So why are we maintaining operating systems while relying on that?
Another day, another annoyance with my field.
#fossil #sqlite #git #filesystems #databases #scm #vcs
#FileSystems #Journaling #exFAT
"#FAT and FAT variants are fairly reliable, but will occasionally corrupt a file.
#NTFS is robust and reliable, but when it breaks, it breaks hard and recovery/repair is about a 50/50 possibility. #EXT4 is very robust and almost never corrupts a file. Repair and recovery in those rare cases is almost always successful. ZFS is solid. I've never run into problems with it.
HFS+ is the worst file system ever created."
https://m.youtube.com/watch?v=_h30HBYxtws
#filesystems #journaling #exfat #fat #ntfs #ext4
Over the last few days I've made a huge progress in the implementation of a full blown FAT12 driver for my OS. It supports now all the major C file I/O functions, which are accessible from User Mode applications through System Calls. A lot of testing happened by the implementation of a simple "copy" function within the Command shell.
The next big step is the implementation of sub directories - instead of working only with a flat root directory ;-) #osdev #internals #infosec #filesystems
#filesystems #infosec #internals #osdev
Default #filesystems, but notably missing many #unix varieties of the 1980s, 1990s workstation era.
https://en.m.wikipedia.org/wiki/List_of_default_file_systems
It's pretty phenomenal how thoroughly Apple has crippled Dropbox in the latest MacOS versions. I get that Dropbox has to use Apple's APIs to sync properly (now), but to impose Apple's new hostility to traditional file systems on third-party apps is pretty appalling. And it appears to be largely all-or-nothing - you have to go out of your way to sync one file in one folder.
Wasted a good amount of time researching why I couldn't see any folders on my new Mac.
#dropbox #apple #macos #filesystems
Attempting to use bcachefs #Linux #Filesystems #blog https://kevincox.ca/2023/06/10/bcachefs-attempt/
I am thrilled that our latest paper on #data #synchronization is out and freely available! For the first time it uses our previous theoretical results to provide algorithms and a sample implementation that run in near #linear time.
This, finding a provably correct subquadratic synchronization algorithm for many #filesystems was one of the main theoretical problems in operational transformation (OT) and conflict-free replicated data types (CRDT). It's great to see our research into the algebraic theory of filesystem synchronization leading to this wonderful result, which we hope will pave the way to speed up a host of collaboration and decentralised data tools in the #cloud.
#cloud #filesystems #linear #synchronization #data
@marcel @ActionRetro This issue is OFC far less of a problen on modern systems with #Journaling #Filesystems and #Snapshots as well as #Checksumming...
So on #APFS, #ZFS & #btrfs as well as even #ext4 in #journalless-mode the lilelyhood of loosing data unless one were to bake a device is negligible.
#journalless #ext4 #btrfs #ZFS #APFS #checksumming #snapshots #filesystems #journaling
@rq The main problem is that an install doesn't come with the tools to read and write to those files.
I actually support @chozu's suggestion of #SQLite (it has those tools). #Filesystems are a failed experiment that has led to nothing but gratuitous data-loss and corruption (particularly for those suffering from unreliable infrastructure).
#Databases with some object support are a better idea.
#sqlite #filesystems #databases
@tay @root @theresnotime There's something to be said for embedding #metadata in serialized formats of some data, when not keeping it in a #database capable of handling the metadata.
#Filesystems have generally shown themselves to be an unsatisfyingly limited way to manage untyped blobs and objects.
#metadata #database #filesystems
@theresnotime My recent ranting about #databases, #filesystems & #consistency might've had to do with similar circumstances. :3
#databases #filesystems #consistency
Does anyone know where I might have heard of Koios the extended attribute file system tagging tool? Maybe a recommendation or paper? Are you using it or know more used alternatives? #digipres #FileSystems #FileTagging #InfoMgmt #EDRMS
#edrms #infomgmt #filetagging #filesystems #digipres
Yep! Now the zfs is common, it wouldn't be hard to expose it. Most of the work is already there. Batch up the work, let the user control when it gets added to the next transaction group, and get notification when it's in the ZIL.
#filesystems #transactions #databases
Hm, the more I read on #filesystems & the various failure modes of using them for object or data storage the more I'm aghast that we're tolerating filesystems without exposed #transactions.
Just ensuring something is written in the right order and actually is properly written to hardware is way too failure-prone and simple software crashes can seriously break things as it is.
It's not like #databases haven't figured out ways to do incremental writes that are still collectively transactional.
#filesystems #transactions #databases