Hiya folks,
I am a windows xp home user and for awhile I have been thinking about changing my OS, the only problem is that I don't know where to start. Is it called Unix or Linux? Are they the same thing? It's really confusing.
I would really appreaciate some help on this. I have looked all... (1 Reply)
suppose I have data in a log file in the below format
date|time|name|email|address|SSN
date|time|name|email|address|SSN
date|time|name|email|address|SSN
is it possible to create a search engine which takes input as three filters out of which two filters should be optional?
say i give... (4 Replies)
Please tell me details about terms FIN, ACK, SYN, RST; used in TCP based communication. Also tell me any RFC or other document which tell me details about these terms. (1 Reply)
I was analyzing a TCP snoop. And found following scenario
From Server to Client ---> SEQ 2993 ACK 1744 WIN 8192 LEN 13
From Server to Client ---> SEQ 3006 ACK 1744 WIN 8192 LEN 13
From Client to server --> SEQ 1744 ACK 3019 WIN 3304
I just want to know Why Packet 1 and 2... (3 Replies)
Hi,
I have the requirement to sniff packets from
the Ethernet card on my Linux machine and
process it and feed it to a RANAP protocol stack.
So far I have written the raw packet sniffer
and successfully sniffing packets and do little
processing. However, for huge number of packets ... (9 Replies)
VOP_READDIR(9) BSD Kernel Developer's Manual VOP_READDIR(9)NAME
VOP_READDIR -- read contents of a directory
SYNOPSIS
#include <sys/param.h>
#include <sys/dirent.h>
#include <sys/vnode.h>
int
VOP_READDIR(struct vnode *vp, struct uio *uio, struct ucred *cred, int *eofflag, int *ncookies, u_long **cookies);
DESCRIPTION
Read directory entries.
vp The vnode of the directory.
uio Where to read the directory contents.
cred The caller's credentials.
eofflag Return end of file status (NULL if not wanted).
ncookies Number of directory cookies generated for NFS (NULL if not wanted).
cookies Directory seek cookies generated for NFS (NULL if not wanted).
The directory contents are read into struct dirent structures. If the on-disc data structures differ from this then they should be trans-
lated.
LOCKS
The directory should be locked on entry and will still be locked on exit.
RETURN VALUES
Zero is returned on success, otherwise an error code is returned.
If this is called from the NFS server, the extra arguments eofflag, ncookies and cookies are given. The value of *eofflag should be set to
TRUE if the end of the directory is reached while reading. The directory seek cookies are returned to the NFS client and may be used later
to restart a directory read part way through the directory. There should be one cookie returned per directory entry. The value of the
cookie should be the offset within the directory where the on-disc version of the appropriate directory entry starts. Memory for the cookies
should be allocated using:
...;
*ncookies = number of entries read;
*cookies = (u_int*)#
malloc(*ncookies * sizeof(u_int), M_TEMP, M_WAITOK);
ERRORS
[EINVAL] An attempt was made to read from an illegal offset in the directory.
[EIO] A read error occurred while reading the directory.
SEE ALSO vnode(9)AUTHORS
This manual page was written by Doug Rabson.
BSD July 24, 1996 BSD