Re: Alright, you jdk14 geeks...

From: Charles Swiger (cswiger_at_mac.com)
Date: 02/02/05

  • Next message: Nick Pavlica: "Re: FreeBSD 5.3 I/O Performance / Linux 2.6.10 | Continued Discussion"
    Date: Tue, 1 Feb 2005 18:48:27 -0500
    To: John <john@starfire.mn.org>
    
    

    On Feb 1, 2005, at 6:10 PM, John wrote:
    > Once it is BUILT on the NFS system - will I be able to INSTALL
    > it on my clients? Has anyone tried anything like this?

    Once you've got a native JDK built as a package on FreeBSD, you can
    install it on other FreeBSD client machines, yes, no problem. If you
    want to distribute the JDK to machines owned by someone else who are
    your business clients, well, that is another story.

    > Is this OK with the license agreement?

    You need to understand the license agreements yourself:

    http://www.sun.com/software/communitysource/j2se/java2/license.html
    http://www.sun.com/software/communitysource/j2se/java2/
    thirdpartylicense.txt

    "This Attachment C is only effective for the Technology
    specified in Attachment B, upon execution of Attachment D
    (Commercial Use License) including the requirement to pay
    royalties. In the event of a conflict between the terms of
    this Attachment C and Attachment D, the terms of Attachment
    D shall govern."

    If you don't understand what the license means or what the royalties
    are for redistributing a commercial version of Java, talk to your
    laywer and Sun.

    -- 
    -Chuck
    _______________________________________________
    freebsd-questions@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-questions
    To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
    

  • Next message: Nick Pavlica: "Re: FreeBSD 5.3 I/O Performance / Linux 2.6.10 | Continued Discussion"

    Relevant Pages

    • Re: Installation Product ID from Office 2003
      ... Unless you have a volume license or similar you can install each retail copy of the Office products, including Project, on only one computer per license and the system checks to see if an installation using that CD key has already been activated on another computer. ... If you have installed a copy of Project on your own computer you cannot use the same key to activate it on another, including those of your clients. ...
      (microsoft.public.project)
    • Re: Re-installing XP on system rebuild
      ... For the former, and since you are supposedly a "system builder", there are no other issues if the "new" system is a "repair" of the original system also built by you. ... I just want to get a clean install on the new system then delete the old os from the old drive that will be slaved to the new drive. ... the license died with the original computer and a new license will need to be purchased. ...
      (microsoft.public.windowsxp.general)
    • Re: Installer Run App feature
      ... you don't need to specify a path for EXEs built into the ... while be able to provide the variable Profile.cpf to clients separately. ... So this installer app allows the developer to shell out to one application ... at the end of the install app. ...
      (microsoft.public.dotnet.framework.compactframework)
    • Re: New Install - Outlook
      ... license for Outlook, use it (for each user on SBS comes with the license for ... > I suggest to install the complete package when setting up SBS2003. ... > If you do not want the clients to have OL2003, ... > that has an account in SBS. ...
      (microsoft.public.windows.server.sbs)
    • Re: Moving TS license svc to 2003 member srv
      ... It was issued a built in license from the license server. ... >> one of your W2K Pro or XP Pro clients. ...
      (microsoft.public.win2000.termserv.apps)