A suggestion for building the kernel batchly.

Hello.

I just finished my first jhalfs!

All packages were installed without any single keypress for
my part. But 
when the build entered the kernel stage (135-kernel),
"make" began to 
prompt me for kernel options. That's because I use the
config file from 
my host system, which is LFS-6.1.1 with linux-2.6.11.12, and
there are 
new options in 2.6.12.5 that need to be set manually.

Well, I just suggest: shouldn't it be a good idea to accept
the defaults 
for those new options, and let the build be executed
batchly? I have 
achieved that by issuing:

    yes "" | make

instead of simply:

    make

Does it make sense?


*david
-- 
http://linuxfromscratch.org/mailman/listinfo/alfs-discu
ss
FAQ: http://www.linux
fromscratch.org/faq/
Unsubscribe: See the above information page

El Domingo, 26 de Marzo de 2006 14:30, David Rosal escribió:
> Hello.
>
> I just finished my first jhalfs!

Good 

Mine is running yet GCC test suites :-/

> All packages were installed without any single keypress
for my part. But
> when the build entered the kernel stage (135-kernel),
"make" began to
> prompt me for kernel options. That's because I use the
config file from
> my host system, which is LFS-6.1.1 with
linux-2.6.11.12, and there are
> new options in 2.6.12.5 that need to be set manually.

Well, we expect the users submmint a .config file suitable
for the kernel 
version that will be compiled and adapted to their hardware.

After all, this is "Linux From Scratch" and the
user should be aware about how 
their kernel is actually configured.


-- 
Manuel Canales Esparcia
Usuario de LFS nº2886:       http://www.linuxfroms
cratch.org
LFS en castellano: http://www.escomp
oslinux.org/lfs-es http://www.lfs-es.com
TLDP-ES:                           http://es.tldp.org
-- 
http://linuxfromscratch.org/mailman/listinfo/alfs-discu
ss
FAQ: http://www.linux
fromscratch.org/faq/
Unsubscribe: See the above information page

On 3/26/06, M.Canales.es <manuellinuxfromscratch.org>
wrote:
>
> Well, we expect the users submmint a .config file
suitable for the kernel
> version that will be compiled and adapted to their
hardware.

Manuel, there's a very easy workaround for this.

if [ "$SUPPLIED_A_CONFIG" = Y ]; then
    yes "" | make oldconfig
else
    whatever_jhalfs_uses_for_the_config
fi

`make oldconfig' will adjust it as David mentioned. 
Config's created
from that version will come out the same.  There's a lot of
output,
though, so you may want to redirect the output.

--
Dan
-- 
http://linuxfromscratch.org/mailman/listinfo/alfs-discu
ss
FAQ: http://www.linux
fromscratch.org/faq/
Unsubscribe: See the above information page

El Domingo, 26 de Marzo de 2006 18:25, Dan Nicholson
escribió:

> `make oldconfig' will adjust it as David mentioned. 
Config's created
> from that version will come out the same.  There's a
lot of output,
> though, so you may want to redirect the output.

Current status:

   - To keep the code clar and simple, the kernel build is
handled in a
    similar way in both LFS, HLFS anc CLFS modules.

   - If no no .config file is suppiield, the kernel build is
skipped.

  - HLFS requires a .config file with the proper GRSECURITY
options
    activated.

  - CLFS requires two .config files: one for the boot phase
(minimal and no
   modules) and one for the final system. Both configured
for the $TARGET
   system.

Thus, a "yes "" | make oldconfid"
could be allowed only in LFS, or HLFS if the 
host system is a previous HLFS system, or in same cases of
the chrrot method 
in CLFS.

There is many "if" and unknow variables in that
equation.


-- 
Manuel Canales Esparcia
Usuario de LFS nº2886:       http://www.linuxfroms
cratch.org
LFS en castellano: http://www.escomp
oslinux.org/lfs-es http://www.lfs-es.com
TLDP-ES:                           http://es.tldp.org
-- 
http://linuxfromscratch.org/mailman/listinfo/alfs-discu
ss
FAQ: http://www.linux
fromscratch.org/faq/
Unsubscribe: See the above information page