# CoreOS Published articles for CoreOS. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## CoreOS 45 Test Week DevFeed: [CoreOS 45 Test Week]() Original publisher: [Read original article]() Author: Lukáš Růžička Published: 2026-09-16T08:00:00Z Content type: news Language: en Sources: [Fedora Magazine]() Topics: [Fedora](), [Testing](), [Wiki]() Tags: [2026](), [bugs](), [community](), [contribution](), [coreos](), [download](), [event](), [fedora-linux-45](), [fedora-project-community](), [qa](), [release](), [test-week](), [testing]() ### AI overview Fedora CoreOS and QA teams are organizing a Test Week beginning September 21, 2026, to help the community test Fedora CoreOS based on Fedora 45 content before it reaches the testing and stable streams. ### Source excerpt The Fedora CoreOS and QA teams are gearing up for Fedora 45, and we need your help! We are organizing a Fedora CoreOS Test Week starting on September 21, 2026. This event is a great opportunity for the community to test Fedora CoreOS (FCOS) based on Fedora 45 content before it officially reaches the testing [...] ## 【分布式系统百科】分布式 KV 存储对比：etcd、TiKV 与 FoundationDB DevFeed: [【分布式系统百科】分布式 KV 存储对比：etcd、TiKV 与 FoundationDB]() Original publisher: [Read original article]() Author: Liao Tonglang Published: 2026-04-13T00:00:00Z Content type: comparison Language: zh Sources: [土法炼钢 - 系统与基础设施]() Topics: [etcd](), [Raft](), [Kubernetes]() Tags: [bbolt](), [boltdb](), [compaction](), [coreos](), [distributed](), [distributed-systems](), [errcompacted](), [etcd](), [go](), [k8s](), [kubernetes](), [lease](), [mmap](), [mvcc](), [raft](), [readindex](), [revision](), [single-raft-group](), [ssd](), [v3](), [wal](), [watch]() ### AI overview This Chinese-language comparison examines etcd, TiKV, and FoundationDB as distributed key-value stores for metadata. It focuses on architecture, implementation, performance, and limitations, with detailed coverage of etcd's single Raft group, MVCC, Watch, Lease, bbolt storage engine, linearizable reads, compaction, and defragmentation. ### Source excerpt 一个典型的架构评审场景：团队需要一个分布式键值存储来承载新系统的元数据。候选方案三个----etcd、TiKV、FoundationDB。三者都提供强一致性保证，都经过大规模生产验证，但设计目标截然不同。选错了，轻则性能不达标，重则数据丢失后无法恢复。这篇文章从架构、实现、性能和局限四个维度，把三个系统拆开来看。 ## Ultimate Linux on the Desktop DevFeed: [Ultimate Linux on the Desktop]() Original publisher: [Read original article]() Published: 2017-01-16T15:09:26Z Content type: opinion Language: en Sources: [Jessie Frazelle]() Topics: [Linux](), [Containers]() Tags: [containers](), [coreos](), [hardware](), [kernel](), [linux]() ### AI overview The author describes a personal Linux desktop setup based on CoreOS Container Linux. They adapted the server-oriented operating system for desktop graphics, removed server-specific components, and ran applications in containers, citing customization, automatic updates, a container-oriented filesystem, and TPM support as benefits. ### Source excerpt Over the past couple of years I have set out to create the ultimate Linux on the desktop experience for myself. Obviously everyone who runs Linux has their own opinions on things. What this post will outline is my ultimate Linux on the desktop experience. So just remember that before you get your panties in a knot on HackerNews because you live and die by Xmonad (I live and die by i3, fight me). First, you should already know that I run everything on my laptop in containers. I outlined this in my posts about Docker Containers on the Desktop and Runc Containers on the Desktop. Base OS I used to use Debian as my base OS but I recently decided to try and run CoreOS' Container Linux on the desktop. Container Linux is made for servers, so obviously it doesn't have graphics drivers. I added them and made a few other horrible tweaks that I'm sure would make some people at CoreOS cringe. I am not proud of these things but overall it worked! Mostly the changes for graphics drivers were the same exact changes you would make installing Gentoo on your host: setting VIDEO_CARDS="intel i915" in /etc/portage/make.conf, emerge-ing sys-kernel/linux-firmware etc, etc. Then I cut out the things I don't need that only pertain to if you are using Container Linux on your server, cluster management tools, support request tools (lolz) etc. These were all pretty simple changes that I made to a new ebuild that I cloned from the coreos-base/coreos ebuild. I need to clean up the mess I've made of my forks of the coreos build scripts, init, ebuilds, manifest, and base layout. But you can checkout the desktop branch at each of those. Let me go over some of the benefits I get from using CoreOS' Container Linux as my base OS. I can build my own images, it's Gentoo and I know emerge so I can customize the base anyway I want. CoreOS' Container Linux uses the same auto update system as ChromeOS, which is all based on Google's Omaha. So all I need to do to have auto updates for my OS is continuously r