Sponsored Content
Full Discussion: LM 19.1 from pendrive
Operating Systems Linux LM 19.1 from pendrive Post 303033755 by Neo on Thursday 11th of April 2019 08:41:25 AM
Old 04-11-2019
OK

Enough jake19.

If you do not like a user here for what ever reason, just ignore the discussion.

Thanks

Last edited by hicksd8; 04-11-2019 at 11:21 AM..
These 2 Users Gave Thanks to Neo For This Post:
 

6 More Discussions You Might Find Interesting

1. Red Hat

helo how to mount pendrive on redhat 9

helo my sysem is running on redhat 9. now i want to take data from redhat 9 pc to pen drive. but when i plug it it is not detected. can u tell me how to mount pendrive on redhat9. amit (1 Reply)
Discussion started by: amitpansuria
1 Replies

2. UNIX for Dummies Questions & Answers

boot from a pendrive

Can anybody explane 'How to boot from a pendrive' ?Is it possible to load Operating System from a pendrive----? How? (5 Replies)
Discussion started by: Ajith kumar.G
5 Replies

3. UNIX for Dummies Questions & Answers

Copying files unto a usb pendrive/external disk from Solaris 9

Hi all, Can anybody help me with how I can connect a usb pendrive or external disk to a Sun Server which runs on Solaris 9? I am able to connect the usb drive to a windows server easily and copy files but am wondering if it is possible to do that with Solaris. Any help will be appreciated. thanks. (3 Replies)
Discussion started by: rahmantanko
3 Replies

4. SCO

mount the pendrive on the unixware 7.1.4

please let me know how to mount the pendrive on the unixware (1 Reply)
Discussion started by: deepthi.s
1 Replies

5. UNIX for Dummies Questions & Answers

Unable to acces my pendrive in linux

Hi Gurus, in linux I am unable to access my pendrive(i am even not seeing the icon or location for my pendrive ). Please anyany could help me to get rid of this issue. regards, Sanjay :) (4 Replies)
Discussion started by: sanjay.login
4 Replies

6. Slackware

Which USB pendrive image to install Slackware on an old AMD K6 3D ?

Holla, I have been trying to install a recent distro, with a minimum X such as jwm, but unfortunately my cdrom is broken and I can only boot the USB port, with a pendrive. AMD K6 3D is today too old for being for linux. Is there an image of slackware than runs that processor and that can... (5 Replies)
Discussion started by: raptor34
5 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 06:23 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy