From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: xm dmesg output Date: Wed, 30 Nov 2005 10:15:07 -0600 Message-ID: <438DD00B.9@us.ibm.com> References: <1133212285.16113.3.camel@dyn95341161> <520fab8eb58226fb4c917f1628d27477@cl.cam.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Adam Heath Cc: xen-devel List-Id: xen-devel@lists.xenproject.org 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 > > >