Mailinglist Archive: opensuse (3863 mails)
| < Previous | Next > |
Re: [SLE] Error Compiling kernel-source 2.6.2
- From: Trey Sizemore <trey@xxxxxxxxxxx>
- Date: Fri, 20 Feb 2004 22:05:18 -0500
- Message-id: <1077332717.2625.24.camel@xxxxxxxxxxx>
On Fri, 2004-02-20 at 21:50, Anders Johansson wrote:
> Not really. Distros love modules, because it makes it easy for them to
> compile a one-size-fits-all kernel, where people just pick the modules
> they need. Like filesystems. If you use reiserfs, there's really no need
> for you to do that as a module. You might want to get the ones you don't
> use right now as modules though, just in case you want to try them out
> in future.
>
> Hotplugging things is probably also a good idea to compile as modules.
> You never know what USB device the wife'll bring home tomorrow :)
>
> I normally compile the things I use into the kernel, and the things I
> don't use but I might like to try in future I compile as modules, and
> the rest I just leave out
>
> > So this would be 'mv /home/trey/kernel2.6/archi386/boot/bzImage
> > /boot/vmlinuz-2.6.3-trey1'?
>
> arch/i386, not archi386. Apart from that, yes exactly.
>
> > I am using reiserfs...should this be compiled as a module or directly in
> > the kernel?
>
> I would compile it directly into the kernel.
>
> > >
> > > Step 8: edit /boot/grub/menu.lst
> > > You can copy the default "Linux" entry, change the title and the name of
> > > the kernel (the default is vmlinuz, change that to vmlinuz-2.6.3-trey1).
> > So both entries will be in /boot/grub/menu/lst?
>
> Right. That way you can boot back into your existing 2.4 setup by just
> selecting it in grub
>
> > > If you used an initrd, change that name too, otherwise you can simply
> > > delete that line
> > Sorry, not sure if I'm using initrd or not.
>
> Look in /etc/sysconfig/kernel, on the INITRD_MODULES line. It lists the
> modules you're currently using in your initrd. If you compile them into
> the kernel, and not as modules, then you won't need an initrd
>
> > I'm using the 'nv' driver right now. So should just the eth0 and
> > snd-card-0 aliases be copied over? None of the other aliases in this
> > file?
>
> with the "nv" driver you won't need the nvidia alias, that's correct.
> As for the other aliases, well, the ones you're using.
>
> It's difficult to give a general answer. A few modules have changed
> names in 2.6, so for those you'll need to create an alias with the new
> name. But the important thing is to get you up and running and on the
> net, then you can pick off the rest as you discover what isn't working.
>
Alright, I'll give it a try. By the way, I noticed you're running
Evolution 1.5.4. Did you get it from Red Carpet, and how do you like it
compared to previous versions?
--
Cheers,
Trey
---
The universe is change; our life is what our thoughts make it.
--Antoninus, Marcus Aurelius
10:03pm up 1 day 3:25, 1 user, load average: 0.14, 0.39, 0.33
Linux linux 2.4.21-144-default #1 Fri Nov 14 00:01:36 UTC 2003 i686 i686
i386 GNU/Linux
> Not really. Distros love modules, because it makes it easy for them to
> compile a one-size-fits-all kernel, where people just pick the modules
> they need. Like filesystems. If you use reiserfs, there's really no need
> for you to do that as a module. You might want to get the ones you don't
> use right now as modules though, just in case you want to try them out
> in future.
>
> Hotplugging things is probably also a good idea to compile as modules.
> You never know what USB device the wife'll bring home tomorrow :)
>
> I normally compile the things I use into the kernel, and the things I
> don't use but I might like to try in future I compile as modules, and
> the rest I just leave out
>
> > So this would be 'mv /home/trey/kernel2.6/archi386/boot/bzImage
> > /boot/vmlinuz-2.6.3-trey1'?
>
> arch/i386, not archi386. Apart from that, yes exactly.
>
> > I am using reiserfs...should this be compiled as a module or directly in
> > the kernel?
>
> I would compile it directly into the kernel.
>
> > >
> > > Step 8: edit /boot/grub/menu.lst
> > > You can copy the default "Linux" entry, change the title and the name of
> > > the kernel (the default is vmlinuz, change that to vmlinuz-2.6.3-trey1).
> > So both entries will be in /boot/grub/menu/lst?
>
> Right. That way you can boot back into your existing 2.4 setup by just
> selecting it in grub
>
> > > If you used an initrd, change that name too, otherwise you can simply
> > > delete that line
> > Sorry, not sure if I'm using initrd or not.
>
> Look in /etc/sysconfig/kernel, on the INITRD_MODULES line. It lists the
> modules you're currently using in your initrd. If you compile them into
> the kernel, and not as modules, then you won't need an initrd
>
> > I'm using the 'nv' driver right now. So should just the eth0 and
> > snd-card-0 aliases be copied over? None of the other aliases in this
> > file?
>
> with the "nv" driver you won't need the nvidia alias, that's correct.
> As for the other aliases, well, the ones you're using.
>
> It's difficult to give a general answer. A few modules have changed
> names in 2.6, so for those you'll need to create an alias with the new
> name. But the important thing is to get you up and running and on the
> net, then you can pick off the rest as you discover what isn't working.
>
Alright, I'll give it a try. By the way, I noticed you're running
Evolution 1.5.4. Did you get it from Red Carpet, and how do you like it
compared to previous versions?
--
Cheers,
Trey
---
The universe is change; our life is what our thoughts make it.
--Antoninus, Marcus Aurelius
10:03pm up 1 day 3:25, 1 user, load average: 0.14, 0.39, 0.33
Linux linux 2.4.21-144-default #1 Fri Nov 14 00:01:36 UTC 2003 i686 i686
i386 GNU/Linux
| < Previous | Next > |