That's fine, we can leave it out. Originally I thought yast2 may be needed in the image due to the various yast2- scripts, but perhaps not.
Cheers, Bernard > -----Original Message----- > From: Erich Focht [mailto:[EMAIL PROTECTED] > Sent: Tuesday, June 20, 2006 2:44 > To: Bernard Li > Cc: [email protected] > Subject: Re: [Oscar-devel] SUSE Linux 10.0 support status > > On Tuesday 20 June 2006 10:15, Bernard Li wrote: > > > I plan to add "yast2" to the rpmlist, would anybody object to that? > > Actually I wonder if the various yast2- RPMs are actually > needed in the > > image...?? > > On the master: yes. On the client: better leave it away. Can > you please > explain why you want it? I currently can't imagine using it > on a cluster > node. > > Nobody should actually manage their cluster clients by > invoking a graphical > user interface on each of them, this just leads to getting them out of > sync. In order to be scalable things need to be done on the > master and in the > image. > > If people want to manage their data-center with OSCAR, then > they'll certainly > use other rpmlists than the default cluster rpmlists we > provide. And be able > to add yast2 if they need it. > > Regards, > Erich > _______________________________________________ Oscar-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-devel
