I would have thought that this only makes sense in the context of a "point-in-time release". i.e. you have a server which isn't updated as regularly as your desktop. The onus then is on the user to ensure that the versions of packages they are using are "safe". I don't see this as a problem with the rolling release system that Arch uses. Where it does make sense is if a publicly available, LTS type "server" repository is used. Then it would be up to the maintainer of the repo to keep on top of security fixes. regards Chris -- Calling the unnamed register the unnamed register really does nothing but negate the name the unnamed register and render the unnamed register useless as a name, thus the unnamed register is named the unnamed register and is no longer the unnamed register as it is named the unnamed register, so where is the unnamed register to be found and what do we call it! Steve Oualline, The book of vim.
