Sponsored Content
Full Discussion: Make .iso mountable in LDOM
Operating Systems Solaris Make .iso mountable in LDOM Post 302981790 by pressy on Monday 19th of September 2016 01:19:08 PM
Old 09-19-2016
can you see the "iso" in OBP with "show-disks"?

I would try to "unbind" and "bind" the LDOM again... may be you will get an error to investigate on bind... (in use or something like that)

regards
P
 

6 More Discussions You Might Find Interesting

1. Programming

Why ""No mountable file system"

I tried to install OpenMotif under Mac OS in the computing lab today, but I got "No mountable file system". Is it because I don't have the administrator's privilege? (0 Replies)
Discussion started by: endeavour1985
0 Replies

2. Solaris

iso files to make bootable dvd image

Hey all, I'm a newbie to iso files and I just downloaded the 2 iso files for *cough* ms2003 R2 *cough* trial software. After I downloaded the iso files I just dragged them to my burn software gui and sure enough it burned to dvd 2 iso files. When I attempted to boot the image using VMware... (0 Replies)
Discussion started by: bdsffl
0 Replies

3. Fedora

make bootable usb from iso

I need to boot the ultimate boot cd from an usb stick. Do I just copy the iso image to the usb key? How do I make the usb stick bootable? (4 Replies)
Discussion started by: locoroco
4 Replies

4. Red Hat

How to make boot.iso image from rhel6 installation dvd iso ?

Hello Everyone, Can anyone let me know how to make minimal boot.iso from rhl6 installation dvd iso image. I have a dvd image with me but i want to make just a minimal boot media. Somehow it is not shipped with dvd iso. I know we can download boot.iso from redhat site but is there any anyway we... (5 Replies)
Discussion started by: Rohit Bhanot
5 Replies

5. Solaris

How can I install Solaris 10 on an LDom using an iso?

Hello, I am trying to install Solaris 10 on a newly created LDom. Here are the commands I ran to create the LDom: ldm add-domain ldg2 ldm add-vcpu 8 ldg2 ldm add-memory 2g ldg2 ldm add-vnet vnet2 primary-vsw0 ldg2 ldm add-vdsdev /dev/dsk/c0t5000CCA01535E20Cd0s0 vol2@primary-vds0 ldm... (8 Replies)
Discussion started by: bstring
8 Replies

6. SuSE

How To make bootable USB with multiple ISO Files?

Hi All, I would need your assistance to make a bootable USB with SUSE LINUX Enterprise Server I have already downloaded relevant OS (Trail Version) packages @ 1) SLES-11-SP4-DVD-i586-GM-DVD1 2) SLES-11-SP4-DVD-i586-GM-DVD2 when I tried to open these packages with PowerISO one of the... (7 Replies)
Discussion started by: Leaner_963
7 Replies
uevent(n)							    User events 							 uevent(n)

__________________________________________________________________________________________________________________________________________________

NAME
uevent - User events SYNOPSIS
package require Tcl 8.4 package require uevent ?0.2? package require logger ::uevent::bind tag event command command tag event details ::uevent::unbind token ::uevent::generate tag event ?details? ::uevent::list ::uevent::list tag ::uevent::list tag event _________________________________________________________________ DESCRIPTION
This package provides a general facility for the handling of user events. Allows the binding of arbitrary commands to arbitrary events on arbitrary tags, removal of bindings, and event generation. The main difference to the event system built into the Tcl/Tk core is that the latter can generate only virtual events, and only for wid- gets. It is not possible to use the builtin facilities to bind to events on arbitrary (pseudo-)objects, nor is it able to generate events for such. Here we can, by assuming that each object in question is represented by its own tag. Which is possible as we allow arbitrary tags. More differences: [1] The package uses only a two-level hierarchy, tags and events, to handle everything, whereas the Tcl/Tk system uses three levels, i.e. objects, tags, and events, with a n:m relationship between objects and tags. [2] This package triggers all bound commands for a tag/event combination, and they are independent of each other. A bound command cannot force the event processing core to abort the processing of command coming after it. API
The package exports three commands, as specified below: ::uevent::bind tag event command Using this command registers the command prefix to be triggered when the event occurs for the tag. The result of the command is an opaque token representing the binding. Note that if the same combination of <tag,event,command> is used multiple times the same token is returned by every call. The signature of the command prefix is command tag event details where details contains the argument(s) of the event. Its contents are event specific and have to be agreed upon between actual event gener- ator and consumer. This package simply transfers the information and does not perform any processing beyond that. ::uevent::unbind token This command releases the event binding represented by the token. The token has to be the result of a call to ::uevent::bind. The result of the command is the empty string. ::uevent::generate tag event ?details? This command generates an event for the tag, triggering all commands bound to that combination. The details argument is simply passed unchanged to all event handlers. It is the responsibility of the code generating and consuming the event to have an agreement about the format and contents of the information carried therein. The result of the command is the empty string. Note that all bound commands are triggered, independently of each other. The event handlers cannot assume a specific order. They are also not called synchronously with the invokation of this command, but simply put into the event queue for processing when the sys- tem returns to the event loop. Generating an event for an unknown tag, or for a <tag,event> combination which has no commands bound to it is allowed, such calls will be ignored. ::uevent::list In this form the command returns a list containing the names of all tags which have events with commands bound to them. ::uevent::list tag In this format the command returns a list containing the names of all events for the tag with commands bound to them. Specifying an unknown tag, i.e. a tag without event and commands, will cause the command to throw an error. ::uevent::list tag event In this format the command returns a list containing all commands bound to the event for the tag. Specifying an unknown tag or unknown event, will cause the command to throw an error. BUGS, IDEAS, FEEDBACK This document, and the package it describes, will undoubtedly contain bugs and other problems. Please report such in the category uevent of the Tcllib SF Trackers [http://sourceforge.net/tracker/?group_id=12883]. Please also report any ideas for enhancements you may have for either package and/or documentation. KEYWORDS
bind, event, generate event, unbind CATEGORY
Programming tools COPYRIGHT
Copyright (c) 2007 Andreas Kupries <andreas_kupries@users.sourceforge.net> uev 0.2 uevent(n)
All times are GMT -4. The time now is 08:17 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy