On 06/12/2013 01:54 PM, John Austin wrote:
On Tue, 2013-06-11 at 21:22 -0400, Doug wrote:
> On 06/11/2013 09:00 PM, Joe Zeff wrote:
>> On 06/11/2013 05:29 PM, Tim wrote:
>
>> Agreed. However, it can be argued that if you know enough to do that,
>> you should also know enough to be careful with rm. As root, unless I'm
>> deleting exactly one file, I use ls first to see exactly what I'm going
>> to delete. It's a form of "measure twice, cut once" that's
prevented at
>> least one disaster over the years. (N.B.: once you've examined the
>> results of ls, the safest way to use rm is to use the up arrow to get
>> back the preceding command line, then edit it. That's probably the best
>> way to be sure that what you delete is what you listed.)
>
> I find that when you are going to perform some kind of action on a file,
> and you have found it using ls -la, highlight the file and ctrl-shift-c.
> Then whetever your command is, command ctrl-shift-v.
>
> That's a better option than command filename-without-last-part* because
> there may be two or more identical first part filenames, but different
> extensions. The most obvious is filename and filename.bak. Another
> common example is a filename with two or more version numbers in the
> extensions.
>
> --doug
>
>
> --
> Blessed are the peacemakers..for they shall be shot at from both sides.
> --A.M.Greeley
Tip from this list I think
If using "su -" regularly
add this to /root/.bashrc to obtain the root prompt in red
PS1="\[\033[1;31m\][\u@\h:\w]$\[\033[0m\] "
John
That is a good tip ...but probably not for the colour-blind ;-)
Thanks.
--
Regards,
Rejy M Cyriac (rmc)