Re: Size of lppsource for NIM

I think it's possible to do this, but I would strongly discourage it.

All it would be achieving would be exchanging a small amount of disk space
for an awful lot of trouble. Creating a complete new lppsource is a fairly
trivial undertaking. Creating a tailored one with links to other source
directories would involve a lot more work and I suspect it would be error
prone. If a mistake was made - linking to the wrong file, or omitting one
altogether - you might not realise until months after and it could be tricky
to diagnose the problems at that time.

--
Simon Green

-----Original Message-----
From: IBM AIX Discussion List [mailto:aix-l@xxxxxxxxxxxxx] On Behalf Of
Enrique Sanchez Vela
Sent: 23 September 2006 04:12
To: aix-l@xxxxxxxxxxxxx
Subject: Re: Size of lppsource for NIM


--- Matt Lawrence <matt@xxxxxxxxxxxxxxx> wrote:

When building a NIM server to serve multiple
versions & maintenance levels
of AIX, it seems to me that creating hard links for
the filesets that have
not changed makes more sense than to create a
completely seperate tree.

Does this make sense? Does anyone have a quick
script for accomplishing
this task? Any other suggestions?

-- Matt
It's not what I know that counts.
It's what I can remember in time to use.


Matt,

Interesting idea you are proposing, however, remember
that the SPOT and lppsource are both exported via NFS,
I am not sure a symbolic or hard link will work ....

would it ?? you bet I'm testing it.

regards,
Enrique.

Enrique Sanchez Vela
email: esanchezvela@xxxxxxxxx
--------------------------------------
http://www.savetheinternet.com/

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

Relevant Pages