Andreas Tille <andr...@an3as.eu> writes: > So what is the proper / suggested fix? I see two options:
> 1. Use a shell wrapper instead. > 2. Enforce binfmt_misc somehow (if yes - how?) > I wonder how other packages which are using the same technique are solving > this problem. I'm pretty sure that we enable binfmt_misc by default, and it would be nice to avoid having to write simple shell wrappers for every Java application. But I'm not sure how to detect whether binfmt_misc is set up to warn the user or to enable it or whatnot. For that, I'd have to defer to other folks here, who hopefully know more about the setup and history. Note that it's going to be hard to ensure that it's enabled on any system, since users may be building their own kernels without including that support. -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-java-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/871v0egmtm....@windlord.stanford.edu
