Sponsored Content
Full Discussion: Dummy Questions
Top Forums UNIX for Dummies Questions & Answers Dummy Questions Post 302085448 by slayer666 on Thursday 17th of August 2006 10:12:31 AM
Old 08-17-2006
to be more clear
these are questions from last years quizez
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Dummy Needs Help

I am ftp-ing (I think) files from one computer to another and I am using the Put command to do this. Is there a way for me to string these commands together and Put several files at once? Thanks, Amy (4 Replies)
Discussion started by: amygdala
4 Replies

2. UNIX for Advanced & Expert Users

Using dummy files

what do you record or look for when using these dummy files to test I/O throughput on disk drives. i have no clue and reading from books sure aint helping much. i know all about the creation and every other thing there is to it but when it comes to actual testing, how do i use them this is... (4 Replies)
Discussion started by: TRUEST
4 Replies

3. UNIX for Dummies Questions & Answers

Unix Dummy

i need to learn unix real quick and i have completely no idea how. could anyone please tell me how to get material to get me going??? I am IT oriented. PLEASE ANY ONE???????????????? :confused: (3 Replies)
Discussion started by: quarmenna
3 Replies

4. Shell Programming and Scripting

Dummy need help :(

This drive me nut, any can show me how to do it ?? str1='Case Modify 10001 20002 30003 40004|Report Create 3417176211|Case Modify 10002 20002 30003 40004' and str2='Case Modify 10001' if str1 ~ str2 then str1='Report Create 3417176211|Case Modify 10002 20002 30003 40004' Thanks, (8 Replies)
Discussion started by: sabercats
8 Replies

5. Shell Programming and Scripting

Dummy questions about how to get the size of a directory by command

Hi, 'ls -ld' is no use .... I want to get the total size of a directory including subdir. Any advice? Thanks in advance (2 Replies)
Discussion started by: GCTEII
2 Replies

6. UNIX for Dummies Questions & Answers

Dummy questions about how to get the size of a directory by command

Hi, 'ls -ld' is no use .... I want to get the total size of a directory. Any advice? Thanks in advance! (4 Replies)
Discussion started by: GCTEII
4 Replies

7. UNIX for Dummies Questions & Answers

more questions froma a dummy

thanks all fro your help on my last question my Unix class is officially my least favorite :( as I am not sure I will ever get it :confused: :eek: . okay so I have a couple more these may seem basic but I had never heard of UNIX untill last week when classes started. first of what does the tty,... (2 Replies)
Discussion started by: cinnamonbear
2 Replies

8. Shell Programming and Scripting

Unix Dummy!

Hi everyone!! i need some help to do the next exercice, if some one can help-me! Perform a script to swap two lines of a file. The name of file as the two line numbers are passed as a parameter. It should be verify that the file exists, have the necessary permits and lines. i try... (3 Replies)
Discussion started by: freixo
3 Replies

9. Homework & Coursework Questions

Print questions from a questions folder in a sequential order

1.) I am to write scripts that will be phasetest folder in the home directory. 2.) The folder should have a set-up,phase and display files I have written a small script which i used to check for the existing users and their password. What I need help with: I have a set of questions in a... (19 Replies)
Discussion started by: moraks007
19 Replies

10. UNIX for Beginners Questions & Answers

Dummy Question

Where can I get UNIX? (1 Reply)
Discussion started by: ciao303
1 Replies
bart_rules(4)							   File Formats 						     bart_rules(4)

