02-21-2010
Quote:
Originally Posted by
sponnusa
I don't know what causes the write call to pass always!
Well, you're not doing raw I/O. Really only the kernel can do truly raw I/O, and worrying about write errors is the kernel's job.
If writes don't fail, what about reads? Try reading the data back.
7 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I want to do a low level format like in windows (C:\format c:) but I don't know how it works in unix or linux.. Can somebody help me ? thnx :) (3 Replies)
Discussion started by: day
3 Replies
2. HP-UX
Hello
How to access to a second hard disk on a HP-UX system?
Thanks (3 Replies)
Discussion started by: ouniss
3 Replies
3. IP Networking
Hi,
What is the best reference that gives in detail on nic cards configuration , assigning multiple ip addresses to a single interface, netlink library etc and all basic stuff at this level..?
Thanks (2 Replies)
Discussion started by: Gopi Krishna P
2 Replies
4. AIX
Hello All
I have a system running AIX 61 shared uncapped partition (with 11 physical processors, 24 Virtual 72GB of Memory) .
The output from NMON, vmstat show a high run queue (60+) for continous periods of time intervals, but NO paging, relatively low I/o (6000) , CPU % is 40, Low network.... (9 Replies)
Discussion started by: IL-Malti
9 Replies
5. Programming
Hi friends,
I hope everyone is fine and doing well. I queried in my previous thread about the low-level qualities of C/C++ languages.I really thank you people for explaining, it was really helpful. One more ambiquity that I have in my mind is regarding the unix system calls like open, creat,... (1 Reply)
Discussion started by: gabam
1 Replies
6. Programming
Hi friends,
I hope everyone is doing well and fine. I have always been hearing that C/C++ are relatively low-level as compared to Java/C# etc. Could you please tell me some low-level qualities of C/C++? And I think disk deframenters are written in C/C++, please correct me if I am wrong. And please... (5 Replies)
Discussion started by: gabam
5 Replies
7. Programming
How to use X11 without Xlib not XCB? How draw window directly on low level?
I must use anyway window manager like Motif?
I have ridden that X11 has server-client architecture, client send via TCP/IP to port 6000 request for primitives and get replies.
Where is detailed description of it? In X11... (0 Replies)
Discussion started by: AndrzejB
0 Replies
TM(4) Kernel Interfaces Manual TM(4)
NAME
tm - TM-11/TU-10 magtape interface
DESCRIPTION
The files mt0, ..., mt7 refer to the DEC TU10/TM11 magtape. When closed it can be rewound or not, see below. If it was open for writing,
two end-of-files are written. If the tape is not to be rewound it is positioned with the head between the two tapemarks.
If the 0200 bit is on in the minor device number the tape is not rewound when closed.
A standard tape consists of a series of 512 byte records terminated by an end-of-file. To the extent possible, the system makes it possi-
ble, 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 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
are named rmt0, ..., rmt7. 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 byte count is returned when a tape mark is read, but another read will fetch the first record of the new
tape file.
FILES
/dev/mt?, /dev/rmt?
SEE ALSO
tp(1)
BUGS
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.
TM(4)