Hello
How do I switch off color mode on console (we have just BW monitor at the server) and not for all terminal connections?
On 24/08/06, "Petr "Qaxi" Klíma" qaxi@seznam.cz wrote:
How do I switch off color mode on console (we have just BW monitor at the server) and not for all terminal connections?
Assuming you mean X server. I think you just need to change the color depth in X configuration file.
Sudev Barar napsal(a):
On 24/08/06, "Petr "Qaxi" Klíma" qaxi@seznam.cz wrote:
How do I switch off color mode on console (we have just BW monitor at the server) and not for all terminal connections?
Assuming you mean X server. I think you just need to change the color depth in X configuration file.
No, no I mean text console ...
On 25/08/06, "Petr "Qaxi" Klíma" qaxi@seznam.cz wrote:
Sudev Barar napsal(a):
On 24/08/06, "Petr "Qaxi" Klíma" qaxi@seznam.cz wrote:
How do I switch off color mode on console (we have just BW monitor at the server) and not for all terminal connections?
Assuming you mean X server. I think you just need to change the color depth in X configuration file.
No, no I mean text console ...
look at .bash* files in your home or the /etc/bashrc (or similar) files.
Ken McLennan napsal(a):
G'day there One & All,
No, no I mean text console ...
look at .bash* files in your home or the /etc/bashrc (or similar) files.
Wouldn't it be in the man page for the terminal software?
There is no terminal software. (except sw managing "virtual consoles" <you know Alt+F1 .. F6> and I do not know where to look for info.
It is VGA display connected directly to VGA card ...
Petr "Qaxi" Klíma schrieb:
Ken McLennan napsal(a):
G'day there One & All,
No, no I mean text console ...
look at .bash* files in your home or the /etc/bashrc (or similar) files.
Wouldn't it be in the man page for the terminal software?There is no terminal software. (except sw managing "virtual consoles" <you know Alt+F1 .. F6> and I do not know where to look for info.
It is VGA display connected directly to VGA card ...
in /etc/DIR_COLORS change line "color tty" to "color none"
regards Thomas
Thomas Prangenberg schrieb:
Petr "Qaxi" Klíma schrieb:
Ken McLennan napsal(a):
G'day there One & All,
No, no I mean text console ...
look at .bash* files in your home or the /etc/bashrc (or similar) files.
Wouldn't it be in the man page for the terminal software?There is no terminal software. (except sw managing "virtual consoles" <you know Alt+F1 .. F6> and I do not know where to look for info.
It is VGA display connected directly to VGA card ...
in /etc/DIR_COLORS change line "color tty" to "color none"
regards Thomas _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
color is supposed to be UPPERCASE ... sorry --> COLOR none
On Fri, 25 Aug 2006, Thomas Prangenberg wrote:
Petr "Qaxi" Klíma schrieb:
Ken McLennan napsal(a):
G'day there One & All,
No, no I mean text console ...
look at .bash* files in your home or the /etc/bashrc (or similar) files.
Wouldn't it be in the man page for the terminal software?There is no terminal software. (except sw managing "virtual consoles" <you know Alt+F1 .. F6> and I do not know where to look for info.
It is VGA display connected directly to VGA card ...
in /etc/DIR_COLORS change line "color tty" to "color none"
The notion of color is part of the terminal capabilities. And the answer should be, change the default TERM environment variable to linux-m instead of linux.
Still I looked for the proper place to set the TERM environment and I could not find where one should put it. Either mingetty should be told (which apparently is not possible) or one can do it conditionally based on tty being used.
Both will not change the colors seen during the boot process. Maybe this is a good question for Red Hat's knowledgebase or bugzilla ?
It probably is a kernel boot parameter.
Kind regards, -- dag wieers, dag@wieers.com, http://dag.wieers.com/ -- [all I want is a warm bed and a kind word and unlimited power]
in /etc/DIR_COLORS change line "color tty" to "color none"
The notion of color is part of the terminal capabilities. And the answer should be, change the default TERM environment variable to linux-m instead of linux.
Ye, ye ... but where to set that console is linux-m for default ---
Still I looked for the proper place to set the TERM environment and I could not find where one should put it. Either mingetty should be told (which apparently is not possible) or one can do it conditionally based on tty being used.
Both will not change the colors seen during the boot process. Maybe this is a good question for Red Hat's knowledgebase or bugzilla ?
It probably is a kernel boot parameter.
With color during bootime, respectively INIT time I can help you ...
from /etc/sysconfig/init
# color => new RH6.0 bootup # verbose => old-style bootup # anything else => new style bootup without ANSI colors or positioning #BOOTUP=color BOOTUP=verbose # Turn on graphical boot #GRAPHICAL=yes GRAPHICAL=no
On Fri, 25 Aug 2006, "Petr "Qaxi" Klíma" wrote:
in /etc/DIR_COLORS change line "color tty" to "color none"
The notion of color is part of the terminal capabilities. And the answer should be, change the default TERM environment variable to linux-m instead of linux.
Ye, ye ... but where to set that console is linux-m for default ---
That's the question :) I have no answer.
Still I looked for the proper place to set the TERM environment and I could not find where one should put it. Either mingetty should be told (which apparently is not possible) or one can do it conditionally based on tty being used.
Both will not change the colors seen during the boot process. Maybe this is a good question for Red Hat's knowledgebase or bugzilla ?
It probably is a kernel boot parameter.
With color during bootime, respectively INIT time I can help you ...
from /etc/sysconfig/init
But that's not the correct fix. I found this that explains it a little bit:
http://www.tldp.org/HOWTO/Text-Terminal-HOWTO-9.html#console_
But no answers in there.
BTW Even on monochrome screens you can see 'colors'. (bold, underline, different shades of gray) What happens on your console when colors are shown ?
Kind regards, -- dag wieers, dag@wieers.com, http://dag.wieers.com/ -- [all I want is a warm bed and a kind word and unlimited power]
On Fri, 2006-08-25 at 16:22 +0200, Dag Wieers wrote:
On Fri, 25 Aug 2006, "Petr "Qaxi" Klíma" wrote:
in /etc/DIR_COLORS change line "color tty" to "color none"
The notion of color is part of the terminal capabilities. And the answer should be, change the default TERM environment variable to linux-m instead of linux.
Ye, ye ... but where to set that console is linux-m for default ---
That's the question :) I have no answer.
man init :-))
I'm not really being snippy here, I've had to look for this before and took the same tortuous route that has been started here! They do *not* make it easy. But it's always a good reminder to say "max xxx" or "google xxx". It lets us appear guru-like without exposing very much of our ignorance! ;=))
<snip>
And I still don't, but maybe a clue? Kernel parameter *if* allowed. I'm looking for the list of those on my machine now. Haven't found them yet, but ...
Maybe what's shown here?
http://www.faqs.org/docs/Linux-HOWTO/BootPrompt-HOWTO.html#ss2.6
2.6 Passing Arguments to the `init' program. Any remaining arguments that were not picked up by the kernel and were not interpreted as environment variables are then passed onto process one, which is usually the init program.
...
3.4 Other Misc. Kernel Boot Arguments These various boot arguments let the user tune certain internal kernel parameters.<snip other interesting stuff>
The `console=' Argument Usually the console is the 1st virtual terminal, and so boot messages appear on your VGA screen. Sometimes it is nice to be able to use another device like a serial port (or even a printer!) to be the console when no video device is present. It is also useful to capture boot time messages if a problem stops progress before they can be logged to disk. An example would be to use console=ttyS1,9600 for selecting the 2nd serial port at 9600 baud to be the console. More information can be found in linux/Documentation/serial-console.txt
However, this HOWTO is not updated recently, soooooo .... who really knows.
<snip sig stuff>
HTH
On Fri, 2006-08-25 at 11:44 -0400, William L. Maltby wrote:
On Fri, 2006-08-25 at 16:22 +0200, Dag Wieers wrote:
On Fri, 25 Aug 2006, "Petr "Qaxi" Klíma" wrote:
<snip>
man init :-))
I'm not really being snippy here, I've had to look for this before and took the same tortuous route that has been started here! They do *not* make it easy. But it's always a good reminder to say "max xxx" or "google xxx". It lets us appear guru-like without exposing very much of our ignorance! ;=))
<snip>
And I still don't, but maybe a clue? Kernel parameter *if* allowed. I'm looking for the list of those on my machine now. Haven't found them yet, but ...
Was having so much fun, forgot to make my suggestion, based upon the man page. Maybe TERM=linux-m at end of grub line vmlinuz... ?
<snip>
On 25/08/06, William L. Maltby BillsCentOS@triad.rr.com wrote:
And I still don't, but maybe a clue? Kernel parameter *if* allowed. I'm looking for the list of those on my machine now. Haven't found them yet, but ...
Was having so much fun, forgot to make my suggestion, based upon the man page. Maybe TERM=linux-m at end of grub line vmlinuz... ?
There's further documentation in /usr/share/doc/initscripts-7.93.24.EL/sysconfig.txt about the options in /etc/sysconfig/init. The grub man page's a bit sparse but the info page is more forthcoming. Under the "* Serial terminal::" section...
grub> serial --unit=0 --speed=9600 grub> terminal serial
The command `terminal' (*note terminal::) chooses which type of terminal you want to use. In the case above, the terminal will be a serial terminal, but you can also pass `console' to the command, as `terminal serial console'. In this case, a terminal in which you press any key will be selected as a GRUB terminal.
However, note that GRUB assumes that your terminal emulator is compatible with VT100 by default. This is true for most terminal emulators nowadays, but you should pass the option `--dumb' to the command if your terminal emulator is not VT100-compatible or implements few VT100 escape sequences. If you specify this option then GRUB provides you with an alternative menu interface, because the normal menu requires several fancy features of your terminal.
There could be more in there but my "info" navigation's useless :)
Will.
On Fri, 2006-08-25 at 17:15 +0100, Will McDonald wrote:
On 25/08/06, William L. Maltby BillsCentOS@triad.rr.com wrote:
And I still don't, but maybe a clue? Kernel parameter *if* allowed. I'm looking for the list of those on my machine now. Haven't found them yet, but ...
Was having so much fun, forgot to make my suggestion, based upon the man page. Maybe TERM=linux-m at end of grub line vmlinuz... ?
Tried this, NG. But with what Will discovered below, maybe the OP is approaching nirvana?
I think I need to read up on grub. I also tried the "append=" stuff, but no help (I didn't read up on it, I wonder if I used the rght syntax? Maybe that's only a LILO construct?).
There's further documentation in /usr/share/doc/initscripts-7.93.24.EL/sysconfig.txt about the options in /etc/sysconfig/init. The grub man page's a bit sparse but the info page is more forthcoming. Under the "* Serial terminal::" section...
grub> serial --unit=0 --speed=9600 grub> terminal serialThe command `terminal' (*note terminal::) chooses which type of terminal you want to use. In the case above, the terminal will be a serial terminal, but you can also pass `console' to the command, as `terminal serial console'. In this case, a terminal in which you press any key will be selected as a GRUB terminal.
However, note that GRUB assumes that your terminal emulator is compatible with VT100 by default. This is true for most terminal emulators nowadays, but you should pass the option `--dumb' to the command if your terminal emulator is not VT100-compatible or implements few VT100 escape sequences. If you specify this option then GRUB provides you with an alternative menu interface, because the normal menu requires several fancy features of your terminal.
There could be more in there but my "info" navigation's useless :)
IIUC, all this, including the "man init" statement about receiving CONSOLE from kernel, relates only to devices, but doesn't help on the "terminal type" (TERM=).
I'll take one last stab by "info grub", viewing the /usr/share/doc/initscripts-7.93.24.EL/sysconfig.txt Will discovered and then move on to things I need to do.
Will
<snip sig stuff>
On Fri, 2006-08-25 at 12:33 -0400, William L. Maltby wrote:
On Fri, 2006-08-25 at 17:15 +0100, Will McDonald wrote:
On 25/08/06, William L. Maltby BillsCentOS@triad.rr.com wrote:
And I still don't, but maybe a clue? Kernel parameter *if* allowed. I'm looking for the list of those on my machine now. Haven't found them yet, but ...
Was having so much fun, forgot to make my suggestion, based upon the man page. Maybe TERM=linux-m at end of grub line vmlinuz... ?
Tried this, NG. But with what Will discovered below, maybe the OP is approaching nirvana?
I think I need to read up on grub. I also tried the "append=" stuff, but no help (I didn't read up on it, I wonder if I used the right syntax? Maybe that's only a LILO construct?).
Nope. My original "TERM=" and "append=..." looks OK.
There's further documentation in /usr/share/doc/initscripts-7.93.24.EL/sysconfig.txt about the options
<snip>
There could be more in there but my "info" navigation's useless :)
Well, I navigated. But it didn't help. Good navigation doesn't help the case of no valid destination! ;-)
IIUC, all this, including the "man init" statement about receiving CONSOLE from kernel, relates only to devices, but doesn't help on the "terminal type" (TERM=).
This reinforced by both the grub stuff and the sysconfig text that Will referenced.
I'll take one last stab by "info grub", viewing the /usr/share/doc/initscripts-7.93.24.EL/sysconfig.txt Will discovered and then move on to things I need to do.
Kernel param list didn't help. The closest I can see is what Dag originally found, the BOOTUP in sysconfig for init. And that comes too late to address output before init is invoked. Kernel seems to have a *few* "pre-defined" types of displays it supports. VGA, some serial, a couple specials (for HP) and MDA (IIRC, a really old type?).
With the assumption that everything is VT100 (or ANSI) compatible and no way I discovered to pass a kernel param that changes the behavior (or TERM= equivalent value), I think the BOOTUP is as close as you get *unless* you make your own kernel. In there you should be able to suppress the "printk" escape sequences that produce "bold", etc.
The is a parameter, "earlyprintk=" that *might* offer a slim hope. But you'll have to chase that, I'm on to other things I need to do.
Will
<snip sig stuff>
William L. Maltby schrieb:
On Fri, 2006-08-25 at 12:33 -0400, William L. Maltby wrote:
On Fri, 2006-08-25 at 17:15 +0100, Will McDonald wrote:
On 25/08/06, William L. Maltby BillsCentOS@triad.rr.com wrote:
And I still don't, but maybe a clue? Kernel parameter *if* allowed. I'm looking for the list of those on my machine now. Haven't found them yet, but ...
Was having so much fun, forgot to make my suggestion, based upon the man page. Maybe TERM=linux-m at end of grub line vmlinuz... ?
Tried this, NG. But with what Will discovered below, maybe the OP is approaching nirvana?
I think I need to read up on grub. I also tried the "append=" stuff, but no help (I didn't read up on it, I wonder if I used the right syntax? Maybe that's only a LILO construct?).
Nope. My original "TERM=" and "append=..." looks OK.
There's further documentation in /usr/share/doc/initscripts-7.93.24.EL/sysconfig.txt about the options
<snip>
There could be more in there but my "info" navigation's useless :)
Well, I navigated. But it didn't help. Good navigation doesn't help the case of no valid destination! ;-)
IIUC, all this, including the "man init" statement about receiving CONSOLE from kernel, relates only to devices, but doesn't help on the "terminal type" (TERM=).
This reinforced by both the grub stuff and the sysconfig text that Will referenced.
I'll take one last stab by "info grub", viewing the /usr/share/doc/initscripts-7.93.24.EL/sysconfig.txt Will discovered and then move on to things I need to do.
Kernel param list didn't help. The closest I can see is what Dag originally found, the BOOTUP in sysconfig for init. And that comes too late to address output before init is invoked. Kernel seems to have a *few* "pre-defined" types of displays it supports. VGA, some serial, a couple specials (for HP) and MDA (IIRC, a really old type?).
With the assumption that everything is VT100 (or ANSI) compatible and no way I discovered to pass a kernel param that changes the behavior (or TERM= equivalent value), I think the BOOTUP is as close as you get *unless* you make your own kernel. In there you should be able to suppress the "printk" escape sequences that produce "bold", etc.
The is a parameter, "earlyprintk=" that *might* offer a slim hope. But you'll have to chase that, I'm on to other things I need to do.
Will
<snip sig stuff>
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Sorry if I ask something stupid, if Petr's modification of the /etc/sysconfig/init file provides for a black and white bootup (it does) and an entry in /etc/profile or the respective .bashrc files provides a black and white login (TERM=linux-m/export TERM) what is the benefit of defining the black and white term on kernel level before these steps. Best regards, Thomas
On Fri, 2006-08-25 at 21:43 +0200, Thomas Prangenberg wrote:
William L. Maltby schrieb:
On Fri, 2006-08-25 at 12:33 -0400, William L. Maltby wrote:
On Fri, 2006-08-25 at 17:15 +0100, Will McDonald wrote:
On 25/08/06, William L. Maltby BillsCentOS@triad.rr.com wrote:
<snip>
Sorry if I ask something stupid, if Petr's modification of the /etc/sysconfig/init file provides for a black and white bootup (it does) and an entry in /etc/profile or the respective .bashrc files provides a black and white login (TERM=linux-m/export TERM) what is the benefit of defining the black and white term on kernel level before these steps. Best regards, Thomas
IIUC, the BOOTUP change occurs only when init starts up, not during kernel (dmesg) output. Of course, the clarity they provide in getting us to spend so much effort on finding a seemingly simple answer may lead us to wrong conclusions.
<snip sig stuff>
William L. Maltby spake the following on 8/25/2006 1:19 PM:
On Fri, 2006-08-25 at 21:43 +0200, Thomas Prangenberg wrote:
William L. Maltby schrieb:
On Fri, 2006-08-25 at 12:33 -0400, William L. Maltby wrote:
On Fri, 2006-08-25 at 17:15 +0100, Will McDonald wrote:
On 25/08/06, William L. Maltby BillsCentOS@triad.rr.com wrote:
> <snip>
Sorry if I ask something stupid, if Petr's modification of the /etc/sysconfig/init file provides for a black and white bootup (it does) and an entry in /etc/profile or the respective .bashrc files provides a black and white login (TERM=linux-m/export TERM) what is the benefit of defining the black and white term on kernel level before these steps. Best regards, Thomas
IIUC, the BOOTUP change occurs only when init starts up, not during kernel (dmesg) output. Of course, the clarity they provide in getting us to spend so much effort on finding a seemingly simple answer may lead us to wrong conclusions.
You will soon get to a point where the billable hours to fix it will outweigh the cost of a color monitor. ;-)
On Fri, 2006-08-25 at 14:27 -0700, Scott Silva wrote:
William L. Maltby spake the following on 8/25/2006 1:19 PM:
On Fri, 2006-08-25 at 21:43 +0200, Thomas Prangenberg wrote:
William L. Maltby schrieb:
On Fri, 2006-08-25 at 12:33 -0400, William L. Maltby wrote:
On Fri, 2006-08-25 at 17:15 +0100, Will McDonald wrote:
On 25/08/06, William L. Maltby BillsCentOS@triad.rr.com wrote: >><snip>
Sorry if I ask something stupid, if Petr's modification of the /etc/sysconfig/init file provides for a black and white bootup (it does) and an entry in /etc/profile or the respective .bashrc files provides a black and white login (TERM=linux-m/export TERM) what is the benefit of defining the black and white term on kernel level before these steps. Best regards, Thomas
IIUC, the BOOTUP change occurs only when init starts up, not during kernel (dmesg) output. Of course, the clarity they provide in getting us to spend so much effort on finding a seemingly simple answer may lead us to wrong conclusions.
You will soon get to a point where the billable hours to fix it will outweigh the cost of a color monitor. ;-)
Yep! And so we see the underlying cause of the demise of the concept of "craftsmanship".
On 25/08/06, William L. Maltby CentOS4Bill@triad.rr.com wrote:
On Fri, 2006-08-25 at 14:27 -0700, Scott Silva wrote:
You will soon get to a point where the billable hours to fix it will outweigh the cost of a color monitor. ;-)
Yep! And so we see the underlying cause of the demise of the concept of "craftsmanship".
Meeeeow! :)
I just figured the guy had some sort of terminal that b0rked whenever something with colour codes were attempted to be displayed.
Will.
-
"Petr \"Qaxi\" Klíma" -
Dag Wieers -
Ken McLennan -
Scott Silva -
Sudev Barar -
Thomas Prangenberg -
Will McDonald -
William L. Maltby -
William L. Maltby