Let's talk about Zen-Stable baby
Let's talk about you and me!
There is some confusion about zen-stable, and we haven't had any regular articles lately - so I figured I'd just write one really quick :D
Nothing major, a few people don't understand some of the things it does and what not, so i'll clear it up in true or false format!
Idea: Zen-Stable release patches apply over the latest upstream stable release!
FALSE! The release patches include the latest upstream stable releases, so they do not apply on top of them. The patches always apply on top of the base kernel version for that release.
For example, 2.6.33-zen2 INCLUDES 2.6.33.1, but the patch is supposed to be applied on top of 2.6.33 :D
Idea: Zen-Stable doesn't keep things i want up to date enough, like BTRFS, aufs, tuxonice, squashfs, BFS
FALSE! Zen stable git trees are frequently updated across the board. Presently the 2.6.31-2.6.33 branches receive all updates, while 2.6.30 receives some updates (basically everything except btrfs and bfs). They also remain updated to the latest upstream stable revisions for that release. So if zen-stable is too outdated for you, you're too new!
Idea: There is basically no difference between zen.git and zen-stable.git!
FALSE! Zen-stable never sees pre-release kernels (-rc kernels), nor does it merge experimental git trees like wireless-testing, drm-next (or any of the other drm-testing branches), sound-2.6, etc. If you desire these things, zen.git is the place for you!
Idea: I don't need to re-clone the tree to switch between zen-stable and zen.git
TRUE! Look in the Documentation->Tutorials section if you don't know how!
Idea: Zen operates on crude oil and raw meat!
FALSE! The zen kernel operates purely on vegetable oil, self-generated electricity, and a little bit of distilled water.
Forgot your password?
New user?
