You may have inferred from my other thread(Console not sending cr on
Linux), that I did get a service running, but it was not on the plug.
It was on a "PC Engines Alix-1c" http://www.pcengines.ch/alix1c.htm
with 256MB, and an internal 2GB Compact Flash drive.
That was the backup platform waiting in the wings in case I had problems
with the plug. I already had a bootable thumbdrive with the 9.10 ubuntu
on it. Installed the Ubuntu CLI, Open JDK headless JRE and Karaf in a
very straight forward way.
BTW - what is the best practice for installing a Karaf that will be used
as a service - as root or as it's own user?
Project timelines forced that alternative for now, perhaps around the
time you get your plug I can rejoin the attack on putting up a decent
plug platform for karaf? The key I think is bootable tumbdrive with a
fast booting slim os.
cheers,
John
Chris Custine wrote:
This is really good info John. Should save me some time when I
finally get mine. I ordered the ProSyst card as well but I would like
to see all of the open source projects running well also. When I get
mine up and running we should compare notes and I will create some
docs on the wiki. If you come up with anything else that needs to be
documented or addressed fell free to reply to this thread or start a
new one.
Thanks,
Chris
--
Chris Custine
FUSESource :: http://fusesource.com
My Blog :: http://blog.organicelement.com
Apache ServiceMix :: http://servicemix.apache.org
Apache Felix :: http://felix.apache.org
Apache Directory Server :: http://directory.apache.org
On Thu, Dec 24, 2009 at 12:45 PM, John E. Conlon <[email protected]
<mailto:[email protected]>> wrote:
Hi Chris,
See inline comments...
Chris Custine wrote:
The service wrapper doesn't have a libwrapper.so compiled for
Arm so this
isn't going to work at the moment.
Suspected so. Yesterday was a plunge ahead and temporarily ignore
reality kind of day.
I have been developing my bundles (based on OSGi WireAdmin/Config
Admin services ) and have been testing them on a Karaf working in
an 256M Ubuntu CLI based virtualbox vm running on my intel dev
machine. Karaf is very cool and easy to work with and the docs
are straightforward and to the point. But now I need to move the
virtual to the real world. I hope to do it on the plug, but if I
encounter too much friction I can always go with a small intel
based box as well.
I have a SheevaPlug coming next week so
I will certainly be doing something about this, but in the
mean time if you
want to use the service wrapper you will have to get the
native source for
Tanuki Service Wrapper 3.2.3 and set up a cross compiler for
Arm on a Linux
machine.
Time permitting I may look into this. Thanks for the tip.
I know the Service Wrapper works well and there are a lot of
features, but is it possible to just start Karaf in the background?
I'll try to add this to Karaf some time in the next month or two.
That would be very good.
Just out of curiosity, other than the service wrapper is
everything else
running OK?
So so...
The os shipping on the plug is somewhat of a hodgepodge and needs
some holes patched up to make it more usable.
See:
http://plugcomputer.org/plugwiki/index.php/New_Plugger_How_To
Even with the patches the plug is very slow to boot and starting
Karaf (until the prompt) takes around 25 seconds!
See also the intro of:
http://crichton.homelinux.org/~marc/eib_sheeva.html
<http://crichton.homelinux.org/%7Emarc/eib_sheeva.html>
My experiences, and the comments from the above blog writer, make
me think that a clean OS install is the way to go.
Also, are you running this on the ProSyst mBedded Server with
J9 or are you using Felix and have all of the Java bits
installed manually?
There is a long backlog for shipping the plug so our earlier
prototyping was done on the sister product to the plug the OpenRD
client. (A plug mother board with lots of I/O options.) Then I
used J9 and ProSyst mBedded Server. (As you probably already know
the ProSyst dev kit is available as a buying option along with the
plug. Price is ~$39. But the ProSyst run times are evaluation only.)
But for Java, I prefer to work in SE JVMs and found the J9
Foundation Profile too constraining. Although ProSyst marketing
and support were helpful, here too I prefer to work with a larger
community based OpenSource OSGi framework like Felix or Equinox.
As for now the Java on the Plug is an OpenJDK headless JRE. I
simply (after all the fixes noted above) installed a headless JRE
on the plug with a:
apt-get update openjdk-6-jre-headless
command.
happy holidays,
John
Thanks,
Chris
--
Chris Custine
FUSESource :: http://fusesource.com
My Blog :: http://blog.organicelement.com
Apache ServiceMix :: http://servicemix.apache.org
Apache Felix :: http://felix.apache.org
Apache Directory Server :: http://directory.apache.org
On Wed, Dec 23, 2009 at 7:01 PM, John E. Conlon
<[email protected] <mailto:[email protected]>>wrote:
Having problems running karaf as a service on a Sheeva Plug <
http://www.marvell.com/products/embedded_processors/developer/kirkwood/sheevaplug.jsp
.
# cat /etc/issue
Ubuntu jaunty (development branch) \n \l
# cat /etc/debian_version
5.0
# uname -a
Linux debian 2.6.22.18 #1 Thu Mar 19 14:46:22 IST 2009
armv5tejl GNU/Linux
After installing the wrapper feature
ka...@root> wrapper:install
Creating file:
/opt/felix/apache-felix-karaf-1.2.0/bin/karaf-wrapper
Creating file:
/opt/felix/apache-felix-karaf-1.2.0/bin/karaf-service
Creating file:
/opt/felix/apache-felix-karaf-1.2.0/etc/karaf-wrapper.conf
Creating file:
/opt/felix/apache-felix-karaf-1.2.0/lib/libwrapper.so
Creating file:
/opt/felix/apache-felix-karaf-1.2.0/lib/karaf-wrapper.jar
After linking
ln -s
/opt/felix/apache-felix-karaf-1.2.0/bin/karaf-service
/etc/init.d/
I am not able to start the service. Here is what I get...
jcon...@debian:/opt/felix/apache-felix-karaf-1.2.0$
bin/karaf-service
start
Starting karaf...
Killed
Any ideas or trouble shooting tips?
thanks,
John
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
<mailto:[email protected]>
For additional commands, e-mail:
[email protected]
<mailto:[email protected]>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
<mailto:[email protected]>
For additional commands, e-mail: [email protected]
<mailto:[email protected]>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
