do we need Plymouth?
by Chris Murphy
cc: cloud@, server@ fpo
Hi,
When troubleshooting early boot issues with a console, e.g. virsh console, or the virt-manager console, or even a server's remote management console providing a kind of virtual serial console... the boot scroll is completely wiped. This is a new behavior in the last, I'm not sure, 6-12 months? Everything before about 3 seconds is cleared as if the console reset command was used, as in it wipes my local scrollback.
I captured this with the script command, and when I cat this 76K file, it even wipes the local console again. So there is some kind of control character that's ordering my local console to do this. The file itself contains the full kernel messages. I just can't cat it. I have to open it in a text editor that ignores this embedded console reset command.
With the help of @glb, we discovered that this is almost certainly Plymouth. When I boot with parameter plymouth.enable=0 the problem doesn't happen. And hence the higher level question if we really even need Plymouth in Server or Cloud editions?
I suppose ideally we'd track down the problem and fix plymouth, so that existing installations get fixed. Whereas if we remove plymouth, we have to ponder whether and how to remove plymouth from existing installations. Unless we flat out aren't using it at all.
Any ideas?
Plymouth is in the @core group in fedora-comps, so pretty much everything gets it.
https://pagure.io/fedora-comps/blob/main/f/comps-f37.xml.in#_635
--
Chris Murphy
1 year, 8 months
Opera Mini Apk 2022
by mR DEV
Opera Mini allows you to browse the internet fast and privately whilst saving up to 90% of your data. The Opera Mini internet browser has a massive amount of functionalities all in one app and is trusted by millions of users around the world every day.
• Private Browser
Opera Mini is a secure browser providing you with great privacy protection on the web. Use private tabs to browse incognito & browse privately without leaving a trace on your device or being tracked.
https://ammarz.org/opera-mini/
1 year, 8 months
Technical Specification discussion
by Peter Boy
We decided to further discuss section 1.2 (File System and Storage Organization) on the mailing list to prepare a final decision next meeting.
The text on hackmd is for an unknown reason broken. Instead to spend time to repair it I’ve transferred the text to our team page, a task we had to do anyway.
You find the text at:
https://docs.fedoraproject.org/en-US/server-working-group/docs/server-tec...
Because it has not yet been finalized, it is not linked anywhere.
I have made some modifications to section 1.2 and taken up suggestions from Chris.
Some comments on our discussion and the draft.
I am convinced that a technical specification has to include a description and explanation of the properties and also a rationale if they are not self-explanatory. And the storage organization is on the one hand not self-explanatory and on the other hand one of the distinguishing features of Fedora Server.
A serious and genuine specification involves setting out goals and intentions and deriving technical properties from them (and justifying the effort involved). Otherwise, it would be a superfluous legitimization effort and a waste of time, which I would not be willing to do.
The text also does not restrict future flexibility (see Chris 17:7:41 UTC). In any case, we need to periodically review the techn. spec. We really shouldn't leave it for another 8 years or so. And then Chris is welcome to propose BTRFS as default again and maybe the technical and organizational realities will be different than when we last discussed it. And we are free to decide on a different rationale and implementation. Or maybe we can keep the basic principle and only change the implementation.
1 year, 8 months
Regrets on attending today's IRC meeting
by John W. Himpel
All,
I am volunteering today at a Multi-Agency Resource Center in our area to provide food and other essential goods and
services to victims of the recent flash flooding in our area. As a result, I will be unable to address the
Wildfly/ansible agenda item at today's meeting.
Perhaps we can address this topic at out next meeting.
John Himpel
1 year, 8 months
