From: Christian Kujau <lists@nerdbynature.de>
To: fstests@vger.kernel.org
Subject: README: fsgqa needs a home directory too
Date: Fri, 31 Jan 2020 13:22:49 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.22.395.2001311318390.2831@trent.utfs.org> (raw)
generic/128 whould fail with:
QA output created by 128
+su: warning: cannot change directory to /home/fsgqa: No such file or directory
Adjust README to create a home directory too. And (totally unrelated),
fix the 404 for the udf_test tool.
Signed-off-by: Christian Kujau <lists@nerdbynature.de>
--- README.orig 2020-01-12 08:43:34.000000000 -0800
+++ README 2020-01-31 13:18:12.494026480 -0800
@@ -19,7 +19,7 @@
(Note that for RHEL and CentOS, you may need the EPEL repo.)
- run make
- run make install
-- create fsgqa test user ("sudo useradd fsgqa")
+- create fsgqa test user ("sudo useradd -m fsgqa")
- create fsgqa group ("sudo groupadd fsgqa")
- create 123456-fsgqa test user ("sudo useradd 123456-fsgqa")
@@ -33,7 +33,7 @@
- install administrative tools specific to the filesystem you wish to test
- If you wish to run the udf components of the suite install
mkudffs. Also download and build the Philips UDF Verification Software
- from http://www.extra.research.philips.com/udf/, then copy the udf_test
+ from https://www.lscdweb.com/registered/udf_verifier.html, then copy the udf_test
binary to xfstests/src/. If you wish to disable UDF verification test
set the environment variable DISABLE_UDF_TEST to 1.
--
BOFH excuse #220:
Someone thought The Big Red Button was a light switch.
next reply other threads:[~2020-01-31 21:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-31 21:22 Christian Kujau [this message]
2020-02-17 12:53 ` README: fsgqa needs a home directory too Eryu Guan
2020-02-19 0:33 ` Christian Kujau
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=alpine.DEB.2.22.395.2001311318390.2831@trent.utfs.org \
--to=lists@nerdbynature.de \
--cc=fstests@vger.kernel.org \
/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.