On 7/28/24 11:09 PM, Samuel Sieb wrote:
On 7/28/24 7:56 PM, home user via users wrote:
I have a few follow-up questions.
1. correct or wrong:
During the boot process, before log-in becomes available, there is no way to "freeze" and "unfreeze" the messages appearing on the monitor.
correct
2. correct or wrong:
Not all messages displayed on the monitor during the boot process, before log-in becomes available, are stored in /var/log/boot.log* files.
If you have "quiet" on the kernel command line, then all of what you see gets stored unless there's a high-priority kernel message of some sort.
I have neither "quiet" nor "plymouth" in my kernel command line. But having looked at various /var/log/ files, I'm not finding everything I see during the boot process. Example: them tealish-colored messages. I've stopped looking for them by color. Rather, I notice they're 3-4 lines long (wrapped) on the monitor during the boot process, but I'm not seeing such long entries in the /var/log/ files that I looked at.
2.a If (2) above is correct, where are the other messages stored?
Everything is in the journal. Once the journal gets started, dmesg is dumped into the journal first.
3. If there are a group of lines in a log file that I want to put in a post to this list, and that log file uses formatting codes, what are the best ways to put that group of lines into an e-mail message to this list without the formatting codes, WITHOUT manually retyping those lines in the e-mail, and WITHOUT having to manually delete every formatting code character?
"cat" it in a terminal, then copy from there.
I'll have to play with that a little.
--
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue