> mrepo does some things about leaving ISO's mounted as loopbacks, which I > personally don't like as I am suspicious of loopbacks and don't want to > keep track of which ones are used/free and when.
I remember my problem now. I did not like how mrepo left the ISO images mounted all the time and I wanted instead to mount them on demand, so I tried to move this to autofs. The problem is that my ISO images are on a filer, which is automounted, and under these circumstances autofs simply cannot find the ISO images to mount. > Here at work we have a huge library of trees (basically every distro > we've ever built) on NFS via autofs and I frequently import that with > --available-as to use as an install source. Think I will sleep on this. I am fond of the way the installer handles ISO images on its own. In the long run I may need to make the contents of the ISO image available via http anyway and the ISO trick does not work with a url. Where does Cobbler store the trees if it is instructed to import them? What is the recommended way of relocating the trees to a different path? I intend to use replication, and if I go the route of expanding the ISOs then I would prefer to do this with Cobbler on the master. I would want to store the trees on my filer so that I needn't sync it to my sub-cobblers. Thanks, Chris _______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
