Slashdot Mirror
Man Page Project Can Now Use Official POSIX Docs
Martin_Sturm writes "The IEEE consortium announces in a recent press release that it granted permission to the Linux Man Page Project to incorporate material from the official documentation on the POSIX standard. Obviously this is very good news for the Man Page project which now has access to a huge amount of good documentation. Until recently the project could not use this documentation due to copyright restricions."
I love my man! 3
real *nix users dont need man pages!
A programmer is a machine for converting coffee into code.
And back before we had all this open-schopen source, we had to decompile our programs so that we could figure out how it works.
And before we had fancy-shmancy C/C++, we disassembled our programs and found out how they worked from there.
And we liked it!
/^[A-Z0-9._%+-]+@[A-Z0-9.-]+\.[A-Z]{2,4}$/i
Do they have SCO's permission?
In return for the free content, all man pages will be required to incorporate ascii-art banner ads.
(Ahem.) I like man chiefly because the default (command-line) browser program doesn't suck quite so much. I'm sure there are technically superior ways to store documentation, but man is very readable. info, on the other hand, blows.
"'I pass the test,' she said. 'I will diminish, and go into the West, and remain Galadriel.'"
- JRR Tolkien.
$ man cp
"The UNIX man page system sucks. Use the info system instead."
so...
$ info cp
"The UNIX man page system sucks. Use the info system instead."
Does this mean no more cruel messages telling us to see the info pages?
Look out!
If one more Slashbot makes a "DO U HAVE SCO'S PERMISSION? LOL" reference, I will touch your junk liberally.
Most man pages have long since been written from scratch for Linux. It would seem that any man pages still missing must be pretty rarely used, or for obsolete commands.
There are differences between UNIXes and Linux distributions and BSD distributions. What do the POSIX man pages document, and is it more trouble than it is worth to use them as a basis for Linux man pages?
I really don't know, this is not a troll, I didn't even know that there were POSIX man pages.
Infuriate left and right
A programmer is a machine for converting coffee into code.
I see a lot of people bitching about how info sucks. Well, you know what? Maybe it does. But have you actually tried to write a man page?
The syntax for roff just sucks. Info, on the other hand, is a fairly reasonable way to write documentation.
The most interesting point of this story is that the entire planet wasn't given permission to reprint the posix standard from day one. It's a standard isn't it?
Isn't promoting standards one of the main reasons for the IEEE consortium's existance? How do you promote standards by not allowing anyone to reprint them?
And the Linux Man Page Project expresses how grateful they feel. Whatever.
Samsung took back my unlocked bootloader because Google wants me to rent movies. They're both evil.
Does that mean well get some docs on the pthreads rwlocks and posix semaphores ? Just yesterday I needed them, and sadly discovered they were missing ,(
While GNU's perfectly within its rights to call their own creation GNU/info they were getting laughed at too much when they tried to insist on GNU/HTML :-)
"'I pass the test,' she said. 'I will diminish, and go into the West, and remain Galadriel.'"
- JRR Tolkien.
Use the right tool, don't let the wrong tool use you.
- Barrie
How would the 650 page GCC manual look as a man page?
Like it was done by someone who didn't understand the Unix documentation scheme.
The man pages were never the entire body of Unix documentation, just the first volume. The second volume consisted of longer, more tutorial or in depth documents for the programs that needed it. (Like some compilers, or awk, or [t]roff, etc.)
Way back in prehistory I worked with a port of Version 7 Unix (UTS) that came with a complete set of printed manuals -- the man pages were only half the documentation.
That said, info is lame, and commands that have no man page because they have info doubly so.
-- Alastair
I find the lack of examples in man pages to be a real pain....Example take a look at the crontab manual, it would be nice to see how to formulate an example to place into the crontabs. You'll find such things in Solaris.
The syntax for roff just sucks.
Try using XSLT to generate troff. The CStyleX package will let you generate concise troff macros for GNU style C programming interface man pages (just like the screenshot on this page):
http://www.ioplex.com/~miallen/cstylex/
Actually the best part is that this will also generate HTML from the same source XML. And nothing prevents you from generting PostScript in the future or just about anything else for that matter. IOW you write XML run make and get man pages and HTML.
PS: The package hasn't been updated in a while. The latest man.xsl and ref.xsl transforms are in the libmba package cited on the page referenced.
Sorry, four digits. But then, I did use the Arpanet before the Jan 1982 switchover to TCP/IP, so I am damn old.
Today's man pages look almost the same as 1981 man pages from Bell Labs, so you haven't missed much by being young.
(Since this is not very informative:)
At that time, HTML didn't yet exist (or, at least, wasn't ubiquitous as it is now), so info made at least some sense (although I've always preferred man pages and n/troff docs myself).
Nowadays, however, it makes no sense at all to continue with info when HTML/XML is so common.
All of the info docs should be translated to HTML or XML and the old, obsolete info format should be abandoned.
Those who sacrifice security to condemn liberty deserve to repeat history or something. - Benjamin Santayana