Sponsored Content
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News autonom.us aims to be think-tank on network service software licensing issues Post 302222322 by Linux Bot on Wednesday 6th of August 2008 02:10:06 PM
Old 08-06-2008
autonom.us aims to be think-tank on network service software licensing issues

08-06-2008 11:00 AM
Network services are one of the fastest growing areas in modern software. However, while network services have much of the convenience of free software, only a minority are available under a free license. In fact, it was only last November that the Free Software Foundation (FSF) released the GNU Affero General Public License for network services. Under these conditions, last week's announcement of the formation of autonom.us, a new activist group "to focus on issues of software freedom in network services," seems overdue. The group's immediate plans are still evolving, but currently, its main goal -- so far as it has one yet -- seems to be as a policy discussion and advocacy group.



Source...
 

3 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Perl 5.8.8 licensing issues

I have a question about the perl license on Solaris machine. The scenario is we have perl 5.6.1 installed on Solaris server. Our developers are planning to use a module which is not installed on the server. We did search CPAN website and found some availability matrix CPAN Testers Matrix:... (3 Replies)
Discussion started by: sudhiroracle
3 Replies

2. Emergency UNIX and Linux Support

Network related issues

Oflate we are finding a few servers experiencing severe slowness. What would be the commands that I need to try to postmortem the situation? (3 Replies)
Discussion started by: ggayathri
3 Replies

3. Hardware

Arduino Robot Tank Project

Normally I'm not into kits, but I thought my wife would enjoy this one since she is a big fan of robots and droids on StarWars! We are done with the basic mechanical assembly and starting on the electronics assembly today. The robot's "brain" consists of three levels. The Arduino board, on... (5 Replies)
Discussion started by: Neo
5 Replies
IFSERVICES(5)						       Network configuration						     IFSERVICES(5)

NAME
ifservices-* - control network services with ifup/down SYNOPSIS
/etc/sysconfig/network/ifservices-<configuration_name>/ DESCRIPTION
The directory /etc/sysconfig/network/ifservices-<configuration_name>/ is read by the script /etc/sysconfig/network/scripts/ifup-services which starts and stops system services when an interface is set up/down. ifup-services is used by /sbin/ifup, which is the command line user interface for setting up network interfaces. This is useful if you don't have a permanent network connection. If you sometimes boot without network and plug in the network cable later you can add links to system services in this directory. These services will then be started with ifup and stopped with ifdown. The configuration name used for ifservices-* should match exactly the configuration name of the ifcfg-* file for the interface. For the usage with NetworkManager (where you don't necessarily need a ifcfg-* file) you can also use /etc/sysconfig/network/ifser- vices-<interface>-<essid>/ (for wlan interfaces) or if that does not exist /etc/sysconfig/network/ifservices-<interface>/. As a final fallback /etc/sysconfig/network/ifservices/ is checked as well. If NetworkManager is active services will be stopped after the interface is down. The links in this directory are equal to the links in the runlevel directories /etc/init.d/rc*.d/ They have to point to service start scripts which are usually in /etc/init.d/. Links starting with 'S' are start links, which are called in alphabetical order after ifup has set up the interface. Links starting with 'K' are kill links which are called before ifdown takes down the interface. See also section Sequencing Directories in boot (7). EXAMPLE
In this example we use an interface with MAC address 00:de:ad:be:af:00. This interface is not always physically connected. As soon as you plug in the cable ypbind and autofs should be started. When you pull the cable they should be stopped. This can be reached with: in file /etc/sysconfig/network/ifcfg-eth-id-00:de:ad:be:af:00 ... STARTMODE=ifplugd ... in dir /etc/sysconfig/network/ifservices-eth-id-00:de:ad:be:af:00/ S10portmap -> /etc/init.d/portmap S20ypbind -> /etc/init.d/ypbind S30autofs -> /etc/init.d/autofs S20autofs -> /etc/init.d/autofs K30ypbind -> /etc/init.d/ypbind Now you have to disable the start of this services at boot time chkconfig ypbind off chkconfig autofs off Notes: You may call scripts/create-ifservices-directory [<interface_name>] to create a directory with the links from this example. This will cre- ate the directory ifservices-<interface_name> or if no interface name was given ifservices-template. Maybe you have to add also variable IFPLUGD_PRIORITY. For details about startmode ifplugd read ifup (8). The service portmap had to be added because ypbind needs it. This service is still started at boot time because it does not need an active network connection. But ypbind may now be started earlier as usual. Therefore we make sure that portmap is started before. Starting an already running service again does not affect the service. SEE ALSO
ifup(8), ifcfg(5). AUTHOR
Christian Zoz <zoz@suse.de> sysconfig February 2005 IFSERVICES(5)
All times are GMT -4. The time now is 01:33 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy