From: Petr Vorel <pvorel@suse.cz>
To: "Enji Cooper (yaneurabeya)" <yaneurabeya@gmail.com>
Cc: ltp@lists.linux.it, automated-testing@lists.yoctoproject.org
Subject: Re: [LTP] [PATCH v2 1/6] doc: INSTALL: dma_thread_diotest.c: Remove runltp from doc
Date: Mon, 23 Feb 2026 13:02:39 +0100 [thread overview]
Message-ID: <20260223120239.GB462451@pevik> (raw)
In-Reply-To: <C2672F75-E168-4039-B13C-4E9456E96FFD@gmail.com>
> > On Feb 22, 2026, at 12:21 PM, Petr Vorel <pvorel@suse.cz> wrote:
> >> Hi!
> >>>>>>> @@ -105,9 +105,9 @@ Quick Start
> >>>>>>> $ ./configure
> >>>>>>> $ make all
> >>>>>>> # make install
> >>>>>> ^
> >>>>>> This should be $ (not caused by this patch but worth fixing)
> >>>>> I can change it, but IMHO for creating /opt/ltp is needed to run it as root
> >>>>> for a first time. Or one must chmod/chown /opt/ltp under root.
> >>>> Huh? The make install should just work fine. I'm just pointing out the
> >>>> typo # vs $. Or did I miss something?
> >>> Yeah, I understand it and plan to change # => $. I talked about /opt (our
> >>> default prefix) usually not being writable by regular users (installing any
> >>> software using standard system prefix will have this problem). Root is needed
> >>> only for creating /opt/ltp. That was the reason for the original user to use '#'.
> >>> But as I wrote, I'm ok to change the prompt.
> >> Ah, that's a bit confusing then because in shell script # is a comment.
> >> I usually prefix commands that needs root with sudo instead. So what
> >> about "$ sudo make install" ?
> > +1, good point.
> > I'll merge whole patchset with this change tomorrow.
> Using markdown and sudo would make it unambiguous. I’m not sure if markdown makes sense here, but at the very least I would reference sudo or made the directions explicitly state that the command must be run as root.
> Just my 2 cents...
> -Enji
> Example:
> ```bash
> $ ./configure
> $ make all
> $ sudo make install
> ```
I would prefer to drive away from GitHub Markdown, when we have readthedocs
https://linux-test-project.readthedocs.io/en/latest/index.html
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-02-23 12:03 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-05 12:15 [LTP] [PATCH v2 0/6] Remove runltp Petr Vorel
2026-02-05 12:15 ` [LTP] [PATCH v2 1/6] doc: INSTALL: dma_thread_diotest.c: Remove runltp from doc Petr Vorel
2026-02-17 9:19 ` Cyril Hrubis
2026-02-17 10:23 ` Andrea Cervesato via ltp
2026-02-19 20:20 ` Petr Vorel
2026-02-20 8:12 ` Andrea Cervesato via ltp
2026-02-20 11:47 ` Cyril Hrubis
2026-02-20 15:34 ` Petr Vorel
2026-02-20 16:35 ` Cyril Hrubis
2026-02-22 20:21 ` Petr Vorel
2026-02-22 20:26 ` Enji Cooper (yaneurabeya)
2026-02-23 12:02 ` Petr Vorel [this message]
2026-02-23 15:44 ` Petr Vorel
2026-02-05 12:15 ` [LTP] [PATCH v2 2/6] testscripts/lvmtest.sh: Replace runltp with kirk Petr Vorel
2026-02-17 9:22 ` Cyril Hrubis
2026-02-05 12:15 ` [LTP] [PATCH v2 3/6] runltp: Remove Petr Vorel
2026-02-17 9:29 ` Cyril Hrubis
[not found] ` <E8C09635-59E1-4DB0-A223-7D05616029E4@gmail.com>
2026-02-18 21:09 ` Anders Roxell
2026-02-19 8:29 ` Jan Stancek via ltp
2026-02-05 12:15 ` [LTP] [PATCH v2 4/6] pan: Remove Petr Vorel
2026-02-17 9:34 ` Cyril Hrubis
2026-02-05 12:15 ` [LTP] [PATCH v2 5/6] tools: Remove tools used by runltp Petr Vorel
2026-02-17 9:46 ` Cyril Hrubis
2026-02-05 12:15 ` [LTP] [PATCH v2 6/6] kirk: Remove runltp-ng symlink Petr Vorel
2026-02-17 9:50 ` Cyril Hrubis
[not found] ` <29BA2651-45AB-4A29-973D-AAE15C887ACB@gmail.com>
2026-02-18 21:10 ` Anders Roxell
2026-02-11 9:17 ` [LTP] [PATCH v2 0/6] Remove runltp Andrea Cervesato via ltp
2026-02-11 9:20 ` Petr Vorel
2026-02-20 11:55 ` Andrea Cervesato via ltp
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=20260223120239.GB462451@pevik \
--to=pvorel@suse.cz \
--cc=automated-testing@lists.yoctoproject.org \
--cc=ltp@lists.linux.it \
--cc=yaneurabeya@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 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.