最近看到兩篇文章: The Problem with CSS 和 Everything You Know about CSS is wrong ,都是 sitepoint 為新書作宣傳的文章,談的是 CSS 排版的問題。
CSS 排版難學又難精,因為其當初並沒有為排版而設的規則,因此即使要做幾個簡單的 Column,也必需走很遠的路:理解一大堆 CSS 的
Our old SAN was set up in the traditional way: the SAN backend units didRAID-5 interally, and this RAID-5 space was carved up into LUNs and usedby the frontend fileservers. For natural reasons all of our fileservers wound up using LUNs from all of our SAN backends.This setup has low overhead , decent resilience,and decent performance.Our new fileservers are set up inan entirely different way, and among other things they use RAID-1instead of RAID-5. Although we were
Our new fileserver setup requiresthat all of the LUNs exported by the backend SAN be exactly the samesize, down to the block, so that we can always mirror two arbitrary LUNstogether. We wanted our basic LUN size to be around 200 to 250 GB, butthat's a large range of possible sizes, and it still left us to pick asensible exact block size.
Our first approach was to take our 750 GB Seagate SATA disks and dividethem up into three equal
最近看到兩篇文章: The Problem with CSS 和 Everything You Know about CSS is wrong ,都是 sitepoint 為新書作宣傳的文章,談的是 CSS 排版的問題。
CSS 排版難學又難精,因為其當初並沒有為排版而設的規則,因此即使要做幾個簡單的 Column,也必需走很遠的路:理解一大堆 CSS 的
To simplify, BitTorrent breaks files up into blocks, checksums eachblock, and then has all of the clients (the peers) swap blocks back andforth. The checksums for all the blocks are in the .torrent metainfofile that each client has, so you know when you get a bad copy of ablock (and as a side effect, a malicious client can't serve you trojandata).
(One might think that trojan data would be relatively harmless. ButBitTorrent is used to distribute things that