On Tue, Nov 14, 2006 at 08:07:50AM -0500, Marc Ravensbergen wrote:
> Hi, first I'd like to mention that openbsd 4.0 is a first for me, and I
> am really liking it so far (I am a linux refugee...). Eg., it's nice to
> be able to rip out my usb cd burner, plug it in, and be able to actually
> use the thing again. Try that under linux and the cd burner is unsuable
> until you reboot... Not to mention that the whole "secure by default"
> thing is very appealing.
Welcome aboard!
> I am having a hard time getting java to work on openbsd. Java is a
> deal-breaker for me as I use it all day every day for work. What I've
> done is taken a tar of the linux version, and untarred it in openbsd. I
> have turned on linux emulation by modifying the variable in
> /etc/sysctl.conf, and I've mounted the /proc "filesystem". I have also
> pkg_added redhat-base8.xxx.
>
> However, whenever I run java, I get a "Can't detect initial thread stack
> location - find_vma failed" error. This is for sun's jdk 1.5.06 as well
> as one of the newer 1.6 versions. IBM's jdk1.4 says it cannot read or
> write (not sure exactly anymore) to /proc/xxxx. I've tried running all
> three versions as root to check for permission errors, but it makes no
> difference. I've googled for hours trying to find a solution, but can't
> seem to fix it.
>
> I really don't want to download the source for java and compile... I am
> on dialup so every byte counts. A little while ago I tried java on
> netbsd and got it working through linux emulation as well. I had
> problems with netbsd so it didn't stick around, but I believe that java
> on bsd through emulation should be possible; probably just an oversight
> somwhere on my part.
>
> If anybody can give me some tips or tricks I would really appreciate it.
Well, the *sane* way of doing this involves building it from ports.
Those are there for a reason, after all. Burning it to a CD and putting
the CD in your machine may be useful if you have access to a faster
network elsewhere; but I'd strongly suggest just downloading the source
and being done with it. For additional points, tweak altq(9) so that you
can still browse at an acceptable speed.
If you want to try your way, -current's emulators/fedora just *might*
build on a -stable system; those libraries are a lot newer, and *might*
fix your problem. Of course, there's no reason to assume either...
Joachim
