[gentoo-catalyst] custom motd gets blanked

[gentoo-catalyst] custom motd gets blanked

[Tod Herman]

When building livecd with custom motd, the custom motd gets moved into the build environment correctly, but then get's blanked when the livecdfs-update.sh tries to cat missing generic-motd.txt and minimal-motd.txt files into /etc/motd.  Bug entered on bugzilla: http://bugs.gentoo.org/show_bug.cgi?id=127186

Can cheat and change the > to >> in the line from livecdfs-update.sh that is the offender: 

gentoo-release-minimal )
                cat /etc/generic.motd.txt /etc/minimal.motd.txt > /etc/motd
                sed -i 's:^##GREETING:Welcome to the Gentoo Linux Minimal Installation CD!:' /etc/motd

Probably should check if custom motd being used and if so skip the Tweaking the MOTD section.



-- 
gentoo-catalyst@gentoo.org mailing list

Re: [gentoo-catalyst] custom motd gets blanked

[Andrew Gaffney]

Tod Herman wrote:
> When building livecd with custom motd, the custom motd gets moved into the build environment correctly, but then get's blanked when the livecdfs-update.sh tries to cat missing generic-motd.txt and minimal-motd.txt files into /etc/motd.  Bug entered on bugzilla: http://bugs.gentoo.org/show_bug.cgi?id=127186
> 
> Can cheat and change the > to >> in the line from livecdfs-update.sh that is the offender: 
> 
> gentoo-release-minimal )
>                 cat /etc/generic.motd.txt /etc/minimal.motd.txt > /etc/motd
>                 sed -i 's:^##GREETING:Welcome to the Gentoo Linux Minimal Installation CD!:' /etc/motd
> 
> Probably should check if custom motd being used and if so skip the Tweaking the MOTD section.

If you're not building a Gentoo release, you probably shouldn't be using the 
gentoo-release-* types. They do all sorts of stuff that you typically wouldn't 
want, except on a Gentoo release.

-- 
Andrew Gaffney                            http://dev.gentoo.org/~agaffney/
Gentoo Linux Developer                                   Installer Project

-- 
gentoo-catalyst@gentoo.org mailing list

Re: [gentoo-catalyst] custom motd gets blanked

[Tod Herman]

and yet I suspect the blanked file wasn't intended.  also suspect that much of the "all sorts of stuff" the rest of the scripts do is wanted.

----- Original Message ----
From: Andrew Gaffney <agaffney@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Sent: Wednesday, March 22, 2006 11:30:38 AM
Subject: Re: [gentoo-catalyst] custom motd gets blanked

Tod Herman wrote:
> When building livecd with custom motd, the custom motd gets moved into the build environment correctly, but then get's blanked when the livecdfs-update.sh tries to cat missing generic-motd.txt and minimal-motd.txt files into /etc/motd.  Bug entered on bugzilla: http://bugs.gentoo.org/show_bug.cgi?id=127186
> 
> Can cheat and change the > to >> in the line from livecdfs-update.sh that is the offender: 
> 
> gentoo-release-minimal )
>                 cat /etc/generic.motd.txt /etc/minimal.motd.txt > /etc/motd
>                 sed -i 's:^##GREETING:Welcome to the Gentoo Linux Minimal Installation CD!:' /etc/motd
> 
> Probably should check if custom motd being used and if so skip the Tweaking the MOTD section.

If you're not building a Gentoo release, you probably shouldn't be using the 
gentoo-release-* types. They do all sorts of stuff that you typically wouldn't 
want, except on a Gentoo release.

-- 
Andrew Gaffney                            http://dev.gentoo.org/~agaffney/
Gentoo Linux Developer                                   Installer Project

-- 
gentoo-catalyst@gentoo.org mailing list




-- 
gentoo-catalyst@gentoo.org mailing list

Re: [gentoo-catalyst] custom motd gets blanked

[Chris Gianelloni]

