Linked by Eugenia Loli on Sat 15th Jan 2005 02:09 UTC, submitted by Paul Best
Permalink for comment
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/25/13 0:45 UTC
Linked by Thom Holwerda on 05/24/13 23:59 UTC
Linked by Thom Holwerda on 05/24/13 22:33 UTC
Linked by Howard Fosdick on 05/24/13 21:41 UTC
Linked by Thom Holwerda on 05/24/13 14:44 UTC
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
More News »
Sponsored Links



Ty for the tip, but for a soho or in my case i fail at the 2nd rule of the requirement list to run systemimager. That will work for large envs like unis or companys, where you buy hardware in trucks all from the same supplier.
But for that, managing a big park of pcs, i would go with rembo pxe system deployament, to get an always fresh copy on boot and manage all client sofware snapshots from one point.
what i would love (why not doing it myself some might ask?) it would be the combination of the power of a versioning control system with some capabilities of remote deploying bits of source/bin files.
The same way fbsd ports system and cvsup deals with ftp+cvs to answer all their needs.
Why not combining the power of subversion for rollbacks and maintaining the proper version always updated, applying patches by diffing the current trunk, with the bittorrent protocol for rapidly and not network stressfull deployament?
With the option to building the packages locally before installing/upgrading instead of downloading them, as binaries, from one spot.
ricardo