Thanks for looking!
On Friday 23 October 2009 16:11:06 Marc Herbert wrote:
> In case you are using Linux you can pinpoint which files are accessed
> like this:
>
> echo 1 > /proc/sys/vm/block_dump
> dmesg -c
If you was more careful, you'd know I already did that. And there was NO
SPECIFIC FILE m
On Thu, Oct 22, 2009 at 06:47:43PM +, K??rlis Repsons wrote:
> I've set up a system, which has some disks, that are not always used, but are
> always mounted. OS and program files are all in other place and the only
> program, which still reads some blocks (echo 1 > /proc/sys/vm/block_dump),
Hello there,
dear reader, in case there can be found some solution or I can add my
observation for future improvements, I try explaining one problem with bash.
I've set up a system, which has some disks, that are not always used, but are
always mounted. OS and program files are all in other pla
> The problem is dead-simple. You cannot run this command multiple times:
>
> cp -R ./dirfoo ./dirfoo.backup
>
Sorry to add yet another (last) off topic message but I must do justice
to GNU cp. GNU cp actually does support the above thanks to a
(non-standard) option:
cp -R -T ./dir
Jo King a écrit :
>> thanks for reply. agree it's not a
>> bug with bash.
>>
>> i am inclinded to agree with the comments but bash is
>> popular and attracts a lot of newbies into scripting - a bit
>> of smart 'correction' of their wrong ways would at least
>> keep the cpu available for other proce
