How about I trick "cobbler import". What's the minimum I need to have cobbler import work?
For example, # mkdir -p /usr/distros/5Server-x86_64 # cd /usr/distros/5Server-x86_64 # scp vmlinuz initrd.img . # cobbler import --name=5Server-x86_64 --mirror=/usr/distros/5Server-x86_64 ....this fails with.... No distro signature for kernel at /var/www/cobbler/ks_mirror What's the minimum I need to add to /usr/distros/5Server-x86_64 to get import to work? Is there just a single "signature file" I can copy over? Paul On Mon, Sep 14, 2009 at 10:55 AM, Michael DeHaan<[email protected]> wrote: > >> I think we can get replicate to bring things over like you want, but I >> don't think it will be accepted for 2.0. I can see a relatively simple >> patch to fix this and get it in 2.2. But I would have to actually look >> at the code to be sure. Basically if we don't find the kernel and we >> are in full data sync mode, go out of band (http) to get them from the >> remote system. That should generally be good enough in most cases. >> Though I have a strange feeling this could get us in trouble in other >> places. I'll have to play with it (unless you beat me to it... :-D) >> > > > If someone is not using import, the solution is for them > to rsync it themselves and use (in 2.0, for instance) --omit-data. > > A wrapper script around Cobbler replicate would be one such solution. > > --Michael > > _______________________________________________ > cobbler mailing list > [email protected] > https://fedorahosted.org/mailman/listinfo/cobbler > _______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
