Bernd Schemmer wrote:
> Hi,
> 
> (second try; my email to the list seems to got lost)
> 
> Using sloggi  (http://www.roqe.org/sloggi/ <http://www.roqe.org/sloggi/>)  I 
> can change the output of uname for all zones (including the global zone) from 
> within a zone:
> 
> global zone [Mon Dec 31 17:36:11 [EMAIL PROTECTED] 
> /export/install/profiles/sol3]
> # uname -a
> SunOS sol9 5.11 snv_78 sun4u sparc sun4u
> 
> sunstudio12 zone [Mon Dec 31 17:36:23 [EMAIL PROTECTED] /]
> # uname -a
> SunOS sunstudio12 5.11 snv_78 sun4u sparc sun4u
> 
> gcc zone [Mon Dec 31 17:37:12 [EMAIL PROTECTED] /]
> # uname -a
> SunOS gcc 5.11 snv_78 sun4u sparc sun4u
> 
> sunstudio12 zone [Mon Dec 31 17:37:34 [EMAIL PROTECTED] /]
> # slogctl -s MyOS
> MyOS sol9 5.11 snv_78 sun4u
> 
> sunstudio12 zone [Mon Dec 31 17:37:37 [EMAIL PROTECTED] /]
> # uname -a
> MyOS sol9 5.11 snv_78 sun4u sparc sun4u
> 
> gcc zone [Mon Dec 31 17:37:18 [EMAIL PROTECTED] /]
> # uname -a
> MyOS sol9 5.11 snv_78 sun4u sparc sun4u
> 
> global zone [Mon Dec 31 17:36:12 [EMAIL PROTECTED] 
> /export/install/profiles/sol3]
> # uname -a
> MyOS sol9 5.11 snv_78 sun4u sparc sun4u
> 
> 
> The sloggi module was installed before creating the zones; the zones are all 
> sparse zones.
> 
> I think this is a bug.
> 

It is a bug. In sloggi.

It does not properly virtualize the uname data; it only has a single 
copy of its fake uname struct. So when you change the data using slogctl 
it shows up everywhere, even in the global zone. Which is what I assume, 
you think to be the bug: the fact that you change data in the global 
zone form a non-global zone. But that is just what you asked for by 
loading the sloggi kernel module. It hooks the uname system call so 
there is nothing Solaris can do for you after that...

Menno

-- 
Menno Lageman - Sun Microsystems - http://blogs.sun.com/menno
_______________________________________________
zones-discuss mailing list
zones-discuss@opensolaris.org

Reply via email to