This is the mail archive of the cygwin 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: Path confusion

On  1 Apr, Igor Pechtchanski wrote:
>  On Fri, 1 Apr 2005, Luke Kendall wrote:
> > On  1 Apr, To: cygwin@XXXXXX.XXX wrote:
>               ^^^^^^^^^^^^^^^^^^^^^
>  Eh? :-)

A peculiarity of my MUA, when used to reply to my own messages.  Sorry.

> > While just checking that, I also discovered that "man chown" now
> > produces no output.  Other man entries seem fine.
>  >
> > $ cygcheck -s | grep "^cygwin "
> > cygcheck: dump_sysinfo: GetVolumeInformation() failed: 67
> > cygwin                  1.5.13-1
>  FWIW, a better way to produce the above line is "cygcheck -cd cygwin".

Ah!  Thanks.

> > $ man chown | cat -tvu
> > Warning: cannot open configuration file /usr/share/misc/man.conf
>  Heh?  First off, why would you need to pipe this to "cat" (aside from the
>  fact that "-u" is ignored, and "-v" is redundant with "-t")?

The reasons are uninteresting, really.  Historically, on some Unix
systems, there were differences: certain characters you'd only see with
all three options.  And initially, I had tried col -b (in the usual

$ gunzip -c /usr/share/man/man1/chown.1.gz | nroff -man | col -b

and got strange results: partial escape sequences sprinkled through the
output.  (Is that a bug?)  So I replaced the col -b with the cat -tvu.

Like I said, not really interesting.

Co-incidentally, I'm having similar trouble with RPM on FC2 on a
completely different computer: blank output from man, though in that
case it shows all the text plus backspaces and underscores when fed
through cat -tvu: man chown on cygwin still produces no output for me
on Cygwin if I do the same, so the similarity is probably a red herring.

>  Secondly,
>  you don't get the above message with other man pages, do you?

More testing makes me answer "no", I've just found.  The few I'd tried
all happened to work.  I tried a few more this morning, and found
others do have problems.

man man, man sh, work fine.  man col, getfacl is the same as chown: no
man ls produces garbage (so does man setfacl):

$ man ls | cat -v 
Warning: cannot open configuration file /usr/share/misc/man.conf
"^HA11yaem^HY^HcB-^HL^Ho^HYft3:^|o^Hx`^HU~^HOpJ~^HA"^He^HA_%=*GK^HeB:,^Hi`^HuV:^HIx*-^HL-^HLp^Hb-:-?"^Ho-^HLp^Hb`^Hi(R)SwG{7_^HaWt|x/^Ho#^RG?"^Ho^Hc"^Hi^^Ha~^Hn^^HI^He^^HI`^Hi^^HU^Hu^HO+_^Ho=1D              _                                         _
1? ^^HO,S`^He,o^HAb:+M?I^HbAE^HO^Ha4^^HeR^^He/^HcB"^Hi~^HA~^HNx6^HYI^Hb/&"^Hy^^He-:-^^Hu"^HA+~l^Hy.L,^Hc^He`^HUd(dQ,^Hc;IR`^HUT`^HO/^HOL=^HYh&,^Hc7"-^HDQ<(R)Y-l+-V`^HoE^HImUR1`^HObG^^Hu"^HuWE.....^HyaD/T ^^Hu~^HN^^HO%^Ha{a#ae+5x=^HYUn`^HE,(3&>> ^^Huo^HA^He^HyA1/4(<<^He^HY`^He~^Ho^^HA ^HY8H

$ ls -l /usr/share/misc/man.conf
ls: /usr/share/misc/man.conf: No such file or directory

I imagine the problem is the missing man.conf. 

> > $ gunzip -c /usr/share/man/man1/chown.1.gz | nroff -man | head
> > CHOWN(1)                         User Commands                        CHOWN(1)
> > [snip]
>  In addition to what Eric mentioned, it would also be nice to see your
>  mount table, so attaching the output of "cygcheck -svr" would be a good
>  idea here...
>  	Igor

Well, it was attached, but I've removed it since I've just now found
the problem, and it was caused by me.

I finally thought to try the obvious thing: investigate the missing
man.conf.  It's my fault.  My post-install scripts for one of the old
Cygwin release problems (messages about unsupported JNROFF etc. man directives)
was to do this:

    mv /usr/share/misc/man.conf /usr/share/misc/man.conf.old
    cp -p /usr/share/misc/man.conf.default /usr/share/misc/man.conf

But at some stage the JNROFF problem was fixed *and* man.conf.default
was removed, so my post-install caused the problem.

I also confess that the initial brief tests (it seemed like only
"chown" man page had the problem), mislead me completely.

Anyway, the problem is solved.

It would be nice if package maintainers reported fixed bugs in the
announcement messages of new releases; but really, it was my fault.

Thanks for being so patient,


Unsubscribe info:
Problem reports:

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