Anyway on looking at it now, I can't see what actually displays that logo. It seems that /etc/rc.S dot-sources settings.s and the code in settings.s itself dd's it to /dev/null ... so how does it end up on the console? Can you explain (again?) how this works and whether there's something simple I can additionally edit in settings.s or rc.custom.gz on the diskette that preserves the full boot logo. (without having to re-buildit)
John
----Original Message Follows---- From: Tom Oehser <[EMAIL PROTECTED]> To: John Lumby <[EMAIL PROTECTED]> CC: [email protected] Subject: Re: [tomsrtbt] how to pass parms to rc.custom? Date: Tue, 21 Dec 2004 13:12:25 -0500 (EST)
The intention was that most users would be customizing settings.s and rc.custom.gz without rebuilding. If you are doing a rebuild anyway, I think you can modify 1/settings.s, and settings there will be kept.
-Tom
On Tue, 21 Dec 2004, John Lumby wrote:
> Date: Tue, 21 Dec 2004 11:56:35 -0500
> From: John Lumby <[EMAIL PROTECTED]>
> To: [email protected]
> Subject: [tomsrtbt] how to pass parms to rc.custom?
>
> In the supplied rc.custom.gz, there is this (at line 4):
>
> if [ "$IPADDR" != "" ]
> then ... do stuff
> fi
>
> How would I set IPADDR to something such that the stuff is done? Is it
> simply a matter of setting it in 1/settings.s? That's what I think I
> deduce from looking at
> 2/etc/rc.S
> I have been a bit unwilling to put "permanent" settings in 1/settings.s
> since I notice that buildit completely rewrites it (1/settings.s) every time
> I buildit (why does it do that? doesn't trust me? I guess that's
> wise ...) I suppose I can edit the settings.s on the diskette, which is
> the way I am supposed to do it according to the FAQ. But I wonder if
> there's some place on the build directory where I can safely store settings
> like this and have them included in every diskette I build without having to
> think about it.
>
> John
>
>
