11-17-2011
Yes, you can burn the ISO as a CD image which you can boot on your computer.
You can also run a Linux or UNIX operating system inside virtualbox or other software like it.
Some distributions can be installed and booted from an external hard drive.
Some people use cygwin to get a UNIX-like shell on their system, but cygwin's a poor imitation of UNIX because, running natively inside the Windows OS, it must still obey all Windows limits and idiosyncrasies -- case-insensitive filenames; either no symbolic links or a very difficult time using symbolic links; named pipes that often don't work; no hard links at all..
I would definitely not recommend dual-booting, installing another OS beside your main one on your main computer, to someone new to UNIX. If you make one mistake in the setup process, you've ruined two operating systems...
Last edited by Corona688; 11-17-2011 at 01:54 PM..
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi!!,
Is there any way on Ksh to test the files having a particular Extension?
My program looks something like:
for i in *$1*
do
if "$i" != files with ext of .Z
then
compress -f $i
fi
done
Any suggestions???
:):) (1 Reply)
Discussion started by: jyotipg
1 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
Hello,
Can you please help me to see if log files exist in a directory?
I need to scan logs in different directories, so I am using an array to change dynamically.
I need help in the if test statement
dir=/logs/MSD
dir=/logs/UPD
countA=1
while (( countA <= ${#dir
} ))
do
cd ${dir}... (1 Reply)
Discussion started by: drbiloukos
1 Replies
6. Shell Programming and Scripting
Hi,
I am checking for existence of files with the same extensions
#! /usr/bin/ksh
txtfiles = '*.txt'
if
then
cp ${dirpath}/${txtfiles} ${dir2path}
fi
I am getting the following error
line 5: [: too many arguments for the if check condition (4 Replies)
Discussion started by: chen.sara
4 Replies
7. Programming
Hello, I have hundreds of text files to be tested.They are generated by many commands. I should check whether a word in specific position is right, or whether a word in file A is equal to a word in file B. All the file are not the same. I decide to use shell to test every files, so I had to write... (7 Replies)
Discussion started by: 915086731
7 Replies
8. Shell Programming and Scripting
Hi there
I have the following code
SDFFILE_SRC=$BACKEND_DIR/$SDFFILE_MIN_tar
SDFFILE_DST=$SIM_DIR/$SDFFILE_MIN
if ]
....
....
....
fi
Simply I need to check if $SDFFILE_SRC isa newer than $SDFFILE_DST or $SDFFILE_DST does not exist then execute the IF Body.
Although the the... (2 Replies)
Discussion started by: aelhosiny
2 Replies
9. Shell Programming and Scripting
So, I need to find a bunch of files and delete them (this example, but sometimes I need it for something else) and my trusty go-to command has always been:
find . -type f -name '*file*' | xargs -I## rm '##'
Works wonders... But:
touch file\ file\'.txt
touch file.txt
touch file\ file.txt... (6 Replies)
Discussion started by: Mr.Glaurung
6 Replies
10. Shell Programming and Scripting
I have c program that I run like this:
./a.out t1
And my test files look like this all the way up to 100:
t1
t2
t3
Is there a way to run this more efficiently so I don't have to hit up and change the number every time? (4 Replies)
Discussion started by: cokedude
4 Replies
LN(1) BSD General Commands Manual LN(1)
NAME
link, ln -- make links
SYNOPSIS
ln [-Ffhinsv] source_file [target_file]
ln [-Ffhinsv] source_file ... target_dir
link source_file target_file
DESCRIPTION
The ln utility creates a new directory entry (linked file) which has the same modes as the original file. It is useful for maintaining mul-
tiple copies of a file in many places at once without using up storage for the ``copies''; instead, a link ``points'' to the original copy.
There are two types of links; hard links and symbolic links. How a link ``points'' to a file is one of the differences between a hard and
symbolic link.
The options are as follows:
-F If the target file already exists and is a directory, then remove it so that the link may occur. The -F option should be used with
either -f or -i options. If none is specified, -f is implied. The -F option is a no-op unless -s option is specified.
-h If the target_file or target_dir is a symbolic link, do not follow it. This is most useful with the -f option, to replace a symlink
which may point to a directory.
-f If the target file already exists, then unlink it so that the link may occur. (The -f option overrides any previous -i options.)
-i Cause ln to write a prompt to standard error if the target file exists. If the response from the standard input begins with the char-
acter 'y' or 'Y', then unlink the target file so that the link may occur. Otherwise, do not attempt the link. (The -i option over-
rides any previous -f options.)
-n Same as -h, for compatibility with other ln implementations.
-s Create a symbolic link.
-v Cause ln to be verbose, showing files as they are processed.
By default, ln makes hard links. A hard link to a file is indistinguishable from the original directory entry; any changes to a file are
effectively independent of the name used to reference the file. Hard links may not normally refer to directories and may not span file sys-
tems.
A symbolic link contains the name of the file to which it is linked. The referenced file is used when an open(2) operation is performed on
the link. A stat(2) on a symbolic link will return the linked-to file; an lstat(2) must be done to obtain information about the link. The
readlink(2) call may be used to read the contents of a symbolic link. Symbolic links may span file systems and may refer to directories.
Given one or two arguments, ln creates a link to an existing file source_file. If target_file is given, the link has that name; target_file
may also be a directory in which to place the link; otherwise it is placed in the current directory. If only the directory is specified, the
link will be made to the last component of source_file.
Given more than two arguments, ln makes links in target_dir to all the named source files. The links made will have the same name as the
files being linked to.
When the utility is called as link, exactly two arguments must be supplied, neither of which may specify a directory. No options may be sup-
plied in this simple mode of operation, which performs a link(2) operation using the two passed arguments.
COMPATIBILITY
The -h, -i, -n and -v options are non-standard and their use in scripts is not recommended. They are provided solely for compatibility with
other ln implementations.
The -F option is FreeBSD extention and should not be used in portable scripts.
SEE ALSO
link(2), lstat(2), readlink(2), stat(2), symlink(2), symlink(7)
STANDARDS
The ln utility conforms to IEEE Std 1003.2-1992 (``POSIX.2'').
The simplified link command conforms to Version 2 of the Single UNIX Specification (``SUSv2'').
HISTORY
An ln command appeared in Version 1 AT&T UNIX.
BSD
February 14, 2006 BSD