Intro: Josh


 
Thread Tools Search this Thread
The Lounge What is on Your Mind? Intro: Josh
# 1  
Old 08-09-2007
Intro: Josh

Hey,

I had been working in UNIX environments from 1997 to 2007.

From 1997 - 1999 I worked as an Operator in a Solaris environment.

From 1999 - March 2007 I worked mostly in HP-UX, some SCO, some RedHat Linux as an Operator/Programmer(scripter)/Admin.

No luck finding work, so I am going to try and stay connected to UNIX by participating in these forums.

So if you are reading this, what do you do with UNIX?
Login or Register to Ask a Question

Previous Thread | Next Thread

5 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

intro to UNIX - making a sort-of recycle bin (for fun)

Hello, I'm only taking Intro to UNIX in school right now, so please bear with me. My problem is with a sort-of recycle-bin rig I've created for fun. I'm using Ubuntu 9.04, I am the admin. (only user, actually) of this computer. I'm using this script in ~/.bashrc # if files exist, remove contents... (6 Replies)
Discussion started by: jzacsh
6 Replies

2. What is on Your Mind?

Intro ( Mark Thomas )

Houdy everyone! yes I'm a newbie here I'm a big fan of the BSD's, in particular NetBSD. Don't have much use for Linux or the various "distro's" of it ( no flame intended ). I'm going to try Solaris 10 on an i386 box real soon. By day I'm a CAD tech for a local government entity, by night... (0 Replies)
Discussion started by: Mark Thomas
0 Replies

3. Tips and Tutorials

PERL & CPAN Intro for Newbies

So you want to learn a unix scripting language that you'll be able to use in any situation? Perl is your answer ! This is a little intro to installing CPAN modules. If you don't know what CPAN is, check out http://search.cpan.org/. Basicly, it is a massive archive of perl libraries that will... (0 Replies)
Discussion started by: obitus
0 Replies

4. Post Here to Contact Site Administrators and Moderators

New Flash intro from Forum Member.....

New submission for flash intro: What do you think? (2 Replies)
Discussion started by: Neo
2 Replies

5. Post Here to Contact Site Administrators and Moderators

Our First Flash Intro ?

Well, someone created a flash intro for us (their first attempt at SWiSH!) OK, SECOND DRAFT: https://www.unix.com/test_intro2.swf --------------------------- FIRST DRAFT: https://www.unix.com/test_intro1.swf Notice it says "Search before posting a question"..... Well????... (24 Replies)
Discussion started by: Neo
24 Replies
Login or Register to Ask a Question
RCSCLEAN(1)						      General Commands Manual						       RCSCLEAN(1)

NAME
rcsclean - clean up working files SYNOPSIS
rcsclean [options] [ file ... ] DESCRIPTION
rcsclean removes files that are not being worked on. rcsclean -u also unlocks and removes files that are being worked on but have not changed. For each file given, rcsclean compares the working file and a revision in the corresponding RCS file. If it finds a difference, it does nothing. Otherwise, it first unlocks the revision if the -u option is given, and then removes the working file unless the working file is writable and the revision is locked. It logs its actions by outputting the corresponding rcs -u and rm -f commands on the standard output. Files are paired as explained in ci(1). If no file is given, all working files in the current directory are cleaned. Pathnames matching an RCS suffix denote RCS files; all others denote working files. The number of the revision to which the working file is compared may be attached to any of the options -n, -q, -r, or -u. If no revision number is specified, then if the -u option is given and the caller has one revision locked, rcsclean uses that revision; otherwise rcsclean uses the latest revision on the default branch, normally the root. rcsclean is useful for clean targets in makefiles. See also rcsdiff(1), which prints out the differences, and ci(1), which normally reverts to the previous revision if a file was not changed. OPTIONS
-ksubst Use subst style keyword substitution when retrieving the revision for comparison. See co(1) for details. -n[rev] Do not actually remove any files or unlock any revisions. Using this option will tell you what rcsclean would do without actually doing it. -q[rev] Do not log the actions taken on standard output. -r[rev] This option has no effect other than specifying the revision for comparison. -T Preserve the modification time on the RCS file even if the RCS file changes because a lock is removed. This option can suppress extensive recompilation caused by a make(1) dependency of some other copy of the working file on the RCS file. Use this option with care; it can suppress recompilation even when it is needed, i.e. when the lock removal would mean a change to keyword strings in the other working file. -u[rev] Unlock the revision if it is locked and no difference is found. -V Print RCS's version number. -Vn Emulate RCS version n. See co(1) for details. -xsuffixes Use suffixes to characterize RCS files. See ci(1) for details. -zzone Use zone as the time zone for keyword substitution; see co(1) for details. EXAMPLES
rcsclean *.c *.h removes all working files ending in .c or .h that were not changed since their checkout. rcsclean removes all working files in the current directory that were not changed since their checkout. FILES
rcsclean accesses files much as ci(1) does. ENVIRONMENT
RCSINIT options prepended to the argument list, separated by spaces. A backslash escapes spaces within an option. The RCSINIT options are prepended to the argument lists of most RCS commands. Useful RCSINIT options include -q, -V, -x, and -z. DIAGNOSTICS
The exit status is zero if and only if all operations were successful. Missing working files and RCS files are silently ignored. IDENTIFICATION
Author: Walter F. Tichy. Manual Page Revision: 1999-08-27; Release Date: 23:37:10Z. Copyright (C) 1982, 1988, 1989 Walter F. Tichy. Copyright (C) 1990, 1991, 1992, 1993 Paul Eggert. SEE ALSO
ci(1), co(1), ident(1), rcs(1), rcsdiff(1), rcsintro(1), rcsmerge(1), rlog(1), rcsfile(5) Walter F. Tichy, RCS--A System for Version Control, Software--Practice & Experience 15, 7 (July 1985), 637-654. BUGS
At least one file must be given in older Unix versions that do not provide the needed directory scanning operations. GNU
23:37:10Z RCSCLEAN(1)