Sponsored Content
Full Discussion: Unix OS Installer
Operating Systems Linux Gentoo Unix OS Installer Post 302103601 by microuniz on Friday 19th of January 2007 11:21:09 AM
Old 01-19-2007
thats wad my stupid supervisor asked me to do so.

are there simpler and easier ways?

so where are the OSs?
 

8 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Create an installer

I have a software bundle for which I want to create an installer. One of the things I am also looking at, is to be able to install this straight from a CD or any external storage device. How do I go about creating one? This is for Linux. Any advice is welcome !! -- garric (3 Replies)
Discussion started by: garric
3 Replies

2. UNIX for Dummies Questions & Answers

UNIX installer??

hi i wanna ask that is there a software available for unix to install different files... e.g. when we install a file in windows the installation wizard runs and guides us through the process... if so plz tell... and guide thnx! (5 Replies)
Discussion started by: umarbangash
5 Replies

3. Fedora

wubi installer for windows

hello.i need a soft like (wubi support ubuntu) to boot fedora or centos or freebsd.any answer ? Thank You. (2 Replies)
Discussion started by: d4rkm4nx99
2 Replies

4. Solaris

solaris installer

what is the name of the solaris installer? (for both x86 and sparc architecture) In linux it is "anaconda". (7 Replies)
Discussion started by: kingston
7 Replies

5. Solaris

OpenSolaris Installer error

Hi, Whenever i try to install OpenSolaris, I am getting the error "There was an error launching the application. Detail: Failed to fork child process (Not enough space)" I am using the image 2009.06. I have 512 mb ram and 100 gb hard drive with Red Hat and Windows Xp installed. Please... (1 Reply)
Discussion started by: krabu
1 Replies

6. Shell Programming and Scripting

Xfce installer script

Xfce desktop installer script on Ubuntu for home, office or server computers. This script installs Xfce desktop and a set of programs according to user needs starting from an Ubuntu Server base system. It's valid for netbooks, notebooks, desktop computers and servers. For more information... (1 Reply)
Discussion started by: cesar-rgon
1 Replies

7. Shell Programming and Scripting

Yet another simple script installer

Heyas Just recently i tried to apply the GNU Autotools to my project, while it was possible, it took forever to know where to create which files and what to place in each of them. Dare you making a space rather than a tab! Inspired by GNU Autotools, and overhelmed by its functionality and... (0 Replies)
Discussion started by: sea
0 Replies

8. OS X (Apple)

Installer issue

Hi, I have a little problem with an Installer. In my script I have a section that place a keyboard shortcut: #!/usr/bin/perl ################################################################################ # # Create Desktop shortcut for Swedish Menu Commands Document #... (1 Reply)
Discussion started by: peli
1 Replies
supervisor_bridge(3erl) 				     Erlang Module Definition					   supervisor_bridge(3erl)

NAME
supervisor_bridge - Generic Supervisor Bridge Behaviour. DESCRIPTION
A behaviour module for implementing a supervisor_bridge, a process which connects a subsystem not designed according to the OTP design principles to a supervision tree. The supervisor_bridge sits between a supervisor and the subsystem. It behaves like a real supervisor to its own supervisor, but has a different interface than a real supervisor to the subsystem. Refer to OTP Design Principles for more informa- tion. A supervisor_bridge assumes the functions for starting and stopping the subsystem to be located in a callback module exporting a pre- defined set of functions. The sys module can be used for debugging a supervisor_bridge. Unless otherwise stated, all functions in this module will fail if the specified supervisor_bridge does not exist or if bad arguments are given. EXPORTS
start_link(Module, Args) -> Result start_link(SupBridgeName, Module, Args) -> Result Types SupBridgeName = {local,Name} | {global,Name} Name = atom() Module = atom() Args = term() Result = {ok,Pid} | ignore | {error,Error} Pid = pid() Error = {already_started,Pid} | term() Creates a supervisor_bridge process, linked to the calling process, which calls Module:init/1 to start the subsystem. To ensure a synchronized start-up procedure, this function does not return until Module:init/1 has returned. If SupBridgeName={local,Name} the supervisor_bridge is registered locally as Name using register/2 . If SupBridgeName={global,Name} the supervisor_bridge is registered globally as Name using global:register_name/2 . If no name is provided, the supervisor_bridge is not registered. If there already exists a process with the specified SupBridgeName the function returns {error,{already_started,Pid}} , where Pid is the pid of that process. Module is the name of the callback module. Args is an arbitrary term which is passed as the argument to Module:init/1 . If the supervisor_bridge and the subsystem are successfully started the function returns {ok,Pid} , where Pid is is the pid of the supervisor_bridge. If Module:init/1 returns ignore , this function returns ignore as well and the supervisor_bridge terminates with reason normal . If Module:init/1 fails or returns an error tuple or an incorrect value, this function returns {error,Term} where Term is a term with information about the error, and the supervisor_bridge terminates with reason Term . CALLBACK FUNCTIONS
The following functions should be exported from a supervisor_bridge callback module. EXPORTS
Module:init(Args) -> Result Types Args = term() Result = {ok,Pid,State} | ignore | {error,Error} Pid = pid() State = term() Error = term() Whenever a supervisor_bridge is started using supervisor_bridge:start_link/2,3 , this function is called by the new process to start the subsystem and initialize. Args is the Args argument provided to the start function. The function should return {ok,Pid,State} where Pid is the pid of the main process in the subsystem and State is any term. If later Pid terminates with a reason Reason , the supervisor bridge will terminate with reason Reason as well. If later the super- visor_bridge is stopped by its supervisor with reason Reason , it will call Module:terminate(Reason,State) to terminate. If something goes wrong during the initialization the function should return {error,Error} where Error is any term, or ignore . Module:terminate(Reason, State) Types Reason = shutdown | term() State = term() This function is called by the supervisor_bridge when it is about to terminate. It should be the opposite of Module:init/1 and stop the subsystem and do any necessary cleaning up. The return value is ignored. Reason is shutdown if the supervisor_bridge is terminated by its supervisor. If the supervisor_bridge terminates because a a linked process (apart from the main process of the subsystem) has terminated with reason Term , Reason will be Term . State is taken from the return value of Module:init/1 . SEE ALSO
supervisor(3erl) , sys(3erl) Ericsson AB stdlib 1.17.3 supervisor_bridge(3erl)
All times are GMT -4. The time now is 09:11 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy