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(4)							   File Formats 						       networks(4)

NAME
networks - network name database SYNOPSIS
/etc/inet/networks /etc/networks DESCRIPTION
The networks file is a local source of information regarding the networks which comprise the Internet. The networks file can be used in conjunction with, or instead of, other networks sources, including the NIS maps networks.byname and networks.byaddr and the NIS+ table networks. Programs use the getnetbyname(3SOCKET) routines to access this information. The network file has a single line for each network, with the following information: official-network-name network-number aliases Items are separated by any number of SPACE or TAB characters. A `#' indicates the beginning of a comment. Characters up to the end of the line are not interpreted by routines which search the file. This file is normally created from the official network database maintained at the Network Information Control Center (NIC), though local changes may be required to bring it up to date regarding unofficial aliases and/or unknown networks. Network numbers may be specified in the conventional dot (`.') notation using the inet_network routine from the Internet address manipula- tion library, inet(7P). Network names may contain any printable character other than a field delimiter, NEWLINE, or comment character. SEE ALSO
getnetbyaddr(3SOCKET), getnetbyname(3SOCKET), inet(3SOCKET), nsswitch.conf(4), inet(7P) NOTES
The official SVR4 name of the networks file is /etc/inet/networks. The symbolic link /etc/networks exists for BSD compatibility. The network number in networks database is the host address shifted to the right by the number of 0 bits in the address mask. For example, for the address 24.132.47.86 that has a mask of fffffe00, its network number is 803351. This is obtained when the address is shifted right by 9 bits. The address maps to 12.66.23. The trailing 0 bits should not be specified. The network number here is different from that described in netmasks(4). For this example, the entry in netmasks would be 24.132.46.0 fffffe00. SunOS 5.10 17 Jan 2002 networks(4)