I am guessing this is possible to do, but compiling, managing and distributing all those different versions of full sized DVD .isos isn't gunna be fun for anybody. Then consider it's 2.7GB a pop for a revision, if you do it say monthly that's 12 revisions a year... so each year that's about 35GB of space taken up. Also given that FCs come out about every 6 months, it's generally just not worth going down that route in my opinion.
I might instead suggest maybe going into a PXE solution that places a cron job by default for a yum update at say noon or running yum update as background process in the rc.3 folder. I can't say I know how to set-up a PXE server to do this, but I have alot of experience with installing servers via PXE. I may point out, you could have an on-site repository that all the machines on the network point to, instead of having xx numbers of the same downloads going to the official repositories. That is I am guessing this is all on the same network. Then the on-site repository just downloads the latest updates from the official repositories on a daily basis. I believe this is all possible as I am suggesting this, but don't know the actual procedures to setting it up.
Last edited by r3sistance; 01-26-2009 at 09:17 AM.
|