On Sun, May 05, 2002 at 01:54:37PM -0700, Randall R Schulz wrote:
>Chris, Chris, Chris,
>
>Here are a couple of alternate ideas:
>
>1) Require a mount to access /proc (or just /proc/registry).
>From my Thu, 2 May 2002 22:47:31 -0400 mail:
>Long term, this kind of stuff should be somehow "mountabl
Chris, Chris, Chris,
Here are a couple of alternate ideas:
1) Require a mount to access /proc (or just /proc/registry). Use a
mount-time option to enable writability of the registry portion of /proc
(an option to the mount command and a bit in the __flags argument to the
mount system call).
On Fri, 3 May 2002, Robert Collins wrote:
> Two things: if /proc/registry isn't writable, cating 1 to
> /proc/registry/.writeable won't work - without special case code. I'd
> suggest /proc/sysopts/fs/registry/writeable.
>
> Two, why not have two options:
> writeable
> nextwrite
>
> one is persi
> > Hi
> >
> > Cool feature.
> >
> >
> > 08:31am [507]> cat /proc/uptime
> > 3728.83
> > 08:31am [506]> cat < /proc/uptime
> >
> > Boom, cat stack dumbs.
> Chris' implementation of dup() in fhander_virtual is broken, so things
like
> fork(), etc. won't work.
That should read: "My implementation...
> Hi
>
> Cool feature.
>
>
> 08:31am [507]> cat /proc/uptime
> 3728.83
> 08:31am [506]> cat < /proc/uptime
>
> Boom, cat stack dumbs.
Chris' implementation of dup() in fhander_virtual is broken, so things like
fork(), etc. won't work.
Regards
Chris
--
Unsubscribe info: http://cygwin.com/m
> >I see you have made the fhandler_virtual, etc. functions use vanilla
> >path_conv instead of normalized_path or whatever I called it
> >originally.
>
> Yes. This is consistent with all of the other fhandler functions.
>
> >This relies on path_conv::check returning the normalised posix path
in
Just looked at it.
Nice.
Seems to barf on colons in filenames, though, which do occur in the
registry.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: h
Hi
Cool feature.
08:31am [507]> cat /proc/uptime
3728.83
08:31am [506]> cat < /proc/uptime
Boom, cat stack dumbs.
Ciao
Volker
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/do
Robert Collins wrote:
> Two things: if /proc/registry isn't writable, cating 1 to
> /proc/registry/.writeable won't work - without special case code. I'd
> suggest /proc/sysopts/fs/registry/writeable.
>
> Two, why not have two options:
> writeable
> nextwrite
>
> one is persistent (until all
> -Original Message-
> From: Charles Wilson [mailto:[EMAIL PROTECTED]]
> Sent: Friday, May 03, 2002 1:46 PM
> That might work --- but I'd make it auto-reset after every
> atomic write.
> So, you have to say
>$ cat '1' > /proc/registry/.writeable
>
> $
>
>$ cat /proc/re
Chris January wrote:
>>Chris & Chris,
>>
>>Cool!
>>
>>Is the registry as reflected in /proc/registry writable?
>>
> I'm torn between writing "no", and "no, not yet".
> The problem with this is that it is inevitable that at some point or other
> someone will post to the cygwin mailing list complai
On Fri, May 03, 2002 at 03:16:43AM +0100, Chris January wrote:
>I see you have made the fhandler_virtual, etc. functions use vanilla
>path_conv instead of normalized_path or whatever I called it
>originally.
Yes. This is consistent with all of the other fhandler functions.
>This relies on path
> If you do have problems, report them *here*. Don't send me private
> email. Don't send email to ChrisJ. Don't send mail to cygwin-apps,
> cygwin-announce, or cygwin-developers (unless you actually are
> subscribed and want to talk about the implementation). If you think the
> code should be
At 08:30 PM 5/2/2002, you wrote:
>On Fri, May 03, 2002 at 01:14:52AM +0100, Chris January wrote:
> >> Chris & Chris,
> >>
> >> Cool!
> >>
> >> Is the registry as reflected in /proc/registry writable?
> >I'm torn between writing "no", and "no, not yet".
> >The problem with this is that it is inevit
On Fri, May 03, 2002 at 01:14:52AM +0100, Chris January wrote:
>> Chris & Chris,
>>
>> Cool!
>>
>> Is the registry as reflected in /proc/registry writable?
>I'm torn between writing "no", and "no, not yet".
>The problem with this is that it is inevitable that at some point or other
>someone will p
> Chris & Chris,
>
> Cool!
>
> Is the registry as reflected in /proc/registry writable?
I'm torn between writing "no", and "no, not yet".
The problem with this is that it is inevitable that at some point or other
someone will post to the cygwin mailing list complaining they typed rm -rf
/proc/regi
Chris & Chris,
Cool!
Is the registry as reflected in /proc/registry writable?
Randall Schulz
Mountain View, CA USA
At 21:58 2002-05-01, you wrote:
>A couple of months ago Chris January submitted some significant new
>functionality to cygwin which I've finally gotten around to merging into
>
Christopher schrieb:
[...]
> Once you've done all that you'll be able to amaze yourself by typing:
> ls /proc
> or
> ls /proc/registry
[...]
> Have fun.
Yes, that is fantastic;)
$ ls /proc/registry/HKEY_LOCAL_MACHINE/SOFTWARE/GNU/XMail/
MAIL_ROOT
$ ls /proc/registry/HKEY_LOCAL_MACH
> >No problems, but is all the following expected behaviour? Having
> >uncompressed the new .dll and copied it to /bin:
> >
> >1. had to make /proc using mkdir /proc
Yes, same way you have to mkdir /cygdrive if you want it to show up in a
directory listing I'm afraid.
> >
> >2. ls -al / doesn't
At 08:15 02/05/2002 , [EMAIL PROTECTED] a écrit:
>No problems, but is all the following expected behaviour? Having
>uncompressed the new .dll and copied it to /bin:
>
>1. had to make /proc using mkdir /proc
>
>2. ls -al / doesn't actually show /proc
>
>3. ls -al /proc shows (something like)
>
>dr-
No problems, but is all the following expected behaviour? Having
uncompressed the new .dll and copied it to /bin:
1. had to make /proc using mkdir /proc
2. ls -al / doesn't actually show /proc
3. ls -al /proc shows (something like)
dr-xr-xr-x 10 0medicine0 Jan 1 1970 195162
A couple of months ago Chris January submitted some significant new
functionality to cygwin which I've finally gotten around to merging
into the current cygwin sources.
His changes add a /proc filesystem to cygwin. You can see what it does
by downloading the latest bzip2'ed dll from http://cygwi
22 matches
Mail list logo
