Post by William UnruhPost by Gilberto F da SilvaKnowing the remaining charge of a battery is not a simple task like
looking at the level of liquid in a tank. A bottle you look at it or
pick it up to know if it's full or empty. A battery has the same
appearance and weight whether it is charged or empty.
It is necessary for some hardware to convert voltage values for the
computer to try to estimate how much the battery is charged. In the
case of the installer it is quite different. There is a way to know
exactly how much is left to install.
You do not listen do you.
I'm detecting a fair amount of OCPD in this thread. <rolling eyes>
Post by William UnruhAs I have already said, it is NOT simple to know how much time there
is left to install. Downloading time varies by orders of magnitude,
depending on the congenstion between your machine and the server, on
your own computer's congestion,etc. And then there is the
installation time, which depends on many things as well. Counting the
number of files to be downloaded is a very bad estimate of how long
it will take to install them after they have been downloaded.
Counting their length similarly does not tell you what the lenght is.
Ie, you have never tried to write a program to determine what the
installation length is going to be and yet you claim yourself to be
an expert.
I have been exclusively using GNU/Linux for 23 years now, and over the
years, I have installed several GNU/Linux distributions on anything
ranging from laptops and desktops to servers. I used to rll my own
kernels — and I've never built a kernel that wouldn't boot — and I've
even dabbled with Gentoo as both dom0 and domU on the Xen hypervisor.
Not a single one of the distribution installers that had a timer was
ever accurate in its presentation of how much time was needed, and the
timer value would often be all over the place, just as when I'm making
a backup with Timeshift. Those timers are not meant to be accurate;
they are meant to be approximations only.
Clock speed, bus speed, drive latency, download speed, number of
files, file size, number of cores and/or threads, process priority,
number of running processes — e.g. running just the installer versus
running it from within a live session — and even the I/O scheduler,
there are simply too many variables. Even a kernel with real-time
patches would have difficulty catching up.
OP should drop the subject. Even Ubuntu's timer is only making a best
guess, and if that best guess happened to be close enough to the actual
time needed for installing for OP to consider that "accurate", then that
would have been a fluke.
--
With respect,
= Aragorn =