Very true, which was why I mentioned the caution bit. Anyway, you should never use a new thing directly on a production machine, and any changes that can cause corruption (a seg fault straight away is more likely, in my experience), will show up in the test phase. regards Anders On Friday 24 August 2001 02:36, Dave Jones wrote:
On Fri, 24 Aug 2001, Anders Johansson wrote:
One option, that usually works (but may not. Excercize caution) is to use insmod -f
This will work (hopefully) if you have a module built for 2.4.0 and want to load it in a 2.4.2 kernel.
And pray to $DEITY that no big changes were made to any structure/code in the IDE/Block layer during this gap.
Russian roulette with disk data doesn't sound like my idea of fun :)
regards,
Dave.