NAME
bart_rules - bart rules file DESCRIPTION
The bart_rules file is a text file that is used by the bart(1M) command. The rules file determines which files to validate and which file attributes of those files to ignore. Some lines are ignored by the manifest comparison tool. Ignored lines include blank lines, lines that consist only of white space, and com- ments that begin with #. The rules file supports three directives: CHECK, IGNORE, and a subtree directive, which is an absolute path name and optional pattern matching modifiers. Each CHECK, IGNORE, and subtree directive must be on a separate line. Bart supports continuation of long lines using a backslash (). The rules file uses the directives to create logical blocks. Syntax The syntax for the rules file is as follows: [IGNORE attribute...]* [CHECK] [attribute...]* subtree1 [pattern...]* [IGNORE attribute...]* [CHECK] [attribute...]* subtree2 [pattern...]* subtree3 [pattern...]* subtree4 [pattern...]* [IGNORE attribute...]* [CHECK] [attribute...]* ... Rule Blocks Rule blocks are composed of statements that are created by using directives and arguments. There are three types of blocks: Global Block The first block in the file. The block is considered ``global'' if it specifies CHECK and IGNORE statements, but no previ- ous subtree statement. A global block pertains to all subsequent blocks. Local block A block that specifies CHECK and IGNORE statements as well as a subtree directive. The rules in this block pertain to files and directories found in the specified subtree. Heir block A block that contains a null CHECK statement, no arguments. This block inherits the global CHECK statements and IGNORE statements. The order in which CHECK and IGNORE statements appear in blocks is important. The bart command processes CHECK and IGNORE statements in the order in which they are read, with later statements overriding earlier statements. Subtree specifications must appear one per line. Each specification must begin with an absolute path name. Optionally, each specification can be followed by pattern-matching arguments. When a file system being tracked belongs to more than one subtree directive, bart performs the following resolution steps: o Applies the CHECK and IGNORE statements set in the global block. Note that all CHECK and IGNORE statements are processed in order. o Finds the last subtree directive that matches the file. o Processes the CHECK and IGNORE statements that belong to the last matching subtree directive. These statements are processed in the order in which they are read, overriding global settings. Pattern Matching Statements There are two types of pattern matching statements AND For a given subtree directive, all pattern matching statements are logically ANDed with the subtree. Patterns have the following syntax: o Wildcards are permitted for both the subtree and pattern matching statements. o The exclamation point (!) character represents logical NOT. o A pattern that terminates with a slash is a subtree. The absence of a slash indicates that the pattern is not a direc- tory. The subtree itself does not require an end slash. For example, the following subtree example includes the contents of /home/nickiso/src except for object files, core files, and all of the SCCS subtrees. Note that directory names that terminate with .o and directories named core are not excluded because the pat- terns specified do not terminate with /. /home/nickiso/src !*.o !core !SCCS/ CHECK all OR Group multiple subtree directives together. Such subtree directives are logically ORed together. /home/nickiso/src !*.o !core /home/nickiso/Mail /home/nickiso/docs *.sdw CHECK all IGNORE mtime lnmtime dirmtime The files included in the previous example are as follows: o Everything under /home/nickiso/src except for *.o and core files o Everything under /home/nickiso/Mail o All files under /home/nickiso/docs that end in *.sdw For these files, all attributes are checked except for modification times. File Attributes The bart command uses CHECK and IGNORE statements to define which attributes to track or ignore. Each attribute has an associated keyword. The attribute keywords are as follows: acl ACL attributes for the file. For a file with ACL attributes, this field contains the output from acltotext(). all All attributes. contents Checksum value of the file. This attribute is only specified for regular files. If you turn off context checking or if check- sums cannot be computed, the value of this field is -. dest Destination of a symbolic link. devnode Value of the device node. This attribute is for character device files and block device files only. dirmtime Modification time in seconds since 00:00:00 UTC, January 1, 1970 for directories. gid Numerical group ID of the owner of this entry. lnmtime Creation time for links. mode Octal number that represents the permissions of the file. mtime Modification time in seconds since 00:00:00 UTC, January 1, 1970 for files. size File size in bytes. type Type of file. uid Numerical user ID of the owner of this entry. EXAMPLES
Example 1 Sample Rules File The following is a sample rules file: # Global rules, track everything except dirmtime. CHECK all IGNORE dirmtime # The files in /data* are expected to change, so don't bother # tracking the attributes expected to change. # Furthermore, by specifying ``IGNORE contents,'' you save # time and resources. /data* IGNORE contents mtime size /home/nickiso f* bar/ IGNORE acl # For /usr, apply the global rules. /usr CHECK # Note: Since /usr/tmp follows the /usr block, the /usr/tmp # subtree is subjected to the ``IGNORE all.'' /usr/tmp /home/nickiso *.o /home/nickiso core /home/nickiso/proto IGNORE all The following files are cataloged based on the sample rules file: o All attributes, except for dirmtime, mtime, size, and contents, are tracked for files under the /data* subtrees. o Files under the /usr subtree, except for /usr/tmp, are cataloged by using the global rules. o If the /home/nickiso/foo.c file exists, its attributes, except for acl and dirmtime, are cataloged. o All .o and core files under /home/nickiso, as well as the /home/nickiso/proto and /usr/tmp subtrees, are ignored. o If the /home/nickiso/bar/foo.o file exists, it is ignored because it is subject to the last block. SEE ALSO
bart(1M), bart_manifest(4), attributes(5) SunOS 5.11 9 Sep 2003 bart_rules(4)
All times are GMT -4. The time now is 11:11 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy