Debian Planet

Welcome to Debian Planet


Apt-get into it.
Main Menu

  • Home

  • Topics

  • Web Links

  • Your Account

  • Submit News

  • Stats

  • Top 10

  • Debian

    These are important Debian sites one should not be without!

  • Official Debian site

  • Package search

  • Mailing list archives

  • Bug reports

  • Debian on CD

  • Unofficial woody CD ISOs

  • Unofficial APT sources

  • Developers’ Corner

    Other great Debian news sources:

  • Debian Weekly News

  • Kernel Cousin Debian

    (Debian mailing lists digested)
  • Community Groups

    Need help? You’re not alone on this planet.

  • debianHELP

    (User support site)

  • Debian International



  • EsDebian


  • DebianWorld


  • MaximumDebian


  • DebianUsers


  • Debian-BR


  • IRC

    The place to get help on a Debian problem (after reading docs) or to just chat and chill is #debian on

    Many of the Debian Planet staff live there so pop by and say hello.

    Wanna write?

    Got that latest or greatest scoop? Perhaps you have some important news for the Debian community? Submit a news item!

    Or perhaps you’ve written a rather ground breaking insight into some aspect of Debian and you feel compelled to share it with others? Knock up a longer editorial article and send it to the editors.


    DP is sponsored by Xinit Systems and

    Domains paid for and hosted by

    Buy your Debian merchandise at

    Who’s Online

    There are currently, 58 guest(s) and 5 member(s) that are online.

    You are Anonymous user. You can register for free by clicking here.


    Master-Slave Package management
    by Anonymous on Saturday, July 07 @ 13:43:30 BST

    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.

    Your Name: Anonymous [ New User ]



    Allowed HTML:
    <p> <b> <i> <a> <em> <br> <strong> <blockquote> <tt> <li> <ol> <ul>