This is a discussion on New kernel 2.6.7 on Slack 9.1 within the Slackware Linux Support forums, part of the Unix Operating Systems category; --> Hallo to everybody... I just compiled (with my great joy, 'cause the new kernel supports my Adaptec 2400A RAID ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hallo to everybody... I just compiled (with my great joy, 'cause the new kernel supports my Adaptec 2400A RAID controller) and installed on my Slack 9.1 the latest Linux kernel 2.6.7. All is going well... I just wanted to know whether I had to upgrade some Slack (related to kernel) packages to let the new kernel run smooth and well. Thanks in advance Carmine ------------------------ Italian slack user, kernel 2.4.26 / 2.6.7 |
| |||
| Nino <carmine_scn@tin.it> wrote: > > Hallo to everybody... > > I just compiled (with my great joy, 'cause the new kernel supports my > Adaptec 2400A RAID controller) and installed on my Slack 9.1 the latest > Linux kernel 2.6.7. > All is going well... I just wanted to know whether I had to upgrade some > Slack (related to kernel) packages to let the new kernel run smooth and > well. Could you define "smoth and well"? If everything works as it should, there is no problem. |
| |||
| Kai Brust wrote: > > Could you define "smoth and well"? If everything works as it should, > there is no problem. Yes... obviously... :-) I read on this ng that some packages had to be updated before compiling the 2.6.7 kernel (I can't remember which one though.., like something related to 'initrd' or this kind). Anyway I'm writing from a Slack 9.1 with 2.6.7 on... All goes smooth... thanks anyway. Carmine. ------------------------ Italian Slack 9.1 user, Kernel 2.4.26 / 2.6.7 |
| |||
| Nino <carmine_scn@tin.it> schrieb: > I read on this ng that some packages had to be updated before compiling the > 2.6.7 kernel (I can't remember which one though.., like something related > to 'initrd' or this kind). > Anyway I'm writing from a Slack 9.1 with 2.6.7 on... > All goes smooth... Yes, there is a mkinitrd package in -current now. It's main purpose is for the pre-compiled 2.6.7 kernel in testing/. All filesystem drivers are provided as modules, so you need to make a proper initrd to boot into your system. However, this is unneeded if you roll your own and compile in all the required parts. |
| |||
| On Wed, 23 Jun 2004 20:03:39 +0000, Nino wrote: > I read on this ng that some packages had to be updated before compiling the > 2.6.7 kernel (I can't remember which one though.., like something related > to 'initrd' or this kind). You do not need initrd ... that is only necessary for the stock 10.0 testing 2.6.7 kernel, which is missing many drivers which might be necessary to access your root filesystem. The fact that your kernel boots proves that it has those drivers built-in. You might want to look into udev, but the "it ain't broke" factor is not to be neglected. -- /dev/rob0 - preferred_email=i$((28*28+28))@softhome.net or put "not-spam" or "/dev/rob0" in Subject header to reply |
| ||||
| /dev/rob0 wrote: > > > You might want to look into udev, but the "it ain't broke" factor is > not to be neglected. Hallo... yes... you're right...the "if it ain't broken" factor is not to be neglected... so I'm not going to break this rule... Where is 'udev'? bye ------------------------ Italian Slack 9.1 user, Kernel 2.4.26 / 2.6.7 |