11-16-2008
9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello all -
I have two systems.
1) Linux box running Redhat 8.0
2) Tru64 box running V4.0f
From the Linux box I am remotely mounting a directory (nfs mount) that resides on the Tru64 machine.
The directory that is nfs mounted contains two subdirectories:
my_dir1
my_dir2
I want... (3 Replies)
Discussion started by: Heron
3 Replies
2. Shell Programming and Scripting
how can i write content of a variable to a file?
how can i read standard output into a variable? (1 Reply)
Discussion started by: gfhgfnhhn
1 Replies
3. Shell Programming and Scripting
I have log files that contain data generated every 5 minutes.
I want to extract data from the log files to another log file
In each 5 minute series
<log4j:event logger="VistaMonitor" timestamp="1200688175425" time="Fri Jan 18 15:29:35 EST 2008"
Generated twice (I only to get the date... (2 Replies)
Discussion started by: CathyPro
2 Replies
4. Shell Programming and Scripting
Hi,
I have a script with following file permission on box.
-rwxr-xr-x 1 root system 15347 Aug 14 15:08 b_reboot.ksh
Without calculating or watching at -rwxr-xr-x (permission's) of this above mentioned file. I would like to get the file permission assigned to a file.
Basically... (7 Replies)
Discussion started by: ajilesh
7 Replies
5. Shell Programming and Scripting
In my script, I am creating a file ----> then writting one line (i.e. Timestamp) ----> then FTP'ing. The same script can be executed by many other users.
While other users executing this script, they couldn't Over write this one line (i.e. Timestamp)
My expectation
So I wanted to create a... (2 Replies)
Discussion started by: sbmk_design
2 Replies
6. UNIX for Dummies Questions & Answers
Hi Guys,
I want to know is there any method to create a file having 777 permission. I am aware of umask, since it is only giving max. 666 permission for files this is not fulfilling my needs.
Thanks in advance
---------- Post updated at 12:49 AM ---------- Previous update was at 12:31... (10 Replies)
Discussion started by: sanoop
10 Replies
7. Shell Programming and Scripting
Hi,
I want to create a log file for a running ksh , and the log file absolute path I want to give in ksh itself.
To elaborate this - Say I have a ksh - timer.ksh and I want to create a log timer_log.log when I run, to trace this. I am aware of the fact that this can be done using redirection... (4 Replies)
Discussion started by: vinay4889
4 Replies
8. Shell Programming and Scripting
Hello,
I am looking for a UNIX shell script which can help me for access restriction.
1) /home/ram, there are number file with .txt extension, which should be only owned "ram" user.
like as below
ls -lrt *.txt
-rwx------ 1 ram dba 11 Jan 4 2015 PASS1.txt
-rwx------ 1 ram dba 10 Jan 4... (8 Replies)
Discussion started by: mr.trilok
8 Replies
9. Programming
Hi All,
I'm looking for JAVA code to create file in Linux with specific permission
File should be created and saved in Linux in this path \opt\sys\doc by Java with this permission 764
Anyone can help to provide this Java code (3 Replies)
Discussion started by: AbuAliiiiiiiiii
3 Replies
SYF(1) CAO-VLSI Reference Manual SYF(1)
NAME
SYF - Finite State Machine synthesizer.
ORIGIN
This software belongs to the ALLIANCE CAD SYSTEM developed by the ASIM team at LIP6 laboratory of Universite Pierre et Marie CURIE, in
Paris, France.
Web : http://asim.lip6.fr/recherche/alliance/
E-mail : alliance-users@asim.lip6.fr
SYNOPSIS
syf -a|j|m|u|o|r [-CDEOPRSTV] input_name [output_name]
DESCRIPTION
syf is a Finite State Machine synthesizer. syf allows a fast generation of VHDL Data Flow description (see vbe(5)) from a VHDL Finite
State Machine description (see fsm(5)). The input FSM specification can use an internal STACK. Both MOORE and MEALEY FSMs can be synthe-
sized, with output registers if desired. For a MOORE FSM, a timing-optimized implementation that emulates a ROM with microsequencer is
possible. A scan-path for the state registers can also be implemented.
ENVIRONMENT VARIABLES
MBK_WORK_LIB(1)
indicates the path to the read/write directory for the session.
OPTIONS
-a Uses "Asp" as encoding algorithm.
-j Uses "Jedi" as encoding algorithm.
-m Uses "Mustang" as encoding algorithm.
-u Uses an encoding given by user through <input_name>.enc file. In this file, a line started by a # character is a comment. A
valid line contains one state name followed by its hexadecimal code.
-o Uses the one hot encoding algorithm.
-r Uses distinct random numbers for state encoding.
-C Checks the transition's consistency.
-D With this option syf doesn't optimize unused, i.e Don't Care, codes.
-E Saves the encoding result in the <output_name>.enc. This file has the same syntax as <input_name>.enc file which is used by -u
option.
-O With this option syf places registers on the outputs.
-P Implements a scan-path for the state registers, stack registers and possibly output registers. Scan-path mechanism is directely
included in states decoder. Users should use scapin(5) for a correct insertion of a scan-path in a netlist. Please check fsm(5)
for information about scan-path descriptions.
-R This option is only available for MOORE FSM. With this option, syf emulate s a ROM with micro-sequencer implementation : there is
no combinatorial logic between the state registers and the FSM outputs. This can be mandatory for external timing constraints.
See fsm(5) and grog(1) for more on ROM descriptions.
-S With this option syf doesn't take into account the cost of the transitions to compute an encoding.
-V Verbose mode on. Each step of the FSM synthesis is displayed on the standard output, along with some statistics.
EXAMPLE
Environment variables:
setenv MBK_WORK_LIB /alliance/tutorials/dlxm
syf is called as follow (the dlx_ctrl.fsm is already created in /alliance/tutorials/dlxm) :
syf -sE dlx_ctrl
Two files will be generated, a states encoding file dlx_ctrls.enc and a VHDL data flow file /alliance/tutorials/dlxm/dlx_ctrls.vbe
SEE ALSO
fsm(5), vbe(5), vhdl(5), boom(1), boog(1), loon(1), scapin(1), asimut(1), proof(1), MBK_WORK_LIB(1).
BUG REPORT
This tool is under development at the ASIM department of the LIP6 laboratory.
We need your feedback to improve documentation and tools.
ASIM
/LIP6 October 1, 1997 SYF(1)