From: Dominique Martinet <asmadeus@codewreck.org>
To: ericvh@kernel.org, Aayush Patil <aayushpatilsch@gmail.com>
Cc: lucho@ionkov.net, linux_oss@crudebyte.com, corbet@lwn.net,
skhan@linuxfoundation.org, v9fs@lists.linux.dev,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs/filesystems/9p: fix broken external links
Date: Tue, 19 May 2026 21:26:24 +0900 [thread overview]
Message-ID: <agxW8An7fRApCY1r@codewreck.org> (raw)
In-Reply-To: <20260510182856.17569-1-aayushpatilsch@gmail.com>
Aayush Patil wrote on Sun, May 10, 2026 at 11:58:56PM +0530:
> The xcpu.org links for xcpu-talk, kvmfs, and cellfs-talk are dead
> with no archived snapshots available on the Wayback Machine, so
> remove them. The PROSE I/O link redirects to a dead server; replace
> it with an archived version from web.archive.org.S
(I assume the final S is a typo here)
Eric, it looks like you're the one who added these links, would you
happen to have a copy around if you care about keeping these?
Otherwise I'm not sure of the value of listing the papers without the
actual files available, but I don't mind either way.
I agree dead links are of little value though so will pick this up if
there's no reply in a while
>
> Signed-off-by: Aayush Patil <aayushpatilsch@gmail.com>
> ---
> Documentation/filesystems/9p.rst | 5 +----
> 1 file changed, 1 insertion(+), 4 deletions(-)
>
> diff --git a/Documentation/filesystems/9p.rst b/Documentation/filesystems/9p.rst
> index be3504ca034a..65809a1dad21 100644
> --- a/Documentation/filesystems/9p.rst
> +++ b/Documentation/filesystems/9p.rst
> @@ -23,13 +23,10 @@ the 9p client is available in the form of a USENIX paper:
> Other applications are described in the following papers:
>
> * XCPU & Clustering
> - http://xcpu.org/papers/xcpu-talk.pdf
I found http://mirtchovski.postnix.pw/p9/xcpu-talk.pdf but I'm not sure
if it's the same file
> * KVMFS: control file system for KVM
> - http://xcpu.org/papers/kvmfs.pdf
Looks close but perhaps not the same as
https://www.kernel.org/doc/ols/2007/ols2007v2-pages-59-64.pdf ?
> * CellFS: A New Programming Model for the Cell BE
> - http://xcpu.org/papers/cellfs-talk.pdf
Couldn't find anything fo this one
> * PROSE I/O: Using 9p to enable Application Partitions
> - http://plan9.escet.urjc.es/iwp9/cready/PROSE_iwp9_2006.pdf
> + http://web.archive.org/web/20110101152020/http://plan9.escet.urjc.es/iwp9/cready/PROSE_iwp9_2006.pdf
> * VirtFS: A Virtualization Aware File System pass-through
> https://kernel.org/doc/ols/2010/ols2010-pages-109-120.pdf
>
--
Dominique Martinet | Asmadeus
next prev parent reply other threads:[~2026-05-19 12:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-10 18:28 [PATCH] docs/filesystems/9p: fix broken external links Aayush Patil
2026-05-19 12:26 ` Dominique Martinet [this message]
[not found] ` <CABc3pKGKCLydod2NOgETP-z0T5BHep8hyy7z2UF3o+DrWEh5yw@mail.gmail.com>
2026-05-19 13:53 ` Aayush Patil
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=agxW8An7fRApCY1r@codewreck.org \
--to=asmadeus@codewreck.org \
--cc=aayushpatilsch@gmail.com \
--cc=corbet@lwn.net \
--cc=ericvh@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux_oss@crudebyte.com \
--cc=lucho@ionkov.net \
--cc=skhan@linuxfoundation.org \
--cc=v9fs@lists.linux.dev \
/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