Von: Máirín Duffy On 03/12/2013 08:30 AM, Fabian Deutsch wrote:
What about pulling the message stuff into plymouth and using dracut to trigger a reboot which shows the grub menu? Something along the lines: "Press ESC to see deatils or 'b' to enter the bootloader"
This is an interesting idea, but I don't think plymouth makes it any easier to display CJK & Indic glyphs. (Please someone more technical tell me if I'm wrong here, I vaguely remember this being an issue when we wanted to add a messagse to fedup)
I hoped that it would be easier to localize plymouth compared to grub2. In addition to that we'd also get rid of problems resulting of the interaction between grub2 s gfx stack and the kernel/plymouth, and last but not least we wouldn't need to maintain a theme for grub.
- fabian
Hi,
This is an interesting idea, but I don't think plymouth makes it any easier to display CJK & Indic glyphs. (Please someone more technical tell me if I'm wrong here, I vaguely remember this being an issue when we wanted to add a messagse to fedup)
I hoped that it would be easier to localize plymouth compared to grub2. In addition to that we'd also get rid of problems resulting of the interaction between grub2 s gfx stack and the kernel/plymouth, and last but not least we wouldn't need to maintain a theme for grub.
Yea it's not really easier. We start plymouth in the initrd, and we don't have fonts, translations, font rendering libraries or anything in the initrd. we could ship those things in the initrd but it would make the initrd substantially larger.
Of course we can do localized text fine on systems that don't have initrds, or at later points in the boot process after we've switched out of the initrd.
--Ray
Dne 12.3.2013 19:16, Ray Strode napsal(a):
Hi,
This is an interesting idea, but I don't think plymouth makes it any easier to display CJK & Indic glyphs. (Please someone more technical tell me if I'm wrong here, I vaguely remember this being an issue when we wanted to add a messagse to fedup)
I hoped that it would be easier to localize plymouth compared to grub2. In addition to that we'd also get rid of problems resulting of the interaction between grub2 s gfx stack and the kernel/plymouth, and last but not least we wouldn't need to maintain a theme for grub.
Yea it's not really easier. We start plymouth in the initrd, and we don't have fonts, translations, font rendering libraries or anything in the initrd. we could ship those things in the initrd but it would make the initrd substantially larger.
Of course we can do localized text fine on systems that don't have initrds, or at later points in the boot process after we've switched out of the initrd.
--Ray
May be some nice pictogram wold make it without translation.
Vít
Ray Strode wrote:
We start plymouth in the initrd, and we don't have fonts, translations, font rendering libraries or anything in the initrd. we could ship those things in the initrd but it would make the initrd substantially larger.
How about turning the messages that Plymouth needs to display into pictures? There would be a set of pre-rendered image files with translations of the phrase "Press Esc if you want to see what's going on." for all the different locales, and the correct image for the configured locale would be included when the initrd was generated. Plymouth would then just put that picture up on the screen, not caring about what language it's written in or with which font.
The passphrase prompt could be handled the same way. Instead of just a picture of a padlock there would be a picture with a translation of "Enter the disk encryption passphrase."
Are there other messages that Plymouth may need to display? I would guess there aren't so many that the scalability of this approach would be a problem.
Björn Persson
On Thu, Mar 14, 2013 at 3:30 AM, Björn Persson bjorn@xn--rombobjrn-67a.se wrote:
Ray Strode wrote:
We start plymouth in the initrd, and we don't have fonts, translations, font rendering libraries or anything in the initrd. we could ship those things in the initrd but it would make the initrd substantially larger.
How about turning the messages that Plymouth needs to display into pictures? There would be a set of pre-rendered image files with translations of the phrase "Press Esc if you want to see what's going on." for all the different locales, and the correct image for the configured locale would be included when the initrd was generated. Plymouth would then just put that picture up on the screen, not caring about what language it's written in or with which font.
The passphrase prompt could be handled the same way. Instead of just a picture of a padlock there would be a picture with a translation of "Enter the disk encryption passphrase."
Are there other messages that Plymouth may need to display? I would guess there aren't so many that the scalability of this approach would be a problem.
Björn Persson
-- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
When I think of improving the booting experience tonight, I think of a booter that can't repair itself when it's broken not Plymouth...can we fix real broken things before we fix an annoying thing like plymouth?
On Thu, Mar 14, 2013 at 03:37:23AM -0700, Dan Mashal wrote:
When I think of improving the booting experience tonight, I think of a booter that can't repair itself when it's broken not Plymouth...can we fix real broken things before we fix an annoying thing like plymouth?
Of course we can. The code's available and you can attach patches in bugzilla.
Hi,
On Thu, Mar 14, 2013 at 6:30 AM, Björn Persson bjorn@xn--rombobjrn-67a.se wrote:
How about turning the messages that Plymouth needs to display into pictures? There would be a set of pre-rendered image files with translations of the phrase "Press Esc if you want to see what's going on." for all the different locales, and the correct image for the configured locale would be included when the initrd was generated. Plymouth would then just put that picture up on the screen, not caring about what language it's written in or with which font.
Yea, we've talked about doing that before. We've also talked about querying the console font. So definitely possibilities to address the limitation.
--Ray