To answer on some of your questions, one of the goals of Nexenta is to preserve compatibility with OpenSolaris as much as possible but at the same time to provide Debian-like environment for everything else. Things like dpkg/apt/debootsrap/debconf/deb* even Debian installer are our primary interest. We trying to not change OpenSolaris bits much, only what is needed. For instance, SUN_PERSONALITY feature is most powerful and interesting one but at the same time it does not introduces any incompatibilities. Or nexenta-pkgcmd SVR4 package manager wrapper on top of dpkg is another interesting development going on.
On Thu, 2007-07-19 at 19:38 -0700, Tim Spriggs wrote: > That's an interesting "can of worms" because in Debian I am used to > editing /etc/network/interfaces in order to statically configure a set > of network interfaces. In Solaris, I have to manage several files > (/etc/hostname.* /etc/hostname6.* /etc/hosts ...) in order to do the > same things. To take either route is going to make Nexenta > non-conformant to Solaris or Debian. > > I know there are curses configuration tools for linux style systems but > I've never felt the need to look around for one on Solaris systems. In a > sense, the Solaris style is easier to manage with scripts since you > basically have a file for each thing you want to accomplish. > > I think there are some basic questions that need to be answered like: > > 1) Does Nexenta prefer Solaris or Debian/Ubuntu compatibility when > conflicts like these arise? > I would imagine Solaris since the very base of the system is Solaris. > > 2) By core/networking does Nexenta plan on always using all of the bits > available from Sun or will pieces be gradually replaced by Debian > base-system code? > This has been partially answered about the init system in Solaris vs > Debian and Solaris services seem to have won out. > > 3) Ease of configuration is definitely a goal for Nexenta, what kind of > configuration tasks should the most amount of time be spent on? > ie: should tools be built to configure networking in ncurses or > should more time be spent on package configuration? > Personally, I configure the network using vi and the appropriate > /etc files and see no need of a change. Of course, I don't move my > servers around very often. > > Two more cents, > -Tim > > kingneutron wrote: > > --If focus is not going to be on GUI for a while, then it is essential to > > start upgrading the core components (that have ncurses interface) to have > > the same level of functionality as their GUI counterparts... Especially > > for things like network and other sys-config stuff. > > > > _______________________________________________ > gnusol-devel mailing list > [email protected] > http://lists.sonic.net/mailman/listinfo/gnusol-devel > -- Erast _______________________________________________ gnusol-devel mailing list [email protected] http://lists.sonic.net/mailman/listinfo/gnusol-devel
