xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: "xen-devel.GarveyPatrickD@OrdinaryAmerican.net"
	<xen-devel.GarveyPatrickD@OrdinaryAmerican.net>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Inaccessible link
Date: Mon, 21 Nov 2011 09:18:17 +0000	[thread overview]
Message-ID: <1321867097.8866.86.camel@dagon.hellion.org.uk> (raw)
In-Reply-To: <CACm5R6TEeA1AiRwZ9xRvobSkKLzeOLbFfai6vibakpDOXQBZUw@mail.gmail.com>

On Sun, 2011-11-20 at 01:11 +0000,
xen-devel.GarveyPatrickD@OrdinaryAmerican.net wrote:
> http://wiki.xen.org/wiki/Assign_Hardware_to_DomU_with_PCIBack_as_module
> contains a link to the University of Cambridge Computer Laboratory
> copy of the Xen User Manual
> http://www.cl.cam.ac.uk/Research/SRG/netos/xen/readmes/user/user.html#SECTION03231300000000000000
> that responds, "Forbidden
> You don't have permission to access
> /research/srg/netos/xen/readmes/user/user.html on this server."
> 
> Does Xen.org have the right to copy the Xen User Manual onto its own server?

That documentation is built from the Xen source tree (try installing
latex2html then"make docs") and appears to be covered by the GPL so I
think so.

However that particular doc is not well maintained (although the
particular section which is referenced doesn't look so bad). IMHO it
would be better to move the information onto the wiki itself (assuming
it isn't already duplicated somewhere).

Ian.

  reply	other threads:[~2011-11-21  9:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-20  1:11 Inaccessible link xen-devel.GarveyPatrickD
2011-11-21  9:18 ` Ian Campbell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-11-18 19:47 xen-devel.GarveyPatrickD

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1321867097.8866.86.camel@dagon.hellion.org.uk \
    --to=ian.campbell@citrix.com \
    --cc=xen-devel.GarveyPatrickD@OrdinaryAmerican.net \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).