Re: our broken man package

2001-01-09 Thread Stephen Zander
Late, by hey, what the hell... Joey == Joey Hess [EMAIL PROTECTED] writes: Joey In other words, if you can have a religious war over it, we Joey need an alternative. I have never seen a religious war over Joey man. :-) Tom Christiansen has been known to get into them. But then

Re: our broken man package

2001-01-08 Thread Fabrizio Polacco
On Thu, Jan 04, 2001 at 09:04:50AM +, Lars Wirzenius wrote: Ethan Benson [EMAIL PROTECTED]: OpenBSD took another tack on this problem and just did away with cached man pages altogether. (no suid or sgid man) They always re-format a manual page? This might be reasonable, actually.

Re: our broken man package

2001-01-05 Thread Michael Stone
On Fri, Jan 05, 2001 at 01:09:17AM -0300, Nicolás Lichtmaier wrote: There could be a helper setuid program, man-cache-writer. man would call this program and pipe it the catpage. man-cache-writer would just write it's stding to the proper place. End of the problems. No so simple. You don't

Re: our broken man package

2001-01-05 Thread Nicolás Lichtmaier
There could be a helper setuid program, man-cache-writer. man would call this program and pipe it the catpage. man-cache-writer would just write it's stding to the proper place. End of the problems. No so simple. You don't want the trusted program trusting the output of a non-trusted

Re: our broken man package

2001-01-05 Thread Steve Greenland
On 04-Jan-01, 12:32 (CST), Joey Hess [EMAIL PROTECTED] wrote: Lars Wirzenius wrote: And, anyway, caching might be done in a cronjob: look at the pagesa in manpath every night, check which ones have been accessed since the past run, and format those. Then delete anything older than N days

Re: our broken man package

2001-01-05 Thread Arthur Korn
Hi Joey Hess schrieb: And, anyway, caching might be done in a cronjob: look at the pagesa in This seems to be cr^Hontrary to the idea of caching. That's a good idea. Another route to take is to split man into the rendering/caching bit and the command line man page lookup/processing/pager

Re: our broken man package

2001-01-04 Thread Ethan Benson
On Wed, Jan 03, 2001 at 03:23:03PM -0800, Joey Hess wrote: I'm concerned with some breakage in the man program. Here is an example: [snip examples] This is because man runs via a wrapper that makes it run as user man (and makes root's pager run as user man too for some reason). Related

Re: our broken man package

2001-01-04 Thread Joey Hess
Ethan Benson wrote: the problem with this is you end up with the catman files owned by whatever user reads whatever man page. personally as a sysadmin i don't want users gaining write permission to files in any more places under /var then there already is (ahem texmf). i am not certain if

Re: our broken man package

2001-01-04 Thread Ethan Benson
On Wed, Jan 03, 2001 at 11:53:37PM -0800, Joey Hess wrote: Ethan Benson wrote: the problem with this is you end up with the catman files owned by whatever user reads whatever man page. personally as a sysadmin i don't want users gaining write permission to files in any more places under

Re: our broken man package

2001-01-04 Thread Peter Makholm
Lars Wirzenius [EMAIL PROTECTED] writes: On the other hand, we might want to copy the OpenBSD version instead of maintaining our own man. But I leave that to whoever maintains the packages. We have alternatives on almost everything but dpkg and man. If someone thinks it's worth the effort to

Re: our broken man package

2001-01-04 Thread Branden Robinson
On Thu, Jan 04, 2001 at 11:00:19AM +0100, Peter Makholm wrote: Lars Wirzenius [EMAIL PROTECTED] writes: On the other hand, we might want to copy the OpenBSD version instead of maintaining our own man. But I leave that to whoever maintains the packages. We have alternatives on almost

Re: our broken man package

2001-01-04 Thread Colin Watson
Ethan Benson [EMAIL PROTECTED] wrote: On Wed, Jan 03, 2001 at 11:53:37PM -0800, Joey Hess wrote: I'll bet (have not verified) that you can already trick it into writing bogus file by sticking trojan pages elsewhere in your manpath. i just tried it, did not end up with a cached file. [EMAIL

Re: our broken man package

2001-01-04 Thread Joey Hess
Lars Wirzenius wrote: They always re-format a manual page? This might be reasonable, actually. Groff is pretty fast, and most manual pages are short, so it shouldn't take too long even on older hardware. I think it would take a while on my 386 for things like the zshall man page. (Several

Re: our broken man package

2001-01-04 Thread Joey Hess
Peter Makholm wrote: We have alternatives on almost everything but dpkg and man. If someone thinks it's worth the effort to make alternatives for these they should do it. If there is a general agreement that the alternatives is better than the original packages we just switch prioryties. Is

Re: our broken man package

2001-01-04 Thread John Galt
On Thu, 4 Jan 2001, Joey Hess wrote: JHPeter Makholm wrote: JH We have alternatives on almost everything but dpkg and man. If someone JH thinks it's worth the effort to make alternatives for these they JH should do it. If there is a general agreement that the alternatives is JH better than the

Re: our broken man package

2001-01-04 Thread Joey Hess
John Galt wrote: JHIn other words, if you can have a religious war over it, we need an JHalternative. I have never seen a religious war over man. :-) Never heard RMS on info pages? That's a file format religious war, not a man program religious war. -- see shy jo

Re: our broken man package

2001-01-04 Thread John Galt
On Thu, 4 Jan 2001, Joey Hess wrote: JHJohn Galt wrote: JH JHIn other words, if you can have a religious war over it, we need an JH JHalternative. I have never seen a religious war over man. :-) JH JH Never heard RMS on info pages? JH JHThat's a file format religious war, not a man program

Re: our broken man package

2001-01-04 Thread Mark Brown
On Thu, Jan 04, 2001 at 10:35:56AM -0800, Joey Hess wrote: Is that even necessary? I mean, alternatives makes sense for programs like MTAs and editors, which have a diverse range of interface, functionality, and use. Man formats a page and displays it in $PAGER; I'd always thought the

Re: our broken man package

2001-01-04 Thread Joey Hess
Joey Hess wrote: I'm concerned with some breakage in the man program. Here is an example: [EMAIL PROTECTED]:~chmod 700 . [EMAIL PROTECTED]:~cp /usr/share/man/man1/ls.1.gz . [EMAIL PROTECTED]:~man -l ./ls.1.gz man: can't chdir to /home/joey: Permission denied man: ./ls.1.gz: Permission

Re: our broken man package

2001-01-04 Thread Nicolás Lichtmaier
the problem with this is you end up with the catman files owned by whatever user reads whatever man page. personally as a sysadmin i don't want users gaining write permission to files in any more places under /var then there already is (ahem texmf). i am not certain if there is potential

Re: our broken man package

2001-01-04 Thread Ethan Benson
On Thu, Jan 04, 2001 at 07:14:13PM -0800, Joey Hess wrote: Here's one more real fun one. This only works if you are root and /root is mode 700 and $TMP is set to /root/tmp/: [EMAIL PROTECTED]:~man man man: can't create a temporary filename: Permission denied So incredibly broken..

our broken man package

2001-01-03 Thread Joey Hess
I'm concerned with some breakage in the man program. Here is an example: [EMAIL PROTECTED]:~chmod 700 . [EMAIL PROTECTED]:~cp /usr/share/man/man1/ls.1.gz . [EMAIL PROTECTED]:~man -l ./ls.1.gz man: can't chdir to /home/joey: Permission denied man: ./ls.1.gz: Permission denied Another example