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-cb,v 1.1 2016/12/29 23:12:23 wiz Exp $

--- ../docs/man/xmdomain.cfg.pod.5.orig	2008-08-01 16:38:07.000000000 +0200
+++ ../docs/man/xmdomain.cfg.pod.5
@@@@ -4,9 +4,9 @@@@ xmdomain.cfg - xm domain config file for
 
 =head1 SYNOPSIS
 
- /etc/xen/myxendomain
- /etc/xen/myxendomain2
- /etc/xen/auto/myxenautostarted
+ @@XENDCONFDIR@@/myxendomain
+ @@XENDCONFDIR@@/myxendomain2
+ @@XENDCONFDIR@@/auto/myxenautostarted
 
 =head1 DESCRIPTION
 
@@@@ -14,14 +14,14 @@@@ The B<xm>(1) program uses python executa
 domains to create from scratch.  Each of these config files needs to
 contain a number of required options, and may specify many more.
 
-Domain configuration files live in /etc/xen by default, if you store
+Domain configuration files live in @@XENDCONFDIR@@ by default, if you store
 config files anywhere else the full path to the config file must be
 specified in the I<xm create> command.
 
-/etc/xen/auto is a special case.  Domain config files in that
+@@XENDCONFDIR@@/auto is a special case.  Domain config files in that
 directory will be started automatically at system boot if the
-xendomain init script is enabled.  The contents of /etc/xen/auto
-should be symlinks to files in /etc/xen to allow I<xm create> to be
+xendomain init script is enabled.  The contents of @@XENDCONFDIR@@/auto
+should be symlinks to files in @@XENDCONFDIR@@ to allow I<xm create> to be
 used without full paths.
 
 Options are specified by I<name = value> statements in the
@


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-cb,v 1.1.1.1 2011/04/06 09:10:27 cegger Exp $
@