About this list Date view Thread view Subject view Author view Attachment view

From: Dariush Pietrzak (eyck_at_ghost.anime.pl)
Date: Wed 11 Feb 2004 - 10:35:23 GMT


Hi,
 Hmm, wouldn't correct solution be something like this:
when server boots up, vserver utilities report to the kernel the inode
number of vservers directory ( and possibly minor&major number of device on
which it's sitting ), and the vserver barrier becomes
checking the inode instead of some special-case of various volatile
settings? That would require small change in userspace, but wouldn't it be
worth the trouble?

If so, what would be correct way to send vserver inode to kernel?
echo "1245334" > /proc/sys/verver-inode ?

-- 
Key fingerprint = 40D0 9FFB 9939 7320 8294  05E0 BCC7 02C4 75CC 50D9
..The program fails and the power plant explodes, poisoning the earth 
and the sea. Famine and disease sweep the world. All die.
   Oh, the embarrassment.
_______________________________________________
Vserver mailing list
Vserver_at_list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver


About this list Date view Thread view Subject view Author view Attachment view
[Next/Previous Months] [Main vserver Project Homepage] [Howto Subscribe/Unsubscribe] [Paul Sladen's vserver stuff]
Generated on Wed 11 Feb 2004 - 10:36:29 GMT by hypermail 2.1.3