Slashdot Mirror

← Back to Stories (view on slashdot.org)

Distributing In-House Engineering Code?

Posted by Cliff on from the internal-engineering-grapevines dept.

caswelmo asks: "My company has recently moved from Solaris workstations to Windows workstations (Ohhh, the humanity). As an engineering focused company, we use our computers to run many in-house (command line) codes to analyze and design our products. We currently use NAS storage to store everything and use batch files and init scripts to run the correct codes over the network. This makes sure everyone is running the latest version. This also stinks. I know this isn't an original problem, so what are some other solutions for rolling out lots of simple codes like this?"

2 of 49 comments (clear)

  1. Generic question about distributed application by mnmn · · Score: 2, Interesting

    Ok so the Solaris 'code' is on a NAS server, and it is run remotely. You also mentioned you recently moved to Win32.

    Hmmm. It couldnt have been more unclear. Solaris most frequently runs on sparc architectures. Surely the code must be sitting one place, executing on another machine, and somehow the windows machines grab hold of the results...

    So depending on your REAL situation:

    (1) Run apache on the solaris box and display results.

    (2) Run the code on a terminal server machine (Windows2000 terminal services or X11)

    (3) Use rsync or the windows equivalent to redistribute code to all machines

    (4) Use CVS

    (5) Recompile the code for win32.

    To get any more useful advice from slashdot, specify your problem better.

    --
    "Give orange me give eat orange me eat orange give me eat orange give me you." -Nim Chimpsky
  2. Well.... by FooAtWFU · · Score: 1, Interesting
    Remember: A "Windows" workstation just means "we haven't reformatted and installed something better yet". Why not reformat/reinstall yourself a Linux, BSD or even (!) Solaris (x86) distribution? Heck, you could probably put together a CD which would automagically setup and install that sort of thing, and then you can go back and do exactly the same method you used before.

    Why did you switch to Windows workstations? Is it the Windows operating system itself, or is the hardware just cheaper? Surely it's not because of Windows' vastly superior scripting language and abilities! (cough)

    And just remember not to obsess over any sunk costs you've already incurred, like your Windows licenses.

    --
    The World Wide Web is dying. Soon, we shall have only the Internet.