#vfs — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #vfs, aggregated by home.social.
-
🤔 So you're saying #SQLite isn't just for your aunt's recipe app anymore? This article's deep dive into #WAL, #VFS, and other buzzwords is about as riveting as watching paint dry, but now with added latency! 🤷♂️
https://micrologics.org/blog/sqlite-in-production-optimizing-wal-mode-concurrency-and-vfs-layers-for-low-latency-app-servers #database #performance #latency #techbuzzwords #HackerNews #ngated -
SQLite in Production: Optimizing WAL Mode, Concurrency, and VFS Layers
Comments: https://news.ycombinator.com/item?id=49094346
#HackerNews #SQLite #WAL #Mode #Concurrency #VFS #Performance #Optimization
-
Linux 7.2 يضيف OPENAT2_REGULAR لحماية التطبيقات من فتح الملفات الخاصة عن طريق الخطأ
في الإصدار المرتقب 7.2 من نواة لينكس، سيُضاف علم (flag) جديد باسم OPENAT2_REGULAR إلى نظام الملفات الافتراضي VFS. الهدف منه منع التطبيقات من فتح الملفات الخاصة (مثل الأنابيب والأجهزة) عن طريق الخطأ، مما يحمي النظام من...
🔗 https://salehgnutux.github.io/GT-NEWSTECH/ar/gnulinux/linux-7-2-openat2-regular-security/
#Linux_Kernel #أمن #نظام_ملفات #VFS #ملفات_خاصة #برمجة #gnutux
-
Пишем движок для блога на Rust
Недавно я решил завести собственный блог. Сначала посмотрел в сторону SSG, но они показались мне не слишком удобными для того сценария, который я хотел получить. Затем попробовал несколько CMS, однако быстро упёрся в другую проблему: мой сервер оказался слишком слабым для большинства современных решений. В итоге ни одно из готовых решений так и не смогло закрыть все мои требования одновременно. Так и появилась идея сделать небольшую файловую CMS на Rust, которая не требует базы данных, не потребляет много памяти и при этом остаётся достаточно гибкой для повседневного использования. Со временем идея небольшого блогового движка разрослась в полноценную CMS с SSR, виртуальной файловой системой, поддержкой локализации, визуальным редактором статей и горячей перезагрузкой контента. В этой статье я постараюсь показать, как всё это устроено изнутри.
-
"[A]cross much of Africa, Asia and the Middle East, the visa outsourcing giant has become notorious. For people in these regions seeking to travel for work, study or to unite with family, VFS is often their first encounter with the border. And for many, this entails not only the stress and uncertainty of restrictive visa regimes, but also being compelled to hand over cash for what should be optional services — sales that have become central to the VFS Global’s growth.
Since its founding in 2001, VFS has grown into a multi-billion-dollar company whose owners include a major donor to Donald Trump and Dubai’s ruling family. It now holds visa outsourcing contracts with 71 governments worldwide. While applicants are charged a mandatory service fee, VFS has built an adjacent business around selling add-ons such as SMS updates, courier return services and access to premium lounges.
A year-long investigation by Lighthouse Reports, in collaboration with 14 media outlets, has found that VFS has created a system of aggressive – and at times dishonest – upselling. Staff are typically paid low base salaries and awarded bonuses contingent on meeting monthly sales targets for value added services, creating perverse incentives to sell.
Sales of these services have been key to the company’s growing profitability, which has increased fourfold in recent years, and have helped drive huge profits for its investors, our analysis shows.
We also found evidence that customers are exposed to bribery at the hands of both external agents and sometimes VFS staff, as well as repeated mishandling of personal data, amounting to what experts described as “manifestly serious violations of the GDPR”. Internal documents show that contracting governments know about these violations, but rarely take robust action."
https://www.lighthousereports.com/investigation/the-visa-empire-borders-as-a-business/
-
Behold, the tech community's latest spectacle: an #SQLite #VFS that boasts sub-250ms JOIN queries, as if speed alone could woo developers into ignoring the impracticality of managing data in S3 for a relational database. 🚀💾 Meanwhile, #GitHub continues its quest to conquer the world with AI tools no one asked for, because who needs actual innovation when you have buzzwords? 🤖✨
https://github.com/russellromney/turbolite #JOINqueries #AItools #techinnovation #HackerNews #ngated -
Turbolite – a SQLite VFS serving sub-250ms cold JOIN queries from S3
https://github.com/russellromney/turbolite
#HackerNews #Turbolite #SQLite #VFS #S3 #JOINqueries #DatabaseOptimization
-
Half of the support for the #initrd (not to be confused with #initramfs!) was removed from #Linux 7.0 through a #vfs merge from @brauner:
https://git.kernel.org/torvalds/c/996812c453cafa042f2e674738dbf8fa495661f3 and https://git.kernel.org/torvalds/c/ef12d0573a7f5e7a495e81d773ae5f3e98230cd4
""Remove the deprecated linuxrc-based initrd code path and related dead code. The linuxrc initrd path was deprecated in 2020 and this series completes its removal. If we see real-life regressions we'll revert. […]
The no-op load_ramdisk= and prompt_ramdisk= parameters are dropped, and noinitrd and ramdisk_start= gain deprecation warnings.
Initramfs is entirely unaffected. The non-linuxrc initrd path (root=/dev/ram0) is preserved but now carries a deprecation warning targeting January 2027 removal""
-
#VFS support for generic I/O error reporting was merged for #Linux 7.0 by @brauner
https://git.kernel.org/torvalds/c/dd466ea0029961ee0ee6e8e468faa1506275c8a9
""Filesystems currently have no standard mechanism for reporting metadata corruption and file I/O errors to userspace via fsnotify. Each filesystem (xfs, ext4, erofs, f2fs, etc.) privately defines EFSCORRUPTED, and error reporting to fanotify is inconsistent or absent entirely.
This introduces a generic fserror infrastructure built around struct super_block that gives filesystems a standard way to queue metadata and file I/O error reports for delivery to fsnotify.
Errors are queued via mempools and queue_work to avoid holding filesystem locks in the notification path; unmount waits for pending events to drain. A new super_operations::report_error callback lets filesystem drivers respond to file I/O errors themselves (to be used by an upcoming XFS self-healing patchset).
On the uapi side, EFSCORRUPTED and EUCLEAN are promoted from private per-filesystem definitions to canonical errno.h values across all architectures""
-
Support for non-blocking timestamp updates in the #vfs was merged for #Linux 7.0 by @brauner:
https://git.kernel.org/torvalds/c/74554251dfc9374ebf1a9dfc54d6745d56bb9265
""[…] commit 66fa3cedf16a [made] non-blocking direct writes impossible on file systems with granular enough timestamps, which in practice means all of them.
This reworks the timestamp update path to propagate IOCB_NOWAIT through ->update_time so that file systems which can update timestamps without blocking are no longer penalized. […]XFS implements non-blocking timestamp updates by using the new ->sync_lazytime and […]""
-
-
Nur Dumme wählen Nazis! #FckAFD #FckNZS #NazisRaus #AFDverbot #ICE #Gestapo #AFDverbotJetzt #NoNazis #AFDP #FightFascism #tdgr #NAFO #StopAfD #AfD #Germany #FckTrmp #FckPtn #AfDVerbotSofort #Antifa #Demokratie #VfS
-
🚀 Behold, Fly Blog's dazzling revelation of a "performance optimization" feature that no one asked for, starring #Litestream VFS! 🤡 Wrapped in the usual smorgasbord of tech buzzwords, this post might just optimize your reading time by putting you to sleep faster than a sleeping pill. 🌙💤
https://fly.io/blog/litestream-vfs/ #FlyBlog #VFS #performanceoptimization #techbuzzwords #readingtime #HackerNews #ngated -
Miria (2025) [1 min] by Fanny Arteaga | #Canada
https://www.youtube.com/watch?v=aw5vQtpngBY
#2D #2DAnimation #AnimatedShort #AnimatedShortOfTheDay #Animation #VFS #VancouverFilmSchool #StuffedAnimal #Cute #Childhood #Children #Magic
-
Come to the #VfS panel on #OpenScience with Severine Toussaert, @leventneyse.bsky.social @jrgptrs.bsky.social @larsvil.bsky.social . Looking forward to the discussion.
RE: https://bsky.app/profile/did:plc:3kso2jjt5kixxmalsrh3ebc2/post/3ly3piekmrk2c -
Some highlights from various #VFS merges for #Linux 6.17 where @brauner submitted the PR:
https://git.kernel.org/torvalds/c/278c7d9b5e0ca73a75e5151c22fb05c91cb4495f: fallocate() updates bringing support for the BLK_FEAT_WRITE_ZEROES_UNMAP feature and BLK_FLAG_WRITE_ZEROES_UNMAP_DISABLED flag for SCSI, NVMe and device-mapper drivers, and add the FALLOC_FL_WRITE_ZEROES and for ext4 and raw bdev devices; this enables preventing numerous metadata changes and journal I/O, which may lead to significant write amplification and performance degradation in synchronous write mode.
https://git.kernel.org/torvalds/c/57fcb7d930d8f00f383e995aeebdcd2b416a187a: support for the the new file_getattr() and file_setattr() system calls (after lengthy discussions), which allow userspace to set filesystem inode attributes on special files (One of the usage examples is the XFS quota projects.)
https://git.kernel.org/torvalds/c/7879d7aff0ffd969fcb1a59e3f87ebb353e47b7f: ext4 IOCB_DONTCACHE support
https://git.kernel.org/torvalds/c/117eab5c6e31815649d952f6da03f67aa247d29b: An extension to the coredump socket and a proper rework of the coredump code.
-
THE PROBLEM:
#Podman is using the #VFS storage driver which is basically copying entire filesystems for every layer.nginx-proxy-manager image probably expanded from 1.13GB to 15-20GB+ because VFS makes full copies instead of using efficient layers.
This begs the question.
ARE ANY OF YOU WALLIES ACTUALLY USING PODMAN IN PRODUCTION?
WTF?
