Patch management is part of package management
There's two approaches to distributing updates; you candistribute entire new versions of packages, or you can usesome sort of 'patches'. For essentially historical reasons , commercial Unix vendors generally use thelatter approach.
Here is something important about this: if you have patches, patchmanagement needs to be part of the packaging infrastructure, even if itis not done with the package management system and commands. It cannotand should not be something that is just slapped on over top.
Here's why:
誰禁了大衛像？
一條廢柴的自白
三里塚鬥爭事件
《子不語》
Inglourious Basterds
歷史題材配以天馬行空的故事，真的用赤子之心而發揮出無比的創意，教人意
周星馳《喜劇之王2》演員招募？係真唔係先？
昨天同事給我看了這段片，我一直心有慼慼然。
唔通，我心裡面真係仲有團火？
Interesting things can happen when you scale things up
This is a sysadmin war story.
Once upon a time, there were a bunch of IMAP servers. Since this waslong ago, they were running Linux with the 2.4 kernel. They startedout storing their mail on locally attached 72 GB SCSI disks, organizedsimply with one ext2 filesystem per disk, but then they moved thestorage to a faster and more sophisticated SAN backend with RAID-10arrays (still on small fast enterprise disks), giving each server node asingle logical array (
A brief and jaundiced history of Unix packaging systems
In the beginning (in the days of V7 and BSD Unix), Unix systems cameas a great big tarball or the equivalent that included everything andyou just unpacked it onto your machine. If there were problems, peoplepassed around new versions of various bits of source in various ways;you got some, you put them on your system, you recompiled things, and soon.
Shortly after Unix vendors started selling Unix, they discoveredthat they needed some actual mechanism to deliver bugfixes andupdates to their customers
