Master Kernel Thread

[xanikseo]

Holding enter won't harm anything, it just selects the default option.

mahuyar, I have the avahi-daemon problem as well, is it worth fixing, will it cause any problems not having it running? And is there a way of fixing it without re-compiling the kernel?

[mahuyar]

Holding enter won't harm anything, it just selects the default option.

mahuyar, I have the avahi-daemon problem as well, is it worth fixing, will it cause any problems not having it running? And is there a way of fixing it without re-compiling the kernel?

Is it worth fixing.. hmm.. I don't know. It depends on your needs. IIRC, the avahi-daemon is used to scan your network resources automatically such as shared folders, printers and what not. For me, I don't need it since everything is connected locally.

And I don't know how to fix it w/o recompiling the kernel.

[Sokertes]

Thank You Thank You Thank You

I am a long time linux user (RedHat, Gentoo, CentOS) and I installed Ubuntu on my my temp workstation (due to CPU burned out on my main one) that is a 800Mhz with 250M ram and I did not want to wait all week for Gentoo to compile on it so I installed Ubuntu on it cause of all the hype I have read about it.

Needless to say Ubuntu has lived up to its ratings.

I wanted to compile the kernel but have never done it on a deb OS before and when I found this link it worked flawlessly. Now instead of the default kernel with all the default modules (which I hate anyway) my machine boots up with what I need per my hardware and that is it.

Not only does my machine run faster (considering the CPU speed of course) with the compiled 2.6.24 kernel rather the default install kernel. But my boot time is faster without all the default modules loading.

My deb learning curve is on its way thanks to this VERY helpful howto.

I said all that to say this

Thank You Thank You Thank You

I'll shut up now


Sokertes

[spinr34]

Whenever I do "dpkg -i filename.deb" I always get this message.

 linux-image-2.4.19 depends on initrd-tools (>= 0.1.84); however:
  Package initrd-tools is not installed.

I'm using Ubuntu 7.10 and initrd-tools is not available. I'm a fairly new Linux user too and have been messing with this for a day or so and am completely stuck. Any help is appreciated.

Thanks

[tormod]

I'm using Ubuntu 7.10 and initrd-tools is not available.Thanks

initrd-tools has been replaced by initramfs-tools nowadays. You will have to change the dependencies and some postinst scripts in the .deb package. Anyway, why do you want to downgrade to such an old kernel in 7.10?

[spinr34]

initrd-tools has been replaced by initramfs-tools nowadays. You will have to change the dependencies and some postinst scripts in the .deb package. Anyway, why do you want to downgrade to such an old kernel in 7.10?

I'm going to such an old kernel for my work. Is there anywhere I can find a list of which files need to be changed?

[sylecn]

I've got two questions before trying this:
If I didn't change options after importing the old config file, will I get better performance?
How much faster is all-in-one kernel compared to modularized kernel?

[mahuyar]

I've got two questions before trying this:
If I didn't change options after importing the old config file, will I get better performance?
How much faster is all-in-one kernel compared to modularized kernel?

For your first question, are you saying that going with Ubuntu's kernel configuration would give you better performance? If that's the case, you won't "feel" any performance gained, since Ubuntu's kernel configuration is to fit everyone's needs. Note that I have quotations around the word, feel, because it varies among people here. As for me, personally, yes I do notice that the system has become a bit more responsive after changing some options, e.g. Timer Frequency to 1000 Hz. But this doesn't mean you'll get everything done faster, since there are always tradeoffs between throughput and being more responsive.

I don't think I've noticed anything faster by compiling modules into the kernel rather than being modular. That's for your second question, of course.

[nexes]

Has anyone else come across a problem where instead of compiling the modules, it just prints the script used to do the compilation to the terminal window? I can't figure out what exactly is causing it.

I haven't looked too far into it, as I'm not sure how exactly make-kpkg works, but it's not executing that shell script correctly for whatever reason..

# make-kpkg --initrd --revision=386 modules_image
exec debian/rules  DEBIAN_REVISION=386  INITRD=YES  modules_image
for module in  ; do                       \
          if test -d  $module; then                                \
            (cd $module;                                          \
              if ./debian/rules KVERS="2.6.24.2" KSRC="/usr/src/linux-2.6.24" \
                             KMAINT="Unknown Kernel Package Maintainer" KEMAIL="unknown@unconfigured.in.etc.kernel-pkg.conf"      \
                             KPKG_DEST_DIR="/usr/src/linux-2.6.24/.."       \
                             KPKG_MAINTAINER="Unknown Kernel Package Maintainer"        \
                             KPKG_EXTRAV_ARG=""        \
                             ARCH="i386"         \
                             KDREV="386" kdist_image; then    \
                  echo "Module $module processed fine";            \
              else                                                  \
                   echo "Module $module failed.";                  \
                   if [ "X" != "X" ]; then      \
                      echo "Perhaps $module does not understand --rootcmd?";  \
                      echo "If you see messages that indicate that it is not"; \
                      echo "in fact being built as root, please file a bug ";  \
                      echo "against $module.";                     \
                   fi;                                              \
                   echo "Hit return to Continue";                   \
                 read ans;                                        \
              fi;                                                   \
             );                                                    \
          else                                                      \
               echo "Module $module does not exist";               \
               echo "Hit return to Continue?";                      \
          fi;                                                       \
        done

Any help would be appreciated.

[chadjohnson]

Has anyone else come across a problem where instead of compiling the modules, it just prints the script used to do the compilation to the terminal window? I can't figure out what exactly is causing it.

I haven't looked too far into it, as I'm not sure how exactly make-kpkg works, but it's not executing that shell script correctly for whatever reason..

# make-kpkg --initrd --revision=386 modules_image
exec debian/rules  DEBIAN_REVISION=386  INITRD=YES  modules_image
for module in  ; do                       \
          if test -d  $module; then                                \
            (cd $module;                                          \
              if ./debian/rules KVERS="2.6.24.2" KSRC="/usr/src/linux-2.6.24" \
                             KMAINT="Unknown Kernel Package Maintainer" KEMAIL="unknown@unconfigured.in.etc.kernel-pkg.conf"      \
                             KPKG_DEST_DIR="/usr/src/linux-2.6.24/.."       \
                             KPKG_MAINTAINER="Unknown Kernel Package Maintainer"        \
                             KPKG_EXTRAV_ARG=""        \
                             ARCH="i386"         \
                             KDREV="386" kdist_image; then    \
                  echo "Module $module processed fine";            \
              else                                                  \
                   echo "Module $module failed.";                  \
                   if [ "X" != "X" ]; then      \
                      echo "Perhaps $module does not understand --rootcmd?";  \
                      echo "If you see messages that indicate that it is not"; \
                      echo "in fact being built as root, please file a bug ";  \
                      echo "against $module.";                     \
                   fi;                                              \
                   echo "Hit return to Continue";                   \
                 read ans;                                        \
              fi;                                                   \
             );                                                    \
          else                                                      \
               echo "Module $module does not exist";               \
               echo "Hit return to Continue?";                      \
          fi;                                                       \
        done

Any help would be appreciated.

I have this problem too...WTF

*EDIT* Hmm...maybe this is normal? There is output like this when compiling begins as well. And the person at this thread did not complain about such output.

*EDIT 2* Ok, apparently this is due to it not finding any modules to process. Notice that in the for loop ( for module in ; do ) there are no array items to traverse. The question now becomes, should it be finding modules to process?