[-- Attachment #1: Type: text/plain, Size: 1396 bytes --]

On Wed, 2006-03-22 at 10:25 -0600, Tod Herman wrote:
> When building livecd with custom motd, the custom motd gets moved into the build environment correctly, but then get's blanked when the livecdfs-update.sh tries to cat missing generic-motd.txt and minimal-motd.txt files into /etc/motd.  Bug entered on bugzilla: http://bugs.gentoo.org/show_bug.cgi?id=127186
> 
> Can cheat and change the > to >> in the line from livecdfs-update.sh that is the offender: 
> 
> gentoo-release-minimal )
>                 cat /etc/generic.motd.txt /etc/minimal.motd.txt > /etc/motd
>                 sed -i 's:^##GREETING:Welcome to the Gentoo Linux Minimal Installation CD!:' /etc/motd
> 
> Probably should check if custom motd being used and if so skip the Tweaking the MOTD section.

No.  You should not be using livecd/type: gentoo-release-minimal when
you aren't building a Gentoo release.  There is generic-livecd for
*anything* that is not official Gentoo media.  The basic premise is that
the official media requires some things and does some things that users
will not want.  If you're using gentoo-release-* and something is being
overwritten, you're pretty much going to get a simple response from me.
Don't use gentoo-release-* as it is doing what is expected.

-- 
Chris Gianelloni
Release Engineering - Strategic Lead
x86 Architecture Team
Games - Developer
Gentoo Linux

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-catalyst] custom motd gets blanked

[Chris Gianelloni]

[-- Attachment #1: Type: text/plain, Size: 2105 bytes --]

On Wed, 2006-03-22 at 08:48 -0800, Tod Herman wrote:
> and yet I suspect the blanked file wasn't intended.  also suspect that much of the "all sorts of stuff" the rest of the scripts do is wanted.

Since usage of livecd/motd isn't valid for gentoo-release-* I have
instead made it pretty simple.  If you're using livecd/motd and
gentoo-release-* you will get a warning, and your custom motd will be
ignored.

I really wish people would *not* use gentoo-release-* when building
anything that tries to be different from a Gentoo release.  ;]

> ----- Original Message ----
> From: Andrew Gaffney <agaffney@gentoo.org>
> To: gentoo-catalyst@lists.gentoo.org
> Sent: Wednesday, March 22, 2006 11:30:38 AM
> Subject: Re: [gentoo-catalyst] custom motd gets blanked
> 
> Tod Herman wrote:
> > When building livecd with custom motd, the custom motd gets moved into the build environment correctly, but then get's blanked when the livecdfs-update.sh tries to cat missing generic-motd.txt and minimal-motd.txt files into /etc/motd.  Bug entered on bugzilla: http://bugs.gentoo.org/show_bug.cgi?id=127186
> > 
> > Can cheat and change the > to >> in the line from livecdfs-update.sh that is the offender: 
> > 
> > gentoo-release-minimal )
> >                 cat /etc/generic.motd.txt /etc/minimal.motd.txt > /etc/motd
> >                 sed -i 's:^##GREETING:Welcome to the Gentoo Linux Minimal Installation CD!:' /etc/motd
> > 
> > Probably should check if custom motd being used and if so skip the Tweaking the MOTD section.
> 
> If you're not building a Gentoo release, you probably shouldn't be using the 
> gentoo-release-* types. They do all sorts of stuff that you typically wouldn't 
> want, except on a Gentoo release.
> 
> -- 
> Andrew Gaffney                            http://dev.gentoo.org/~agaffney/
> Gentoo Linux Developer                                   Installer Project
> 
> -- 
> gentoo-catalyst@gentoo.org mailing list
> 
> 
> 
> 
-- 
Chris Gianelloni
Release Engineering - Strategic Lead
x86 Architecture Team
Games - Developer
Gentoo Linux

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-catalyst] custom motd gets blanked

[Tod Herman]

Everyone has to start somewhere.  And without warnings up front in any kind of documentation to the contrary, people are going to try to take the easiest path to get a desired result.  Learning to use the tool correctly, and in a way "sanctioned" by those intimately involved in its creation, isn't exactly easy.  Of course, now, having been spanked for my attempts at catalyst glory, i will go back and try and do it all the "right" way.   Thanks just the same Chris.

