If you switch to Linux, then native is the way to go as you will need to
get accustomed with the internals.
You have to forget about eCS. I had OS Warp 3 and came back to it a couple
of times as hardware permited but I had to kiss him goodbye.

The same for BeOS ... I still have hopes for this one.

On Thu, Mar 19, 2015 at 11:15 PM, Rob Hamerling <[email protected]>
wrote:

>
> Thanks Kiste for the offer!
> I must see which of my existing Rexx scripts I want to convert to Bash (or
> Python) and decide for a priority: which first and which later. I could
> also chose to use Regina Rexx, then I (hopefully) would have to convert
> only file/directory/drive names. Another option is to run eCS in VBox and
> not convert anything.
> The more choices the more difficult to choose!!
> Regards, Rob.
>
>
> On 2015-03-19 06:11, 'Oliver Seitz' via jallib wrote:
>
>> Hi Rob!
>>
>> While (as usual) I don't have a lot of spare time these days, I'm quite
>> familiar with bash scripting. If you have any issues which google can't
>> solve, feel free to ask me :-)
>>
>> Greets,
>> Kiste
>>
>> ------------------------------------------------------------------------
>> *Von:* Rob Hamerling <[email protected]>
>> *An:* [email protected]
>> *Gesendet:* 11:50 Mittwoch, 18.März 2015
>> *Betreff:* [jallib] new device files
>>
>>
>> Hi guys,
>>
>> I'm in a transition period: moving from eComStation (OS/2) to Linux, at
>> least for some parts. Easy were Firefox, Thunderbird, Python and
>> Subversion. Now I'm trying to learn the Linux command language... Since
>> so far nobody took over the Jallib device file generation process I
>> thought it might be a good idea to take this as learning exercise. Two
>> birds with one stone: learning bash and updating the device files to the
>> latest MPLAB-X level.  I just committed the (first) results. The new
>> device files are based on MPLAB-X 3.0 (beta), but are only marginally
>> different from the 2.15 level: some fixes, a few new PICS, removal of
>> some pin aliases (like MCLR, ICSP and ICD pins).
>>
>> Regards, Rob.
>>
>> --
>> *Rob H*amerling - http://www.robh.nl <http://www.robh.nl/>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "jallib" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected]. <mailto:unsubscribe@
>> googlegroups.com.>
>> To post to this group, send email to [email protected]. <mailto:
>> [email protected].>
>> Visit this group at http://groups.google.com/group/jallib.
>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "jallib" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected] <mailto:jallib+unsubscribe@
>> googlegroups.com>.
>> To post to this group, send email to [email protected] <mailto:
>> [email protected]>.
>> Visit this group at http://groups.google.com/group/jallib.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> *Rob H*amerling - http://www.robh.nl
>
> --
> You received this message because you are subscribed to the Google Groups
> "jallib" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at http://groups.google.com/group/jallib.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Vasi

-- 
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/jallib.
For more options, visit https://groups.google.com/d/optout.

Reply via email to