On Thu, 28 Aug 2003, David Boyes wrote: > > we build the system through a bunch of rpm commands to create the > > basic structure, and then add the rest of the packages with apt4rpm. > > I'll second this approach. apt is much smarter about getting dependencies > right, and it's also a good framework for managing local repositories, so > you don't have to invent a different wheel to get applications > configurations loaded after you get the base OS working -- you can have a > apps repository and drive the installs the same way. > > I wish the distributors would use it (or at least be friendly to it) rather > than these proprietary update hacks like YOU or RHN. It'd save them a hell > of a lot of bandwidth.
I've put it to many Red Hat lists that one of the factors than ensures I won't use RHN (even before recent support changes) is that it requires me to download stuff from Red Hat, across the world, rather than use a server convenently close to me. If I use a mirror on WAIX, downloads do not count against my monthly allocation, and it comes steaming in at 52Kbytes/sec or so. I recently applied fixes to a client machine in this area using up2date, and for a good part of the time I was getting 5 Kbytes/sec or less: I can do that well via modem. Installing isn't too bad, first time Squid caches the data and subsequent installs run at LAN speeds. In contrast, Debian has (at least) two mirrors on WAIX, if I don't mirror the updates myself (I can do so easily) they too go into my Squid cache. Debian's installer isn't flash, but when it's done my fixes are in place. In contrast, RH expects me to register the system and get the patches at 5k/sec! On Debian, I update the packages list when I want do, On RHL, every time I run up2date it goes and checks the server. At 5k/sec. > > -- db > -- Cheers John. Join the "Linux Support by Small Businesses" list at http://mail.computerdatasafe.com.au/mailman/listinfo/lssb Copyright John Summerfield. Reproduction prohibited.
