My suggestion is that you create multiple .config files, such as: .config.orig .config.myworkstation.2.2.13 .config.mailserver.2.2.13 Then create a couple of scripts which create a symlink, and then perform some operation, for example, the following (untested) script has the name of the config for its first argument, and the arguments to make as the remaining. #!/bin/sh CONFIGV=$1 if [ ! -f $CONFIGV ] then echo not $CONFIGV exit -1 fi shift rm .config ln -s $CONFIGV .config make $@ o, if we call the above script, build: ./build .config.mailserver.2.2.13 xconfig That will link .config.mailserver.2.2.13 as .config, and run xconfig. ./build .config.mailserver.2.2.13 clean dep bZimage On 29 Mar 00, at 20:03, Alain Didierjean wrote:

Any suggestion about how to organize in order to have a single source directory (if achievable), two .configure files and be able to compile upgrades of the kernel for any of the two computers in a practical way, without messing around ? I have a few ideas about how to achieve this, but no time to experiment.

Jerry Feldman Associate Director Boston Linux and Unix user group http://www.blu.org -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/