Tiny Core Linux

General TC => General TC Talk => Topic started by: willowdan on May 30, 2013, 11:52:31 AM

Title: RubyRep
Post by: willowdan on May 30, 2013, 11:52:31 AM

Hi Everyone!

Can someone assist me on installing RubyRep in microcore?

Many thanks and cheers!

Title: Re: RubyRep
Post by: willowdan on May 30, 2013, 11:56:34 AM

By the way, based on the instructions contained in http://www.rubyrep.org/installation.html, I simply extracted the files and folders from the zip file, yet I cannot run the "rubyrep" executable file.

Hope someone can help.

Many thanks and cheers!

Title: Re: RubyRep
Post by: Rich on May 30, 2013, 03:58:48 PM

Hi willowdan
Unless you supply some information, such as what command you gave and what error messages you received, our
guess is as good as yours.

Title: Re: RubyRep
Post by: tinypoodle on May 30, 2013, 05:18:25 PM

Quote from: willowdan on May 30, 2013, 11:56:34 AM

By the way, based on the instructions contained in http://www.rubyrep.org/installation.html, I simply extracted the files and folders from the zip file

Have you got a flawlessly working java runtime environment?

Title: Re: RubyRep
Post by: willowdan on May 30, 2013, 07:28:54 PM

Hi Rich & Tinypoodle,

By simply isueing the "rubyrep" executable file in the commandline, seemingly the sh command is rather being called.

Cheers!

Title: Re: RubyRep
Post by: willowdan on May 30, 2013, 07:32:13 PM

Hi Tinypoodle,

Yes, I have a working java environment.

Cheers!

Title: Re: RubyRep
Post by: willowdan on May 31, 2013, 08:43:20 PM

Anyone have idea?

Cheers!

Title: Re: RubyRep
Post by: tinypoodle on May 31, 2013, 09:11:18 PM

Quote from: willowdan on May 30, 2013, 07:28:54 PM

By simply isueing the "rubyrep" executable file in the commandline, seemingly the sh command is rather being called.

Any vague description could not equal pasting of output ad verbatim.

Title: Re: RubyRep
Post by: willowdan on May 31, 2013, 11:44:02 PM

Hi Tinypoodle,

I mean if I issue "rubyrep generate myrubyrep.conf", the sh is called instead of "rubyrep" executing ...

Cheers!

Title: Re: RubyRep
Post by: tinypoodle on May 31, 2013, 11:54:50 PM

That is providing one more unclear description instead of providing facts...

If any executable is not in your $PATH, you have to call it either with absolute or relative (./command) path, also you have to make it executable in case it is not (chmod +x).

Title: Re: RubyRep
Post by: willowdan on June 01, 2013, 12:08:30 AM

Hi Tinypoodle,

Sorry forgot to mention, I first went into the exact folder where rubyrep is, from there I executed the said command, but the sh was being called instead.

Cheers!

Title: Re: RubyRep
Post by: Rich on June 01, 2013, 12:16:38 AM

Hi willowdan
Make sure the file is executable:

Code: [Select]

chmod +x rubyrepTry it like this:

Code: [Select]

./rubyrep generate myrubyrep.conf

Title: Re: RubyRep
Post by: tinypoodle on June 01, 2013, 12:43:08 AM

"All diagnosticians are from Missouri."

That US state's official motto is "Show me" (earned in 1899, when Congressman Willard D. Vandiver said "I come from a country that raises corn and cotton and cockleburs and Democrats, and frothy eloquence neither convinces nor satisfies me. I'm from Missouri. You've got to show me.")

In diagnosticians' case, it's not a matter of skepticism, but rather a literal, functional need to see whatever is as close as possible to the same raw evidence that you see, rather than your surmises and summaries. Show us.

http://www.catb.org/esr/faqs/smart-questions.html

Title: Re: RubyRep
Post by: willowdan on June 01, 2013, 02:49:31 AM

Hi Rich,

Yes, the rubyrep file is executable already, sti the same experience. What else should I be missing?

Cheers!

Title: Re: RubyRep
Post by: gerald_clark on June 01, 2013, 10:10:52 AM

What you are missing is showing exactly what you typed, and exactly what you get back.

Title: Re: RubyRep
Post by: tinypoodle on June 01, 2013, 10:50:27 AM

Even when making the assumption that the in 3 posts repeated description of "sh is called" - which I highly doubt to be the case - was true, it could still be a description applying to various events (e.g. a subshell being spawned; 'exec').