The same action via ssh sorks fine. Narrowed this down to a portage bug. Package in question is vim, but this would probably happen with anything trying to access /dev/tts/0 during install --------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE = "/tmp/sandbox-app-editors_-_vim-core-6.2-r7-5210.log" chmod: /dev/tts/0 -------------------------------------------------------------------------------- Portage 2.0.50-r1 (default-sparc64-1.4, gcc-3.2.3, glibc-2.3.3_pre20040207-r0, 2.6.3)
s/sorks/works/ :P
This also occurs on x86 (stage3 install from 2004.3 using Portage snapshot) with vim-core-6.3-r2 and vim-6.3-r1 using Portage-2.0.51-r2. For some reason, when running emerge from the serial console, the tty permission check in the configure script is trying to do a chmod() on the controlling terminal (/dev/tts/0) and of course this results in a sandbox violation. Workaround: emerge vim </dev/null
This also happens with vim-6.3.084, a workaround is also `FEATURES="-sandbox" emerge vim`
Az, do you want to add an exception for /dev/tts/*, are there currently exceptions for /dev/tty*? Or punt the bug to vim-core and have them fix their configure script?
Done, will be in next release.
Why is this bug still open?
What's the status here?
@sparc folks - please test this thing and reopen if needed, sandbox maintainer is completely MIA again.