1 |
urpmi can automatically find the media repository path using DNS-SD |
2 |
(Zeroconf), with the "--zeroconf" option: |
3 |
urpmi.addmedia --distrib --zeroconf |
4 |
urpmi.addmedia --zeroconf main media/main/release |
5 |
|
6 |
This option can also be used together with the "--mirrorlist" option, |
7 |
in which case the repositories are configured using Zeroconf if found, |
8 |
and mirrorlist is used as a fallback: |
9 |
urpmi.addmedia --distrib --zeroconf --mirrorlist |
10 |
|
11 |
When searching for the repository using Zeroconf, the request timeouts |
12 |
after a delay of 10 seconds, to avoid hanging urpmi if some hosts are |
13 |
unresolvable. |
14 |
|
15 |
If a repository is found using DNS-SD, urpmi.addmedia will build a |
16 |
complete repository path using fields from /etc/product.id, this way: |
17 |
<advertised repository path>/lowercase(<branch>)/<version>/<arch> |
18 |
|
19 |
To advertise an urpmi repository using DNS-SD, a service record with |
20 |
the instance "_mdv_urpmi" has to be created, specifying the target |
21 |
host and target port where the service is located. |
22 |
In addition, two DNS-SD TXT records must be specified, in the form of |
23 |
key/value pairs: protocol (http, ftp or rsync) and path (repository root). |
24 |
|
25 |
The path value should be the full path to the media repository root, |
26 |
for example /dis if the distribution repository is reachable on |
27 |
http://host:port/dis/official/2010.1/i586 |
28 |
|
29 |
See the urpmi-repository-http.service file for an example of urpmi |
30 |
repository advertising using Avahi. |