----- Original Message ----
From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Sent: Wednesday, March 22, 2006 1:58:13 PM
Subject: Re: [gentoo-catalyst] custom motd gets blanked

On Wed, 2006-03-22 at 08:48 -0800, Tod Herman wrote:
> and yet I suspect the blanked file wasn't intended.  also suspect that much of the "all sorts of stuff" the rest of the scripts do is wanted.

Since usage of livecd/motd isn't valid for gentoo-release-* I have
instead made it pretty simple.  If you're using livecd/motd and
gentoo-release-* you will get a warning, and your custom motd will be
ignored.

I really wish people would *not* use gentoo-release-* when building
anything that tries to be different from a Gentoo release.  ;]

> ----- Original Message ----
> From: Andrew Gaffney <agaffney@gentoo.org>
> To: gentoo-catalyst@lists.gentoo.org
> Sent: Wednesday, March 22, 2006 11:30:38 AM
> Subject: Re: [gentoo-catalyst] custom motd gets blanked
> 
> Tod Herman wrote:
> > When building livecd with custom motd, the custom motd gets moved into the build environment correctly, but then get's blanked when the livecdfs-update.sh tries to cat missing generic-motd.txt and minimal-motd.txt files into /etc/motd.  Bug entered on bugzilla: http://bugs.gentoo.org/show_bug.cgi?id=127186
> > 
> > Can cheat and change the > to >> in the line from livecdfs-update.sh that is the offender: 
> > 
> > gentoo-release-minimal )
> >                 cat /etc/generic.motd.txt /etc/minimal.motd.txt > /etc/motd
> >                 sed -i 's:^##GREETING:Welcome to the Gentoo Linux Minimal Installation CD!:' /etc/motd
> > 
> > Probably should check if custom motd being used and if so skip the Tweaking the MOTD section.
> 
> If you're not building a Gentoo release, you probably shouldn't be using the 
> gentoo-release-* types. They do all sorts of stuff that you typically wouldn't 
> want, except on a Gentoo release.
> 
> -- 
> Andrew Gaffney                            http://dev.gentoo.org/~agaffney/
> Gentoo Linux Developer                                   Installer Project
> 
> -- 
> gentoo-catalyst@gentoo.org mailing list
> 
> 
> 
> 
-- 
Chris Gianelloni
Release Engineering - Strategic Lead
x86 Architecture Team
Games - Developer
Gentoo Linux



-- 
gentoo-catalyst@gentoo.org mailing list

Re: [gentoo-catalyst] custom motd gets blanked

[Chris Gianelloni]

[-- Attachment #1: Type: text/plain, Size: 2242 bytes --]

On Wed, 2006-03-22 at 12:17 -0800, Tod Herman wrote:
> Everyone has to start somewhere.  And without warnings up front in any kind of documentation to the contrary, people are going to try to take the easiest path to get a desired result.  Learning to use the tool correctly, and in a way "sanctioned" by those intimately involved in its creation, isn't exactly easy.  Of course, now, having been spanked for my attempts at catalyst glory, i will go back and try and do it all the "right" way.   Thanks just the same Chris.

*sigh*

I wasn't trying to be an ass or anything.  I was merely pointing you in
the right direction.  Besides, it is pretty clear in the example spec
files installed with catalyst.  You know, the ones that the catalyst
ebuild tells you to read.  Yeah, those...

# This option controls quite a bit of catalyst internals and sets up
several
# defaults.  Each type behaves slightly differently and is explained
below.
# gentoo-release-minimal - This creates an official minimal InstallCD.
# gentoo-release-universal - This creates an official universal
InstallCD.
# gentoo-release-livecd - This creates an official LiveCD environment.
# gentoo-gamecd - This creates an official Gentoo GameCD.
# generic-livecd - This should be used for all non-official media.
# example:
# livecd/type: gentoo-release-minimal
livecd/type:

Now, as you can probably guess, your CD would be "non-official media".

I understand that catalyst is a complex tool to learn, but trying to
make it sound like we didn't try to document this is simply unfair to
those of us that spend our time not only writing the tool, but also
taking the time to write out all of the documentation.  It really isn't
appreciated when you try to lay the onus of blame on the developers when
they've tried their best to make it clear how to proceed.

At any rate, the *real* goal here is to have taught you, and I think we
have.  I apologize if you feel that this wasn't done in the best manner,
but there's not much else that we can do other than provide
documentation explaining the options, which we have.

-- 
Chris Gianelloni
Release Engineering - Strategic Lead
x86 Architecture Team
Games - Developer
Gentoo Linux

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-catalyst] custom motd gets blanked

