Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#8740 - difficult to read output of /etc/rc.d/functions
Attached to Project:
Arch Linux
Opened by Antony Jepson (smurnjiff) - Friday, 23 November 2007, 00:34 GMT
Last edited by Greg (dolby) - Thursday, 05 June 2008, 19:12 GMT
Opened by Antony Jepson (smurnjiff) - Friday, 23 November 2007, 00:34 GMT
Last edited by Greg (dolby) - Thursday, 05 June 2008, 19:12 GMT
|
DetailsDescription:
When booting, the script /etc/rc.d/functions places the status all the way to the right of the screen. For example, it will say: :: Starting OpenNTPD [DONE] The [DONE] is placed to the right edge of the screen, which makes it difficult to which daemon fails, or which daemon is backgrounded. I propose you place the status of each daemon closer to the name of the daemon. Here is a patch: antony@GENTOO ~ % diff -u functions /etc/rc.d/functions --- functions 2007-11-22 18:01:38.000000000 -0500 +++ /etc/rc.d/functions 2007-11-22 17:33:41.000000000 -0500 @@ -17,7 +17,7 @@ USECOLOR="" fi # we use 13 characters for our own stuff -STAT_COL=$[$STAT_COL - 13] +STAT_COL=$[$STAT_COL - 70] # disable colors on broken terminals TERM_COLORS="$(tput colors 2>/dev/null)" Of course, I realise that it depends on the number of columns available; a more conservative change of "STAT_COL=$[$STAT_COL - 30]" could be made instead of "STAT_COL=$[$STAT_COL - 70]". Regardless of the number, 13 is too small. Additional info: * package version(s) core/initscripts-2007.11-2 * config and/or log files etc. /etc/rc.d/functions Steps to reproduce: Simply watch boot output without any modifications to the boot script. |
This task depends upon
Comment by Jan de Groot (JGC) -
Friday, 23 November 2007, 07:25 GMT
On a normal 80x24 screen 70 is way too large.
Comment by Roman Kyrylych (Romashka) -
Friday, 23 November 2007, 09:07 GMT
I have 20" wide TFT and I'm fine with the current output. My output is still 80 chars wide. If you use a framebuffer console with more chars in a row - the only way to fix this is to patch /etc/rc.d/functions by yourself and put NoUpgrade=etc/rc.d/functions in pacman.conf
Comment by Antony Jepson (smurnjiff) -
Friday, 23 November 2007, 17:37 GMT
What is the resolution of your screen during the boot process? I have a 14in screen.
Comment by Roman Kyrylych (Romashka) -
Friday, 23 November 2007, 17:45 GMT
I don't know, but it's standard 80x25 (or 24) chars, with 8x16 font. The physical resulution of my TFT is 1680x1050. Of course it does interpolation to get 80x25 chars.
Comment by Antony Jepson (smurnjiff) -
Friday, 23 November 2007, 20:29 GMT
That probably explains why you agree with the default output. You have a larger screen, thus everything will appear larger. A smaller screen makes it harder to see which status applies to which daemon, even at the same resolution.
Comment by Greg (dolby) -
Monday, 05 May 2008, 22:02 GMT
is this actually a bug? it seems like the one having the problem just uses insane configs
Comment by Gavin Bisesi (Daenyth) -
Wednesday, 04 June 2008, 18:16 GMT
I agree, this seems like user error more than a bug.