|I’m writing this following an install of sid a onto an old 486 Notebook with 8 Megs. As the package – Database grows and grows, the amount of Memory needed to handle it also gets larger. The unstable package database doesn’t fit into the measly ram of this machine. It needed to swap continuously.
A single dpkg-call (independent on whether to list, install or remove one or more Packages) took about 30 minutes, However I have an ingenious idea for distributed package management.
Here is the idea that came to me:
It is very often that we come into a situation, that a machine is overloaded with the task of handling it’s own
package-database (take things like
- the old 486 firewalling you from the nasty big internet
- the little machine feeding your laser-printer
- the old Dec-Station you use as X-Terminal
- the second partition you keep on your Disk to create boot-CD’s
- the embedded-machine to control your washing machine
- and last (but surely not least) your PDA ).
So why not distribute the Truck-load of work to machine that would do this in spare-time, like your Desktop >GHzCpu equipped with 100Megs of ram?
There would have to be something like a net-shared Filesystem on the Slave-machine to be hooked into the Master-machine, and sort of a Deamon
executing the post-install scripts and so on. (ssh?)
And now to the Boot – CD-Thing: what about a Plex-86 running the target-installation in non-X mode?
rob: Why not use potato or slink? With smaller package lists, surely you dont need sid’s features on this laptop.