From: Randy Dunlap <rdunlap@infradead.org>
To: Nadav Tasher <tashernadav@gmail.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: corbet@lwn.net
Subject: Re: [PATCH] docs: replace broken links in ramfs-rootfs-initramfs docs
Date: Sat, 25 Oct 2025 15:20:41 -0700 [thread overview]
Message-ID: <f72d1739-8c3d-4bc8-a26d-8f03b3aecf15@infradead.org> (raw)
In-Reply-To: <20251025171625.33197-1-tashernadav@gmail.com>
On 10/25/25 10:16 AM, Nadav Tasher wrote:
> http://www.uwsg.iu.edu/ doesn't seem to exist anymore.
> I managed to find backups on archive.org, which helped me find
> the right links on https://lore.kernel.org/.
>
> http://freecode.com/projects/afio was also down, so I figured
> it could be replaced with https://linux.die.net/man/1/afio.
>
> Replace broken links to mailing list and aifo tool.
afio
> Signed-off-by: Nadav Tasher <tashernadav@gmail.com>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Tested-by: Randy Dunlap <rdunlap@infradead.org>
> ---
> Documentation/filesystems/ramfs-rootfs-initramfs.rst | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/Documentation/filesystems/ramfs-rootfs-initramfs.rst b/Documentation/filesystems/ramfs-rootfs-initramfs.rst
> index fa4f81099cb4..a9d271e171c3 100644
> --- a/Documentation/filesystems/ramfs-rootfs-initramfs.rst
> +++ b/Documentation/filesystems/ramfs-rootfs-initramfs.rst
> @@ -290,11 +290,11 @@ Why cpio rather than tar?
>
> This decision was made back in December, 2001. The discussion started here:
>
> - http://www.uwsg.iu.edu/hypermail/linux/kernel/0112.2/1538.html
> +- https://lore.kernel.org/lkml/a03cke$640$1@cesium.transmeta.com/
>
> And spawned a second thread (specifically on tar vs cpio), starting here:
>
> - http://www.uwsg.iu.edu/hypermail/linux/kernel/0112.2/1587.html
> +- https://lore.kernel.org/lkml/3C25A06D.7030408@zytor.com/
>
> The quick and dirty summary version (which is no substitute for reading
> the above threads) is:
> @@ -310,7 +310,7 @@ the above threads) is:
> either way about the archive format, and there are alternative tools,
> such as:
>
> - http://freecode.com/projects/afio
> + https://linux.die.net/man/1/afio
>
> 2) The cpio archive format chosen by the kernel is simpler and cleaner (and
> thus easier to create and parse) than any of the (literally dozens of)
> @@ -331,12 +331,12 @@ the above threads) is:
> 5) Al Viro made the decision (quote: "tar is ugly as hell and not going to be
> supported on the kernel side"):
>
> - http://www.uwsg.iu.edu/hypermail/linux/kernel/0112.2/1540.html
> + - https://lore.kernel.org/lkml/Pine.GSO.4.21.0112222109050.21702-100000@weyl.math.psu.edu/
>
> explained his reasoning:
>
> - - http://www.uwsg.iu.edu/hypermail/linux/kernel/0112.2/1550.html
> - - http://www.uwsg.iu.edu/hypermail/linux/kernel/0112.2/1638.html
> + - https://lore.kernel.org/lkml/Pine.GSO.4.21.0112222240530.21702-100000@weyl.math.psu.edu/
> + - https://lore.kernel.org/lkml/Pine.GSO.4.21.0112230849550.23300-100000@weyl.math.psu.edu/
>
> and, most importantly, designed and implemented the initramfs code.
>
--
~Randy
next prev parent reply other threads:[~2025-10-25 22:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-25 17:16 Nadav Tasher
2025-10-25 22:20 ` Randy Dunlap [this message]
2025-10-29 16:06 ` Jonathan Corbet
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=f72d1739-8c3d-4bc8-a26d-8f03b3aecf15@infradead.org \
--to=rdunlap@infradead.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tashernadav@gmail.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
all inboxes | Powered by JetHome®