> Ok I looked into into doing this and I am not sure completely how
> to proceed. When I execute unpack.s I end up with two directories
> 1 and 2. I assume to change the kernel we would replace zImage ,
> map and boot.b in directory 1. Do I just take the kernel, boot.b
> and map from a 6.x system?

No.  Just replace zImage.  When you run buildit.s, map will be 
re-generated automatically by lilo.  The boot.b file does not change.

> Now in directory 2 I assume you need to change the modules in
> /lib/modules. I am confused that the ethernet card module is in
> the pcmcia directory rather than in the net directory.  What is
> the module plip.o in the net directory.

Plip is the parallel link interface protocol (I think), basically, TCP/IP
over a printer port, like, laplink.  In tomsrtbt, the ethernet modules are
all hard-compiled into the kernel, they are not modules at all.  It is
fairly foolproof and not a bad idea for you to just do the same with your
2.2.x kernel, but of course, you could have them be modules if you
want.  I do not include or support, for example, some of the more modern
tools such as modprobe, which might be an issue, although maybe insmod
would work.  Only PCMCIA modules are in the pcmcia directory, those are
NOT used for normal ethernet cards.

> I would really like to get this to work, epecially to get tomsrtbt
> to work with other ethernet cards. You say it is easy but I am not
> sure what exactly needs to be done.

Just run 'make config' or 'make menuconfig' in your 2.2.x kernel
directory, say yes to everything you want, including the ethernet cards
you want, and make sure you say yes to ramdisks, floppy disks, and the
minix filesystem.  Then type 'make clean', then 'make dep', then 'make
zImage'.  Then put arch/i386/boot/zImage into the 1/ directory where you
unpacked it.  Then delete all the 2.0.x modules and the references to them
in the rc.custom.gz and settings.s.  Then run the buildit.s.  Then it
should be ready to install.s and you are done.

One issue I have to adress, is the issue of the intended audience for
tomsrtbt, the audience to which I said 'PS it is easy to put a 2.2.x
kernel onto tomsrtbt'.  That audience is the audience to whom the last
paragraph is not even necessary because they know how to rebuild a kernel.
Tomsrtbt is really intended more for system administrators and seasoned
hackers than for those just figuring out how the pieces fit together.

Not to say that it wouldn't be good for those users also, just that the
support paradigm is to explain things only as far as is needed for those
who already know how to do the tasks, with the exception of the aspects
that are unique to tomsrtbt.

Since there is no *special* or *different* or *unique* requirement for
tomsrtbt with a 2.2.x kernel, that is, no binaries or libraries change,
nothing in /etc changes, nothing in rc.custom.gz or settings.s changes,
I can say, "nothing to it, just do what you would do on *ANY* linux, but
make sure to include support for ramdisks, floppy diskettes, and minix
filesystems", and, voila, it is simple.  If that isn't enough, then you
really need to start with:

 http://linuxdoc.org/
  or
 http://www.geek-girl.com/unix.html
  or
 http://www.ugu.com/            

as you are really trying to learn how _Linux_ works, or how _Unix_ works,
_not_ anything that is really specific to tomsrtbt.  And, I have explicitly
said, again in the FAQ,

        I am not a Unix teacher, questions should be tomsrtbt-specific.

Not that I really mind your asking, just that I want it well documented why
I don't really always offer much help and am frequently abrupt or even, dare
I say, sarcastic.  

-Tom



Reply via email to