From: Norbert Paschedag (noe_at_physik.unizh.ch)
Date: Wed Jan 10 2007 - 14:43:59 CET
Date: Wed, 10 Jan 2007 14:43:59 +0100 (CET) From: Norbert Paschedag <noe@physik.unizh.ch> Message-ID: <Pine.LNX.4.61.0701101423090.8880@hesse.math.TU-Berlin.DE> Subject: [suse-sles-e] sles10 update server via NFS: Why R/W access ???
Hi,
I'm currently experimenting with the setup of a local update server for
sles10 and sdk10. The simplest way (I thought) was to simply export the
a disk containing the patches (obtained via yup) via NFS to the clients,
read-only, of course.
Done that, and on the client I tried to do this:
mount server:/sle10_update/x86_64 /update
rug service-add /update/SLES10/x86_64 --type yum local-sles10-64
rug subscribe local-sles10-64
rug refresh
rug update
This went well until 'rug refresh', at which point rug complained :
ERROR: Failed to parse XML metadata: Access to the path
"/update/SDK10/x86_64/repodata/repomd.xml" is denied
It turned out that the client (i.e. ALL clients using this update server)
need FULL READ/WRITE access to the repository. It does not seem to change
anything there, however.
Can anyone please explain the philosophy behind this (if there is any) ?
How can one set up an RO update server via NFS ?
Regards,
Norbert
---------------------------------------------------------------------
To unsubscribe, e-mail: suse-sles-e-unsubscribe@suse.com
For additional commands, e-mail: suse-sles-e-help@suse.com
This archive was generated by hypermail 2.1.7 : Wed Jan 10 2007 - 16:47:57 CET