Bug 86433 – vim needs to know about /dev/hvc0

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Tom Gall (RETIRED) 2005-03-23 14:38:36 UTC]

Greets,

We've added support for /dev/hvc/0 /dev/hvc0 to baselayout. (for 2005.0) 

This device is the "virtual" console for ppc64 systems running in a partition as well as for JS20 blades.  As such in order to emerge vim on these boxes, we need a fix otherwise one is presented with:

<rangerx86> tried to emerge vim
<rangerx86> --------------------------- ACCESS VIOLATION SUMMARY ---------------------------
<rangerx86> LOG FILE = "/tmp/sandbox-app-editors_-_vim-core-6.3-r3-9514.log"
<rangerx86> chmod:     /dev/hvc/0
<rangerx86> --------------------------------------------------------------------------------

when vim-core is emerged.

Since this is in 2005.0 and the unwashed massses will start to jump on this soon, I've marked this as a major severity. Be nice to avoid the complaints we'll see. 

Thanks!

[Comment 1 Ciaran McCreesh 2005-03-24 08:38:03 UTC]

vim.eclass r1.104:

-       # This should fix a sandbox violation (see bug 24447)
-       for file in /dev/pty/s* /dev/console; do
-               addwrite $file
+       # This should fix a sandbox violation (see bug 24447). The hvc
+       # things are for ppc64, see bug 86433.
+       for file in /dev/pty/s* /dev/console /dev/hvc/* /dev/hvc* ; do
+               [[ -e ${file} ]] && addwrite $file

Think that should do it...