LinMin announces proprietary provisioning for FOSS networks


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News LinMin announces proprietary provisioning for FOSS networks
# 1  
Old 03-25-2008
LinMin announces proprietary provisioning for FOSS networks

Tue, 25 Mar 2008 20:00:00 GMT
Developing a business model around free and open source software (FOSS) can be a delicate balancing game. Many companies in this space opt for models in which revenue comes from sources such as services, rather than the software itself. However, the recently announced LinMin is taking a different approach with a new appliance and imaging appliance: Although it runs and works on FOSS, LinMin's software is proprietary. The company's reasons for this practice raise several core issues about the relationship between FOSS and proprietary software on one hand and business priorities on the other.


Source...
Login or Register to Ask a Question

Previous Thread | Next Thread

3 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Transfer output of a proprietary command to a file

Hi Guys, My problem looks simple. I have a software-proprietary command (not linux) that provides an output, let's say 200 lines. Unfortunately the dumb coders of the software did not include the option ">" or ">>" which allows to transfer output to a file, so I need a way to do that using some... (5 Replies)
Discussion started by: liviusbr
5 Replies

2. UNIX and Linux Applications

JBoss: Difference Standard / proprietary deployment discriptor

can anyone please tell me what is the difference btwn a standard deployment discriptor and a proprietary one???:wall: (3 Replies)
Discussion started by: htshshrm2
3 Replies

3. UNIX for Advanced & Expert Users

Proprietary vs. open Unix

Howdy all, I've used various applications in the past that ran in unix and windoze and unfortunately several of those programs are migrating to a windoze only environment so management is bagging the proprietary unix boxes in the process. AArrgggghh So here's my question for all you serious... (3 Replies)
Discussion started by: bulletbob
3 Replies
Login or Register to Ask a Question
NETWORKS(5)                                                 Linux System Administration                                                NETWORKS(5)

NAME
networks - network name information DESCRIPTION
The file /etc/networks is a plain ASCII file that describes known DARPA networks and symbolic names for these networks. Each line repre- sents a network and has the following structure: name number aliases ... where the fields are delimited by spaces or tabs. Empty lines are ignored. The hash character (#) indicates the start of a comment: this character, and the remaining characters up to the end of the current line, are ignored by library functions that process the file. The field descriptions are: name The symbolic name for the network. Network names can contain any printable characters except white-space characters or the comment character. number The official number for this network in numbers-and-dots notation (see inet(3)). The trailing ".0" (for the host component of the network address) may be omitted. aliases Optional aliases for the network. This file is read by the route(8) and netstat(8) utilities. Only Class A, B or C networks are supported, partitioned networks (i.e., net- work/26 or network/28) are not supported by this facility. FILES
/etc/networks The networks definition file. SEE ALSO
getnetbyaddr(3), getnetbyname(3), getnetent(3), netstat(8), route(8) COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the latest version of this page, can be found at https://www.kernel.org/doc/man-pages/. GNU
/Linux 2008-09-04 NETWORKS(5)