Re: teal(?) messages during boot.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 7/24/24 9:15 AM, home user via users wrote:
(f39 workstation; 6.9.9-100.fc39.x86_64)

Since last patching my stand-alone workstation last Thursday (July 18), I've been seeing messages during boot that are colored some strange color between green and blue (I'm calling it "teal"). Other boot message text is gray.  I don't recall seeing "teal" messages before during boot.  The messages scroll by too fast to catch what they're saying.

question #1
How do I find these "teal" boot messages so I can actually see what they're saying?  "System Log", "Logs", "vim", "more", "less", "cat", "gvim" all do not show color.  (I'm using gnome.)

question #2
When I do "ls", the output is colored:
* some bluish color for directories;
* magenta for image and video files;
* green for "ordinary" (text, LibreOffice, PDF, etc.) data files;
* bold green for executable files;
and so on.  The colors mean something.  What does the "teal" in the boot logs mean?

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.

1.a If (1) above is wrong, how do I "freeze" and "unfreeze" the messages during the boot process?

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.

2.a If (2) above is correct, where are the other messages stored?

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?

--
_______________________________________________
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



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux