color_and_upgradeissues

This is part of The Pile, a partial archive of some open source mailing lists and newsgroups.



Subject: Re: console color code location?
From: "H. Peter Anvin" <hpa@transmeta.com>
Date: Mon, 01 Nov 1999 13:04:00 -0800


Al Elia wrote:

> I'm a FreeBSD guy who's new to Linux...and I need to be able to compile my
> kernel with specific colors (bright white text on a black background).
> Anywone know where/how this is done in the linux kernel source?

Put the relevant escape codes in your /etc/issue.  No need to compile it
into the kernel.  Note that some distributions (including RedHat)
overwrites /etc/issue on boot which is really rather antisocial.

===

Subject: Re: console color code location?
From: "H. Peter Anvin" <hpa@transmeta.com>
Date: Mon, 01 Nov 1999 14:54:47 -0800

Kevin Waterson wrote:
> 
> "H. Peter Anvin" wrote:
> 
> > Al Elia wrote:

> > > I'm a FreeBSD guy who's new to Linux...and I need to
> > > be able to compile my kernel with specific colors
> > > (bright white text on a black background).  Anywone
> > > know where/how this is done in the linux kernel
> > > source?


> > Put the relevant escape codes in your /etc/issue.  No
> > need to compile it into the kernel.  Note that some
> > distributions (including RedHat) overwrites /etc/issue
> > on boot which is really rather antisocial.

> Not really, as this is written from redhat-release


So what if I don't want to have anything to do with
redhat-release in my /etc/issue?  Deleting
/etc/redhat-release will cause programs that are trying to
detect a RedHat installation (to adjust their install
methods, or whathaveyou) to fail, so that isn't really an
option.

In RH6.1 it looks like you can simply overwrite
/etc/rc.d/rc.local; don't know if that's true for other
RedHats.

===

Subject: Re: console color code location?
From: Bill Nottingham <notting@redhat.com>
Date: Mon, 1 Nov 1999 17:56:30 -0500


H. Peter Anvin (hpa@transmeta.com) said: 
> In RH6.1 it looks like you can simply overwrite /etc/rc.d/rc.local;
> don't know if that's true for other RedHats.

Yup, just change where it munges the issue file in rc.local.

===

Subject: Re: console color code location?
From: "H. Peter Anvin" <hpa@transmeta.com>
Date: Mon, 01 Nov 1999 14:57:47 -0800


Bill Nottingham wrote:
> 
> H. Peter Anvin (hpa@transmeta.com) said:
> > In RH6.1 it looks like you can simply overwrite /etc/rc.d/rc.local;
> > don't know if that's true for other RedHats.
> 
> Yup, just change where it munges the issue file in rc.local.
> 

Changes which can't be trivially automated are majorly evil.  That's
what the /etc/rc.d/init.d stuff is there for; an
/etc/rc.d/init.d/makeissue would have been infinitely better.

	-hpa


===
Subject: Re: console color code location?
From: Bill Nottingham <notting@redhat.com>
Date: Mon, 1 Nov 1999 18:02:08 -0500


H. Peter Anvin (hpa@transmeta.com) said: 
> > H. Peter Anvin (hpa@transmeta.com) said:
> > > In RH6.1 it looks like you can simply overwrite /etc/rc.d/rc.local;
> > > don't know if that's true for other RedHats.
> > 
> > Yup, just change where it munges the issue file in rc.local.
> > 
> 
> Changes which can't be trivially automated are majorly evil.  That's
> what the /etc/rc.d/init.d stuff is there for; an
> /etc/rc.d/init.d/makeissue would have been infinitely better.

It shouldn't need to be 'automated' as such; replacing the rc.local
file once should be enough - it won't get changed on upgrades.
===

Subject: Re: console color code location? 
From: Tony Nugent <tony@growzone.com.au>
Date: Tue, 02 Nov 1999 09:07:36 +1000


On Tue Nov 02 1999 at 08:55, Kevin Waterson wrote:

> "H. Peter Anvin" wrote:
> 
> > Al Elia wrote:
> > >
> > > Hello all,
> > >
> > > I'm a FreeBSD guy who's new to Linux...and I need to be able to compile my
> > > kernel with specific colors (bright white text on a black background).
> > > Anywone know where/how this is done in the linux kernel source?
> > >
> > > Thanks!
> > >
> >
> > Put the relevant escape codes in your /etc/issue.  No need to compile it
> > into the kernel.  Note that some distributions (including RedHat)
> > overwrites /etc/issue on boot which is really rather antisocial.
> 
> Not really, as this is written from redhat-release

