Monday, September 25, 2006

Java Studio Creator on dyne:bolic (Intel EM64T processor)

Dyne:bolic is a Linux based completely free OS that has been optimzed for media editing and production. As media editing is one of my hobbies, I chanced upon it (I guess thru Stumble) and now its the third OS on my comp. Guess this should suffice for an introduction...

Coming to the point, I read on its site that a toned down version of GUI environment (was pretty amazed at first, considering it was meant for producing graphics!) was provided so that the application can get a huge chunk of processor instead of the normal GUI environment hogging the processor and RAM. Considering this architecture, isn't it the best thing to run various development environments?? I ran Java Studio Creator on it and had an excellent experience. It was notably faster than my previous experiences (ubuntu i586 comes second, kubuntu amd64, WinXP, all on 512 MB DDR2 RAM, Intel 630 3.00 Ghz, Intel 915GEV motherboard). I could not test it fully coz installing modules (what packages are refered to in it dyne:bolic) is not a child's play. Sun JSC installed but quit once the installation of server commenced, coz some libs were missing... So I tested whatever I had on my hands - i.e. SJSC update 1 with a very light load (a prj with just 3 pages), without any DB support or a server running...

The good part about this combo is- if u've already installed it on some other OS (Linux) on your machine, u dont need to install it for dyne. Just run the creator script in <SJSC's installation directory>/bin and it would run for u. Haven't gone any further in this direction coz I have already tried quite a lot of of combos and need to get back to my project...

This was in response to some posts on Sun's forum which said SJSC ran best on Ubuntu. Yeah its good on it, but its better on dyne:bolic. (testing on the two was done on same load/project)

- Dev | September 25, 2006

Sunday, September 17, 2006

Client Side Encryption

My project deals with managing information of my college, so i do feel the need the of sending the data from client side in encrypted form. I had a small discussion on this topic here.

Now I am thinking of making up a small server that encrypts all the data it has to send to my server while it sends rest of the data as it is to its default destination. Guess it can be implemeted in Java, but I am devoid of any programming experience in that language.

Hows the idea? any comments??

BTW I am a student and dont have finances to go in for a SSL certificate, thats why all these efforts to come up with a new idea.

Thursday, September 14, 2006

Kubuntu - KDE - Unable to log in and work around

PROBLEM DESCRIPTION:
While playing around with my Kubuntu installation, I stopped some services thinking that will make my system's startup faster... but what happened was - the boot process completed successfully and showed me GUI login screen. When I entered the username and password, the screen went blank for a few seconds and then the login screen appeared again.

DIAGNOSIS:
Just to see what was going on, I shifted to console based login. Upon entering the username and password there, the screen was flooded with the following message
-bash: /dev/null - Permission denied

WORKAROUND:
A simple
sudo chmod a+rw /dev/null
and then
startx
started everything normally.

IT AINT OVER YET:
Upon restarting the system, the same problem reappeared indicating that the permissions had been reset.

WORKAROUND:
chmod a+rw /dev/null was added to /etc/rc.local before
exit 0 (which was already written in the file)

DEEPER DIAGNOSIS:
I called one of my friends, a Red Hat certified professional. He explained me all the fundas of runlevels and how things are done in Red Hat. As a part of diagnosis, we shifted to runlevel 5 (current workaround i am using) and everything was working fine. A comparison of services didnt yield much as we found out that udev and MAKEDEV were present in both the levels, which according to us were responsible for dealing with permissions/creation of /etc/null.

I BELIEVE ITS JUST A QUICK FIX THING THAT WE HAVE DONE AND IT IS NOT A PROPER SOLUTION, THEREFORE I HAVE USED WORKAROUND AND NOT SOLUTION EVERYWHERE IN THIS POST. IF ANYONE COMES UP WITH A SOLUTION, THEN PLEASE POST IT IN COMMENTS. THANKS

FINAL WORKAROUND I AM USING:
Shifting to runlevel 5 by editing /etc/inittab -

Original /etc/inittab (first 4 lines only)

# /etc/inittab: init(8) configuration.
# $Id: inittab,v 1.91 2002/01/25 13:35:21 miquels Exp $

# The default runlevel.
id:2:initdefault:

Modified /etc/inittab

# /etc/inittab: init(8) configuration.
# $Id: inittab,v 1.91 2002/01/25 13:35:21 miquels Exp $

# The default runlevel.
id:5:initdefault:

This workaround didnt require editing rc.local.

Regards,
Dev

Wednesday, September 06, 2006

Sun Java Studio Creator on Kubuntu amd64

On my dist (Kubuntu (debian based linux) 6.06 LTS x86_64), JSC quit installation process saying i didnt have compat-libstdc++ and compat-libstdc++-devel rpms installed... It then only installed JSC and reached the end of the installation process. But then, just for the heck of it, I downloaded Sun Java App Server PE 8 update 2. Amazingly, it installed without posing any difficulties!! I was unable to resolve the error (no rpms) coz i have a debian based dist and was unable to find out what libstdc++ it was compiled against, or what exactly is the function of compat-libstdc++ besides providing the compatibility, or how can it be simulated.

I have ubuntu x86 (32 bit edition) installed in my college's lab and there everything worked as a breeze i.e. the compelete JSC alongwith the server was installed without any issues at all...
So what i thought was: I change my installtion's (amd64) config files to match those of x86 installation. Unfotunately, I was unable to locate which config file can make the difference. If any one has any ideas, then **please** share them. Until then, I am deploying the war archive again and again for testing.

BTW I was unable to install Oracle 9ir2 on amd64/x86, so i have switched to latest MySQL with their latest (5.0.3) connectorJ drivers. They work on x86/amd64 installation.