10-20-2005
state machine...
hi,
I am looking for some info on how can we implement state machines.
Conceptually it appears to be good but while implementing it causes lot of confusion..
I have some doubts regarding this concept.
(my explanation may look wired, as I am also not clear on this front)
The commonly adopted strategy to implement state machine is to have array of function pointers to handle a state. When ever appropriate input is recv the array is activated or used to trigger the functions.
(I don't have solid example, sorry for making it difficult to understand)
Can somebody add some info on this...
Regards,
Parasa Kiran
Last edited by parasa; 10-20-2005 at 06:50 AM..
7 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
I am very new to this. I would like to compile the Mach 3.0 kernel. Can someone explain, step-by-step, how to turn all the Mach 3.0 kernel code into a single binary file that will run directly on an x86 computer?
Also, once (and if) I get it working, what software works on it? My goal is... (2 Replies)
Discussion started by: dublinus
2 Replies
2. Shell Programming and Scripting
HI experts
I updated my question here to
eg:
$cat file
ABC: abc ABC FDFD
USB: usb usb_name usb_disk usbdriver USB
PA: PA pa paa
I want to how many usb exactly matched(not match usb_name or usbdriver) in the line cotains"USB:"
thanks in advance (19 Replies)
Discussion started by: yanglei_fage
19 Replies
3. UNIX for Dummies Questions & Answers
hello everyone,
can anyone tell me what drivers the Mach kernel works with. I'm thinking about experimenting with the Mach kernel, and yes I know there are other kernels that are easier to work with but I just want to use the Mach kernel. So with that being said, can the Mach kernel work with... (11 Replies)
Discussion started by: neur0n
11 Replies
4. UNIX for Dummies Questions & Answers
hey everyone,
I'm reading a tutorial on the Mach kernel principles, however, the port and port rights part are kind of confusing to me. I don't know if the book has typos or something but it seems a bit contradictory. It says that "ports, themselves, are not named. It is the port rights that are"... (10 Replies)
Discussion started by: neur0n
10 Replies
5. Solaris
Hi all,
One of my zone is stuck in down state, not able to boot it or halt it
root@xpm9ka1 # zoneadm list -iv
ID NAME STATUS PATH BRAND IP
0 global running / native shared
2 bsmrxdb4 down /zones/bsmrxdb4 native shared
root@xpm9ka1 # zoneadm -z bsmrxdb4 boot
zoneadm: zone... (6 Replies)
Discussion started by: peppeunz
6 Replies
6. Shell Programming and Scripting
Hi
Input File A
L006 AL01 0 (OCK)
L006 A006 0 (OCK)
L011 AR11 1 (NLOCK)
Input File B
L006 AL01 0 (OCK)
L006 A006 0 (OCK)
Need Egrep Command for perfect Match
Thanks (4 Replies)
Discussion started by: asavaliya
4 Replies
7. AIX
Hi Admins,
I am having a whole system lpar in open firmware state on HMC.
How can I bring it to running state ?
Let me know. Thanks. (2 Replies)
Discussion started by: snchaudhari2
2 Replies
LEARN ABOUT BSD
deb-triggers
deb-triggers(5) dpkg suite deb-triggers(5)
NAME
deb-triggers - package triggers
SYNOPSIS
triggers
DESCRIPTION
A package declares its relationship to some trigger(s) by including a triggers file in its control archive (i.e. DEBIAN/triggers during
package creation).
This file contains directives, one per line. Leading and trailing whitespace and everything after the first # on any line will be trimmed,
and empty lines will be ignored.
The trigger control directives currently supported are:
interest trigger-name
interest-await trigger-name
interest-noawait trigger-name
Specifies that the package is interested in the named trigger. All triggers in which a package is interested must be listed using
this directive in the triggers control file. The "noawait" variant does not put the triggering packages in triggers-awaited state.
This should be used when the functionality provided by the trigger is not crucial.
activate trigger-name
activate-await trigger-name
activate-noawait trigger-name
Arranges that changes to this package's state will activate the specified trigger. The trigger will be activated at the start of the
following operations: unpack, configure, remove (including for the benefit of a conflicting package), purge and deconfigure. The
"noawait" variant does not put the triggering packages in triggers-awaited state. This should be used when the functionality
provided by the trigger is not crucial.
If this package disappears during the unpacking of another package the trigger will be activated when the disappearance is noted
towards the end of the unpack. Trigger processing, and transition from triggers-awaited to installed, does not cause activations.
In the case of unpack, triggers mentioned in both the old and new versions of the package will be activated.
Unknown directives are an error which will prevent installation of the package.
The "-noawait" variants should always be favored when possible since triggering packages are not put in triggers-awaited state and can thus
be immediately configured without requiring the processing of the trigger. If the triggering packages are dependencies of other upgraded
packages, it will avoid an early trigger processing run and make it possible to run the trigger only once as one of the last steps of the
upgrade.
The "-noawait" variants are supported since dpkg 1.16.1, and will lead to errors if used with an older dpkg.
The "-await" alias variants are supported since dpkg 1.17.21, and will lead to errors if used with an older dpkg.
SEE ALSO
dpkg-trigger(1), dpkg(1), /usr/share/doc/dpkg-dev/triggers.txt.gz.
1.19.0.5 2018-04-16 deb-triggers(5)