Hey Team, I was pondering methods for reducing my RPM storage footprint for my Spacewalk server in which I'm serving up RHEL 4 & 5 both 32- & 64-bit. The storage overhead isn't THAT much... only ~250G ... but in order to serve content up to Spacewalk more dynamically, I'm using ye olde "mrepo" to gather content in one place on my Spacewalk server and then import that into Spacewalk via spacewalk-repo-sync.
So... what I end up with is... double the RPMs (and double the FUN!) on my server. I was thinking of possible solutions to this and one that came to me was using symlinks from the Spacewalk directory to the yum repositories on the system. so... instead of actual files deep in the "/var/satellite/redhat/x/yyy/package/version/arch/hash/" directory... that the target would instead be a link to the actual file in the corresponding yum repo. I was thinking that with the effort to develop the spacewalk-repo-sync utility... that this might be an option for inclusion. If the repo-sync detects that the URL is file:// then it would create the proper hashed directory structure per norm and place a link at the end of the tree instead of actually copying the file in there. Thoughts? -- Andy Speagle "THE Student" - UCATS Wichita State University
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Spacewalk-devel mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-devel
