03-22-2002
Actually, it is NOT "\n" in Windows. The OS actually
converts text files to represent end-of-line as "\r\n" (CR-LF) when
stored to disk. UNIX however has no such "oddities".
UNIX text files use "\n" to represent end-of-line.
Actually, to UNIX, there is no difference between a binary
or a text file when stored on disk.
If you are using some sort of Windows to UNIX FTP program,
usually selecting "text" file format will do the conversion
for you. Some editors will also do this conversion for you.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I am a completely newby in this forum and a completely newby in Unix too. I have searched this question before I posted it to this forum, but forgive me if it was previously answered! :)
My question is simple. I have a Unix K-shell that receives an argument. But this argument is always between... (2 Replies)
Discussion started by: lvalero
2 Replies
2. UNIX for Dummies Questions & Answers
Hello Forum,
I am having an odd occurence. When i do a su in a terminal or console session, I am able get authenticated as superuser without using the full or correct root password. Anyone have any idea?
-AJ (4 Replies)
Discussion started by: jacobsa
4 Replies
3. UNIX for Dummies Questions & Answers
I am using smartFTP client on my windows machine to connect to a linux box of mine (different location) to download some large files 100+meg. The linux box is running vsftp.
After several minutes of downloading, the connection suddenly dies, and I cannot reconnect to the box via FTP using ANY... (7 Replies)
Discussion started by: Spetnik
7 Replies
4. AIX
Hi,
I have a strange problem. we're trying to connect an IBM pseries, to a Brocade switch, for SAN acess, using a badged emulex card, (IBM FC6239) WE can configure the device to see the fabric. The only problem we have is that the Brocade sees the HBA as storage, and not as a HBA.
We've zoned... (1 Reply)
Discussion started by: praxis22
1 Replies
5. UNIX for Dummies Questions & Answers
I discovered that where 'tr -s' works as expected on grepped input, it appears to completely fail on dig results.
I am not sure if this is because of some sort of non posix compliancy, or what.
Here is what I did:
The command below works as expected, squeezing all repeated spaces to a single... (3 Replies)
Discussion started by: bdmeyersc
3 Replies
6. BSD
Our webserver is running FreeBSD, for the last few days we have been having an issue with our cronjobs/mysql server.
Specifically we have jobs that execute php scripts to do various things to the website. When running these php scripts manually, via external browser, or lynx on the server, they... (8 Replies)
Discussion started by: mrfr0g
8 Replies
7. Solaris
All,
I'm baffled by some sort behavior on SunOS 5.10 and looking for guidance.
Running the command:
sort -t'|' -k5,5 -k7,7 -k1,1 -k2,2 -k3,3 -k6,6 -k8,8 test
Against the file "test":
thirdA||||first||second|Data
thirdB||||first||second|
thirdC||||first||second|Data... (11 Replies)
Discussion started by: effigy
11 Replies
8. Shell Programming and Scripting
Hi,
Does anyone know of any permission bit "translator"? One that can translate the permission bit from its textual value to its octal value and vice versa. It is alright if it is always just rwx but on a lot of occasions nowadays, getting a lots of s, S, t, etc.
-rwxrwxrwx 1 oracle dba... (4 Replies)
Discussion started by: newbie_01
4 Replies
9. UNIX for Dummies Questions & Answers
I have to apologize for my ignorance so this question is probably stupid.
How does awk process a file? Does it read from top of input file to end of file going line by line?
Yoda helped me create an awk script that helps me parse the named.conf file and output it into a .csv file but when... (8 Replies)
Discussion started by: djzah
8 Replies
10. Shell Programming and Scripting
Hi all, I'm trying to use bash to create a basic parser for some text, because basic grep/sed/awk have all my needs covered.
So, I'm creating the chain of grep/sed I need and trying the execute that on the data I gather.
The problem is, it's not working as it does when hardcoded.
e.g.
... (3 Replies)
Discussion started by: beomagi
3 Replies
HCOPY(1) General Commands Manual HCOPY(1)
NAME
hcopy - copy files from or to an HFS volume
SYNOPSIS
hcopy [-m|-b|-t|-r|-a] source-path [...] target-path
DESCRIPTION
hcopy transfers files from an HFS volume to UNIX or vice versa. The named source files are copied to the named destination target, which
must be a directory if multiple files are to be copied.
Copies are performed using a translation mode, which must be one of:
-m MacBinary II: A popular format for binary file transfer. Both forks of the Macintosh file are preserved. This is the recommended
mode for transferring arbitrary Macintosh files.
-b BinHex: An alternative format for ASCII file transfer. Both forks of the Macintosh file are preserved.
-t Text: Performs end-of-line translation. Only the data fork of the Macintosh file is copied.
-r Raw Data: Performs no translation. Only the data fork of the Macintosh file is copied.
-a Automatic: A mode will be chosen automatically for each file based on a set of predefined heuristics.
If no mode is specified, -a is assumed.
If a UNIX source pathname is specified as a single dash (-), hcopy will copy from standard input to the HFS destination. Likewise, a single
dash used as a UNIX destination pathname will cause hcopy to copy the HFS source to standard output.
NOTES
Copied files may have their filenames altered during translation. For example, an appropriate file extension may be added or removed, and
certain other characters may also be transliterated.
The destination target must not be ambiguous; that is, it must be obvious whether the target is on the UNIX filesystem or on an HFS volume.
As a rule, HFS targets must contain at least one colon (:), usually as the beginning of a relative pathname or by itself to represent the
current working directory. To make a UNIX target unambiguous, either use an absolute pathname or precede a relative pathname with a dot and
slash (./).
SEE ALSO
hfsutils(1), hls(1), hattrib(1)
AUTHOR
Robert Leslie <rob@mars.org>
HFSUTILS
13-Jan-1997 HCOPY(1)