xconfig in 1.3.69

xconfig in 1.3.69

Post by Andrew Ro » Thu, 29 Feb 1996 04:00:00



Has anyone else had problems with the xconfig option in 1.3.69? I selected
CONFIG_FAT_FS as a module and also CONFIG_MSDOS_FS, CONFIG_VFAT_FS and
CONFIG_UMSDOS_FS as modules to. When I saved the config though and then
checked .config by hand only CONFIG_FAT_FS was defined. I defined the
other three so the correct modules were built. I've noticed the same
problem under earlier kernels too (1.3.68 certainly). I'm afraid I don't
know enough about tk to debug the scripts though.

Andrew

-----------------------------------------------------------------------------

   Churchill College    Tel (01223) 331594
   Cambridge CB3 0DS    http://www.chu.cam.ac.uk/home/anr1001/home.html    

 
 
 

xconfig in 1.3.69

Post by Gordon Chaff » Thu, 29 Feb 1996 04:00:00




>Has anyone else had problems with the xconfig option in 1.3.69? I selected
>CONFIG_FAT_FS as a module and also CONFIG_MSDOS_FS, CONFIG_VFAT_FS and
>CONFIG_UMSDOS_FS as modules to. When I saved the config though and then
>checked .config by hand only CONFIG_FAT_FS was defined. I defined the
>other three so the correct modules were built. I've noticed the same
>problem under earlier kernels too (1.3.68 certainly). I'm afraid I don't
>know enough about tk to debug the scripts though.

Yes, I've had trouble as well.  Here is a fix:

diff -u linux-1.3.66/scripts/tkgen.c linux/scripts/tkgen.c
--- linux-1.3.69/scripts/tkgen.c        Tue Feb 13 12:12:20 1996

            {
              if(cfg->tok == tok_dep_tristate)
                {
-                 printf("\tif {$%s == 2 } then {\n"
+                 printf("\tif {$%s == 0 } then {\n"
                         "\t\twrite_variable $cfg $autocfg %s $notset $notmod\n"
                         "\t} else {\n"
-                        "\t\twrite_variable $cfg $autocfg %s $%s %s\n"
+                        "\t\twrite_variable $cfg $autocfg %s $%s $%s\n"
                         "\t}\n",
                         cfg->depend.str,
                         cfg->optionname,
--
Gordon Chaffee

http://www-plateau.cs.berkeley.edu/people/chaffee

 
 
 

1. Is 1.3.69 most recent most stable?

I downloaded what I read was supposed to be the latest kernel,
compiler, utilities, etc... for building the new kernel.  It
seems to have blown up and, being a linux newbie, I'm not sure
why.  (Having two 300Mb+ linux partitions prevented self
inflicted disaster.)  Is 1.3.69 more stable than 1.3.100?  What
order do I rebuild a 'new' system.  I don't mind the pains of
learning one's lessons.  I *would* like more info on what
modules, gcc, etc... go together.  Do I recompile gcc.latest.
then linux.new.cool.stuff....?  Then modules, utilities, then
everything else I can't live without?...   I would appreciate any
information (even constructive sarcasm would be better that
stabbing in the dark).  Thanks....   Dale

2. Netscape 3.01 core dump

3. qic-02 Archive SC402 and 1.3.69

4. Impossible to uninstall LILO - fdisk /mbr does not work!!!

5. xemacs 19-13 & linux 1.3.69 (ELF)

6. invalid migic numbers with system libraries and load()

7. 1.3.69 and ftape

8. Setting up a PPP connection

9. 1.3.69 Can't add NCPfs support...

10. Two quick question about configuring the 1.3.69 kernel.

11. Double lock on socket - 1.3.69

12. Strange console boot-time message with 1.3.69 kernel.

13. HOLY SHIT! Looks like a serious problem in kernel 1.3.69.