Well, put the relevant console escape codes into /etc/rc.d/rc.local
then!  :)

===

Subject: Re: console color code location?
From: "H. Peter Anvin" <hpa@transmeta.com>
Date: Mon, 01 Nov 1999 15:06:16 -0800


Bill Nottingham wrote:
> 
> H. Peter Anvin (hpa@transmeta.com) said:
> > > H. Peter Anvin (hpa@transmeta.com) said:
> > > > In RH6.1 it looks like you can simply overwrite /etc/rc.d/rc.local;
> > > > don't know if that's true for other RedHats.
> > >
> > > Yup, just change where it munges the issue file in rc.local.
> > >
> >
> > Changes which can't be trivially automated are majorly evil.  That's
> > what the /etc/rc.d/init.d stuff is there for; an
> > /etc/rc.d/init.d/makeissue would have been infinitely better.
> 
> It shouldn't need to be 'automated' as such; replacing the rc.local
> file once should be enough - it won't get changed on upgrades.
> 

Either way, rc.local should be for *local* stuff.  Just like /usr/local,
it should be *empty*.

	-hap

===

Subject: Re: console color code location?
From: Matthew Campbell <mattcamp@feist.com>
Date: Mon, 1 Nov 1999 17:40:33 -0600 (CST)


H. Peter Anvin writes:
 > Either way, rc.local should be for *local* stuff.  Just like /usr/local,
 > it should be *empty*.

I suppose the code that makes an issue file with the Red hat release
and kernel version could go in a script under /etc/rc.d/init.d,
perhaps called makeissue, and that script could go in the initscripts
or redhat-release package.  Then if someone wants to customize
/etc/issue, they can either create their own issue file (by hand) and
turn off makeissue with something like ntsysv, or they could add code
in /etc/rc.d/rc.local that changes, adds to, or overwrites the issue
file.

Matt

===

Subject: Re: console color code location?
From: R P Herrold <herrold@owlriver.com>
Date: Mon, 1 Nov 1999 21:17:43 -0500 (EST)


One would _hope_ that an update/upgrade would be kind enough
to not mungle with rc.local -- but that turned out not to be
the case, at least with RH versions though 6.0 ...

Those antecedent versions to RH 6.1 recognized that rc.local
was a 'config' file:

$ rpm -V initscripts 
S.5....T c /etc/rc.d/rc.local

... notice the "c".  But they would save custom configuration,
and displace the changed file with the 'latest.'

With 6.1, and the new '.rpmnew' construct being adopted, RH no
longer displaces changes to _this_ file.  This is progress --
but I like the idea of isolating _all_ non-truly local
content, _including_ the generation of the 'issue' file OUT of
rc.local ... perhaps not an infinite improvement, but an
improvement, nonetheless.

-- Russ

On Mon, 1 Nov 1999, Bill Nottingham wrote:

> H. Peter Anvin (hpa@transmeta.com) said: 

> > Changes which can't be trivially automated are majorly evil.  That's
> > what the /etc/rc.d/init.d stuff is there for; an
> > /etc/rc.d/init.d/makeissue would have been infinitely better.
> 
> It shouldn't need to be 'automated' as such; replacing the rc.local
> file once should be enough - it won't get changed on upgrades.

===

Subject: Re: console color code location? 
From: John Summerfield <summer@OS2.ami.com.au>
Date: Wed, 03 Nov 1999 06:53:07 +0800


> H. Peter Anvin writes:
>  > Either way, rc.local should be for *local* stuff.  Just like /usr/local,
>  > it should be *empty*.
> 
> I suppose the code that makes an issue file with the Red hat release
> and kernel version could go in a script under /etc/rc.d/init.d,
> perhaps called makeissue, and that script could go in the initscripts
> or redhat-release package.  Then if someone wants to customize
> /etc/issue, they can either create their own issue file (by hand) and
> turn off makeissue with something like ntsysv, or they could add code
> in /etc/rc.d/rc.local that changes, adds to, or overwrites the issue
> file.
>
Regard the default as a sample. Bill's already said it won't be replaced 
in an upgrade, so fix it one and let's forget it.


===


the rest of The Pile (a partial mailing list archive)

doom@kzsu.stanford.edu