🚀 go-pugleaf

It's 07 May 98  14:18,
We'll return to asdaws@kyneton.net.au and All's
discussion of iBCS

 as> Sorry if this is a bit of a dumb question, but I'm a tad confused  :-)
 as> = I have a perfectly functional Slackware system running the 2.0.30 =
 as> kernel, with iBCS fine.  I have recently downloaded the 2.0.33 kernel
 as> = source, compiled a kernel, and made & installed modules to suit - all
 as> = works great and my system will boot into 2.0.33 fine, however it no =
 as> longer knew about the iBCS module.  I presume this isn't a standard =
 as> kernel module or option, but a separate package.  I extracted the
 as> source = from my slakware CD, and compiled it (under 2.0.33) OK.  When
 as> I boot in = 2.0.33 now however it complains that the iBCS module was
 as> compiled under = 2.0.30  :-(

You need to update iBCS.  I had to do the same when upgrading from
2.0.30 to 2.0.32 (under Red Haat in my case).  Not sure if the docs with
the kernel mention this...

... I've been to the paradise... it's called the DEATH STAR!!!
--
| Fidonet:  Tony Langdon 3:632/367.2
| Internet: tlang@freeway.DIALix.oz.au
|
| Freeway Internet Gateway, Melbourne, Australia.  For information about
| our services and conditions of use, e-mail:
| info@freeway.DIALix.oz.au, to receive a copy of the FAQ.