[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: file_operations::llseek

To: "Frank A. Uepping" <Frank.Uepping@t-online.de>
Subject: Re: file_operations::llseek
From: Robert Love <rml@tech9.net>
Date: 31 Jul 2003 16:03:37 -0700
Cc: kernelnewbies@nl.linux.org
In-Reply-To: <19iM6h-1VRbQe0@fwd07.sul.t-online.com>
List-archive: <http://mail.nl.linux.org/kernelnewbies/>
List-help: <mailto:listar@nl.linux.org?Subject=help>
List-owner: <mailto:riel@nl.linux.org>
List-post: <mailto:kernelnewbies@nl.linux.org>
List-software: Listar version 1.0.0
List-subscribe: <mailto:kernelnewbies-request@nl.linux.org?Subject=subscribe>
List-unsubscribe: <mailto:kernelnewbies-request@nl.linux.org?Subject=unsubscribe>
Original-Recipient: rfc822;kernelnewbies-archive@nl.linux.org
References: <19iM6h-1VRbQe0@fwd07.sul.t-online.com>
Sender: kernelnewbies-bounce@nl.linux.org

On Thu, 2003-07-31 at 15:41, Frank A. Uepping wrote:
> How to implement llseek on a chr device that allows only the sequential 
> read/write of bytes (technically, a llseek is not possible)?
> Should I set the llseek field to no_llseek?

If you have no need for an llseek, yes, set llseek to no_llseek.

	Robert Love


--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive:       http://mail.nl.linux.org/kernelnewbies/
FAQ:           http://kernelnewbies.org/faq/

References:
- file_operations::llseek
  - From: Frank.Uepping@t-online.de (Frank A. Uepping)

Prev by Date: file_operations::llseek
Next by Date: Re: ld.script
Prev by thread: file_operations::llseek
Next by thread: Re: ld.script
Index(es):
- Date
- Thread