From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [PATCH] Testcase for checking lvm module
Date: Fri, 09 Apr 2010 15:43:25 +0200 [thread overview]
Message-ID: <4BBF2EFD.3080907@gmail.com> (raw)
In-Reply-To: <d019d53c1003161205w52930f85t64e26eed8346eae9@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1242 bytes --]
BVK Chaitanya wrote:
> Hi,
>
>
> Attached patch adds a testcase to check for GRUB's lvm module
> functionality. It configures lvm volumes on-the-fly on temporary disk
> images, and tests to see whether grub-shell ls command identifies them
> or not.
>
> Since all of the LVM operations need root privilege, this real test is
> performed only when it is executed as root (or sudo make check); test
> simply passes otherwise. In future we may add sudo-check Makefile
> target to execute these type of tests automatically sing "sudo"
> feature.
>
>
Using sudo in any of the grub scripts isn't an option. Would you like
the programs you install silently acquiring root rights? At the limited
we can make a priviliged-tests target which user will execute like:
sudo make privelegied-tests
Or we can make a script generate-gnu-linux-images.sh which will create
all filesystem and lvm images needing root privelgies. This will also
make repeated make check faster
But it's way better to avoid needing root privelegies in the first
place. In particular operations with images shouldn't need root
privelegies. Have you looked into fakeroot program?
>
>
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 293 bytes --]
prev parent reply other threads:[~2010-04-09 13:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-16 19:05 [PATCH] Testcase for checking lvm module BVK Chaitanya
2010-03-16 19:06 ` BVK Chaitanya
2010-04-09 13:50 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-04-09 13:43 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
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=4BBF2EFD.3080907@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@gnu.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.