>> You can't do that with zones as they stand now. There's a whole list of
>> things you can't do in a non-global zone. So you'd have to pick one
>> environment for the global zone (which can do everything you want), and
>> then one for another zone (which can't do a number of things).
>
>The topic under discussion is giving the user two experiences to
>choose from. Only one experience
>would ever be used at a time, so if zones were used to do this,
>non-global zones wouldn't even fac tor in. You'd just let users
>choose between two global zones. (whether or not the plumbing is the
>re to easily allow that is another question :))
The mechanism may be too heavy weight and/or too limiting.
If a cheaper mechanism is possible which allows for everything to happy
in any zone, then that would be preferrable.
To me, it's not completely a given that this is all required.
I think an inventory is needed of what it is that makes "Solaris"
feel "uncomfortable" to Linux users.
Then we can see what is easy to fix and what is not; and then when we
have the list of things we can find a way to solve all problems.
As I see it, there are several categories:
- missing utilities (functionality, command line options,
...)
- no brainer: just add them/it
- differences in behaviour:
- backspace/delete : unfortunate mistakes made with the
introduction of the IBM PC are hard to rectify but
the observed differences is mostly due to the fact
that command line editing is not on by default
- history up/down (see above)
- command output differences (df vs df -k)
- several solutions proposed
- difference of the order awk/gawk
- PATH?
I don't think it goes much deeper than that.
The reason I may prefer PATH over other solutions is that
scripts when written correctly will set $PATH at the start and
setting PATH will cause them to be correct.
Environment variables or other magic "execution environment" settings
all suffer from the same problem: it is difficult to conceive of a
solution which will cause already running scripts to continue to work.
Casper
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
