EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  <20012002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  <20012002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: VxWorks on Linux
From: Nick Rees <[email protected]>
To: [email protected]
Date: Fri, 9 Nov 2001 17:40:57 -1000 (HST)
Hi,

We are (like many people, I suspect) gradually transitioning from Solaris
to Linux. The driver for this is not the EPICS developers, but
price/performance for data reduction. However, the end result is a knock
on to the EPIC's/real-time developers at our site.

So, I rang my VxWorks sales rep the other day and he came back with a
standard VxWorks quote. Well I laughed. After the laughter had subsided I
explained a bit what we were about and it transpired:

 - Linux support was only available on VxWorks AE for the current time, so
   that was what the quote was for.
 - VxWorks AE was not available for 68k.

I explained that we specifically didn't want or need any of the AE
features, and that we still had quite a lot of 68k machines around. We had
also been pay the odd few $k a year for many years for not much. All we
really needed now was a Linux-based GNU toolset on all of our
architectures (68k, MIPS and PPC), a reasonable debugger, and the VxWorks
libraries. (One problem I have had is getting a good build of the GNU
toolset for architectures other than the 68k).

Well, after this he became somewhat receptive. Also, since all the Hawaii
telescopes are in his sales patch, he asked me how many other people were
in the same boat. I said I would find out, but I suspected there were a
few.

Hence, the question is, how many sites are interested in transitioning to
Linux, and would be willing to do this at a reduced cost with the
possibility that all latest Tornado development suite would not be
available, but the GNU toolchain and debugger would be? If you are
interested, please can one person from each site send me:

1. Contact name
2. Site name
3. #VxWorks licenses
4. VxWorks license number

The latter two are optional, but are may come in handy.

I suspect nothing will come of it, but I felt that if we got a reasonable
number of people responding, baybe WRS might notice.

Also, if someone closer to the collaboration has already taken this up (or
would like to), please let me know anything you have - I won't stand in
your way :-).

Cheers,

-- 
Nick Rees

Joint Astronomy Centre               Ph:       +1 (808) 961-3756
660 N. Aohoku Place                  Fax:      +1 (808) 961-6516
Hilo, HI.  96720                     Internet: [email protected]



Replies:
Re: VxWorks on Linux Steve Lewis
Re: VxWorks on Linux John K Munro Jr
Re: VxWorks on Linux Jim Thomas
Re: VxWorks on Linux Ralph . Lange
References:
RE: How to deal with two network interfaces? Jeff Hill

Navigate by Date:
Prev: et_wish help requested Bill Cruise
Next: Re: VxWorks on Linux Steve Lewis
Index: 1994  1995  1996  1997  1998  1999  2000  <20012002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: RE: How to deal with two network interfaces? Vladis Korobov
Next: Re: VxWorks on Linux Steve Lewis
Index: 1994  1995  1996  1997  1998  1999  2000  <20012002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 10 Aug 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·