On Wed, 22 Nov 2017, Kevin Chadwick wrote:
If you do it manually you are unlikely to do it when you should.
From time to time I type: sync. I am more afraid of hardware failure,
electricity blackout, my own errors, than of hacker attacks.
Even on an 366mhz i386 it does not take very long??
% time /usr/libexec/reorder_kernel
15.430u 2.700s 0:35.24 51.4% 0+0k 1392+2984io 10429pf+0w
This was an Intel Atom N270. I have much weaker processors.
Fair enough I get that but personally I would dump the 10,000 write
flash memory.
It is not only that with many writings EEPROM becomes ROM, but
that it is very slow, specially writing, specialy when attached
to USB, perhaps USB 1.
Actually it is a separate forked process ran at the very end, so not
really.
Yes, it will not spoil the booting if it fails, one can compare it with
the starting of daemons, but the last do not make anymore than
wait for connections. On the other side, the reordering of libraries
does not run in the background, sure for a good reason: to use reordered
libs from the beginning, to run daemons with reordered libraries.
But one could do it as KARK: reorder now for the next boot.
comment out its call in rc. The reordering of libraries can be
disabled, but the definition of the procedure is embedded in rc
and cannot be run manually.
Of course it can, check out the log maybe. I had to get a fresh tarball
from base62.tgz one time when I screwed it up though.
I am speaking of the reordering of libraries, not KARL.
Just see reorder_libs() in rc script. You can disable it
in rc.conf, but you cannot run it manually. KARL cannot
be disabled in rc.conf.
Rodrigo.
