Installation instructions for Enlightenment for Solaris
It's time to kiss CDE and OpenWindows goodbye. Soon you'll have a
nice looking and much more functional enviroment to work with. E
is less cluttered than any other window manager (including CDE, GNOME and KDE),
and it is very very flexable. As a developer or system administrator (me)
you'll find life much more enjoyable with Enlightenment.
To get started, you first need to download and install the base packages.
Use the following steps:
Procedure for installing Enlightenment and its componants:
- First download all the packages listed under "Enlightenment Packages for Solaris" on my downloads page.
- Next, ensure that previous GTK+, GLIB, IMLIB, etc packages are not installed in /usr/local. If you do, please remove them. In a default install of Solaris a /usr/local won't even exist, so you are ready to proceed.
- Uncompress the packages if neccisary using: uncompress CDLTKpackage.pkg.Z
- Now install each of the packages one-by-one using the following method: pkgadd -d ./CDLTKpackage.pkg
- If a package is said to be corrupt, there was probly a problem in the download, delete it and redownload it.
- You must now modify your Borne shell startup script ($HOME/.profile) to include the following lines:
- Once all the packages are installed you can proceed to the following methods for starting it. And when done, you can add in the extra programs that cuddletech provides. (Such as XMMS, GIMP, Eterm, etc)
Now you should have E installed, you can choose from the following methods to start Enlightenment, but USE ONLY ONE.
Procedure for starting Enlightenment WITHOUT modifing CDE/DTLogin:
- In your home directory, add the file .xinitrc, and add the following line:
xset fp+ $HOME/fonts
xset fp rehash
- Save this file and make it executable (chmod 755 .xinitrc)
- Double check to make sure your .profile looks like the one listed earlier, or at least that LD_LIBRARY_PATH includes /usr/local/lib, and PATH includes /usr/local/bin
- Make sure that your default shell is the BORNE shell. CDE's scripts will FAIL if you are not running Borne.
- Now, return to DTLogin on the machine that you've done this and log in, but specify "OpenWindows" as the session choice.
- If all went well, Enlightenment will start after you see the Solaris screen.
The above procedure works because when you start an OpenWindows session with DTLogin, the scripts will first look to see if you have
a .xinitrc in your home directory. If you do it proccess it instead of starting OpenWindows. In the above case, it would start E.
This procedure is useful in two cases: 1) You don't want to modify any more than you absolutely must, or 2) You are mounting /usr/local
and your home directory via NFS and you want E to start on any machine where both are mounted.
The method that follows will actually add Enlightenment as a DTLogin session option, however it does mean adding scripts to your system.
Use these methods exactly as noted and nothing else. If you tinker with scripts in /usr/dt/config and end up messing up CDE, then don't
look at me. Also, let me point out that the "Borne Shell Only" restriction from the earlier proccedure, does not apply to the following.
Procedure for adding Enlightenment to the Session options in dtlogin:
- Add the following file: /usr/dt/config/C/Xresources.d/Xresources.e
- Add the following file: /usr/dt/config/Xsession.e
- Add the following file: /usr/dt/config/Xinitrc.e
- Now install the following 2 images to the /usr/dt/appconfig/icons/C directory: Elogo.bm and Elogo.pm
- Now change the permissions of /usr/dt/config/Xsession.e to 555, ala "chmod 555 /usr/dt/config/Xsession.e"
- Next, verify that you don't have a .xinitrc in your home directory.
- Now go back to the dtlogin screen, and select the "Reset Login Screen" from the options pull down.
- Your done!
There is one more way to start E that I'll mention, which is very useful for debuging purposes. If E won't start properly on your system, use
the following method to determine why:
Procedure for starting Enlightenment for debuging purposes:
- At the dtlogin login screen, enter your login.
- Before entering your password choose "Failsafe" from the Session Options menu.
- Enter your password and login.
- You will see only X and a terminal, with no window manager.
- Double check your important variables (echo $LD_LIBRARY_PATH; echo $PATH). If they are not set properly, then fix your .profile.
- Now start Enlightenment manually by typing: /usr/local/enlightenment/bin/enlightenment
- Enlightenment should start. If it does not then use the messages you'll see in the terminal to determine why.
Important Notes pertaining to Enlightenment on Solaris/SPARC:
- When Enlightenment starts, it is normal for the color to be messed up. When the "screens part",
the color will look correct. This is due to less that amazing Sun video cards and bad color management by X.
- Avoid color heavy applications like GIMP and Mozilla when on 8bit video cards (SparcStation users), the cards
just can't handle the colors and your desktop will get really ugly really quick.
- You can make Solaris even kooler by using TrueType fonts. Learn more in my tutorial.
- If you haven't ever tuned your video cards, this is probly the time to do it. There is a document entitled: "Working with Sun Video Cards"
on my downloads page. This is Sun InfoDoc #10761, which outlines how to tune your video cards.
The most important step is to get out of 8bit color and get running in 24bit mode. Please refer to this document.
- VERY VERY IMPORTANT: Don't complain about Enlightenments performance till you do this! Enlightenment DR16's pager
has some very very neat functions. One of them is called "Snapshoting". This feature will shred your performance on most systems. SPARC processors just don't like this repedative motion, so turn if off immediately. If you continue to run a little slow, try disabling it completely, and then work backwards turning functions on. By right clicking on the pager you can access its properties and turn snapshoting on and off.
- Notes about using Eterm with Solaris Systems: There are some tricks to getting Eterm to work the way most SAs would like, which require rebuilding Eterm. To fix the problem with the scrollback (long line breaks when you scroll back through the term) you should edit the Eterm source file "features.h" and change the refresh_period from 4 to 1, this will make scrollback slower (i see no diffrence) but more reliable. To fix the backspace/delete key issues on Solaris systems (ie: you press BS and get "^H" instead) you should use the configure options: --with-delete="del" --with-backspace="auto". For some reason these backspace issues crop up in the Borne Shell and not BASH, but when logging into lots of systems each day it gets old really fast, this will solve it. These changes will be made to the next update of the CDLTKeterm pkg for Solaris.
- Notes about color issues in E: Some people experience problems with colors when using the CDLTK pkgs, for a variety of reasons. If this problem affects you you should edit the file "/usr/local/etc/imrc". You'll need to modify the lines "Mit-Shm" and "SharedPixmaps", change both values from "on" to "off", then quit and restart E completely. This issue is also seen by shared memory errors on the effected system... I know you want to be hardc0r3 and simply adjust shared memory settings on your system till it works, but I have not meet anyone who has changed shm settings and made this problem go away, so don't waste your time. This change will be default in the next release of CDLTKimlib.
DTlogin Enlightenment Logo's (PM)
Below are several alternate PM's that you could use for your DTlogin screen, simply rename the chosen file to Elogo.pm and place it as mentioned above.
|Ben Rockwood (email@example.com)
|cuddletech: use unix or die.