Re: Once I build a modularized kernel to get HPFS, how does thisaffect updates via up2date?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Just saw this thread, hope you don't mind me dropping in on it.

I've tried to do this with the 2.4.20 kernel too.  In particular, I
needed support for the "Fuji Finepix-3800" camera and it didn't come
with the kernels/modules I've been getting from RH.

When I tried getting the newest kernel and using the "make oldconfig," I
was prompted for some options that were new and didn't come with the RH
kernels.  I answered them pretty much as either "module" or "no, don't
need".

When completed, the kernel wouldn't boot....all of the stuff (image,
etc)was there, but it just wasn't any good.

In the end, I ended up modifying the RH kernel source package for
2.4.18-24 to add my camera to the USB "oddball" list.

Any ideas on the easiest route back to the fold?  I'd like to avoid this
trouble in the future too without having to recompile all my stuff each
time....

Thanks,

Dan D

On Mon, 2003-03-10 at 16:05, Iain Buchanan wrote:
> On Tue, 2003-03-11 at 08:44, James Jones wrote:
> [snip]
> > Once I do this, though, how often do I get to go through the process 
> > again?  I would expect it with a move from one version to another, but 
> > how about kernel updates via up2date within a version? Thanks.
> Firstly you could get the latest (stable) kernel from kernel.org, then
> you wouldn't have to worry about recompiling every time redhat released
> a kernel update.  Plenty of other people (including RedHat) can comment
> on the benefits of using their kernels instead of kernel.org's. 
> Besides, you don't have to keep updating your kernel just because a new
> one is released, unless the new kernel fixes some bugs / security holes
> that you experience.  I've been running 2.4.20 about as long as its been
> released.
> 
> Secondly, I would compile the kernel using RedHats config file, and
> possibly 'make oldconfig' if you're using different source for which the
> config file was written, _without_ doing any changes by yourself.  Then
> make sure it is bootable.  This step weeds out any problems related to
> your process rather than the source you're trying to compile.
> 
> Thirdly, you can change options and add modules (HPFS for example). 
> This step should be short, so long as you don't do a make clean.
> 
> This is just a pointer to get you going.  You'll have to look into
> readmes and so on for more exact steps, but thats half the fun isn't it
> :)
> 
> HTH,
-- 
Dan Devine <dannyboy259@xxxxxxxxx>



-- 
Psyche-list mailing list
Psyche-list@xxxxxxxxxx
https://listman.redhat.com/mailman/listinfo/psyche-list

[Index of Archives]     [Fedora General Discussion]     [Red Hat General Discussion]     [Centos]     [Kernel]     [Red Hat Install]     [Red Hat Watch]     [Red Hat Development]     [Red Hat 9]     [Gimp]     [Yosemite News]

  Powered by Linux