[Tod Herman]

Geez.  Been thru the spec files.  Really do try and solve what I can myself before bothering others.  Also read thru all the scripts when seeking a solution.  Clarity is relative.  And not everything in the example spec files is correct.  Wasn't calling you an ass.  If I wished to, I would have done so clearly.  Have a good day.  

----- Original Message ----
From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Sent: Wednesday, March 22, 2006 3:36:46 PM
Subject: Re: [gentoo-catalyst] custom motd gets blanked

On Wed, 2006-03-22 at 12:17 -0800, Tod Herman wrote:
> Everyone has to start somewhere.  And without warnings up front in any kind of documentation to the contrary, people are going to try to take the easiest path to get a desired result.  Learning to use the tool correctly, and in a way "sanctioned" by those intimately involved in its creation, isn't exactly easy.  Of course, now, having been spanked for my attempts at catalyst glory, i will go back and try and do it all the "right" way.   Thanks just the same Chris.

*sigh*

I wasn't trying to be an ass or anything.  I was merely pointing you in
the right direction.  Besides, it is pretty clear in the example spec
files installed with catalyst.  You know, the ones that the catalyst
ebuild tells you to read.  Yeah, those...

# This option controls quite a bit of catalyst internals and sets up
several
# defaults.  Each type behaves slightly differently and is explained
below.
# gentoo-release-minimal - This creates an official minimal InstallCD.
# gentoo-release-universal - This creates an official universal
InstallCD.
# gentoo-release-livecd - This creates an official LiveCD environment.
# gentoo-gamecd - This creates an official Gentoo GameCD.
# generic-livecd - This should be used for all non-official media.
# example:
# livecd/type: gentoo-release-minimal
livecd/type:

Now, as you can probably guess, your CD would be "non-official media".

I understand that catalyst is a complex tool to learn, but trying to
make it sound like we didn't try to document this is simply unfair to
those of us that spend our time not only writing the tool, but also
taking the time to write out all of the documentation.  It really isn't
appreciated when you try to lay the onus of blame on the developers when
they've tried their best to make it clear how to proceed.

At any rate, the *real* goal here is to have taught you, and I think we
have.  I apologize if you feel that this wasn't done in the best manner,
but there's not much else that we can do other than provide
documentation explaining the options, which we have.

-- 
Chris Gianelloni
Release Engineering - Strategic Lead
x86 Architecture Team
Games - Developer
Gentoo Linux



-- 
gentoo-catalyst@gentoo.org mailing list

Re: [gentoo-catalyst] custom motd gets blanked

[Chris Gianelloni]

[-- Attachment #1: Type: text/plain, Size: 607 bytes --]

On Wed, 2006-03-22 at 12:56 -0800, Tod Herman wrote:
> Geez.  Been thru the spec files.  Really do try and solve what I can myself before bothering others.  Also read thru all the scripts when seeking a solution.  Clarity is relative.  And not everything in the example spec files is correct.  Wasn't calling you an ass.  If I wished to, I would have done so clearly.  Have a good day.  

What exactly is not clear in the documentation?  If nobody tells us, we
can't make it better.

-- 
Chris Gianelloni
Release Engineering - Strategic Lead
x86 Architecture Team
Games - Developer
Gentoo Linux

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]