On Fri, Dec 5, 2008 at 2:01 PM, Shawn Walker <[EMAIL PROTECTED]> wrote: > Aubrey Li wrote: >> >> On Fri, Dec 5, 2008 at 11:01 AM, Shawn Walker <[EMAIL PROTECTED]> >> wrote: >>> >>> Aubrey Li wrote: >>>> >>>> On Fri, Dec 5, 2008 at 12:38 AM, Evan Layton <[EMAIL PROTECTED]> >>>> wrote: >>>>> >>>>> Aubrey Li wrote: >>>>>> >>>>>> On Thu, Dec 4, 2008 at 12:43 PM, A. Stecker <[EMAIL PROTECTED]> wrote: >>>>>>> >>>>>>> some time ago i got the following answer to a similar (or maybe even >>>>>>> the >>>>>>> same) problem. haven't tried myself yet. >>>>>> >>>>>> I'm doing exactly what the following suggested, which is sort of >>>>>> unreasonable. >>>>>> Can we treat /opt the same way as /export/home? >>>>> >>>>> Not really since /opt is part of the BE since it can contain system >>>>> data >>>>> and >>>>> /export/home is shared between BE's since it does not and should not >>>>> contain >>>>> system data. >>>>> >>>> I failed to understand why it's necessary to make /opt being a part of >>>> the >>>> BE. >>> >>> Because traditionally, /opt is the location for add-on software packages >>> such as openoffice and so on, and thus needs to be able to be managed? >>> >> >> Why is openoffice taken as a part of BOOT Environment? >> when we update the system or create a new BE, it is not there, is it? > > I'll put this more simply; packages get installed into /opt. Therefore, the > package system needs to manage that as part of the "BOOT Environment". Boot > environment is more than just what is required to "BOOT" the system. >
Actually the problem is gone if doing a fresh installation but remains if the system is upgraded from 0805. The manual mountpoint setting should fix it. I just wonder, if /opt is one part of BE, then why not treat it the same as the others folders in BE. -Aubrey _______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
