I know what you meant :-) I suggested the command-not-found solution more as a practical addition to such a faq. I remember trying some typical Linux commands as top and sudo on Solaris only to find out I should use prstat and pfexec.
On Wed, May 21, 2008 at 3:23 PM, Bryan Boone <[EMAIL PROTECTED]> wrote: > I mean to admin the box... > Like svccfg vs editing a configuration file. > I performed the steps (previously mentioned) in svccfg to allow tcp > listening; rebooted Solaris; opened a terminal and performed xhost +; logged > into the login server and still didn't get an xwindow back. > In Linux, I edit a file; restart x. > -Bryan > > Niels Van Hee wrote: >>> >>> This is where Linux admin and Solaris admin diverge.... >>> Maybe there should be a faq for linux users migrating to Solaris. >> >> It might be interesting to have a look at Ubuntu's command-not-found >> package (http://packages.ubuntu.com/hardy/command-not-found). In a >> nutshell, this handler informs you of what package you should install >> if you attempt to use a program that hasn't been installed yet. This >> could be adapted to present the user with the Solaris equivalent of a >> Linux command (use pfexec instead of sudo, an alternative for >> ifconfig,...). >> >> >> Best regards, >> -- >> Niels Van Hee >> > -- Niels Van Hee _______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
