When you say "see them" you mean "ability to access them via a
transport protocol" or what I liked to call an "access method". NFS is
just one type of "access method". Wouldn't it be good to support http,
https, ftp, rsync, ssh. Have you ever tried to NFS mount something on
the Internet.
If you see my original post, I thought "--available-as=nfs://etc."
would do as you described, but it doesn't.
So what is the difference between using --available-as=nfs:// and NFS
mounting the path and then using import on the nfs mount point?
Paul
On Sat, Jul 4, 2009 at 9:41 PM, <David.Mackintosh(a)xdroop.com> wrote:
On Sat, Jul 04, 2009 at 12:45:22PM -0700, Paul Company wrote:
> Remember what I was asking:
> >> I'd like to add the distro (CentOS-5.3-x86_64-bin-DVD.iso) but I
don't want to copy the contents over.
>
> Is this possible or do I need to run cobbler on my distro/repo server
> (has lots of disk).
> That doesn't really make cobbler flexible.
> My guess is I just don't understand something.
Personally, I have the OS sources on NFS, and just mount them onto
the cobbler server -- which most of the time is a VM in my case
anyways.
My rationale is that they have to be somewhere, they might as well be
somewhere the cobbler server can see them.
--
/\oo/\
/ /()\ \ David Mackintosh |
dave(a)xdroop.com |
http://www.xdroop.com
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler