- Oct 11, 1999
- 3,064
- 0
- 0
I recently installed a fresh copy of 3.0r2 on a test machine. Being as old as it is, I know for a fact that it contains a recently announced kernel exploit. However, when I do a apt-get dist-upgrade and an apt-get upgrade, I'm left with the same kernel in the end. Yes security.debian.org is in my sources.list.
Is this normal behavior? Does apt treat the kernel differently than other packages?
I'm trying to move over from RH7.3, so I'm used to up2date. With up2date, you had to tweak a config file to get it to upgrade the kernel because defaultly it would leave it alone. Is there a similar configuration tweak I need to do in debian?
Also, it appears that the install kernel is an attempted "catch all/compiled in" kernel. As such I have next to nothing in /etc/modules. Is there a debian hardware detection tool that will build the modules list for me (like kudzu)?
Note: Please do not turn this into a thread about the merits of, or why I should be compiling my own kernel. My goal is to make as analagous a transition as possible from debian to redhat.
Is this normal behavior? Does apt treat the kernel differently than other packages?
I'm trying to move over from RH7.3, so I'm used to up2date. With up2date, you had to tweak a config file to get it to upgrade the kernel because defaultly it would leave it alone. Is there a similar configuration tweak I need to do in debian?
Also, it appears that the install kernel is an attempted "catch all/compiled in" kernel. As such I have next to nothing in /etc/modules. Is there a debian hardware detection tool that will build the modules list for me (like kudzu)?
Note: Please do not turn this into a thread about the merits of, or why I should be compiling my own kernel. My goal is to make as analagous a transition as possible from debian to redhat.