On Fri, Jan 16, 2009 at 2:14 AM, Paul Gress <[email protected]> wrote: > Michael Schuster wrote: >> >> it's the people who aren't in these communities that we want to convince, >> and - or so I understand - giving them something (a lot of) them are >> familiar with (even if it's "inferiour" to what many of "us" know) was seen >> as a valid step in that direction. > > I've been reading this thread for a while now. Some of my thoughts are > why can't you deliver both. In the install, just ask which > personality/flavor you want "solaris classic or gnu". It's just a > simple PATH variable to have it. If you really want to get creative, > give a third choice, a mix to your liking, just link which binaries are > chosen to a different directory, then put that directory first in the > PATH variable. If you keep a text file of these links any future > updates can read this and accommodate the new personality. One could > even create a gui configuration to map out the personality that future > updates can read.
A better, though far more time consuming, solution to my mind would be to do something like what you find in AIX. In AIX, for most common utils, you have both the SysV and BSD behavior available based on the command line flags requested. For example, 'ps -ef' and 'ps aux' both work as expected. The '-' determines which behavior you get. fpsm _______________________________________________ opensolaris-discuss mailing list [email protected]
