[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] xm dmesg output


  • To: "Adam Heath" <doogie@xxxxxxxxxxxxx>
  • From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
  • Date: Tue, 29 Nov 2005 17:58:41 -0000
  • Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Tue, 29 Nov 2005 17:58:33 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcX1CJ6TBWJpv8iaT/2ZJ+CS5FiRjAAAUslw
  • Thread-topic: [Xen-devel] xm dmesg output

 
> Speaking of "xm dmesg", because xm is in /usr/sbin, it 
> implies that a normal user wouldn't normally need to run it.
> 
> 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?

Having a wrapper to make xm available in /usr/sbin/ and /usr/bin seems
pretty gross. It should be in one or the other, but I'm willing to
accept it may currently be in the wrong one. Let's see if anyone has a
strong opinion...

Ian

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.