On Mon, 2007-07-02 at 19:04 +0100, Peter Tribble wrote:
>> On 7/2/07, Tim Foster <[EMAIL PROTECTED]> wrote:
> > [EMAIL PROTECTED] top
> > The command "top" has is unavailable or has different
> > syntax in OpenSolaris.
> > You might want to use the following instead -
> > Example: prstat 1
> I regard the aim as being to provide a useful and user-friendly
> environment, not to explicitly advertise to the user how
> deficient and user-hostile Solaris is.
Okay, what's the alternative ? Given < 6 months, should we
a) have a mechanism similar to the above
b) leave users completely in the dark
c) something else ?
I'd vote for a) or c) but I'm all ears ?
> Fixing this doesn't break compatibility. It enhances the
> environment for everyone. And it's not about Linux or
> whatever - I've been typing 'ps uax' and 'top' since
> well before Linux existed.
You are running a different operating system - I believe that if they
appear different to the end user, that's okay so long as it's easy for
them to get back on their feet.
I'm happy on Mac machines and Solaris boxes switching my brain between
aux and -ef and have been so for ages now, likewise other commands that
behave differently.
Putting on my "let's try to solve the problem, rather than just talk
about it" hat[1], what's the status of top or /usr/ucb/ps in terms of
providing accurate, timely information about Solaris these days ? Is
v3.6 the most recent ?
Would a directory of symlinks put in the right place in your $PATH solve
this problem for most commands for you ?
Now, back to zones stuff:
Following up on Moinak's suggestion of setting $DISPLAY when when
starting an Xsession to ssh into a running zone, I seem to be running
into some probems. I started a failsafe session in the global zone,
xhosted-in the local zone, and tried to start a gnome-session but it
quickly crashed on me:
$ xhost 10.0.0.2+
access control disabled, clients can connect from any host
$ ssh 10.0.0.2 env DISPLAY=10.0.0.1:0 /usr/bin/gnome-session
X_mkdir: Not owner
X_mkdir: Not owner
SESSION_MANAGER=local/usuki-zone:/tmp/.ICE-unix/102204,inet6/usuki-zone:51970,inet/usuki-zone:62087
process 102218: D-Bus library appears to be incorrectly set up; failed
to read machine uuid: Failed to open "/var/lib/dbus/machine-
id": No such file or directory
See the manual page for dbus-uuidgen to correct this issue.
D-Bus not built with -rdynamic so unable to print a backtrace
Cannot locate dbus-daemon
process 102204: D-Bus library appears to be incorrectly set up; failed
to read machine uuid: Failed to open "/var/lib/dbus/machine-
id": No such file or directory
See the manual page for dbus-uuidgen to correct this issue.
D-Bus not built with -rdynamic so unable to print a backtrace
$ ^C
Now, digging a bit, I see that dbus-daemons can't be run in non-local
zones. Hum. Has anyone else got this sort of thing to work in the past ?
Fintanr reminded me that the Trusted Extensions guys have exactly this
sort of model in their implementation of a labelled windowing
environment, so it's got to work somehow...
Any ideas ?
cheers,
tim
[1] all too bloody prevalent on this alias imho
--
Tim Foster, Sun Microsystems Inc, Solaris Engineering Ops
http://blogs.sun.com/timf
_______________________________________________
indiana-discuss mailing list
[email protected]
http://opensolaris.org/mailman/listinfo/indiana-discuss
