From: Harry Wei <jiaweiwei.xiyou@gmail.com>
To: linux@kbdbabel.org
Cc: romfs@googlegroups.com, rdunlap@xenotime.net,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
greg@kroah.com, akpm@linux-foundation.org
Subject: [PATCH]fix a link in Documentation/filesystem/romfs.txt
Date: Fri, 4 Mar 2011 19:59:31 +0800 [thread overview]
Message-ID: <20110304115926.GA4104@gmail.com> (raw)
Hi us,
I think it is a good patch for Documentation/filesystem/romfs.txt.
From: Alexander Kurz <linux@kbdbabel.org>
Hello romfs group,
I have posted a patch to fix the reference to
the outdated ftp site (which still serves genromfs-0.5.1) in
Documentation/filesystems/romfs.txt last month,
but nobody has picked it up yet.
Does anybody like to forward this?
Thanks, Alexander
Thanks.
Best Regards.
Harry Wei.
Signed-off-by: Alexander Kurz<linux@kbdbabel.org>
Signed-off-by: Harry Wei <harryxiyou@gmail.com>
---
Documentation/filesystems/romfs.txt | 3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/Documentation/filesystems/romfs.txt b/Documentation/filesystems/romfs.txt
index 2d2a7b2..3b7ef40 100644
--- a/Documentation/filesystems/romfs.txt
+++ b/Documentation/filesystems/romfs.txt
@@ -17,8 +17,7 @@ comparison, an actual rescue disk used up 3202 blocks with ext2, while
with romfs, it needed 3079 blocks.
To create such a file system, you'll need a user program named
-genromfs. It is available via anonymous ftp on sunsite.unc.edu and
-its mirrors, in the /pub/Linux/system/recovery/ directory.
+genromfs. It is available on http://romfs.sourceforge.net.
As the name suggests, romfs could be also used (space-efficiently) on
various read-only media, like (E)EPROM disks if someone will have the
--
1.7.0.4
next reply other threads:[~2011-03-04 12:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-04 11:59 Harry Wei [this message]
2011-03-04 17:35 ` [PATCH]fix a link in Documentation/filesystem/romfs.txt Randy Dunlap
2011-03-06 21:09 ` Jiri Kosina
2011-03-06 21:12 ` Jiri Kosina
2011-03-07 10:29 ` Harry Wei
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=20110304115926.GA4104@gmail.com \
--to=jiaweiwei.xiyou@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@kbdbabel.org \
--cc=rdunlap@xenotime.net \
--cc=romfs@googlegroups.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.