Hi,

  Just joined the list. I am interested in building VistA for humanitarian
  purposes so I can help local free clinics, meaning no money to fund
  this effort.  I'm familiar with Linux but not
  much with database or Server/Client. I built 3 PC's so far with Win95,
  Win98, NextStep, Linux, and Win2000, all for just fun. 
   (i'm an old Fortran guy, i know, i know...) 
  I plan to install Linux server from scratch, install Apachi,
  install Cache, and Vista. Then configure Vista. Am I stupid, but bold? yes. 
  
  Don't know if these questions were answered before but
  here are my very first questions:

   1. Difference among VistaOffice, Hui Vista, Vista from VA ftp site,
       Vista Viva, etc?
   2. I have desktop PC and wifi laptop. How can I use these to make
      server-client environment?  Is it possible to utilize wifi somehow?
       (both have 10baseT so theoretically I can hook these two via
        network cable but I hate it.)
   3. What would be ideal infrastructure for a small clinic with security
       in mind?  I think at least three clients for front desk, physician, and
       nurse.  And at least one server. Without installing the traditional
       T1 network at the site, can wifi be used to connect all these machines?
       What are the security issues? 
   4. Are there much differences with Suse or Red Hat "Enterprise" server
      and just plain Red Hat or Fedora with all other server components
      added to it? Can I use Debian or Slackware instead of RH?

  That's it for now.  Thanks bunch.

  Jae.


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click
_______________________________________________
Hardhats-members mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/hardhats-members

Reply via email to