You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by chago <na...@visualxs.com> on 2007/11/12 03:59:09 UTC
Re: [ApacheDS] In preparation for 1.0.1 release: candidates
available
Wow, still no way to install this thing on a linux box that doesn't have X11
installed?
Forget about a Solaris installer, or at least prioritize a simple tarball
before it. I'm on Ubuntu PPC and I can't find instructions on how to
install. Really quite frustrating considering all the easy install programs
available, but no simple manual install instructions.
thanks.
Alex Karasulu wrote:
>
> Oh and btw the RPM and the windows executable are also available here:
>
> http://people.apache.org/~akarasulu/apacheds/candidates/1.0.1/apacheds-1.0.1-linux-i386.rpm
> http://people.apache.org/~akarasulu/apacheds/candidates/1.0.1/apacheds-1.0.1-win32-setup.exe
>
> Alex
>
> On 2/21/07, Alex Karasulu <ak...@apache.org> wrote:
>>
>> Yeah but you need a solaris machine with a display to generate the
>> installer script. Basically go through an install on that machine then
>> at
>> the end of the install there is a screen with a button that asks you if
>> you
>> want to create a unmanned installation file. Hit that button and
>> generate
>> the script. Then scp that script to the target headless machine. Then
>> install using the following command:
>>
>> java -jar apacheds-1.0.1-solaris-i386-setup.jar
>> path/to/the<installer-file-you-created>
>>
>> Sorry this issue is still around. I was hoping to have a solaris package
>> available but I have not had time to whip one together.
>>
>> HTH,
>> Alex
>>
>> On 2/21/07, Graham Leggett <mi...@sharp.fm> wrote:
>> >
>> > Alex Karasulu wrote:
>> >
>> > >
>> http://people.apache.org/~akarasulu/apacheds/candidates/1.0.1/apacheds-1.0.1-solaris-i386-setup.jar
>> >
>> >
>> <http://people.apache.org/%7Eakarasulu/apacheds/candidates/1.0.1/apacheds-1.0.1-solaris-i386-setup.jar>
>> >
>> > Is there a workaround for this:
>> >
>> > bash-3.00# java -jar apacheds-1.0.1-solaris-i386-setup.jar
>> > Java Accessibility Bridge for GNOME loaded.
>> >
>> > - Error -
>> > java.awt.HeadlessException:
>> > No X11 DISPLAY variable was set, but this program performed an
>> operation
>> >
>> > which requires it.
>> > java.awt.HeadlessException:
>> > No X11 DISPLAY variable was set, but this program performed an
>> operation
>> > which requires it.
>> > at
>> >
>> java.awt.GraphicsEnvironment.checkHeadless(GraphicsEnvironment.java:159)
>> > at java.awt.Window.<init>(Window.java:317)
>> > at java.awt.Frame.<init>(Frame.java:419)
>> > at
>> > net.sourceforge.mlf.metouia.borders.MetouiaDotsBuffer.<init>(
>> > MetouiaDotsBuffer.java :105)
>> > at
>> > net.sourceforge.mlf.metouia.borders.MetouiaDots.<init>(MetouiaDots.java
>> > :66)
>> > at
>> > net.sourceforge.mlf.metouia.borders.MetouiaToolBarBorder.<init>(
>> > MetouiaToolBarBorder.java:49)
>> > at
>> > net.sourceforge.mlf.metouia.MetouiaLookAndFeel.initComponentDefaults(
>> > MetouiaLookAndFeel.java:241)
>> > at
>> > javax.swing.plaf.basic.BasicLookAndFeel.getDefaults(
>> > BasicLookAndFeel.java:107)
>> > at
>> > javax.swing.plaf.metal.MetalLookAndFeel.getDefaults(
>> > MetalLookAndFeel.java:1392)
>> > at javax.swing.UIManager.setLookAndFeel(UIManager.java:441)
>> > at javax.swing.UIManager.setLookAndFeel(UIManager.java :481)
>> > at
>> > com.izforge.izpack.installer.GUIInstaller.loadLookAndFeel(
>> > GUIInstaller.java:346)
>> > at
>> > com.izforge.izpack.installer.GUIInstaller.<init>(GUIInstaller.java:111)
>> > at
>> > sun.reflect.NativeConstructorAccessorImpl.newInstance0 (Native Method)
>> > at
>> > sun.reflect.NativeConstructorAccessorImpl.newInstance(
>> > NativeConstructorAccessorImpl.java:39)
>> > at
>> > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(
>> > DelegatingConstructorAccessorImpl.java :27)
>> > at java.lang.reflect.Constructor.newInstance(Constructor.java
>> > :494)
>> > at java.lang.Class.newInstance0(Class.java:350)
>> > at java.lang.Class.newInstance(Class.java:303)
>> > at com.izforge.izpack.installer.Installer.main (Installer.java
>> > :62)
>> >
>> >
>> > Regards,
>> > Graham
>> > --
>> >
>> >
>>
>
>
--
View this message in context: http://www.nabble.com/-ApacheDS--In-preparation-for-1.0.1-release%3A-candidates-available-tf3268468.html#a13699015
Sent from the Apache Directory Project mailing list archive at Nabble.com.
Re: [ApacheDS] In preparation for 1.0.1 release: candidates
available
Posted by chago <na...@visualxs.com>.
The user forum for Ubuntu on PPC can be found here:
http://ubuntuforums.org/forumdisplay.php?f=133
The downloads of Fiesty Fawn can be found here (desktop/server)
http://cdimage.ubuntu.com/ports/releases/feisty/release/
Gutsy is here:
http://cdimage.ubuntu.com/ports/releases/gutsy/release/
Torrents are also available.
-- jim
Alex Karasulu wrote:
>
>> > FWIW, the i386 rpm seems to work OK on my PPC architecture.
>
> Cool. I have a PPC MacBookPro which I intend to install Linux on here
> shortly and expose to the team so we can better test this
> architecture. I was going to install Fedora or CentOS on it. However
> is there a Ubuntu distro for PPC? Can't seem to find one. Looks like
> there's only one for SPARC.
>
--
View this message in context: http://www.nabble.com/-ApacheDS--In-preparation-for-1.0.1-release%3A-candidates-available-tf3268468.html#a13712244
Sent from the Apache Directory Project mailing list archive at Nabble.com.
Re: [ApacheDS] In preparation for 1.0.1 release: candidates available
Posted by Alex Karasulu <ak...@apache.org>.
On Nov 12, 2007 11:20 AM, Chris Custine <cc...@apache.org> wrote:
> > /var/lib/apacheds - Used for configuration and runtime data (partitions).
> > Also holds subdirectories for different configurations of apacheds. Comes
> > with a 'default' config. (Maybe /usr/local/apacheds/configs?)
>
> This directory is specified by the FHS specs ( http://www.pathname.com/fhs/
> ) and is used by many other programs that have data storage needs (MySQL,
> Postgres, etc.)
Thanks Chris this was a great move! We should adhere at a minimum to
the FHS specs.
> > So, you can see I don't know much about it, but I may know enough to get
> it
> > up and running although in a very manual manner. Assuming the init.d
> script
> > works on Ubuntu. The init.d script wants the name of an instance when
> > starting/stopping. How does it find this name parameter when the system is
> > starting up the server? It doesn't seem to default to anything...
>
> Yeah, this was an oversight and I think we are going to have to figure out a
> better way to do this in the next release. There are basically 2 options:
> we create a config that says which instances get started by default (so
> starting stopping the service starts/stops all named instances ), or we
> create a new init for each instance. I have seen it done both ways so
> suggestions are welcome.
I like the idea of having multiple init scripts for different
instances. This aligns with how services are represented in UNIX sort
of the way Oracle appends _instancename to the service name. If we
have a default, foo, and bar instance than we can have
apacheds_default, apacheds_foo, and apacheds_bar init scripts. Then
when using chkconfig and the service scripts you can just configure or
launch that as a separate service.
> > FWIW, the i386 rpm seems to work OK on my PPC architecture.
Cool. I have a PPC MacBookPro which I intend to install Linux on here
shortly and expose to the team so we can better test this
architecture. I was going to install Fedora or CentOS on it. However
is there a Ubuntu distro for PPC? Can't seem to find one. Looks like
there's only one for SPARC.
> Yes, with the Java installers, the platform id is largely irrelevant since
> Java has to be there seperately. So I guess we could just make copies for
> the other platforms in case we ever do a yum repo or any of the other distro
> repos.
A repo for both deb and rpm based variants would be great to have.
Alex
Re: [ApacheDS] In preparation for 1.0.1 release: candidates
available
Posted by chago <na...@visualxs.com>.
Hi Chris. So is the file located at /opt/apacheds-1.5.1/bin/apacheds a tanuki
warpper binary renamed to apacheds? If so, I didn't see a wrapper binary for
Ubuntu/ppc/32 at their website. If I did find such a wrapper binary, can I
just replace the current one?
I think I read that their wrapper binary has some hardcoded dependencies on
the /var/run directory. I moved my pid stuff to /var/lock.
I don't mean to question the use of the Tanuki library, but it sure is
complicating my life; at least on this somewhat obscure platform. It's just
that an old Mac notebook makes an excellent 1U server complete with battery
backup for a fraction of the cost of a "real" server. I'd love to get
apacheds working with it.
-- jim
Chris Custine-2 wrote:
>
> This was inherited from the Tanuki wrapper daemon and is basically a
> mechanism to launch the java program as a different user. This is a
> necessary hack since Java doesn't do setuid I didn't like a lot of that
> either, but the Tanuki wrapper works really well and has a lot of
> potential. Maybe we can make some improvements or suggestions to them.
>
--
View this message in context: http://www.nabble.com/-ApacheDS--In-preparation-for-1.0.1-release%3A-candidates-available-tf3268468.html#a13713470
Sent from the Apache Directory Project mailing list archive at Nabble.com.
Re: [ApacheDS] In preparation for 1.0.1 release: candidates
available
Posted by chago <na...@visualxs.com>.
Thank you for all that detail Chris. I manually installed the program onto my
Ubuntu PPC box and only changed the /opt/* directory to /usr/local/* and
/var/run to /var/lock. I followed the instructions generated by using the
alien program and the i386 RPM.
At this point, I believe I am running into a 386/ppc problem. When the start
script attempts to launch /usr/local/apacheds-1.5.1/bin/apacheds, I get:
: cannot execute binary file
At first I thought this may be a permission problem, but I ensured the
script was running under the correct user (apacheds) and the owner and group
permissions are set to this user. I assume the file is an i386 binary and
that is the problem. At this point, I suppose I should try invoking the java
program directly instead of depending on this launcher script?
-- jim
Chris Custine-2 wrote:
>
> On Nov 12, 2007 8:53 AM, chago <na...@visualxs.com> wrote:
>
>>
>> I know nearly nothing about linux, although I am running Ubuntu on my mac
>> TiBook (ppc).
>>
>> I installed alien which can install rpms and convert between many install
>> packages. I used it to generate a pre/post scripts and unpack the rpm
>> into
>> a
>> local directory. I can also use alien to install the rpm. Other than some
>> inappropriate (for ubuntu) directories, it seems like it would install
>> fine.
>>
>> I really don't have the skill to write an install script. I was baffled
>> by
>> a
>> lot of the /etc/init.d/apacheds file, especially the recursive launch of
>> the
>> script when run-as does not match current user. I'm not even sure what
>
>
> This was inherited from the Tanuki wrapper daemon and is basically a
> mechanism to launch the java program as a different user. This is a
> necessary hack since Java doesn't do setuid I didn't like a lot of that
> either, but the Tanuki wrapper works really well and has a lot of
> potential. Maybe we can make some improvements or suggestions to them.
>
>
>> directories are preferred when installing the different sections of the
>> code. For example, the current codebase works with these separate
>> directories...
>>
>> /etc/init.d - Used for apacheds start/stop script (same for ubuntu)
>> /etc/sysconfig - Used for specifying a couple directory paths (don't know
>> where ubuntu would want these. Seems like a waste of a folder for just
>> storing some "conf" data. I suppose they exist because they are conf data
>> for the server proper and not the server instance.)
>
>
> Exactly... this is just to have a place to set global env data before the
> rest of the script runs so that the admin doesn't have to edit the init
> script. This lets these customizations survive upgrades.
>
>
>> /var/lib/apacheds - Used for configuration and runtime data (partitions).
>> Also holds subdirectories for different configurations of apacheds. Comes
>> with a 'default' config. (Maybe /usr/local/apacheds/configs?)
>
>
> This directory is specified by the FHS specs (
> http://www.pathname.com/fhs/) and is used by many other programs that
> have data storage needs (MySQL,
> Postgres, etc.)
>
>
>> /var/run - Holds the pid apacheds is running on. (/var/lock in ubuntu)
>> /opt/apacheds-1.5.1 - Holds the implementation of the server, including
>> the
>> bin directory for launching. (not sure where this should go, maybe
>> /usr/local/apacheds-1.5.1?)
>
>
> This is again specified by FHS, but as long as the location is reflected
> in
> the init script, it can go anywhere.
>
>
>>
>>
>> So, you can see I don't know much about it, but I may know enough to get
>> it
>> up and running although in a very manual manner. Assuming the
>> init.dscript
>> works on Ubuntu. The init.d script wants the name of an instance when
>> starting/stopping. How does it find this name parameter when the system
>> is
>> starting up the server? It doesn't seem to default to anything...
>
>
> Yeah, this was an oversight and I think we are going to have to figure out
> a
> better way to do this in the next release. There are basically 2 options:
> we create a config that says which instances get started by default (so
> starting stopping the service starts/stops all named instances ), or we
> create a new init for each instance. I have seen it done both ways so
> suggestions are welcome.
>
>
>>
>>
>> FWIW, the i386 rpm seems to work OK on my PPC architecture.
>>
> Yes, with the Java installers, the platform id is largely irrelevant since
> Java has to be there seperately. So I guess we could just make copies for
> the other platforms in case we ever do a yum repo or any of the other
> distro
> repos.
>
> Thanks for the discussion. Like Alex said, any help in this area is
> welcome.
>
> Chris
>
>
>>
>> Alex Karasulu wrote:
>> >
>> > You're right. It's lame that we have all these GUI installers and no
>> > tarball. Someone has to
>> > scratch this itch. Wanna give it a try?
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/-ApacheDS--In-preparation-for-1.0.1-release%3A-candidates-available-tf3268468.html#a13708105
>> Sent from the Apache Directory Project mailing list archive at
>> Nabble.com.
>>
>>
>
>
--
View this message in context: http://www.nabble.com/-ApacheDS--In-preparation-for-1.0.1-release%3A-candidates-available-tf3268468.html#a13712005
Sent from the Apache Directory Project mailing list archive at Nabble.com.
Re: [ApacheDS] In preparation for 1.0.1 release: candidates available
Posted by Chris Custine <cc...@apache.org>.
On Nov 12, 2007 8:53 AM, chago <na...@visualxs.com> wrote:
>
> I know nearly nothing about linux, although I am running Ubuntu on my mac
> TiBook (ppc).
>
> I installed alien which can install rpms and convert between many install
> packages. I used it to generate a pre/post scripts and unpack the rpm into
> a
> local directory. I can also use alien to install the rpm. Other than some
> inappropriate (for ubuntu) directories, it seems like it would install
> fine.
>
> I really don't have the skill to write an install script. I was baffled by
> a
> lot of the /etc/init.d/apacheds file, especially the recursive launch of
> the
> script when run-as does not match current user. I'm not even sure what
This was inherited from the Tanuki wrapper daemon and is basically a
mechanism to launch the java program as a different user. This is a
necessary hack since Java doesn't do setuid I didn't like a lot of that
either, but the Tanuki wrapper works really well and has a lot of
potential. Maybe we can make some improvements or suggestions to them.
> directories are preferred when installing the different sections of the
> code. For example, the current codebase works with these separate
> directories...
>
> /etc/init.d - Used for apacheds start/stop script (same for ubuntu)
> /etc/sysconfig - Used for specifying a couple directory paths (don't know
> where ubuntu would want these. Seems like a waste of a folder for just
> storing some "conf" data. I suppose they exist because they are conf data
> for the server proper and not the server instance.)
Exactly... this is just to have a place to set global env data before the
rest of the script runs so that the admin doesn't have to edit the init
script. This lets these customizations survive upgrades.
> /var/lib/apacheds - Used for configuration and runtime data (partitions).
> Also holds subdirectories for different configurations of apacheds. Comes
> with a 'default' config. (Maybe /usr/local/apacheds/configs?)
This directory is specified by the FHS specs (
http://www.pathname.com/fhs/) and is used by many other programs that
have data storage needs (MySQL,
Postgres, etc.)
> /var/run - Holds the pid apacheds is running on. (/var/lock in ubuntu)
> /opt/apacheds-1.5.1 - Holds the implementation of the server, including
> the
> bin directory for launching. (not sure where this should go, maybe
> /usr/local/apacheds-1.5.1?)
This is again specified by FHS, but as long as the location is reflected in
the init script, it can go anywhere.
>
>
> So, you can see I don't know much about it, but I may know enough to get
> it
> up and running although in a very manual manner. Assuming the init.dscript
> works on Ubuntu. The init.d script wants the name of an instance when
> starting/stopping. How does it find this name parameter when the system is
> starting up the server? It doesn't seem to default to anything...
Yeah, this was an oversight and I think we are going to have to figure out a
better way to do this in the next release. There are basically 2 options:
we create a config that says which instances get started by default (so
starting stopping the service starts/stops all named instances ), or we
create a new init for each instance. I have seen it done both ways so
suggestions are welcome.
>
>
> FWIW, the i386 rpm seems to work OK on my PPC architecture.
>
Yes, with the Java installers, the platform id is largely irrelevant since
Java has to be there seperately. So I guess we could just make copies for
the other platforms in case we ever do a yum repo or any of the other distro
repos.
Thanks for the discussion. Like Alex said, any help in this area is
welcome.
Chris
>
> Alex Karasulu wrote:
> >
> > You're right. It's lame that we have all these GUI installers and no
> > tarball. Someone has to
> > scratch this itch. Wanna give it a try?
> >
>
> --
> View this message in context:
> http://www.nabble.com/-ApacheDS--In-preparation-for-1.0.1-release%3A-candidates-available-tf3268468.html#a13708105
> Sent from the Apache Directory Project mailing list archive at Nabble.com.
>
>
Re: [ApacheDS] In preparation for 1.0.1 release: candidates
available
Posted by chago <na...@visualxs.com>.
I know nearly nothing about linux, although I am running Ubuntu on my mac
TiBook (ppc).
I installed alien which can install rpms and convert between many install
packages. I used it to generate a pre/post scripts and unpack the rpm into a
local directory. I can also use alien to install the rpm. Other than some
inappropriate (for ubuntu) directories, it seems like it would install fine.
I really don't have the skill to write an install script. I was baffled by a
lot of the /etc/init.d/apacheds file, especially the recursive launch of the
script when run-as does not match current user. I'm not even sure what
directories are preferred when installing the different sections of the
code. For example, the current codebase works with these separate
directories...
/etc/init.d - Used for apacheds start/stop script (same for ubuntu)
/etc/sysconfig - Used for specifying a couple directory paths (don't know
where ubuntu would want these. Seems like a waste of a folder for just
storing some "conf" data. I suppose they exist because they are conf data
for the server proper and not the server instance.)
/var/lib/apacheds - Used for configuration and runtime data (partitions).
Also holds subdirectories for different configurations of apacheds. Comes
with a 'default' config. (Maybe /usr/local/apacheds/configs?)
/var/run - Holds the pid apacheds is running on. (/var/lock in ubuntu)
/opt/apacheds-1.5.1 - Holds the implementation of the server, including the
bin directory for launching. (not sure where this should go, maybe
/usr/local/apacheds-1.5.1?)
So, you can see I don't know much about it, but I may know enough to get it
up and running although in a very manual manner. Assuming the init.d script
works on Ubuntu. The init.d script wants the name of an instance when
starting/stopping. How does it find this name parameter when the system is
starting up the server? It doesn't seem to default to anything...
FWIW, the i386 rpm seems to work OK on my PPC architecture.
Alex Karasulu wrote:
>
> You're right. It's lame that we have all these GUI installers and no
> tarball. Someone has to
> scratch this itch. Wanna give it a try?
>
--
View this message in context: http://www.nabble.com/-ApacheDS--In-preparation-for-1.0.1-release%3A-candidates-available-tf3268468.html#a13708105
Sent from the Apache Directory Project mailing list archive at Nabble.com.
Re: [ApacheDS] In preparation for 1.0.1 release: candidates available
Posted by Alex Karasulu <ak...@apache.org>.
You're right. It's lame that we have all these GUI installers and no
tarball. Someone has to
scratch this itch. Wanna give it a try?
Alex
On Nov 11, 2007 9:59 PM, chago <na...@visualxs.com> wrote:
>
> Wow, still no way to install this thing on a linux box that doesn't have X11
> installed?
>
> Forget about a Solaris installer, or at least prioritize a simple tarball
> before it. I'm on Ubuntu PPC and I can't find instructions on how to
> install. Really quite frustrating considering all the easy install programs
> available, but no simple manual install instructions.
>
> thanks.
>
>
>
> Alex Karasulu wrote:
> >
> > Oh and btw the RPM and the windows executable are also available here:
> >
> > http://people.apache.org/~akarasulu/apacheds/candidates/1.0.1/apacheds-1.0.1-linux-i386.rpm
> > http://people.apache.org/~akarasulu/apacheds/candidates/1.0.1/apacheds-1.0.1-win32-setup.exe
> >
> > Alex
> >
> > On 2/21/07, Alex Karasulu <ak...@apache.org> wrote:
> >>
> >> Yeah but you need a solaris machine with a display to generate the
> >> installer script. Basically go through an install on that machine then
> >> at
> >> the end of the install there is a screen with a button that asks you if
> >> you
> >> want to create a unmanned installation file. Hit that button and
> >> generate
> >> the script. Then scp that script to the target headless machine. Then
> >> install using the following command:
> >>
> >> java -jar apacheds-1.0.1-solaris-i386-setup.jar
> >> path/to/the<installer-file-you-created>
> >>
> >> Sorry this issue is still around. I was hoping to have a solaris package
> >> available but I have not had time to whip one together.
> >>
> >> HTH,
> >> Alex
> >>
> >> On 2/21/07, Graham Leggett <mi...@sharp.fm> wrote:
> >> >
> >> > Alex Karasulu wrote:
> >> >
> >> > >
> >> http://people.apache.org/~akarasulu/apacheds/candidates/1.0.1/apacheds-1.0.1-solaris-i386-setup.jar
> >> >
> >> >
> >> <http://people.apache.org/%7Eakarasulu/apacheds/candidates/1.0.1/apacheds-1.0.1-solaris-i386-setup.jar>
>
> >> >
> >> > Is there a workaround for this:
> >> >
> >> > bash-3.00# java -jar apacheds-1.0.1-solaris-i386-setup.jar
> >> > Java Accessibility Bridge for GNOME loaded.
> >> >
> >> > - Error -
> >> > java.awt.HeadlessException:
> >> > No X11 DISPLAY variable was set, but this program performed an
> >> operation
> >> >
> >> > which requires it.
> >> > java.awt.HeadlessException:
> >> > No X11 DISPLAY variable was set, but this program performed an
> >> operation
> >> > which requires it.
> >> > at
> >> >
> >> java.awt.GraphicsEnvironment.checkHeadless(GraphicsEnvironment.java:159)
> >> > at java.awt.Window.<init>(Window.java:317)
> >> > at java.awt.Frame.<init>(Frame.java:419)
> >> > at
> >> > net.sourceforge.mlf.metouia.borders.MetouiaDotsBuffer.<init>(
> >> > MetouiaDotsBuffer.java :105)
> >> > at
> >> > net.sourceforge.mlf.metouia.borders.MetouiaDots.<init>(MetouiaDots.java
> >> > :66)
> >> > at
> >> > net.sourceforge.mlf.metouia.borders.MetouiaToolBarBorder.<init>(
> >> > MetouiaToolBarBorder.java:49)
> >> > at
> >> > net.sourceforge.mlf.metouia.MetouiaLookAndFeel.initComponentDefaults(
> >> > MetouiaLookAndFeel.java:241)
> >> > at
> >> > javax.swing.plaf.basic.BasicLookAndFeel.getDefaults(
> >> > BasicLookAndFeel.java:107)
> >> > at
> >> > javax.swing.plaf.metal.MetalLookAndFeel.getDefaults(
> >> > MetalLookAndFeel.java:1392)
> >> > at javax.swing.UIManager.setLookAndFeel(UIManager.java:441)
> >> > at javax.swing.UIManager.setLookAndFeel(UIManager.java :481)
> >> > at
> >> > com.izforge.izpack.installer.GUIInstaller.loadLookAndFeel(
> >> > GUIInstaller.java:346)
> >> > at
> >> > com.izforge.izpack.installer.GUIInstaller.<init>(GUIInstaller.java:111)
> >> > at
> >> > sun.reflect.NativeConstructorAccessorImpl.newInstance0 (Native Method)
> >> > at
> >> > sun.reflect.NativeConstructorAccessorImpl.newInstance(
> >> > NativeConstructorAccessorImpl.java:39)
> >> > at
> >> > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(
> >> > DelegatingConstructorAccessorImpl.java :27)
> >> > at java.lang.reflect.Constructor.newInstance(Constructor.java
> >> > :494)
> >> > at java.lang.Class.newInstance0(Class.java:350)
> >> > at java.lang.Class.newInstance(Class.java:303)
> >> > at com.izforge.izpack.installer.Installer.main (Installer.java
> >> > :62)
> >> >
> >> >
> >> > Regards,
> >> > Graham
> >> > --
> >> >
> >> >
> >>
> >
> >
>
> --
> View this message in context: http://www.nabble.com/-ApacheDS--In-preparation-for-1.0.1-release%3A-candidates-available-tf3268468.html#a13699015
> Sent from the Apache Directory Project mailing list archive at Nabble.com.
>
>
Re: [ApacheDS] In preparation for 1.0.1 release: candidates available
Posted by Felix Knecht <fe...@apache.org>.
chago schrieb:
> Wow, still no way to install this thing on a linux box that doesn't have X11
> installed?
>
> Forget about a Solaris installer, or at least prioritize a simple tarball
> before it. I'm on Ubuntu PPC and I can't find instructions on how to
> install. Really quite frustrating considering all the easy install programs
> available, but no simple manual install instructions.
>
> thanks.
>
>
>
> Alex Karasulu wrote:
>
>> Oh and btw the RPM and the windows executable are also available here:
>>
>> http://people.apache.org/~akarasulu/apacheds/candidates/1.0.1/apacheds-1.0.1-linux-i386.rpm
>> http://people.apache.org/~akarasulu/apacheds/candidates/1.0.1/apacheds-1.0.1-win32-setup.exe
>>
>> Alex
>>
>> On 2/21/07, Alex Karasulu <ak...@apache.org> wrote:
>>
>>> Yeah but you need a solaris machine with a display to generate the
>>> installer script. Basically go through an install on that machine then
>>> at
>>> the end of the install there is a screen with a button that asks you if
>>> you
>>> want to create a unmanned installation file. Hit that button and
>>> generate
>>> the script. Then scp that script to the target headless machine. Then
>>> install using the following command:
>>>
>>> java -jar apacheds-1.0.1-solaris-i386-setup.jar
>>> path/to/the<installer-file-you-created>
>>>
>>>
I haven't tried, but does it also doesn't works when running in headless
mode?
java -Djava.awt.headless=true -jar apacheds-1.0.1-solaris-i386-setup.jar
(http://java.sun.com/developer/technicalArticles/J2SE/Desktop/headless/)
Felix