Hi I guess setting start/exec for the service:instance in question to a startup script other than say fs-user would do ( just in the miniroot repository ), but again this is messy I guess.
Enda "??????? ??????.???.?? =?UTF-8?Q?=E0=B3=8D(Narendra_Kumar.S.S, ssnkumar at gmail.com" wrote: > So, what is the final decision here? > What I could understand from the previous discussions is that, miniroot > is going to change in the future. > So, are we giving some solutions to customer, who already have hit this > problem? > Will this solution come as a patch or permanent fix or a workaround? > > And regarding the fix, I have one suggestion (which actually Dave Miner > also suggested sometime back). > Take the case of fs-usr, which is delivered by both SUNWsibi and SUNWcsr. > Both are having different contents. > Now, add code to this fs-usr to sense where it is executing. > If it is in miniroot, just exit. > Else, continue. > > But, how to sense where it is executing? > Is there any environment variable or command to know that, it is > executing in miniroot? > > We can do this for all those scripts which are part of miniroot and also > delivered by some other package (with different content). > And this could be a long term fix, till the time miniroot is redisigned. > > -Narendra > > > On 10/6/06, *Angela Byrne - Solaris Sustaining* <angela.byrne at sun.com > <mailto:angela.byrne at sun.com>> wrote: > > Channing also has a concern here:- > > 119081-28 SunOS 5.10: CD-ROM Install Boot Image Patch > > 119081-28 cannot install until 118855-28 is installed. > > 119081-28 REQUIRES 122539-06 and the only way to satisfy this > is for a customer to install 118855-28. > > This is due to 118855-28 obsoleting 122539-06 and 122539-06 > itself cannot be released and is marked as BAD. > > I will let Channing comment further. > > Angela > > > > Casper.Dik at Sun.COM <mailto:Casper.Dik at Sun.COM> wrote: > >> I was wondering if there are any other reasons customers patch the > >> miniroot besides driver updates. Obviously they get other > updates with > >> the patches they are using, but I believe in general it is used for > >> device updates, correct? If so, does the ITU process that we offer > >> during install not suffice for this? In particular if this > feature was > >> enhanced to be more usable and more automated and could find drivers > >> without user intervention? > > > > It's not that simple; with all the new PCI/PCI-express support and > > bugs fixes in that area (Such as the HP hang, etc), customers > generally > > need to install the main kernel patches in the miniroot. > > > > And if the kernel jumbo patch needs to go in, well, that pretty much > > settles it and arguing over whether all or some patches are > needed is > > then purely acedemic. > > > > Casper > > > _______________________________________________ > install-discuss mailing list > install-discuss at opensolaris.org <mailto:install-discuss at > opensolaris.org> > http://opensolaris.org/mailman/listinfo/install-discuss > > > > > -- > Warm Regards, > ??????? ??????.???.??? > (S.S.Narendra Kumar) > > Visit my blogs at: > http://ssnarendrakumar.blogspot.com/ > http://blogs.sun.com/roller/page/ssnkumar > <http://blogs.sun.com/roller/page/ssnkumar> > ___ ___ __ _ > / __/ / __/ / | / / > _\ \ _ \ \ / /| |/ / > \___/ \___/ /_/ |__/ > > > ------------------------------------------------------------------------ > > _______________________________________________ > install-discuss mailing list > install-discuss at opensolaris.org > http://opensolaris.org/mailman/listinfo/install-discuss
