From: "Robert Collins" <robert.collins@itdomain.com.au>
To: <cygwin@cygwin.com>, "Randall R Schulz" <rrschulz@cris.com>
Subject: Re: /dev/registry
Date: Fri, 08 Feb 2002 23:42:00 -0000 [thread overview]
Message-ID: <00e801c1b13d$6fe38e30$0200a8c0@lifelesswks> (raw)
In-Reply-To: <5.1.0.14.2.20020206082639.00a9eb48@pop3.cris.com>
===
----- Original Message -----
From: "Randall R Schulz" <rrschulz@cris.com>
> The suggestion about ioctl() begs the question of where to get the
file
> descriptor to which to apply the ioctl() call, and does not open the
> registry to scripting languages that have no direct access to the
Cygwin or
> Windows APIs. It does not really simplify the task of adding the
ability to
> Cygwin, but obscures the basic access behind the obscure and
overloaded
> catch-all interface that is ioctl(). It is true that this would make
> inadvertent registry corruption less likely, but it only by virtue of
> making so much less accessible.
Yah. I've been quite on this one. I'd like to point out that Cygwin has
had a patch for /dev/registry some time ago. I support a good
implementation of this, and like the .dword etc suffix idea. I also
think that a mount command should be *required* to active /dev/registry,
and that a read-only and read-write mode should be provided... to allow
for users with different needs, allowing read only requirements to
result in lower risk.
Rob
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2002-02-09 7:42 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-04 19:57 /dev/registry Gareth Pearce
2002-02-06 3:23 ` /dev/registry Barubary
2002-02-06 3:47 ` /proc (was: Re: /dev/registry) Chris January
2002-02-06 4:24 ` Ralf Habacker
2002-02-06 16:54 ` Chris January
2002-02-07 1:57 ` Pavel Tsekov
2002-02-06 16:51 ` Warren Young
2002-02-06 8:56 ` /dev/registry Randall R Schulz
2002-02-08 23:42 ` Robert Collins [this message]
2002-02-09 10:43 ` /dev/registry Christopher Faylor
2002-02-09 13:17 ` /dev/registry Robert Collins
-- strict thread matches above, loose matches on Subject: below --
2002-02-03 12:07 /dev/registry Chris January
2002-02-03 10:49 ` /dev/registry Gerald Villemure
2002-02-03 11:02 ` /dev/registry Daniel Adams
2002-02-03 11:14 ` /dev/registry Charles Wilson
2002-02-03 12:00 ` /dev/registry Christopher Faylor
2002-02-03 12:07 ` /dev/registry roland
2002-02-03 23:15 ` /dev/registry Gerald Villemure
2002-02-04 0:36 ` /dev/registry Corinna Vinschen
2002-02-04 14:43 ` /dev/registry Greg Mosier
2002-02-04 14:53 ` /dev/registry Michael A Chase
2002-02-05 5:28 ` /dev/registry Lapo Luchini
2002-02-05 9:28 ` /dev/registry Christopher Faylor
2002-02-05 13:46 ` /dev/registry Ralf Habacker
2002-02-05 14:03 ` /dev/registry Larry Hall (RFK Partners, Inc)
2002-02-05 14:07 ` /dev/registry Michael A Chase
2002-02-03 12:07 ` /dev/registry Michael F. March
2002-02-03 12:07 ` /dev/registry Jon Foster
2002-02-03 12:07 ` /dev/registry Lapo Luchini
2002-02-04 18:50 ` /dev/registry Gary R. Van Sickle
2002-02-10 0:18 ` /dev/registry Robert Collins
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='00e801c1b13d$6fe38e30$0200a8c0@lifelesswks' \
--to=robert.collins@itdomain.com.au \
--cc=cygwin@cygwin.com \
--cc=rrschulz@cris.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).