head 1.2; access; symbols; locks; strict; comment @# @; 1.2 date 2017.03.20.18.06.07; author bouyer; state dead; branches; next 1.1; commitid UIkDeoKV4TqUGjKz; 1.1 date 2016.12.29.23.12.23; author wiz; state Exp; branches; next ; commitid rbn5RRsoW55uZVzz; desc @@ 1.2 log @Remove obsolete patches, they are obsolete since the switch to the 46 version @ text @$NetBSD: patch-ca,v 1.1 2016/12/29 23:12:23 wiz Exp $ --- ../docs/man/xend-config.sxp.pod.5.orig 2010-04-07 16:12:04.000000000 +0000 +++ ../docs/man/xend-config.sxp.pod.5 @@@@ -4,7 +4,7 @@@@ xend-config.sxp - Xen daemon configurati =head1 SYNOPSIS -/etc/xen/xend-config.sxp +@@XENDCONFDIR@@/xend-config.sxp =head1 DESCRIPTION @@@@ -12,7 +12,7 @@@@ The xend(1) program requires xend-config parameters which determine the behavior of the daemon at runtime. The parameters are specified in S-expression format. See the example -configuration file in I for details. +configuration file in I<@@XENDCONFDIR@@/xend-config.sxp> for details. =head1 OPTIONS @@@@ -82,13 +82,13 @@@@ Defaults to I<1024>. =item I -The name of the script in I that will be run to +The name of the script in I<@@XENDCONFDIR@@/scripts> that will be run to setup the networking environment. This can be any name, but in general is either I or I. =item I -The name of the script in I that will be run to +The name of the script in I<@@XENDCONFDIR@@/scripts> that will be run to setup a virtual interface when it is created or destroyed. This needs to (in general) work in unison with the I. @@@@ -113,7 +113,7 @@@@ domains should be saved when a crash occ The name of an application or script that can handle external device migration, such as for example virtual TPM migration. An example -script is I. +script is I<@@XENDCONFDIR@@/scripts/external-device-migrate>. =item I @ 1.1 log @Fix build. Not sure if this makes sense, since it's for the removed xen 4.1. @ text @d1 1 a1 1 $NetBSD: patch-ca,v 1.1.1.1 2011/04/06 09:10:27 cegger Exp $ @