Ben:
Sorry about the lapse in activity/communications; I’ve been extremely busy with other work.
I did get the notice yesterday announcing the release of Lx 4.0 Beta, so I proceeded to download the file from SourceForge.
(By some fortunate coincidence, my installed Lx 4.0 Alpha version failed during the download of the Beta file…
…ever run out of gas as you pull up to the pump? )
Anyway, Beta downloaded & written to thumb drive via Rosa, loaded live version = OK, installed from Beta live version via the install option = OK (using it now to write this.)
QUESTION:
Discover shows a mere 1,315 update files totaling approximately 1.1GB waiting, if prior experience is any indication, to mercilessly mutilate my installation. (Presumably without update progress status indicators, of course!)
(“The optimist asked for a taste of the pessimist’s wine…” - from Hallowed Be Thy Name by Emerson Lake & Palmer, lyrics by Peter Sinfield https://youtu.be/q8cjlvI6wIY)
Last time I attempted the Alpha version update, you suggested I use this command in Konsole, which I did:
$ sudo dnf --refresh upgrade
The resulting screen output was so large a file that apparently it exceeded some size limit; I was unable afterward to scroll the screen display up to the beginning of the file, as it had been overwritten, at least as far as the display screen was able to show.
This time I want to direct the output to be simultaneously displayed on the screen as well as written to a file, and as much fun as this purports to be ("Masochist: “Beat me.”… Sadist: “No.”), I only want to do it once, if at all possible.
I have found a potential solution in the CLI “tee” command; however, there appears to be some discussion about the intricacies of how the resulting combination of stdout and stderr will be chronologically displayed, with several complex options suggested.
I don’t know how familiar you are with this command, or to what extent it may make any difference, but if so:
Since I want to obtain full, accurate, detailed (and especially useful!) information regarding the progress of this update process, what command string(s) would you consider the optimally preferred choice for debugging purposes?
I appreciate your assistance with this, Ben, and I respect your opinion.
I really do want to obtain and address every last bit of relevant information so this upcoming release will be stable and optimized.
I know it’s only in Beta now, and I don’t mind tracing and correcting every fault detail, but I don’t want to do this incompletely and leave any stone unturned.
What do you think about the issue of stdout and stderr entries appearing out of chronological sequence in the output file?
Is this a concern?
Do you advise combining them into a single file?
Any other thoughts and/or suggestions?
Your thoughts would be greatly appreciated.
I’m eager to dive into this… this version so far looks really good!
Thanks, Ben
Sincerely,
Michael Orlando