This is the mail archive of the cygwin-developers@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Symlinks under /proc


On Sat, 26 Feb 2005, Christopher Faylor wrote:

> On Sat, Feb 26, 2005 at 10:50:52PM -0500, Igor Pechtchanski wrote:
> >On Sat, 26 Feb 2005, Christopher Faylor wrote:
> >
> >> On Wed, Feb 02, 2005 at 12:03:52PM -0500, Igor Pechtchanski wrote:
> >> >a) mknod cannot set the mode of many devices.
> >> >   Even though I run "mknod -m666" for all of them, everything except fd*,
> >> >   mem, port, sd*, and scd* has mode 600.  I've compared strace outputs
> >> >   for "mem" and "kmem", and chmod succeeds in both cases, but the mode
> >> >   for kmem is not changed.  Weird.
> >>
> >> I was thinking of making a 1.5.13 release and thought I'd fix this bug.
> >> However, I can't duplicate it anymore.  I didn't try to get rid of the
> >> special /dev handling from the DLL but all of the device nodes have the
> >> correct permissions after running your script and I can change them
> >> afterwards without a problem.
> >>
> >> Can you still duplicate this problem, Igor?
> >
> >Now[*] I get the reverse of the problem.  The mode is set correctly (and
> >is changeable) for all devices *except* fd*, mem, port, sd*, and scd*.
> >For those, the mode is fixed at 666.  There is no error code returned, and
> >chmod simply does nothing.  This, BTW, is happening in a regular directory
> >(/ddev), with the virtual /dev still in place...
>
> I saw this for mem and scd*, sd* and fixed the problem.  I didn't see it for
> mem or port.

Oops, I didn't test "port", and just assumed it would be the same gang.
I did see it for all the rest, though, and it's fixed now (tested for all
the devices I had).

One remaining issue is what to do with /dev/com*.  Should /dev be a
managed mount just for those?

> >Another glitch that *is* reproducible for me is that bash cannot
> >tab-complete any top-level directory or file (unless PWD=/, in which case
> >"ls ^I^I" works, but "ls ./^I^I" doesn't).  I can provide more details if
> >needed.
>
> I think this was the problem that Corinna recently tracked down.  bash
> is trying to do an opendir '//' rather than '/'.  Nevertheless, I have
> checked in a patch which stops a standalone '//' or '\\' from being
> treated specially.

Great, this now also works.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha@cs.nyu.edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor@watson.ibm.com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"The Sun will pass between the Earth and the Moon tonight for a total
Lunar eclipse..." -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]