Re: BDI TNG

["Pete Cook" <kf2qd-at-terraworld.net>]

I'm a slackware fan myself - I've been able to get it up and running with a
minimum of hassle - (slack 7/Bigslack which installed EVERYTHING from zip
files toSlack 8 which requires I install a bit myself) and run it under
umsdos so I don't have to try to come up with another hard drive but for now
that one only works with uptp 2.2.19, 2.4??? can do nasty things to the file
system and then crash if run with umsdos. Because of that restriction I
personally would not be interrestd in anything for a 2.4 kernel - Brian has
been working on a slack install and when I find out what is wrong with my
kernel I should have it running. It sounds like he might be able to do it
with a couple tarballs which I think makes for the best install I have seen
under any OS. Install using the pkgtools under setup or go to / and tar -xzf
(seems to work... or should it be -xvf) and everything is in place in a
matter of a few seconds.

Pete

> Hi Folks
>
> After banging my head against a problem Ray pointed out to me a while
back, I
> have come to the conclusion that a brand new BDI build is required. This
will
> be RedHat 7.2 based, with a whole bunch of new packages, but I have a
> quandary - Should I use the latest 2.4.17 kernel with rtai or an old,
buggy
> 2.4.4 with rtlinux-3.1 (or even 2.4.1 & rtl-3.0) ??
> Using rtai means loosing steppermod, and will require a minimum computer
spec
> of ~233Mhz. Running a 2.4.x-rtl kernel will mean forgoing the advantages
of a
> journaling filesystem, but will run on lower spec computers.
>
> Adapting the RH install shell is going to be a major nightmare so that
both
> options could be accommodated, and I'd rather not go that route - The
> alternatives are to build an rtl-3.x kernel and EMC (either as an rpm or
> tarball) and leave the user to manually install them. or drop rtlinux
> altogether. The last option being my personal preference.
>
> Comments please.
>
> Regards, Paul.
>
>