(Illustration by Gaich Muramatsu)
On Tue, Jul 20, 1999 at 02:10:29PM +0800, LEE, Yui-wah (Clement) wrote: > Yes, I think this is the problem. You can pick a different "rvm starting > address" -- instead of using the default 0x20000000 (for linux) , use > something like 0x50000000 (or other) with rdsinit. You have two methods > to use rdsinit and rvmutl: 1. run them manually (then read rdsinit(8) > and rvmutl(8) for more details); or 2. use a modified version of > vice-setup-rvm. Of course, the script vice-setup-rvm can serve as an > example if you want to run the two programs manually. Right. In vice-setup-rvm there is the following code: case `uname -sr` in "NetBSD 1.2" ) rvmstart=0x20000000 ;; NetBSD\ 1.3* ) rvmstart=0x50000000 ;; NetBSD\ 1.4* ) rvmstart=0x50000000 ;; FreeBSD\ 2.2* ) rvmstart=0x50000000 ;; FreeBSD\ 3* ) rvmstart=0x50000000 ;; *) rvmstart=0x20000000 ;; esac Hopefully `uname -sr` gives something unique (like Linux 2.2.10-VA), so we can add a special case. Otherwise just change the default entry to 0x50000000. It looks like this might be safe on normal linux kernels as well. JanReceived on 1999-07-20 09:37:56