![]() Wine needs to abuse the system, because it needs to run Windows applications. # sandboxctl -c wine run useradd -m -d /home/wine wine ![]() ![]() Let's create the sandbox and Wine user: # sandboxctl -c wine create NETBSD_RELEASE_SETS="base etc xbase xetc xfont" NETBSD_RELEASE_RELEASEDIR="/home/washbear/netbsd-i386" Configuring sandboxctlĭownload some i386 NetBSD sets into a directory: $ mkdir -p ~/netbsd-i386/binary/sets & cd ~/netbsd-i386/binary/setsĬreate a new config file for sandboxctl in /usr/pkg/etc/sandboxctl/nf: SANDBOX_TYPE=netbsd-release This one will allow Wine to map the null page (which it needs to do for cursed reasons): # sysctl -w vm.user_va0_disable=0Īdd them to /etc/nf to make them permanent. Things are mysteriously silent: # sysctl -w hw.audio0.multiuser=1 This one will allow multiple system users to play audio,Īnd will save you some debugging if you're wondering why You'll need to enable some sysctl variables. ![]() I learned a little bit more about how X11 works while trying this,įirst, install the sandboxctl package: # pkgin install sandboxctl Too much - sandboxctl creates a chroot based on a fresh system image, Maybe you also don't trust the Windows applications you're running Which is a neat tool for quickly shelling into a different NetBSD userspace. We'll see if this was a viable alternative to re-reviewing the On amd64 without resorting to running real Windows in So a 32-bit sandbox seems like a reasonable way to use 32-bit Wine "Mainline pkgsrc" can't do strange multi-arch Wine builds yet, To be built with 32-bit libraries to run a lot of older Windows It's current year, my machine runs amd64, and Wine needs I recently updated the Wine package to a recent stable version,Īnd now want to play some old Windows games on NetBSD. Running Wine in a 32-bit sandbox on 64-bit NetBSD Running Wine in a 32-bit sandbox on 64-bit NetBSDĭisclaimer: this is completely mad science, and mostly a learning
0 Comments
Leave a Reply. |