The reason why I have multiple directories is just so that I may have kernels that are compiled for the hardware that exist only on the specific groups of machines. For example, if the Pentium machines have Adaptec 2940UW SCSI adapters, but the 486 machines only have IDE drives, then obviously the 486 machines don't need the 2940UW driver compiled into the kernel. If xconfig can do that, then it may be possible for you to just have one directory. But I have never used xconfig to do that before. So I really can't say anything about it. But I know the previous method well, and have used it many times before. If you can mount NFS via PLIP, and if it is fast enough, then you may be able to do just that -- compile on a fast machine, mount the drive via NFS on the notebook, and install the kernel. Regards, Kenneth Tan ------------------------------------------------------------------------------ C. J. Kenneth Tan E-mail: cjtan@acm.org Telephone: 1-403-220-8038 cjtan@ieee.org 1-403-606-4257 cjtan@computer.org Facsimile: 1-403-284-1980 URL: <A HREF="http://www.cuug.ab.ca/~tanc"><A HREF="http://www.cuug.ab.ca/~tanc</A">http://www.cuug.ab.ca/~tanc</A</A>> 1-403-244-4123 "A working program without comment is a time bomb waiting to explode." -- Steve Oualline ------------------------------------------------------------------------------ On Wed, 19 Aug 1998, Rodolfo Pilas wrote:
On Tue, 18 Aug 1998 15:36:07 -0600 (MDT), C. J. Kenneth Tan wrote:
No, I am not using the processor and memory of each machine to compile and install the kernel. I compile the kernel on a powerful machine, then just install the kernel over network. This way, if I have a set of Pentiums, I'll untar the kernel source to a directory, say for example, /usr/src/586kernel and just symlink /usr/src/linux to that directory when I am compiling the kernel on a more powerful machine like a PII. Then for the 486 machines, I'll untar the sources to something like /usr/src/486kernel, then symlink /usr/src/linux to it before compiling. Then the Pentium machines that need the kernel will just mount, via NFS, /usr/src/586kernel to /usr/src/linux to install the kernel. Similarly, the 486 machines will mount /usr/src/486kernel via NFS to install the kernel. The kernels will only need to be compiled once. I don't know anything about PLIP, so I can't say anything about that. However, if you are in a LAN environment, then you definitely have a fast enough network connection.
I don't think you really understood the solution that I was describing in my original mail. Hopefully, this will clear things up a bit.
Yes! I do not underestand your first message. Now I hope to have understood your tips. I will use it!
However I do not have already a clear idea about the reason to have diferent source directories for each group of machines. The xconfig can maintain (save and load) configurations for each one of your groups or machines.
(PLIP: is a kernel option that enables you to have network conection through paralel ports with a "laplink" wire. With PLIP I can mount by NFS).
----/ / _ Rodolfo Pilas ---/ / (_)__ __ ____ __ rodolfo@linux.org.uy --/ /__/ / _ \/ // /\ \/ / ICQ# 17461636 -/____/_/_//_/\_,_/ /_/\_\ la oportunidad de dominar tu computadora ------------------------------------------------------------------- Personal Official Web Page -> <A HREF="http:///www.internet.com.uy/rodolfo"><A HREF="http:///www.internet.com.uy/rodolfo</A">http:///www.internet.com.uy/rodolfo</A</A>> Gente Como Uno BBS -> <A HREF="http://www.geocities.com/SiliconValley/4838"><A HREF="http://www.geocities.com/SiliconValley/4838</A">http://www.geocities.com/SiliconValley/4838</A</A>> Grupo Usuarios Linux Uruguay [UYLUG] -> <A HREF="http://www.linux.org.uy"><A HREF="http://www.linux.org.uy</A">http://www.linux.org.uy</A</A>>
PGP Public Key Fingerprint = EE 6C 76 53 2B D9 2F 53 7B CE E3 69 8C ED 84 09
- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e