;-)
Wait for RedHat 6.1 or Slackware 4.1 or ...
to be released. Then ask around as someone may be willing
to give you their old CD distribution.
;-)
Chuck
[EMAIL PROTECTED] wrote:
>
> On Sun, 25 Jul 1999, Steve Youngs wrote:
>
> > Hey! Did you see what Brian Willis wrote on Jul 23 ?
> >
> > BW> I have kernel 2.0.18 and I'm in the process of adding patches to
> get
> > BW> my kernel current. Well, I've
> > BW> downloaded all patches up to 2.2.10 (wow, there were a lot of
> patches
> > BW> for 2.1). So, I started
> >
> > Here's where you went wrong. If you have kernel 2.0.18 you can
> > only patch that to 2.0.37
> >
> > 2.1.x was the development kernel that later became 2.2.0. Being very
> new
> > to Linux like you are you should stay right away from the development
> > kernels (odd numbered 2.1.x or 2.3.x).
>
> In general, this is true. I started with slackware 3.0 when it was
> already obsolete, and I had to use 1.3.18 to get support for my mighty
> 2x cdrom. I had a lot of fun with it for a year, and I don't have
> anything bad to say about it. :-). I'm using 2.0.37 now, with a couple
> of local patches, and it will be a while before I go with 2.2.
> It would be nice if some kind soul would make patch paths from
> everything to everything else, but I can understand why nobody has done
> so yet.
>
> Lawson
> >< Microsoft free environment
>
> This mail client runs on Wine. Your mileage may vary.
>
> >
> > Also, I would forget about trying to upgrade your system from 2.0.x to
> > 2.2.x it is possible, but a whole lot can go wrong. The best piece of
> > advice I could give you would be to spend a couple of bucks on a
> current
> > Linux distribution CD.
> >
> > BW> Do I only need to recompile the kernel? "Running LINUX" from
> O'Reilly
> > BW> says that can create some
> > BW> problems. I don't want to continue adding patches if I need to
> > BW> recompile the kernel to fix problems
> > BW> that will help me down the road. I'd appreciate any advice!!
> >
> > You actually have to re-compile the kernel for those patches to be
> > included into it. You are patching the kernel source code not the
> actual
> > kernel binary. Once you re-compile the patched source code you get a
> new
> > kernel binary that has the updates from the patch. You can apply
> multiple
> > patches (2.0.18 apply all patches to 2.0.37) then re-compile the kernel
> > after that.
> >
> > Another reason to re-compile the kernel would be to add support for
> > something you want that isn't there by default or to remove support for
> > something that you don't need. A smaller kernel is better because you
> use
> > less memory.
> >
> >
> > Regards, Steve Youngs <[EMAIL PROTECTED]> ICQ: 34307457
> > ------------------------------------------------------------
> > | __ |
> > | Isn't it good to know that / / __ ___ __ ____ __ |
> > | There _IS_ an alternative! / /__ / // _ \/ // /\ \/ / |
> > | /____//_//_//_/\_,_/ /_/\_\ |
> > ------------------------------------------------------------
> >
>
> ___________________________________________________________________
> Get the Internet just the way you want it.
> Free software, free e-mail, and free Internet access for a month!
> Try Juno Web: http://dl.www.juno.com/dynoget/tagj.
