Solaris / OpenSolarisThis forum is for the discussion of Solaris and OpenSolaris.
General Sun, SunOS and Sparc related questions also go here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Location: Hendrik Ido Ambacht, Zuid-Holland, Nederland, Europa
Distribution: Sun Solaris-Exp-Dev-Edit, Ubuntu 9.10 Karmic Koala AMD64
Posts: 134
Original Poster
Rep:
I got opera browser (9.22) running on Sun Solaris (11/06)
I used some valuable information from BlastWave "HOWTO Use Blastwave".
After installing the PKG-GET (+ KDE and GNOME), these steps made it avalable to install Opera:
Code:
Don't do that unless you have Solaris 10
What I do recommend is that you change the root users home directory location to /root and nothing more fancy than that.
You can edit the /etc/passwd file and change the entry for the root user thus :
root:x:0:1:Super-User:/root:/sbin/sh
Be very diligent about creating the root users home directory right away and ensure that it is only readable by the root
user :
# mkdir /root
# chmod 700 /root
# chown root:root /root
Also, you may be wondering why you should not change the root users default shell to bash.
Simply put, any other shell than /sbin/sh will be a dynamically linked executable with dependencies.
If you were to check /sbin/sh you would find that it is a standalone program :
$ ldd /sbin/sh
ldd: /sbin/sh: file is not a dynamic executable or shared object
That means that your machine can suffer some horrible disaster and still be able to function in single user mode if you
can boot the kernel and get to a running shell with the root user. That is becuase the root user only needs /sbin/sh to
have a fully functional shell. If you were to use bash or any other shell then you would need a stack of dependencies.
Those dependencies may not exist if they are on some other file system or on a damaged file system.
The first advice is controversial. The consensus is never log in as root but either su to it or user RBAC.
You are strongly discouraged to use any browser or similar application as root.
The first advice is controversial. The consensus is never log in as root but either su to it or user RBAC.
You are strongly discouraged to use any browser or similar application as root.
The second advice doesn't apply to Solaris 10.
I think the first advice, is valid upon newly installing Solaris? Because only root account exists, and the advice states that when root logs in, he will end up in "/" and there will .profile files etc sprinkled all over the top directory. Therefore, as quick as possible, log in via command line and create a /root directory, which is root's home.
I think the first advice, is valid upon newly installing Solaris? Because only root account exists, and the advice states that when root logs in, he will end up in "/" and there will .profile files etc sprinkled all over the top directory. Therefore, as quick as possible, log in via command line and create a /root directory, which is root's home.
If I understood the advice correctly?
That isn't my advice. Never log in as root, unless there is no other choice obviously. After installation, log in in console mode, not graphical, and create a regular user account. log-out and never login again as root.
Use the user login acount just created and switch to root (su) only and only when necessary. Promptly leave the su shell when done.
Using a graphic environment or a browser as root is defeating Unix security model.
If there are commands you often need to run that require specific privileges, use RBAC/pfexec.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.