Hi,
i wrote:
> > Why there are two sets of file accessing system calls must have historical
> > reasons.
to...@tuxteam.de wrote:
> [...] file descriptor is a
> kernel thing, FILE* is libc, i.e. userspace [1] (I know *you* know it,
> but it might be interesting for others).
Well, at least it did
cor...@free.fr (12023-07-13):
> In linux systems, are file descriptor and file handle meaning the same
> stuff?
File descriptors are the standards Unix file descriptors.
In the Unix specification, the word handle is used to designate either a
file descriptor or a FILE * pointer of the stdio
On Thu, Jul 13, 2023 at 08:49:38AM +0200, Thomas Schmitt wrote:
> Hi,
>
> cor...@free.fr wrote:
> > In linux systems, are file descriptor and file handle meaning the same
> > stuff?
>
> In the programming language C on Linux (more generally: on POSIX systems)
> "File descriptor" is an integer
Hi,
cor...@free.fr wrote:
> In linux systems, are file descriptor and file handle meaning the same
> stuff?
In the programming language C on Linux (more generally: on POSIX systems)
"File descriptor" is an integer number handed out by system calls like
open(2), pipe(2), socket(2), and others. It
cor...@free.fr wrote:
> In linux systems, are file descriptor and file handle meaning the same
> stuff?
Almost.
A file handle is a variable that can hold a file descriptor. You
might reuse the file handle to hold a different file descriptor
later.
-dsr-
5 matches
Mail list logo
