12-27-2007
itz not abt "why i would want to do that", its about "why does it happen"... ever since i have started working on unix, i have been fascinated by itss simplicity and consistency... itz so unUNIX like, not allowing to do something that could be done......
anyways thanks for ur help
Its not about "why I would want to do that", its about "why does it happen"... Ever since I have started working on unix, I have been fascinated by its simplicity and consistency. Its so un-unix-like, not allowing to do something that could be done. Anyway, thanks for your help.
See
rule 9 please.
Last edited by blowtorch; 12-27-2007 at 11:54 PM..
Reason: grammar
6 More Discussions You Might Find Interesting
1. HP-UX
Hello,
I'm trying to test if a directory specified in a script parameter is available or not.
I wrote a little code to do so, but there's a problem because I receive an error message.
My code:
#Verify command parameter
if
then
echo 'Incorrect command parameter'
echo... (3 Replies)
Discussion started by: santuna
3 Replies
2. UNIX for Advanced & Expert Users
Hi,
I am trying to test if there are files in a directory and if theres i want to get a list. Any ideas? Thanks in advance (1 Reply)
Discussion started by: RSAM2007
1 Replies
3. Shell Programming and Scripting
This is the code:
while test 1 -eq 1
do
read a
$a
if test $a = stop
then
break
fi
done
I read a command on every loop an execute it.
I check if the string equals the word stop to end the loop,but it say that I gave too many arguments to test.
For example echo hello.
Now the... (1 Reply)
Discussion started by: Max89
1 Replies
4. Shell Programming and Scripting
How to check weather a string is like test* or test* ot *test* in if condition (5 Replies)
Discussion started by: johnjerome
5 Replies
5. Shell Programming and Scripting
Hi,
I have a Python unit test cases source code file which contains more than a hundred test case methods. In that, some of the test case methods already have prefix 'test' where as some of them do not have. Now, I need to add the string 'test' (case-sensitive) as a prefix to those of the... (5 Replies)
Discussion started by: royalibrahim
5 Replies
6. Shell Programming and Scripting
Is there a way for a bash script to test if it can cd into a directory without actually attempting to cd into it?
I am looking for something along the lines of:
if ;then
#code to execute
fi
except in this case I don't want to test if the directory exists; what I want is to test... (8 Replies)
Discussion started by: dexdex200
8 Replies
GO-CLEAN(1) General Commands Manual GO-CLEAN(1)
NAME
go - tool for managing Go source code
SYNOPSIS
go clean [-i] [-r] [-n] [-x] [ packages ]
DESCRIPTION
Clean removes object files from package source directories. The go command builds most objects in a temporary directory, so go clean is
mainly concerned with object files left by other tools or by manual invocations of go build.
Specifically, clean removes the following files from each of the source directories corresponding to the import paths:
_obj/ old object directory, left from Makefiles
_test/ old test directory, left from Makefiles
_testmain.go
old gotest file, left from Makefiles
test.out
old test log, left from Makefiles
build.out
old test log, left from Makefiles
*.[568ao]
object files, left from Makefiles
DIR(.exe)
from go build
DIR.test(.exe)
from go test -c
MAINFILE(.exe)
from go build MAINFILE.go
In the list, DIR represents the final path element of the directory, and MAINFILE is the base name of any Go source file in the directory
that is not included when building the package.
OPTIONS
-i The -i flag causes clean to remove the corresponding installed archive or binary (what 'go install' would create).
-n The -n flag causes clean to print the remove commands it would execute, but not run them.
-r The -r flag causes clean to be applied recursively to all the dependencies of the packages named by the import paths.
-x The -x flag causes clean to print remove commands as it executes them.
For more about specifying packages, see go-packages(7).
AUTHOR
This manual page was written by Michael Stapelberg <stapelberg@debian.org>, for the Debian project (and may be used by others).
2012-05-13 GO-CLEAN(1)