From: Anthony Liguori <aliguori@us.ibm.com>
To: Adam Heath <doogie@brainfood.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: xm dmesg output
Date: Wed, 30 Nov 2005 10:15:07 -0600 [thread overview]
Message-ID: <438DD00B.9@us.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0511291113570.1621@gradall.private.brainfood.com>
Adam Heath wrote:
>Speaking of "xm dmesg", because xm is in /usr/sbin, it implies that a normal
>user wouldn't normally need to run it.
>
>
xm dmesg requires root privileges (in order to make the readconsolering
hypercall) which means that it can only be run by root. There's no
point in cluttering a user's path with things that he cannot run :-)
The only exception would be users with sudo privileges. I think it's
common enough to put /usr/sbin and /sbin in sudo users PATHs though so
they don't need it in /usr/bin.
Regards,
Anthony Liguori
>However, xm provides several informational commands, dmesg being just one of
>them. And, since the normal dmesg is in /bin, it might make sense to have
>them available in /usr/bin as well.
>
>However, this could just be done with a shell script wrapper. Would such a
>patch be accepted?
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.xensource.com
>http://lists.xensource.com/xen-devel
>
>
>
next prev parent reply other threads:[~2005-11-30 16:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-28 21:11 xm dmesg output David F Barrera
2005-11-29 10:26 ` Keir Fraser
2005-11-29 17:15 ` Adam Heath
2005-11-30 16:15 ` Anthony Liguori [this message]
2005-11-29 22:15 ` David F Barrera
2005-11-30 11:39 ` Keir Fraser
2005-12-01 17:49 ` David F Barrera
2005-12-01 18:37 ` Adam Heath
2005-12-01 19:04 ` David F Barrera
-- strict thread matches above, loose matches on Subject: below --
2005-11-29 17:58 Ian Pratt
2005-11-30 2:46 ` Horms
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=438DD00B.9@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=doogie@brainfood.com \
--cc=xen-devel@lists.xensource.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.