How exactly is devfs_contexts supposed to work, when is it applied?

The default settings in the file appear to be applied, here is a sample: root@test:/etc/flask# stat /dev/null /dev/random

  File: "/dev/null"
  Size: 0               Blocks: 0          IO Block: 1024   Character Device
Device: 7h/7d   Inode: 9           Links: 1     Device type: 1,3
Access: (0666/crw-rw-rw-)  Uid: (    0/    root)   Gid: (    0/    root)
Access: Thu Jan  1 01:00:00 1970
Modify: Thu Jan  1 01:00:00 1970
Change: Thu Jan  1 01:00:00 1970

  SID: 33
  S_context: system_u:object_r:null_device_t

  File: "/dev/random"
  Size: 0               Blocks: 0          IO Block: 1024   Character Device
Device: 7h/7d   Inode: 13          Links: 1     Device type: 1,8
Access: (0666/crw-rw-rw-)  Uid: (    0/    root)   Gid: (    0/    root)
Access: Thu Jan  1 01:00:00 1970
Modify: Thu Jan  1 01:00:00 1970
Change: Fri Jan 18 03:38:15 2002

  SID: 130
  S_context: system_u:object_r:random_device_t

However I added the following line to the file:
/vc/0 system_u:object_r:devtty_t

But then after loading the new policy it's still not there! root@test:/etc/flask# make load
install -m 644 -o root -g root policy /ss_policy
/usr/bin/load_policy /ss_policy

Success
root@test:/etc/flask# stat /dev/vc/0

  File: "/dev/vc/0"
  Size: 0               Blocks: 0          IO Block: 1024   Character Device
Device: 7h/7d   Inode: 83          Links: 1     Device type: 4,0
Access: (0666/crw-rw-rw-)  Uid: (    0/    root)   Gid: (    5/     tty)
Access: Thu Jan  1 01:00:00 1970
Modify: Thu Jan  1 01:00:00 1970
Change: Fri Jan 18 03:38:15 2002

  SID: 34
  S_context: system_u:object_r:device_t
root@test:/etc/flask#

PS I'm running 2.4.17 with the latest patch for the utilities (thanks Stephen).

-- 
http://www.coker.com.au/bonnie++/     Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/       Postal SMTP/POP benchmark
http://www.coker.com.au/projects.html Projects I am working on
http://www.coker.com.au/~russell/     My home page

--
You have received this message because you are subscribed to the selinux list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.