On Thu, Oct 4, 2012 at 8:32 AM, Earnie Boyd wrote:
> On Thu, Oct 4, 2012 at 7:30 AM, Sean Murphy wrote:
>>
>> That did it. Placed the executable in /bin, and it ran as expected.
>>
>
> You should not move /usr/sbin files to /bin. You should use
> /usr/sbin/BINARY or add /usr/sbin to the PATH var
On Thu, Oct 4, 2012 at 7:30 AM, Sean Murphy wrote:
>
> That did it. Placed the executable in /bin, and it ran as expected.
>
You should not move /usr/sbin files to /bin. You should use
/usr/sbin/BINARY or add /usr/sbin to the PATH variable. You'll get
confused when an update seemingly replaces
On Wed, Oct 3, 2012 at 10:31 PM, Larry Hall (Cygwin)
wrote:
> On 10/3/2012 8:26 PM, Sean Murphy wrote:
>
>
> Try /usr/sbin/hdparm.exe. /usr/sbin is not in your path by default.
>
> --
> Larry
>
> _
>
> A: Yes.
>> Q: Are you sure?
On 10/3/2012 8:26 PM, Sean Murphy wrote:
Hello all,
Decided to check out hdparm today after reading about the utility.
After install, I attempted to run the utility by executing a check on my
computer's hard drive and received a message from bash stating that
the hdparm command could not be fou
Hello all,
Decided to check out hdparm today after reading about the utility.
After install, I attempted to run the utility by executing a check on my
computer's hard drive and received a message from bash stating that
the hdparm command could not be found. Can anyone else confirm
this behavior?
5 matches
Mail list logo