06-30-2008
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
OK, the title is a little vague, but basically i was gonig through some files and ran into some strange syntax... heres what it looks like:
... 1&>~/<file extension>
where ... is a chain of commands (the 1&>~ is part of the arguments) and the file extension is just a pointer to a file... (1 Reply)
Discussion started by: DrAwesomePhD
1 Replies
2. Shell Programming and Scripting
export check=$(expandname $(dirname $(which $0))) (2 Replies)
Discussion started by: chandhar
2 Replies
3. Shell Programming and Scripting
can anyone explain the code for me... i am new to shell programming
while getopts ":S:D:U:" OPTION "$@"
do
case $OPTION in
S) SRVR=$OPTARG;;
D) DB="$OPTARG"; USEDB="use $OPTARG";;
U) UID=$OPTARG;;
:) MISSINGOPTARG="$MISSINGOPTARG -$OPTARG";;
?) if
then
... (2 Replies)
Discussion started by: chandhar
2 Replies
4. UNIX for Dummies Questions & Answers
I am trying to list output in columns in csh. What would be the syntax for this shell if in ksh it is: ls -d !(*SNMP*) ? (0 Replies)
Discussion started by: charlie11k
0 Replies
5. Shell Programming and Scripting
IN the book below example showed
find /home/tolstoy -type d -print | Find all directories
sed 's;/home/tolstoy/;/home/lt/;' | Change name, note use of semicolon delimiter
while read newdir Read new directory name
do
mkdir $newdir ... (7 Replies)
Discussion started by: convenientstore
7 Replies
6. Shell Programming and Scripting
I know that I want to entirely replace line 3 in my file filename.txt. I have tried all sorts of variations of
sed 3,3,c\replacement stuff\ filename.txt with no success.
about the only thing that causes any reaction is
sed 3,3c\\ filename.txt
but it just prints out the whole file.
... (13 Replies)
Discussion started by: SusanDAC
13 Replies
7. UNIX for Dummies Questions & Answers
Hi everyone,
I got some code here that I've been working on, but I've gotten stuck. I cant figure out what is wrong with the syntax.
sub cksum{
my $uint32_t = \buffer;
my $word_count;
my $bias;
(
#uint32_t checksum = $bias
$word_count = $bias
while ($word_count>=0)
... (2 Replies)
Discussion started by: TeamUSA
2 Replies
8. Shell Programming and Scripting
hi!
pls help me :)
cd folder
for f in *; do
...
done
this circle takes all files from folder1
i need only .pdf files
but it may be like a.pdf or a.PDF
what syntax must i use?
smth like it:
cd folder
for f in *.(pdf|PDF); do (2 Replies)
Discussion started by: optik77
2 Replies
9. Shell Programming and Scripting
Hi all,
I'm trying to decrypt a GnuPG file but not having much luck. I'm new to using it and have tried 4 different ways to do it but nothing works. Here are examples of the attempts I have made:
gpg -o ./file_name.tar.Z --passphrase-fd 0 ./file_name.tar.Z.gpg 0<./password.txt
cat... (5 Replies)
Discussion started by: Korn0474
5 Replies
10. UNIX for Dummies Questions & Answers
Query with perl syntax
Aim: is to change a perl script to use a new file
I was required to replace
- entries \"$entries\"
with
-lib <full_path_to_filename>
So in the code detector.pm
sub rundetector
{
my $class = shift;
mkdir($resultDirectory);
my... (3 Replies)
Discussion started by: sa@@
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)