linux-kernel - Re: [PATCH 001/001] CHAR DRIVERS: a simple device to give daemons a /sys-like interface

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <5202B674.7060005@linuxtoys.org>
Date:	Wed, 07 Aug 2013 14:04:52 -0700
From:	Bob Smith <bsmith@...uxtoys.org>
To:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
CC:	Arnd Bergmann <arnd@...db.de>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 001/001] CHAR DRIVERS: a simple device to give daemons
 a /sys-like interface

Greg Kroah-Hartman wrote:
>> 	cat /dev/proxyctrl   # what is the offset?
>> 	echo 2 > /dev/proxyctrl  # set offset to 2
>
> You have language bindings right there in bash for this api, what you
> are saying is that you don't want to write new syscall bindings for new
> languages, which is fine, don't do that, use the ones we already have
> for the vast number of different IPC types.

You are correct.  There very much is a protocol in use.  Just as
there is for setting ip_forward in /proc.  And from your previous
comment, it doesn't have to be ASCII.  It could be binary or XML.

>
> What is your specific requirements, I see you couch them in terms of
> what you have created, but none in terms of actual requirements with no
> specific implementation.

You are correct.  I have been giving them in terms of my goal. The
title still captures it: "a simple device to give daemons a /sys-like
interface".

I am not a kernel programmer.  I am an Electrical Engineer trying to
control a robot. So I don't know what you mean by "actual requirements"
or a "specific implementation".   If you point me at a working example
I'll be happy to try to provide these.

>
> And all of my other outstanding questions still remain, please address
> those as well.
Yes, understood.

Greg, once again let me thank you for your patience while dealing
with an EE (who probably needs more adult supervision).

thanks
Bob Smith

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/