Since all of the components I've accumulated are now a single monolithic linux server, I was wondering if anyone would be interested in it.
This is what it does:
I build a gold image in vmware server, of XP sp2. I sysprep it with my custom inf files(you'd need to get a drivers folder, as it's a gig by itself). I resize the partition to the lowest value I can. I use G4U to upload it to the vsftp component of my server. I use MIDS(a frontend for G4U) to download the image to the end stations.
WPKG is used to manage hosts, upgrading software, patches, etc.
A web server(pmwiki on apache) hosts packages that I built with one of the free packaging installations. It also is the front end where I can simply put in a password, then click the package I want to install. It also holds registry files, package clusters, etc. Adding new links is easy using pmwiki, where I can edit it from anywhere, even sitting at a end station repairing a pc. Additionally, pmwiki hosts the updates page, where techs are informed of changes, scheduling, call lists, etc.
I use it to maintain a VERY fast build cycle, wherein I can test a build, update it and have it sitting on a server for deployment in a matter of hours. It then is deployed in a matter of minutes(MIDS is the best thing ever! It's so good I named the system MIDS in honor). I can keep the stations upgraded, patched and tweaked using WPKG(windows packager). It is a beginning to end management system, and all of it is opensourced.
used:
G4U,mids,wpkg,fedora core,vsftpd,samba,apache, pmwiki
It's really a conglomeration of a lot of other folks hard work, with a little tweaking on my part.
It is very fast, very flexible, and has cut floor time from days to minutes. I can have a fully built image, including all applications off the server and onto the floor in under 5 minutes, join the domain and ready to work on.
Included in a temp folder would be iso's for g4u,mids,etc. plus documentation on the process.
Anyone think this might make a decent appliance? It's probably large, but it could be pared down. I didn't see where there would be a minimum...but I sure wish this had existed when I started trying to figure out how to do all these things.
This is what it does:
I build a gold image in vmware server, of XP sp2. I sysprep it with my custom inf files(you'd need to get a drivers folder, as it's a gig by itself). I resize the partition to the lowest value I can. I use G4U to upload it to the vsftp component of my server. I use MIDS(a frontend for G4U) to download the image to the end stations.
WPKG is used to manage hosts, upgrading software, patches, etc.
A web server(pmwiki on apache) hosts packages that I built with one of the free packaging installations. It also is the front end where I can simply put in a password, then click the package I want to install. It also holds registry files, package clusters, etc. Adding new links is easy using pmwiki, where I can edit it from anywhere, even sitting at a end station repairing a pc. Additionally, pmwiki hosts the updates page, where techs are informed of changes, scheduling, call lists, etc.
I use it to maintain a VERY fast build cycle, wherein I can test a build, update it and have it sitting on a server for deployment in a matter of hours. It then is deployed in a matter of minutes(MIDS is the best thing ever! It's so good I named the system MIDS in honor). I can keep the stations upgraded, patched and tweaked using WPKG(windows packager). It is a beginning to end management system, and all of it is opensourced.
used:
G4U,mids,wpkg,fedora core,vsftpd,samba,apache, pmwiki
It's really a conglomeration of a lot of other folks hard work, with a little tweaking on my part.
It is very fast, very flexible, and has cut floor time from days to minutes. I can have a fully built image, including all applications off the server and onto the floor in under 5 minutes, join the domain and ready to work on.
Included in a temp folder would be iso's for g4u,mids,etc. plus documentation on the process.
Anyone think this might make a decent appliance? It's probably large, but it could be pared down. I didn't see where there would be a minimum...but I sure wish this had existed when I started trying to figure out how to do all these things.
