Inside the "install" directory on the floppy is a list of files shown on the attached screenshot. I would guess the INSTALL file is the "setup" but I'll need to know how to run that when I get it copied over. So it looks like I need to cp the files from the floppy to the /tmp and then create the "tar" file to ftp to VM? Do I have that right?
Hi,
I am facing a weired problem in my FTP script. I want to transfer multiple files from remote server to local server everyday, using mget * in my script. I also, want to send an email for successful or failed FTP. My script works for file transfer, but it don't send any mail. There is... (2 Replies)
I am using shell script to do secure ftp. I have done key file setup to do password less authentication. Following are the FTP Details:
FTP Client has Sun SSH.
FTP Server has F-Secure.
I am using SCP Command to do secure copy files. When I am doing this, I am getting the foll error
scp:... (2 Replies)
Hi Experts...
Greetings for the day..!
I just want to FTP the files to mainframe system..
my code is not working..and also i need to put the files in a particular directory in a specific naming format...
ftp -i -n ${HOST_NAME} << END_FTP
user ${USER_NAME} ${PASSWORD}
put ${FILE_NAME}... (3 Replies)
Hi,
I want to run a process on server a, pulling files from server b and pushing it to server c.
Can i do that without dropping the files on server a?
Thanks,
Samit (2 Replies)
Hi ,
We are facing a weird problem in our project. we need to send some xml & audio files to a remote FTP server from a Linux box, we are doing this in Perl script using Net::FTP->. Issue here is.. when FTPed the files using Perl scripts, only empty files ( 0 byte) are getting created on the... (2 Replies)
Validating the size of file transferred from ftp server to the local system.
File type: Text file/Flat file
Source System: Windows / Unix Systems
Target System is always: Unix
Mode of Transfer : ASCII
We have generic ftp shell script that transfers the files from different ftp servers. ... (2 Replies)
I am trying to FTP files to a Windows server through my Linux machine. I have setup the file transfer with no problems but am having problem deleting those files from the Linux box. My current non-working solution is below. Any ideas, anyone?? :wall: Please be gentle, I'm fairly new to this... (4 Replies)
Hi,
I'm new to shell script..I have one requriement like -
In one server have more than one files,I want to ftp those files to some otehr server..
Ex : test1.pdf
test2.pdf
Please suggest me how to do (3 Replies)
I need to transfer files from a Windows server to the Unix server and have to run some shell script on it to get the required output.
Is it possible to transfer files from Windows server to unix server through any shell script?
If so can you please help me with the details.
Thanks in... (8 Replies)
Discussion started by: ssk250
8 Replies
LEARN ABOUT V7
ht
HT(4) Kernel Interfaces Manual HT(4)NAME
ht - RH-11/TU-16 magtape interface
DESCRIPTION
The files mt0, mt1, ... refer to the DEC RH/TM/TU16 magtape. When opened for reading or writing, the tape is not rewound. When closed,
it is rewound (unless the 0200 bit is on, see below). If the tape was open for writing, a double end-of-file is written. If the tape is
not to be rewound the tape is backspaced to just between the two tapemarks.
A standard tape consists of a series of 512 byte records terminated by a double end-of-file. To the extent possible, the system makes it
possible, if inefficient, to treat the tape like any other file. Seeks have their usual meaning and it is possible to read or write a byte
at a time. Writing in very small units is inadvisable, however, because it tends to create monstrous record gaps.
The last octal digit of the minor device number selects the drive. The middle digit selects a controller. The initial digit is even to
select 800 BPI, odd to select 1600 BPI. If the 0200 bit is on (initial digit 2 or 3), the tape is not rewound on close. Note that the
minor device number has no necessary connection with the file name, and in fact tp(1) turns the short name x into `/dev/mtx'.
The mt files discussed above are useful when it is desired to access the tape in a way compatible with ordinary files. When foreign tapes
are to be dealt with, and especially when long records are to be read or written, the `raw' interface is appropriate. The associated files
may be named rmt0, ..., rmt7, but the same minor-device considerations as for the regular files still apply.
Each read or write call reads or writes the next record on the tape. In the write case the record has the same length as the buffer given.
During a read, the record size is passed back as the number of bytes read, provided it is no greater than the buffer size; if the record is
long, an error is indicated. In raw tape I/O, the buffer must begin on a word boundary and the count must be even. Seeks are ignored. A
zero count is returned when a tape mark is read; another read will fetch the first record of the next tape file.
FILES
/dev/mt?, /dev/rmt?
SEE ALSO tp(1)BUGS
The magtape system is supposed to be able to take 64 drives. Such addressing has never been tried.
Taking a drive off line, or running off the end of tape, while writing have been known to hang the system.
If any non-data error is encountered, it refuses to do anything more until closed. In raw I/O, there should be a way to perform forward
and backward record and file spacing and to write an EOF mark explicitly.
HT(4)