We know from Section 1.7 that modules are split between public modules put in a
$MEGAWAVE2 and private modules put in
Actually, for the MegaWave2 administrator things are a little bit more complicated : the administrator may
want to be able to check new public modules and new kernel binaries before making them available for plain users.
Therefore, the administrator has his own
$MEGAWAVE2 directory wich is not necessary the same as the
$MEGAWAVE2 directory of plain users.
$MEGAWAVE2 directory is called private MegaWave2
(with associated environment variable
$PRIVATE_MEGAWAVE2) whereas the
$MEGAWAVE2 directory of plain users is called public MegaWave2 (
Of course, if you don't plan to update the system or if the only user is the administrator you should set
Notice that the administrator always has