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."

229 comments

  1. yay! by Ozone+Depletion · · Score: 2, Funny

    I love my man! 3

    1. Re:yay! by Anonymous Coward · · Score: 0

      Yeah, I love your man too.

    2. Re:yay! by Anonymous Coward · · Score: 0

      I love you, your man, the parent poster, and the parent poster's man.

    3. Re:yay! by Paleomacus · · Score: 2, Funny

      man bind,man kill,man bash, man touch, and man finger are my favorites

  2. bah! by monkey_jam · · Score: 3, Funny

    real *nix users dont need man pages!

    1. Re:bah! by Richard_at_work · · Score: 2

      Nope, GNU seems to think they need info pages more tho :(

    2. Re:bah! by plams · · Score: 1, Funny

      real *nix user not need man!
      real *nix user need wo-man! badly!

    3. Re:bah! by bersl2 · · Score: 4, Insightful

      Seriously, besides GNU, who else favors info over man? I find the system difficult to navigate. For instance, when I was first learning {,ba}sh... damn, the bash info page sucks.

    4. Re:bah! by Uber+Banker · · Score: 1

      Real *nix systems are POSIX compliant, Linux is not.

    5. Re:bah! by Anonymous Coward · · Score: 1, Informative

      Get pinfo then. It's much more usable than that crappy info.

    6. Re:bah! by Anonymous Coward · · Score: 0

      Unix is archaic. Linux is not.

    7. Re:bah! by SlashDotAgent · · Score: 1

      real *nix users compose man pages!

    8. Re:bah! by madpierre · · Score: 1

      One word ...

      Emacs ;)

      --
      siggy played guitar
    9. Re:bah! by Mr.+Piddle · · Score: 1

      Seriously, besides GNU, who else favors info over man?

      Leave it to GNU to create something clumsier than a man page for quick reference and less useful than HTML or PDF for large documents. Man pages are one area that OpenBSD, for example, got it right.

      --
      Vote in November. You won't regret it.
    10. Re:bah! by Mr.+Piddle · · Score: 1

      Unix is archaic. Linux is not.

      I'll take my vi text editor that doesn't render HTML instead of displaying the text, thank you very much!

      Also, saying "Linux" is too general. For example, it would be better to say, "Red Hat is archaic. Debian is not."

      --
      Vote in November. You won't regret it.
    11. Re:bah! by scotch · · Score: 1

      elvis? use vim

      --
      XML causes global warming.
    12. Re:bah! by anthonyrcalgary · · Score: 1

      I'm just happy I won't have to SSH to my OpenBSD machine to get some decent man pages anymore.

      --
      When someone might yell at me, it has to be OpenBSD.
    13. Re:bah! by bersl2 · · Score: 1

      Too bad I use vi ;)

    14. Re:bah! by JoeBuck · · Score: 5, Informative

      The format is not info but texinfo, which produces output in many forms: TeX (for typeset documents), HTML, as well as info; furthermore, the man pages for many GNU programs are now produced by automatic conversion from the info source.

      Texinfo beats roff format for man pages because it supports structure and hyperlinks. XML (or SGML) formats are even better, but "man format" sucks. And I've written a lot of "man pages" in my career.

    15. Re:bah! by aled · · Score: 1

      I agree. I just can't stand info. Only useful thing is that the info files are plain text enough that I can search them. On the other hand I don't want to read again a man page for more than quick reference (ie: parameters names). Both methods are obsolete. What I really like is something like .chm. At least works for me.

      --

      "I think this line is mostly filler"
    16. Re:bah! by Oggust · · Score: 1
      Yes we do.

      This reminds me, back on old-school unix dialects, there used to be a command learn that had short tutorials on different tools. You'd do

      learn vi

      and it'd start an interactive little course on it. And if you quit it, it would remember where you were so you could pick up where you left off. As I remember it, it was pretty cool. It had data in some vaguely troff-like format IIRC. Anyway, I haven't seen it around any linux or other modern boxes. Anybody know what happened to it, and where it came from?

      /August.

      --
      "An object declared as type _Bool is large enough to store the values 0 and 1." -- 6.1.2.5, C99 standard.
    17. Re:bah! by Prior+Restraint · · Score: 1

      I just wrote my first man page earlier this month. I'm kind of hoping I won't have to do it again any time soon, though it's doubtful; our system's documentation is virtually nonexistent.

    18. Re:bah! by Bob+Uhl · · Score: 1
      Actually, once one gets use to the info keybindings and way of doing things, it's quite nice. I couldn't live without the bash info pages (and I recall the old days of thumbing through ksh or csh man pages). It does take some getting used to, though. Part of that is due to the emacs-inspired keybindings; these were a lot more intuitive when emacs was more commonly used (I use it almost constantly, so to me this is no big deal); part due to info's origin as a pre-HTML hypertext platform.

      Considering all it does, though (online and prettily printed docs), it's damn nice. Anyone who has ever used TeX or its derivatives (e.g. LaTeX or texinfo) cringes at the thought of going back to HTML. Even roff is better than HTML at real document preparation.

    19. Re:bah! by Anonymous Coward · · Score: 0

      learn is still used. Last semester, it was part of a lab I had in my intro to computer science engineering class. FWIW, it was on Digital Unix 4.0d.

    20. Re:bah! by Anonymous Coward · · Score: 0
      actually you can find places where *Microsoft* has better posix (ISO/IES:9945-1:1990) compliance than Unix or Linux systems.

      I don't know about "*nix", though. Is that better than Unix in some way?

    21. Re:bah! by mullein · · Score: 2, Informative
      Seriously, besides GNU, who else favors info over man? I find the system difficult to navigate. For instance, when I was first learning {,ba}sh... damn, the bash info page sucks.

      I always hated using info pages until I came across pinfo, a colorized info/man viewer using arrow keys. That phrase is insufficient to describe its utility. It actually makes info pages useful! Debian has it in package repositories and I'd guess that other Linux distributions, perhaps BSDs, etc. package it.

    22. Re:bah! by Anonymous Coward · · Score: 0
      "man format" sucks.
      $ man format
      No manual entry for format
      Hey, you're right!
    23. Re:bah! by kbrannen · · Score: 1
      Seriously, besides GNU, who else favors info over man? I find the system difficult to navigate. For instance, when I was first learning {,ba}sh... damn, the bash info page sucks.

      Totally agree! Either use "tkinfo", or if you redirect the output of "info", you will get something a little more like "man" output. E.g. try "info bash | less".

  3. Man pages are evil... by inertia187 · · Score: 4, Funny
    It's evil because there's a deamon involved, and this command:
    $ man mount
    --
    A programmer is a machine for converting coffee into code.
    1. Re:Man pages are evil... by Anonymous Coward · · Score: 3, Funny

      maybe you need to try these command first ...

      man date

      man strip

      i'd leave the dollar sign out that's illegal
      in most states.

    2. Re:Man pages are evil... by Anonymous Coward · · Score: 0

      Or try this:

      $ man woman

    3. Re:Man pages are evil... by Anonymous Coward · · Score: 0

      I think these are much worst:

      $ man fsck

      and

      $ man jobs

    4. Re:Man pages are evil... by Anonymous Coward · · Score: 5, Funny
      Check out the complete output:
      $ man woman
      No manual entry for woman
      How appropriate.
    5. Re:Man pages are evil... by PowerPill · · Score: 2, Funny

      Yes and if you: $ man pump too many times you could go blind.

    6. Re:Man pages are evil... by Feztaa · · Score: 3, Funny
      Yeah, but once you learn out how to mount, you can:
      $ mount /woman
    7. Re:Man pages are evil... by supersteve1440 · · Score: 1

      $ man touch

    8. Re:Man pages are evil... by Anonymous Coward · · Score: 0

      touch woman && man touch

    9. Re:Man pages are evil... by jrockway · · Score: 3, Interesting

      Try M-x woman in emacs.

      --
      My other car is first.
    10. Re:Man pages are evil... by St.+Vitus · · Score: 1

      What is this 'woman'? Hmmm...

      $ man woman
      no manual entry for woman

      That's ok. finger's disabled for security reasons.

  4. A play on "The Grumpy Man" from SNL by DarkHelmet · · Score: 3, Funny
    Real Linux hackers do not use man! They look at the source and figure out how the program works from the command line!

    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
    1. Re:A play on "The Grumpy Man" from SNL by Anonymous Coward · · Score: 5, Funny

      Shhh ! You're gonna wake up one of these 3 digits slashdot ID elders. And you know how they love to speak about good ol'time...

    2. Re:A play on "The Grumpy Man" from SNL by Surazal · · Score: 2, Funny

      You know, back in *my* day, we didn't have these fancy-schmancy SCSI cables to help us write our data to disk. No, in my day, we had to write it down using burnt sticks we pulled from smoldering camp fires. Then we ran across the savana, burnt stick and all. And when we got to our destination to write that data to disk, when we got an error, we had to run all the way back to our camp and yell out at the top of our lungs "WRITE ERROR! CHECK CONDITION!" Then we had to run all the way back just to get the sense key data.

      Beat *that*!

      --
      --- Journals are boring; Go to my web page instead
    3. Re:A play on "The Grumpy Man" from SNL by Anonymous Coward · · Score: 0

      Damn, I knew it...

    4. Re:A play on "The Grumpy Man" from SNL by pla · · Score: 1

      Real Linux hackers do not use man! They look at the source and figure out how the program works from the command line!

      You may jest, but I've had to resort to this more than a few times, for programs with badly out-of-date man pages... Happily typing along, look up feature "foo", try using the --foo=bar switch, and then wondering why the hell I end up with 206 pages of seemingly-random garbage. Messy (and slow), but 100% effective in figuring out just what "foo" does.

      Apropos (no pun intended) of the actual FP, many such inaccuracies in man pages seem to involve the interaction of POSIX compliance with the familiar classic UNIX-like tools. So, with luck, this may actually mean the man pages will become a tad more accurate in the near future.

    5. Re:A play on "The Grumpy Man" from SNL by Anonymous Coward · · Score: 0
      And when we got to our destination to write that data to disk, when we got an error, we had to run all the way back to our camp and yell out at the top of our lungs "WRITE ERROR! CHECK CONDITION!" Then we had to run all the way back just to get the sense key data.

      Beat *that*!

      Ok, I'll try :

      Youngster ! Back in my days we didn't even have legs to run or lungs to yell ! But we were already coding DNA.
    6. Re:A play on "The Grumpy Man" from SNL by mce · · Score: 3, Funny

      You already had disks to run to and write on? Jeez, I guess it shows that my 3-digit slashdot ID is considerably lower than yours. :-) Back when I started, we had to use our brain. That good ol'technology did save us a lot of useless running, though...

    7. Re:A play on "The Grumpy Man" from SNL by SlashDotAgent · · Score: 1

      Just like Real SlashDot hackers do not use WYSIWYG comment posting forms, but rather just write the HTML code?

      Oh, wait.

    8. Re:A play on "The Grumpy Man" from SNL by Anonymous Coward · · Score: 0

      Let me guess, five miles uphill in the snow...Both ways? ;p

    9. Re:A play on "The Grumpy Man" from SNL by iminplaya · · Score: 1

      a brain???...you hadda....aaawww, nevermind

      If Claudia Shiffer married The Brain, could we call her Claudia Shiffer-Brains?

      --
      What?
    10. Re:A play on "The Grumpy Man" from SNL by niko9 · · Score: 1

      Shhh ! You're gonna wake up one of these 3 digits slashdot ID elders. And you know how they love to speak about good ol'time...

      Not to worry, it's fleet enema time at the ward.

      But wait, how do they get them to comply with said enema so easily you ask???

      Next time you see a nurse running down the ward hallway with a boom box, that's playing that God awful GNU/RMS tune, and there are whords of old geezers running after her with their Linux powered walkers....

      well kids, now you now, and it ain't pretty.

    11. Re:A play on "The Grumpy Man" from SNL by Russ+Steffen · · Score: 5, Funny

      Ach, you kids and your "brains." When I started we had to do all our thinkin' with just a few neurons at the top of our spinal chords. And we liked it! We loved it!

      Brains? Luxury...

    12. Re:A play on "The Grumpy Man" from SNL by Surazal · · Score: 2

      Spinal cords!?

      Ok, you know, there are some jokes that never get old. Others were born that way. Back in my day, all the jokes were old! Why, some of our jokes were so old that we would just we wouldn't have to tell the whole joke for it

      --
      --- Journals are boring; Go to my web page instead
    13. Re:A play on "The Grumpy Man" from SNL by kfg · · Score: 1

      Neurons? What do you need neurons for? In my day we were just atoms and had to monitor the state of our electrons in the outer shell to get anything done.

      Kids with their computers today don't know what that's like.

      Oh, wait.

      KFG

    14. Re:A play on "The Grumpy Man" from SNL by aled · · Score: 1

      Parent should have been modded "informative"!

      --

      "I think this line is mostly filler"
    15. Re:A play on "The Grumpy Man" from SNL by davie · · Score: 1

      Quiet, you!

      --
      slashdot broke my sig
    16. Re:A play on "The Grumpy Man" from SNL by Anonymous Coward · · Score: 0

      "Old"? Bah!
      Back in my day, things didn't get old, because time didn't exist! If I had the 4th dimension back then like you kids did today, I coulda' done some real damage!

    17. Re:A play on "The Grumpy Man" from SNL by zoeblade · · Score: 2, Informative

      Saturday Night Live? If that sketch is what it sounds like, it was pre-Python. I forget who performed it originally (At Last, the 1948 show?), but it had some of the Python members in it, if I recall correctly.

  5. Who cares about the IEEE? by Anonymous Coward · · Score: 4, Funny

    Do they have SCO's permission?

  6. errno.h? by Anonymous Coward · · Score: 0

    so i wonder if these docs contain any SCO confidential trade secrets....

  7. Ooooh... by mikeophile · · Score: 1

    So now they are going to be packed with even more manly goodness?

  8. However... by SnowZero · · Score: 4, Funny

    In return for the free content, all man pages will be required to incorporate ascii-art banner ads.

    1. Re:However... by plams · · Score: 3, Funny

      would the ads be context sensitive? you know, adapt themselves to the user's preferences?

      > man mount

      * Do you realise that 10% of all males *
      * are GAY? * * * * K-Y-Jelly in K-mart *
      * * * * only $9.95!!!1!! * * * * * * * *

      NAME

      mount - mount a file system

      SYNOPSIS

      mount [-lhV]

      mount -a [-fFnrsvw] [-t vfstype] [-O optlist]
      mount [-fnrsvw] [-o options [,...]] device | dir
      mount [-fnrsvw] [-t vfstype] [-o options] device dir
      etc..

  9. man, that's cool! by adrianbaugh · · Score: 4, Insightful

    (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.
    1. Re:man, that's cool! by Anonymous Coward · · Score: 5, Informative

      Try reading info pages with "pinfo" instead of "info" - you'll like info pages much more when you've got a decent viewer =)

    2. Re:man, that's cool! by adrianbaugh · · Score: 1

      > Try reading info pages with "pinfo" instead of "info" - you'll like info pages much more when you've got a decent viewer =)

      Woo, thanks for the tip! That's much better.

      --
      "'I pass the test,' she said. 'I will diminish, and go into the West, and remain Galadriel.'"
      - JRR Tolkien.
    3. Re:man, that's cool! by GammaTau · · Score: 2, Interesting

      Try reading info pages with "pinfo" instead of "info" - you'll like info pages much more when you've got a decent viewer =)

      Yeah, pinfo is definitely better than the default info viewer. The only problem with pinfo is that it's not really standard. If I log on to a system I'm not familiar with (and then I often really _need_ documentation), I can't be sure if "pinfo foo" will work whereas "man foo" will work with almost 100% certainity.

      Because it is pretty much guaranteed that man pages can be read on every system without any viewer brain damage, it also leads to a situation where many people write only man pages and additional documentation in other formats (like plain text or HTML). I know that info can view man pages when info pages are not found but I rarely bother. I just use "man foo" and if that doesn't give what I'm searching for, then check /usr/share/doc or search the web.

    4. Re:man, that's cool! by Anonymous Coward · · Score: 0


      $ man, that's cool!

      Unmatched '.

    5. Re:man, that's cool! by Anonymous Coward · · Score: 0

      I still hate info, even with pinfo. Generally I want a brief synopsis of the various options/commands of a program. Not some overly wordy book about it. Man pages give me concise information quickly, I don't have to search through a bunch of stupid nodes, and I don't have to page through 9820347923847 pages to get what I'm after.

    6. Re:man, that's cool! by evilad · · Score: 1

      Nice, but doesn't add much to an info: url in Konq...

    7. Re:man, that's cool! by Anonymous Coward · · Score: 0

      man is very readable. info, on the other hand, blows.

      My beef with info isn't so much the reader itself, as the horrendously badly designed help files for so many programs.

      Try "info bash", for example - and you'll find that the bash info pages are split into sections based on which other shell each feature came from!

      That's right - if you want to look up a function, you have to know whether it came from the Bourne shell, or the C shell, or whether it's unique to bash, before you can look it up!

      Want to know about bash command-line options? GNU documentation standards say that "info bash invoking" should get you that. Um... nope. In fact I've never managed to find the help on command-line options, although I expect it's in there somewhere.

      It's even worse when info tries to be clever. If I type "info sh", I get the info page for shred. Yup, that's what I wanted, honest.

      *sigh*

    8. Re:man, that's cool! by WWWWolf · · Score: 1

      Man rules for individual proggy information.

      Yet, for user's manuals and other very comprehensive and large references, Info is very nice if you have a decent browser. I use XEmacs' Info browser and it works beautifully. (the stand-alone info browser wasn't cool.)

      And Texinfo sources and also be TeXed and then printed, which would be handy in some situations.

      I think Perl is the only thing I frequently use that doesn't have Info docs even if it should. I think the reason why Perl doesn't have Info files is that everyone knows the Camel Book is so handy thing to have =)

    9. Re:man, that's cool! by keeg · · Score: 1

      Or if you don't have pinfo, but happen to use KDE, "info:/program" in konqueror gives you a nice viewer as well. (works with "man:/..." as well).

    10. Re:man, that's cool! by Anonymous Coward · · Score: 0

      Embedding perldoc source in modules is pretty cool. Now if only it had occured to someone that this "hypertext" thing wasn't just a passing fad, maybe Perl would have Info files rather than crippled flat files (like manpages).

    11. Re:man, that's cool! by pixelbeat · · Score: 1

      info is very non intuitive, but easy when
      you know how. here is a tip sheet

  10. Lot's of truth in the Parent! by Saeed+al-Sahaf · · Score: 0, Flamebait
    Funny, because... The man page format *does* suck. But I guess one must say it differently to avoid to "troll" modifier.

    Truth is, man pages are almost unreadable, unless you already know the material, they are not designed for the unwashed like you and I. They are meant for the gurus and the Illuminati who already know the material, basically an exercise in masturbation.

    --
    "Who are in control, they are not in control of anything - they don't even control themselves!" - Glen Beck
    1. Re:Lot's of truth in the Parent! by zurab · · Score: 1
      Truth is, man pages are almost unreadable, unless you already know the material, they are not designed for the unwashed like you and I. They are meant for the gurus and the Illuminati who already know the material, basically an exercise in masturbation.


      Most developers who would be interested in reading POSIX standards would be comfortable using man pages.

      For a better view of man page documentation, try typing man:/traceroute (or your favorite program) in Konqueror, or simply man:/ for man pages index.
    2. Re:Lot's of truth in the Parent! by Spoing · · Score: 1
      1. Truth is, man pages are almost unreadable, unless you already know the material,

      Exactly.

      1. they are not designed for the unwashed like you and I.

      *BLINK* This "you and I" you speak of...figure of speach?

      --
      A firewall can not protect you from yourself. Turn off what you do not need. Do not use the firewall to do your work.
    3. Re:Lot's of truth in the Parent! by Saeed+al-Sahaf · · Score: 1

      So this is an eletist project. As I thought. This is one of many of the reasons Linux will never win against M$, the "Linux Attitude".

      --
      "Who are in control, they are not in control of anything - they don't even control themselves!" - Glen Beck
    4. Re:Lot's of truth in the Parent! by Anonymous Coward · · Score: 0

      It's spelled "speech", oh great genius.

    5. Re:Lot's of truth in the Parent! by Spoing · · Score: 1

      Er...joke?

      --
      A firewall can not protect you from yourself. Turn off what you do not need. Do not use the firewall to do your work.
    6. Re:Lot's of truth in the Parent! by Saeed+al-Sahaf · · Score: 1
      Sure, sure, flame me for my ignorance of spelling, avoid addressing the meaning of the post, it's the regular here.

      No, not really a joke, I really do think these documentation projects are not "intuitive", and I really do think that this is a flaw.

      No big deal, not a reason for a flame war...

      --
      "Who are in control, they are not in control of anything - they don't even control themselves!" - Glen Beck
    7. Re:Lot's of truth in the Parent! by Anonymous Coward · · Score: 0

      Huh? What the fuck is 'eletist', and what is this 'M$' you speak of that Linux must win against?

      If you're gonna be a flaming asshole, at least learn to type.

    8. Re:Lot's of truth in the Parent! by Anonymous Coward · · Score: 0

      How about the "Windows Attitude" which is why people who know what they are doing will eventually move to Linux. You have to invest a bit of time in learning the tools before you use them. It's fuckers like you that expect nice pretty pictures and to be spoon fed wizards and dialog boxes. FUCK OFF!

  11. Typical GNU utility man page... by compass46 · · Score: 4, Funny

    $ 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."

    1. Re:Typical GNU utility man page... by petabyte · · Score: 4, Informative

      Umm, both my slackware and gentoo boxes have a full man page for cp. Apparently they're from the fileutils package.

      I'd suggest everyone load up the funny-manpages and asr-manpages if you're bored.

      man lart

    2. Re:Typical GNU utility man page... by Brandybuck · · Score: 1
      Hah hah. Now for a quote from a REAL man page:

      This man page is not kept up to date except when volunteers want to maintain it. If you find a discrepancy between the man page and the software, please check the Info file, which is the authoritative documentation.

      If we find that the things in this man page that are out of date cause significant confusion or complaints, we will stop distributing the man page. The alternative, updating the man page when we update the Info file, is impossible because the rest of the work of maintaining GNU CC leaves us no time for that. The GNU project regards man pages as obsolete and should not let them take time away from other things.


      Emphasis added...
      --
      Don't blame me, I didn't vote for either of them!
  12. No more see info? by zsau · · Score: 4, Interesting

    Does this mean no more cruel messages telling us to see the info pages?

    --
    Look out!
    1. Re:No more see info? by myc_lykaon · · Score: 1
      Does this mean no more cruel messages telling us to see the info pages?

      I sincerely hope so. The info pages are about as much use as a handbrake on a canoe. I'm very surprised that the info page writers ignored the 'those who seek to re-invent the wheel are doomed to do so badly' adage.

    2. Re:No more see info? by JohnFluxx · · Score: 1

      um, if it could be done, a handbrake _would_ be useful on a canoe.

    3. Re:No more see info? by Haeleth · · Score: 1

      The info pages are about as much use as a handbrake on a canoe.

      Now you're trolling. Some info pages - bash springs to mind - are very bad, but others - like those for GCC and GNU make - are very useful.

      I'm very surprised that the info page writers ignored the 'those who seek to re-invent the wheel are doomed to do so badly' adage.

      Which wheel do you have in mind?

      Man? Nope, even the worst info page is superior to its man equivalent, on account of, eg, having little features like cross-referencing and splitting it up into multiple pages so you don't have to press PageDown 500 times to get to the bit you're interested in.

      HTML? Nope, texinfo was invented before HTML.

      Do enlighten us - what is this perfect documentation format you have in mind (that existed before texinfo)?

    4. Re:No more see info? by myc_lykaon · · Score: 1
      Do enlighten us - what is this perfect documentation format you have in mind (that existed before texinfo)?

      And now we see the goalposts shifting before our very eyes. I said that info pages are worse than man. You say 'Oh no they aren't' a la Widow Twankey and then request a perfect doc system and if I can't, then through your warped logic, ipso facto I'm wrong.

      You don't seem to grasp that no document system is either perfect, or even perfect for a single example. Meeting user expectation is probably the best to target generally. I expect certain things from man and generally I get them. What flags? Thats at the top after synopsis man. What does the command do generally? Thats at the top in the description. How would I use this command in real life? Jump to EXAMPLES using /EXAMP. What does this command relate to? Jump to SEE ALSO with /SEE. No hitting PgDown like a maniac. What about all commands that use foo? 'man -k foo'. Hell, it isn't perfect, but it does what any system really should do - it meets expectations of a competent user. It is possible, but possibly undesirable to meet the expectations of an incompetent user...

  13. If one more.. by Anonymous Coward · · Score: 2, Funny

    If one more Slashbot makes a "DO U HAVE SCO'S PERMISSION? LOL" reference, I will touch your junk liberally.

    1. Re:If one more.. by Anonymous Coward · · Score: 0

      Do YOU have SCO's permission to touch my junk now?

  14. Woot by Dark+Lord+Seth · · Score: 1, Insightful

    Now if only GNU software would stop forcing that damnable alternative "info" ( which makes about as much sense as women ) down everyone's throath, things would be nice and happy.

    1. Re:Woot by Anonymous Coward · · Score: 0

      ha! women I understand, but info *shrug*

  15. Meh. by Anonymous Coward · · Score: 0

    Doesn't matter, the free BSD projects have always had better man pages than Linux.

  16. How useful is this? by A+nonymous+Coward · · Score: 4, Interesting

    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.

    1. Re:How useful is this? by dietz · · Score: 4, Informative

      I really don't know, this is not a troll, I didn't even know that there were POSIX man pages.

      There are no POSIX man pages. But previously they weren't allowed to even quote the POSIX standard in their manpages. They had to rewrite it all and hope they didn't introduce any inaccuracies in their rewriting.

      Now they can just quote the standard itself where they want to.

      This is mostly important for programming documentation (e.g. "man 3 strerror")

    2. Re:How useful is this? by matusa · · Score: 2, Informative

      It's extremely useful for things like 'this glibc function deviates slightly from POSIX section xx.yy, which states:'

      Another good one is 'This extension[/odd syntax/whatever] is for compliance which POSIX section aa.bb, which states as follows:'

      (purposeful inconsistency.. boredom otherwise)

    3. Re:How useful is this? by aled · · Score: 1

      Oh yes! oh yes! At last I'll know what the f*** does all those @*#@!$@#! functions and constants and the like!
      Tell me that we also get solved those mistery man pages like "this program does what the program with the same name usually does in other (unspecified) (*nix or something) implementations, with the apropiate random desviations and platform dependent (unspecified) behaviour and programmer non-standard custom surprises"
      No? weeell it was too good to be, er... good.

      --

      "I think this line is mostly filler"
    4. Re:How useful is this? by Anonymous Coward · · Score: 0

      Oh, come. You can't claim Linux is any worse than other operating systems in this regard.

      In Windows, for example, they have this wonderful thing called "context-sensitive help". You right-click on something and select "What's this?", and it tells you.

      For example... right click on a check box labelled "Reverse foo frobnication polarity", and you'll get a helpful little box that says "Select this option to reverse the foo frobnication polarity. Default: not selected."

      Man, what wouldn't I give for a GNU-style long option --reverse-foo-frobnication-polarity...

    5. Re:How useful is this? by benedict · · Score: 1

      Wouldn't that sort of quote be considered "fair use"
      anyway?

      --
      Ben "You have your mind on computers, it seems."
    6. Re:How useful is this? by Anonymous Coward · · Score: 0

      A paragraph or two might be considered "fair use".

      But quoting hundreds of paragraphs all over the project very well might not be. Even though each specific man page is sort of a seperate document, if they're all written as part of the same project, the quotes might be all considered together.

      "The Linux Man Pages project quoted 500 paragraphs of our copyrighted document" might not go over well if they were taken to court.

      But IANAL, so this is conjecture, in case you couldn't tell.

    7. Re:How useful is this? by ralphclark · · Score: 1

      This would have been a good thing if it had happened five years ago. But the shortsightedness of the standards bodies concerned (what fscking use is a standard that nobody is allowed to read?) kept it out of our hands so all the Linux software we know and love may have diverged from the original standard somewhat.

      So why the belated change of heart? They had no choice, that's why. Let me illustrate:

      As open source adoption in the enterprise has spread, it's increasingly the case that the ONLY exposure most people have to POSIX is through the bastardized interpretations available through open source software. For example, it seems that most Solaris deployments (in the investment banking industry at least) are still, even today, set up with the C shell as the login default. It seems to be a universal that frustrated programmers and admins then smuggle in bash, zsh, whatever.

      Soon enough these OSS shells become the shell of choice throughout the system and people then get tempted to use them for scripting as well because of the POSIX feature set originally borrowed from the Korn shell.

      Now sometimes these scripts are specific to the adopted shell, but conscientious scripters (who often don't know if these OSS shells have been installed on any given system) will instead leverage their POSIX knowledge from these shells to write Korn shell scripts instead, which they know can be migrated to any Solaris system without hassle.

      Thus these techs become familiar with a POSIX standard, and refer to it as POSIX, possibly without realizing that it isn't necessarily authentic POSIX.

      The standards bodies must surely have realized that they were therefore effectively losing control of the standard altogether. The de facto owners of a standard are the maintainers of the most commonly used software which purports to follow that standard (q.v. Microsoft's erstwhile plans to "embrace and extend" Java).

      Personally I think it is by this point mostly irrelevant. Modern implementations - even commercial implementations - do diverge somewhat because of holes and historical errors in the standards themselves, where the policy of vendors differs in how to deal with these ambiguities. The OSS approach has been to always make the software do, by default, what the user most likely intended it to do. Where idiocy is required to make it follow the standard strictly, this is available by setting some environment cvariable or whatever. Sun Microsystem's approach has been to slavishly obey every crappy aspect of the standard to the letter. Thus, for example, some Sun versions of egrep (on Solaris 8 I think) will fail to work properly at all if you provide an pattern like '^thing(foo|bar|)$' containing an empty alternate - because this is undefined in the relevant POSIX standard. Whereas the GNU version instead matches the null branch correctly to a null string - it will match lines consisting of "thingfoo", "thingbar" and "thing". This makes a whole lot more sense than the POSIX standard does.

      So in my opinion this is too little too late. GNU should have had full representation on the POSIX committee a long time ago. At this stage in the game it's just far too late. What should happen now (and probably will) is that the POSIX standards will slowly be brought into line with existing practice as in the most popular implementations. If not, these committees are only hastening their own end by making themselves irrelevant.

  17. Yeah, but... by inertia187 · · Score: 5, Funny
    They still need to improve the hideous grammar of the man pages:
    $ man nothing
    No manual entry for nothing
    --
    A programmer is a machine for converting coffee into code.
    1. Re:Yeah, but... by Shadowlore · · Score: 1
      Even better:
      $ man woman
      No manual entry for woman
      And In closing ....
      $ man "karma whore"
      No manual entry for karma whore
      Damn!
      --
      My Suburban burns less gasoline than your Prius.
  18. Has anyone here tried to write man pages? by Pyromage · · Score: 5, Interesting

    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.

    1. Re:Has anyone here tried to write man pages? by Meowing · · Score: 1

      The pod2man tool that comes with Perl makes the process relatively painless. POD isn't really Perl-specific, it works well to build standalone documentation.

    2. Re:Has anyone here tried to write man pages? by adrianbaugh · · Score: 1

      It does, but on the other hand it's fairly easy to take an existing man page, rip out all the content and replace it with your own. I did that for a small application I wrote when I couldn't be bothered to learn roff syntax properly and, although it's a bit of a cop-out, it's easy enough.

      --
      "'I pass the test,' she said. 'I will diminish, and go into the West, and remain Galadriel.'"
      - JRR Tolkien.
    3. Re:Has anyone here tried to write man pages? by Walterk · · Score: 1

      As a writer of two (1, 2) man pages, I can say that I find the syntax of roff not that bad. I guess you get used to strange languages once you learn more of them. If you find roff hard, try writing Perl scripts without any alphanumerical tokens.

    4. Re:Has anyone here tried to write man pages? by ncc74656 · · Score: 1
      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?

      I have. The markup used by man ([gnt]roff -man, really) isn't that complicated. If you've ever used a non-WYSIWYG word processor or written your own HTML, throwing together a manpage shouldn't be that difficult to figure out. You should be able to figure out enough to get by just by looking at the system-provided manpages.

      --
      20 January 2017: the End of an Error.
    5. Re:Has anyone here tried to write man pages? by FattMattP · · Score: 1
      The syntax for roff just sucks. Info, on the other hand, is a fairly reasonable way to write documentation.
      So what? People read docs far more than they write them. roff may be hard to write but at least it's easier to read and navigate.
      --
      Prevent email address forgery. Publish SPF records for y
    6. Re:Has anyone here tried to write man pages? by belmolis · · Score: 2

      I hate to tell you this, but those of us who predate TeX used *roff to write all sorts of things, including my dissertation. Writing elaborate man pages (e.g. with tables) is probably painful for anyone who doesn't already know *roff well, but most man pages require only a handful of macros and no understanding of how to write them or any of the other fine points.

    7. Re:Has anyone here tried to write man pages? by zsau · · Score: 1

      Complaints about info are generally about the interface. Perhaps someone should right the info program in a reasonable way. Everything in one page and scrolling line-by-line would be a great start. Also, a very nice and quick response a la man when there isn't an infopage would be nice. Why did they change the frontend when the backend was the problem?

      --
      Look out!
    8. Re:Has anyone here tried to write man pages? by Anonymous Coward · · Score: 0

      Acutally, using the 'an' macro package that
      man pages are written with is pretty straight
      forward. Probably easier than basic HTML.
      What you must be confusing things with is
      basic low-level n/troff. Low-level troff *is*
      somewhat difficult, but, it is also very power-
      ful.

    9. Re:Has anyone here tried to write man pages? by Pyromage · · Score: 1

      Perl without alphanum tokens? Yeah, that sounds like a pretty apt comparison :)

    10. Re:Has anyone here tried to write man pages? by Pyromage · · Score: 1

      I'm going to have to disagree with you there. One, people don't write docs enough :) That's why there's a need for a man page project.

      Two, info has cross-references. A lot of things are easier to read in a format with links, like HTML, which texinfo can output to. Now, this doesn't mean that texinfo is the optimal format, but I think man is certainly *not* the optimal format.

    11. Re:Has anyone here tried to write man pages? by justins · · Score: 1

      The complaint I've always had was pretty much unrelated to info itself. The whole notion of putting a message in a man page to the effect that it's just a placeholder and the user really ought to be using info if they want to find what they are looking for is basically akin to telling users to go fuck themselves. At least it sure feels that way when you're trying to get help from the machine...

      Add in a few whiny, clueless geek justifications for this user-hostile behavior and Linux folks certainly send many a user scampering back to Microsoft, with good reason.

      --
      Now before I get modded down, I be to remind whoever might read this that what I am saying is FACT. - bogaboga
    12. Re:Has anyone here tried to write man pages? by Haeleth · · Score: 1

      The whole notion of putting a message in a man page to the effect that it's just a placeholder and the user really ought to be using info if they want to find what they are looking for is basically akin to telling users to go fuck themselves. At least it sure feels that way when you're trying to get help from the machine...

      To you, maybe. To me it seems perfectly reasonable. I use "foo --help" if I want a list of command-line options, "man foo" if I want a summary of what foo does and basic descriptions of those options, and "info foo" if I want the full manual.

      Add in a few whiny, clueless geek justifications for this user-hostile behavior and Linux folks certainly send many a user scampering back to Microsoft, with good reason.

      Was that whiny and clueless? I hope not. Because I went scampering back to Microsoft a long time ago, and I *still* use man and info all the time...

    13. Re:Has anyone here tried to write man pages? by zsau · · Score: 1

      True; I forgot to mention that they should also name the program 'man' and have it read man pages if it can't find the relevant info pages (the assumption being that when there's both, the info page is preferred/doesn't say see the man page). (In other words, keep the interface the same, just change the backend.)

      --
      Look out!
    14. Re:Has anyone here tried to write man pages? by roqetman · · Score: 1

      I just write it in Perl's POD and run it through pod2man. Very easy.

    15. Re:Has anyone here tried to write man pages? by FattMattP · · Score: 1
      Two, info has cross-references. A lot of things are easier to read in a format with links, like HTML, which texinfo can output to. Now, this doesn't mean that texinfo is the optimal format, but I think man is certainly *not* the optimal format.
      I agree that cross-references can be very handy. Personally, my problem with info is that I can't figure out how to show all of the nodes on one page. I find it confusing to follow the nodes and then try to go back. It's much easier for me to go up and down a single page like in man.
      --
      Prevent email address forgery. Publish SPF records for y
  19. Who uses man anymorE? by Anonymous Coward · · Score: 0
  20. Wow. by Anonymous Coward · · Score: 0

    This is even better than the "my head hurts" stories.

  21. GNU info sucks. by Cryptnotic · · Score: 1, Troll

    Damn, the GNU-gestapo modded you flamebait already.
    Oh well, I have to agree with you. GNU info sucks.

    --
    My other first post is car post.
    1. Re:GNU info sucks. by AuMatar · · Score: 1

      Can someone tell me the point of info? I understand that it might be useful to have links to other utilities documentation, or split up the documentation into subcatagories, but do we really need info to do that? Why not just HTML and your favorite browser?

      --
      I still have more fans than freaks. WTF is wrong with you people?
    2. Re:GNU info sucks. by adrianbaugh · · Score: 2, Funny

      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.
    3. Re:GNU info sucks. by Anonymous Coward · · Score: 0

      Rather, HTML gets laughed at when Latex2HTML was created.

  22. favorite man command by gearheadsmp · · Score: 0

    I've heard the following command is popular in some places:
    $ man fsck

  23. Many man pages were already direct copies by Fefe · · Score: 1

    This is obviously a good thing to do for the Open Group. I wonder, though, why they say they grant the permission to the Linux Man Page Project. Their documents are freely redistributable anyway, so this in effect gives the content away.

    Many Linux man pages were already direct or very close copies, any the BSD man pages are also very close. And why wouldn't they? The content is quite formulaic and there is not much space for exploring language creativity, it's technical documentation after all.

  24. wtf? This wasn't automatic? by visualight · · Score: 4, Interesting

    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.
    1. Re:wtf? This wasn't automatic? by vidarh · · Score: 4, Informative

      Many standards organisations survive to a large extent on income generated by selling copies of the standards documents. It's only in recent years started becoming common for standards documents to be available free. Still, even now most ANSI and ISO standards for instance still costs money.

    2. Re:wtf? This wasn't automatic? by CRCulver · · Score: 2, Interesting

      Standards, when published in print, are often sold for a heck of a lot of money. Take for instance the Unicode standard. It's an open standard, and quite important for internationalisation in our digital age, but you'll pay $74 to get it. When Linus was developing Linux, he had to get his POSIX information through Minix because it was too expensive to go right to POSIX.

    3. Re:wtf? This wasn't automatic? by Oscar_Wilde · · Score: 1

      No, standards organizations like to make money from the information they provide. Many (most?) are for profit enterprises.

      You can often get hold of free, electronic, copies of standards via university libraries.

    4. Re:wtf? This wasn't automatic? by Anonymous Coward · · Score: 1, Informative

      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?

      Generally the IEEE (and ISO, ANSI, etc) don't make the standards available without some serious outlays of cash. I once needed access to a particular ANSI standard (X9.19, if you're curious), and found it cost ~$80. I managed to get a copy through ILL, and found that it was 20-30 staple-bound pages (most of which was legal garbage, with about 2 pages of useful info).

      Often ISO and IEEE will make the final draft available online, which is pretty useful, but you generally can't claim compliance without either buying the standard and/or going through expensive testing regimens. NIST will put the full final standard online, but they're always marked as being unofficial, if you want to claim compliance you have to buy the paper copy.

      It's the standard way of handling standards.

    5. Re:wtf? This wasn't automatic? by Anonymous Coward · · Score: 0

      This is commonly considered to be a major reason why TCP/IP won out over proprietory/paid-for standards. IETF standards are free to all to download, and other standards have a major hassle/price bump, so why bother with them? IETF rocks, the rest suck.

    6. Re:wtf? This wasn't automatic? by Homology · · Score: 1
      It's only in recent years started becoming common for standards documents to be available free. Still, even now most ANSI and ISO standards for instance still costs money.

      Indeed, and this makes it harder to write man pages to be distributed with free OS. Note that only the Linux project have a license, not everyone elses. Like Theo de Raadt of OpenBSD says : POSIX license

      > Having POSIX in man page form might be a good thing.

      Let us stay realistic. They did not make their documentation free. They gave someone a free license. That is not the same.

    7. Re:wtf? This wasn't automatic? by Haeleth · · Score: 1

      Take for instance the Unicode standard. It's an open standard, and quite important for internationalisation in our digital age, but you'll pay $74 to get it.

      Or just download the free PDFs from the Unicode Consortium's website. You aren't permitted to print them, but I for one can cope with missing out on the dead tree format.

  25. Good Show by t0ny · · Score: 0, Offtopic

    I like "The Man Show", but its just not the same since they got the Jimmy Kimmel and Adam Carolla impersonators on there.

    --

    Manipulate the moderator system! Mod someone as "overrated" today.

  26. Good, by noselasd · · Score: 2

    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 ,(

    1. Re:Good, by boots@work · · Score: 1

      You could already have got that information from the OpenGroup web site. This has always been a useful companion to the Linux manpages when for example one needs to be exactly sure about when a particular error will occur.

  27. Could this mean... by rhythmx · · Score: 2, Informative
    the beginnings of Linux-3.0.0??? from Linux kernel readme:
    WHAT IS LINUX? Linux is a Unix clone written from scratch by Linus Torvalds with assistance from a loosely-knit team of hackers across the Net. It aims towards POSIX compliance.
    The next major version will be released when the new kernel will break support for almost all existing binaries. If all the kernel interfaces are tweaked and made to be posix compliant. We may be seeing the Linux-3.0.0 soon!
  28. Caution! NSFW! by Anonymous Coward · · Score: 0

    Offensive ASCII graphic in parent post! Do not look!

  29. Certain interesting pages: by Anonymous Coward · · Score: 0

    man drake
    man date
    man atee
    man tego
    man ohman
    man dennishopper_man

  30. I use Gentoo... by Anonymous Coward · · Score: 0

    how does this affect me?

  31. Man & Info by ciaran_o_riordan · · Score: 0

    > besides GNU, who else favors info over man?

    When I need a quick reference, I use --help, when I need in-depth documentation, I look at an Info manual.

    If you don't like the command line 'info' utility, use one of the GNOME or KDE front ends, or try 'info --vi-keys', or try an alternative commandline info reader such as pinfo. (or write your own frontend, the GNU Info file format is very simlpe.)

    How would the 650 page GCC manual look as a man page? or how would you break it down into 300 individual pages? How do you turn 650 pages worth of manpages into a printable (and readable) book?

    I hated info when I was a newbie, but once you get used to it, it's quite good.

    1. Re:Man & Info by AJWM · · Score: 5, Informative

      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
    2. Re:Man & Info by Anonymous Coward · · Score: 0
      or try 'info --vi-keys'
      That is so much better. Thanks for the info ;)
    3. Re:Man & Info by torpor · · Score: 1

      I still lovingly remember the entire collection of MIPS documentation that came with my Magnum and R3200 systems. The 'man' 'manual' was about 5 inches thick, and the 7 others were hefty too, but the biggest stack of all were the updates and inserts.

      i never did get around to 'merging' all that into one big doc system before i (stupidly) threw it all out in the 90's, but if i had i would probably be very proud of that Unix Documentation Collection... ;)

      --
      ; -- the corruption of government starts with its secrets. a truly free people keep no secrets. --
  32. What I like about 'man' by baywulf · · Score: 1

    You can generate postscript output for printing like this for example:

    man -t ls

    Don't know if this can be done with info?

    1. Re:What I like about 'man' by andrel · · Score: 1
      Most info files are written using texinfo which outputs various formats including Info, PDF and HTML. The hardcopy manuals sold by GNU Press come from the same source file as the softcopy documentation on your computer.

      (Texinfo is several years older than either PDF or HTML. If web browsers had already existed the GNU project probably wouldn't have invented info browsers.)

  33. Remind me again...? by Anonymous Coward · · Score: 0

    What does "POS" stand for?

    1. Re:Remind me again...? by Anonymous Coward · · Score: 0

      Point of Sale

  34. What are Man pages? by Omega1045 · · Score: 1, Funny

    I don't understand what these "Man" pages are? Is this some sort or web pages of porn for women, is it gay? Is this trendy? Should I "like" or "groove" on "Man" pages?

    --

    Great ideas often receive violent opposition from mediocre minds. - Albert Einstein

  35. Use POD and pod2man by barries · · Score: 2, Informative
    Yeah, it's trival: use POD. And pod2man. Or any other format you want (po2html, pod2text, etc) on almost any system with Perl on it. And integrate it in to your program as online help. And usage. And and and...

    Use the right tool, don't let the wrong tool use you.

    - Barrie

  36. Examples..... by nighty5 · · Score: 2, Insightful

    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.

    1. Re:Examples..... by Anonymous Coward · · Score: 0

      Yeah, no shit. Back when I was doing some Linux network programming I would log into our AIX box to look up the man pages, which had lots of actual in context examples, and didn't require you to memorize the network programming bible.

    2. Re:Examples..... by Anonymous Coward · · Score: 0

      Errr, do you mean like the ones you get with:
      man 5 crontab
      in the "Example" section?

      Don't forget there are intentionally separate pages for programs and config files.

    3. Re:Examples..... by Anonymous Coward · · Score: 0

      Matt Dillon's cron package has examples in the manpages. Blame yourself for using Vixie!

    4. Re:Examples..... by Anonymous Coward · · Score: 0

      My 'man 5 crontab' (on a fedora box) gives examples and lists Paul Vixie as the author.

    5. Re:Examples..... by Shadowlore · · Score: 2, Informative
      Insightful?!?!?! It's dead wrong!

      I teach System Admin. Had a class this week in fact. Used the man page on crontab to do it, and it included examples right there in the manpage.


      EXAMPLE CRON FILE
      # use /bin/sh to run commands, no matter what /etc/passwd says
      SHELL=/bin/sh
      # mail any output to `paul', no matter whose crontab this is
      MAILTO=paul
      #
      # run five minutes after midnight, every day
      5 0 * * * $HOME/bin/daily.job >> $HOME/tmp/out 2>&1
      # run at 2:15pm on the first of every month -- output mailed to paul
      15 14 1 * * $HOME/bin/monthly
      # run at 10 pm on weekdays, annoy Joe
      0 22 * * 1-5 mail -s "It's 10pm" joe%Joe,%%Where are your kids?%
      23 0-23/2 * * * echo "run 23 minutes after midn, 2am, 4am ..., everyday"
      5 4 * * sun echo "run at 5 after 4 every sunday"


      That is taken from the man page for crontab, section 5, from RH9/Fedora. I also contains a detailed description of each field.
      --
      My Suburban burns less gasoline than your Prius.
  37. SCO relevancy? by Anonymous Coward · · Score: 1, Interesting

    Maybe this screws SCO and their hope to cash in on #DEFINE's?

  38. XSLT to generate man pages by KidSock · · Score: 4, Interesting

    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.

    1. Re:XSLT to generate man pages by lewp · · Score: 2, Insightful

      XSLT? He wants easier, not harder. That's probably the one thing I wouldn't recommend he try.

      --
      Game... blouses.
    2. Re:XSLT to generate man pages by Anonymous Coward · · Score: 0

      Congradulations on becomming the highest jargon per minute winner!

    3. Re:XSLT to generate man pages by juhaz · · Score: 1

      Well XSLT may be bit hard to write, but it only needs to be done once - when you have the stylesheet you can transform bazillion source documents without ever touching it again.

  39. Re:Lot's [sic] of truth in the Parent! by AJWM · · Score: 1

    I can understand how someone who is so illiterate as to put an apostrophe in "lots" might have trouble reading man pages.

    The fact is, however, that most people who would refer to them will have no problem at all.

    (Nor does a preemptive attempt to avoid a troll rating make it any less a troll.)

    --
    -- Alastair
  40. POSIX standard onlin by fredex · · Score: 2, Interesting
    The article says:
    Another was the recent decision to make the POSIX standard freely available on the Internet.
    but where are they "freely" available? I've just scored both ieee and open group websites and the best I can find is some PDF documents at prices beginning around $105 and going up. Not what I call freely available.
    1. Re:POSIX standard onlin by Anonymous Coward · · Score: 2, Informative

      Download POSIX 2001.

      (POSIX 2001 and SUSv3 are the same document.)

    2. Re:POSIX standard onlin by Anonymous Coward · · Score: 0

      Really? Isn't the point of SUS to add lots of stuff on top of POSIX?

    3. Re:POSIX standard onlin by Anonymous Coward · · Score: 0

      Really? Isn't the point of SUS to add lots of stuff on top of POSIX?

      Not any longer.

  41. Under what terms? by The+Wicked+Priest · · Score: 1

    I couldn't find it spelled out just what the license terms (if any?) would be. Not to be paranoid, but if the license isn't sufficiently liberal, this has the potential to be a trap.

    --
    Share and Enjoy: 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
    1. Re:Under what terms? by swordgeek · · Score: 0, Flamebait

      Oh yes, The License. What about The License? We can't touch ANYTHING that isn't blessed by The License, lest it be a trap set by our enemies to smite us.

      Fuck the license! The GPL and the endless whining over license minutae have done more harm to Linux and its public image than Microsoft, SCO, the RIAA, and bad hygiene combined!

      Every single FUCKING preemptive license question is a guarantee that even more people are going to explicitly avoid Linux, and free software in general.

      --

      "People who do stupid things with hazardous materials often die." -- Jim Davidson on alt.folklore.urban
  42. Re:nothing by Anonymous Coward · · Score: 0

    ...Soviet Russian man format...what's it all about? Is it cool, or is it whack?

  43. Grow Up by Saeed+al-Sahaf · · Score: 1

    If I invalidated arguments here at Slashdot based on grammar and spelling (there, their, they're), there would not be much left to read. Grow up.

    --
    "Who are in control, they are not in control of anything - they don't even control themselves!" - Glen Beck
    1. Re:Grow Up by AJWM · · Score: 1

      Perhaps. It's just rather ironic that someone complaining that man pages are poorly written demonstrates a an inability to use the language correctly, one that I've not seen in man pages.

      In an informal technical discussion, grammar and spelling can often be forgiven if the main point is clear. When the main point is complaining about writing, grammar and spelling become rather relevant to the point.

      --
      -- Alastair
    2. Re:Grow Up by Anonymous Coward · · Score: 0

      OK, I will not point out all the mistakes you've made in your post.

  44. Grumpy middle-aged man wakes up by JoeBuck · · Score: 4, Interesting

    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.

  45. Re:[dog@linux:/home]$ man weiner (Sc ore:5, Funny) by Anonymous Coward · · Score: 0

    Best post ever.

  46. I'll have to thank [IEEE Pres] Dr Chang... by LordKazan · · Score: 1

    I'll have to stop into [IEEE President] Dr Chang's office and thank him on behalf of slashdot (he's the CS department chair where i go to school)

    --
    If you cannot keep politics out of your moderation remove yourself from the Mod Lottery.. NOW!
    1. Re:I'll have to thank [IEEE Pres] Dr Chang... by Anonymous Coward · · Score: 0

      (he's the CS department chair where i go to school)

      Do you sit on him daily?

  47. wow... by pb · · Score: 1

    You *are* pretty old for someone with a 4-digit uid! :)

    --
    pb Reply or e-mail; don't vaguely moderate.
  48. Source code... by Anonymous Coward · · Score: 0

    Linux fucking sucks.

    Use FreeBSD instead.

  49. Release Notes (man-pages-1.65.Announce) by An+Anonymous+Hero · · Score: 4, Informative

    (Since this is not very informative:)
    RELEASE
    The Linux man page maintainer proudly announces. . .

    man-pages-1.65.tar.gz - man pages for Linux

    POSIX
    This release is the first to contain the POSIX 1003.1-2003 man pages. The directories man0p, man1p, man3p contain descriptions of the headers, the utilities, and the functions documented in that standard.

    Permission to distribute these POSIX man pages has just been obtained, and the pages in man0p, man1p, man3p were derived from the POSIX html pages by some silly conversion script. No doubt the result is still full of flaws, and all of this can be much improved. Corrections, scripts, etc. are welcome - aeb@<snip>.

    In order to use this, put in {/usr/share/misc/}man.conf{ig} or so your favourite order of looking at these pages, for example,
    MANSECT 1p:1:8:0p:3p:2:3:4:5:6:7:9:tcl:n:l:p:o
    or set the MANSECT environment variable.

    OTHER PAGES
    The remaining pages are most of the section 2, 3, 4, 5, 7 man pages for Linux, and in addition section 1 man pages for the fileutils-4.0 utilities, and section 5 and 8 man pages for the timezone utilities.

    [The latter were taken from ftp://elsie.nci.nih.gov/pub/tzcode2001a.tar.gz.] [The section 3 man pages for the db routines have been taken from ftp://ftp.terra.net/pub/sleepycat/db.1.86.tar.gz.] [The rpc man pages were taken from the 4.4BSD-Lite CDROM.]

    Differences from version 1.64:

    POSIX pages were added

    The man pages

    chroot.2 clone.2 intro.2 mkdir.2 remap_file_pages.2

    errno.3

    sk98lin.4

    elf.5 protocols.5 raw.7

    are new or have been updated. Typographical or grammatical errors have been corrected in several other places.

    Here is a breakdown of what this distribution contains:

    Section 0p = POSIX headers
    Section 1p = POSIX utilities
    Section 3p = POSIX functions

    Section 1 = user commands (intro, and pages not maintained by FSF)
    Section 2 = system calls
    Section 3 = libc calls
    Section 4 = devices (e.g., hd, sd)
    Section 5 = file formats and protocols (e.g., wtmp, /etc/passwd, nfs)
    Section 6 = games (intro only)
    Section 7 = conventions, macro packages, etc.
    Section 8 = system administration (intro only)

    Usually, there are no section 1, 6 and 8 man pages because these should be distributed with the binaries they are written for. Sometimes Section 9 is used for man pages describing parts of the kernel.

    Note that only Section 2 is rather complete, but Section 3 contains several hundred man pages. If you want to write some man pages, please do so and mail them to aeb@<snip>.

    The following people (listed in alphabetical order by first name) wrote, edited, or otherwise contributed to this project:

    <snip>

    Copyright information:

    For the POSIX pages permission to distribute was given by IEEE and the Open Group, see POSIX-COPYRIGHT.

    For the remaining pages, please note that these man pages are distributed under a variety of copyright licenses. Although these licenses permit free distribution of the nroff sources contained in this package, commercial distribution may impose other requirements (e.g., acknowledgement of copyright or inclusion of the raw nroff sources with the commercial distribution).
    If you distribute these man pages commercially, it is your responsibility to figure out your obligations. (For many man pages, these obligations require you to distribute nroff sources with any pre-formatted man pages that you provide.) Each file that contains nroff source for a man page also contains the author(s) name, email address, and copyright notice.
    1. Re:Release Notes (man-pages-1.65.Announce) by Anonymous Coward · · Score: 0
      errno.3
      We will be hearing from SCO's lawyers very soon...
  50. Grammar police by Anonymous Coward · · Score: 0

    You mean, "The truth is, man pages are almost unreadable; unless you already know the material, they are not designed for the unwashed like you and me." If you want to be extra pedantic, replace like with such as as well.

    1. Re:Grammar police by Anonymous Coward · · Score: 0


      You mean, "...they are not designed for the unwashed like you and me."

      Filling in the implied, missing word, gives:

      ...they are not designed for the unwashed like you and me are.

      Since when does the subject of a verb take the accusative case?
      </flame>

    2. Re:Grammar police by Anonymous Coward · · Score: 0

      No, there is no implied verb, because like is not a conjunction and takes only a noun in the accusative case. If you used as, for example, "they are not designed for the unwashed as you and I are", then you would have a point.

  51. man pages? by Brandybuck · · Score: 1

    man pages for Linux? Next thing you know, Beastie will be ice skating...

    --
    Don't blame me, I didn't vote for either of them!
  52. konqui as a man and info viewer by InodoroPereyra · · Score: 1

    Or just use "info:whatever" in Konqueror. Even doing "info:" will show you an index of Info pages. You can do the same trick with man pages: "man:whatever".

  53. Re:Captain's Log: My Anus is too Fucking Tight by Beek · · Score: 0, Offtopic

    Thank you for reminding why I use the +6 Troll modifier :-)

  54. But is it ok for...? by koafc · · Score: 1

    Is it ok for women to use? They never said.

  55. (re: pinfo) by Tomble · · Score: 1
    Yeah, I use that quite a bit, it's nice, but it's a bit buggy (the slightly old version I have from Debian, at least)- I forget the exact details, but IIRC it would muck about with the file names or node names or something. Whatever it was, it affected GDB and GDBM, and it assumed references to one were actually references to the other (I forget which way round it did this).

    Perhaps this was something to do with the format itself, but IIRC the plain old info command didn't do that. Actually, hold on...

    ...OK: No, GNU info doesn't, and pinfo thought gdb was short for gdbm. This may be fixed in newer versions, but the web page doesn't seem to say, and I don't care enough to try installing from source. Apart from that, it is a pretty good info browser, especially considering how I used to get tied in knots before by GNU info (hate hate hate GNU info).

    --
    Be careful! New moon tonight.
    1. Re:(re: pinfo) by Haeleth · · Score: 1

      No, GNU info doesn't, and pinfo thought gdb was short for gdbm.

      WFM (pinfo 0.6.7).

      I've noticed in the past that GNU info and pinfo handle $INFOPATH and directory files slightly differently, so maybe your problem is connected with that.

  56. Whatever... by bluewee · · Score: 1

    Never read it, nor thought ever to, but I guess all the more power to them...

    --
    [blue] - The Ministry of Information approved this message...
  57. Re: Why info? by some+guy+I+know · · Score: 2, Informative
    Can someone tell me the point of info? [...] Why not just HTML and your favorite browser?
    The info format was created a long time ago.
    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
  58. Re: Why info? by some+guy+I+know · · Score: 1

    BTW, many, many utilities exist for translating info docs into HTML.

    --
    Those who sacrifice security to condemn liberty deserve to repeat history or something. - Benjamin Santayana
  59. They're doing this 10 years too late by njdj · · Score: 1

    If IEEE had made this POSIX documentation freely available 10 years ago, that would have helped the free software community a lot.

    Doing it now, after volunteers have painstakingly written >95% of the man pages from scratch, is almost irrelevant.

  60. Re: Improving grammer by some+guy+I+know · · Score: 1
    They still need to improve the hideous grammar of the man pages
    How about "man anything"?
    --
    Those who sacrifice security to condemn liberty deserve to repeat history or something. - Benjamin Santayana
  61. Re:Could this mean... Linux 2.x is dying? by jasoneyre · · Score: 1

    Come on...

    Where are the early-warning trolls? :)

    Cheerz,
    jason

    --
    THSsMCHshrtrTHN160chrs -- And I don't even like to SMS!
  62. Re:Lot's [sic] of truth in the Parent! by Anonymous Coward · · Score: 0

    I hate grammer nazis, and I'm sure I'll get bit too. His basic argument is sound I believe, man pages are written assuming you already have a base understanding of the material at hand. Thats not necissarily bad if your an admin learning a new trick or service, but for someone truely new to Unix its hell. I remember being dropped at the bash prompt after installing Red Hat 5.1 years ago and being told "read the man pages!" if I ever had a problem. They didn't help, at all. Now that I'm much more experienced their not that bad, but their not all that approachable by most normal human beings either. I'm not suggestioning that every man page be dumbed down for newbies, but some sort of middle ground or newbie friendly help system would be nice.

  63. Re:[dog@linux:/home]$ man weiner (Sc ore:5, Funny) by Anonymous Coward · · Score: 0

    That's beautiful

  64. POSIX Compliance? by j.leidner · · Score: 1
    It would be interesting to hear about plans for integrating "STANDARD COMPLIANCE" sections into the Linux version of the POSIX man pages (or other Linux-specific material).

    How are the two document bases (GNU man documents vs. POSIX man documents) going to be integrated?

  65. Are SCO Posix-compliant? by tiger99 · · Score: 1
    I wonder if this will provoke Desperate Darl McFraud to even greater acts of lunacy if he thinks Linux has been given an unfair advantage?

    BTW I hope this also applies to xBSD and any other free OS, and I hope it marks the beginning of a trend towards standards being free and open, but somehow I think not, because the standards bodies have not yet devised an alternative way of funding their work.

    Sad, but the cost of acquiring lots of standards, in order to be able to do essential work, really damages small to medium buisnesses, whereas the big boys nuy one copy and distribute it, usually illegally, on their intranet.

    BTW I am all for standards compliance, it is best for everyone, but first there has to be a standard, and then it has to be properly documented and published with full disclosure, by a competent standards organisation, or it is worthless, like the slogan "We set the standard" which IIRC originated some years ago from the vile, later to be convicted, Monopolist. Standard? Windoze? I think not, more like a randomly drifting set of obscure, inaccurately documented, and convoluted APIs which may change at any time without prior warning.

  66. Re: Why info? by bfields · · Score: 1
    The info format was created a long time ago. 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.

    There are still some things I miss when using html documentation that I appreciate in info:

    • structured navigation: u, n, p take me, respectively, up a level, to the next section, and to the previous section. My understanding is that html gives the ability to express that kind of structure but that most browsers don't currently provide a convenient user interface for it; so maybe that'll change some day.
    • easy searching: ^S and / are extremely helpful; no browser I use seems to provide similar functionality for documents split between multiple pages.

    --Bruce Fields

  67. Re: Why info? by Black+Acid · · Score: 1
    structured navigation: u, n, p take me, respectively, up a level, to the next section, and to the previous section. My understanding is that html gives the ability to express that kind of structure but that most browsers don't currently provide a convenient user interface for it; so maybe that'll change some day.

    Galeon supports mouse gestures for this. Left-down is previous, right-down is next, and up-left-right-up is table of contents. These gestures use link rel tags, if present.
  68. In lieu of pinfo or konqueror ... by Imran · · Score: 1
    BTW, if you don't have access to either pinfo or konqueror, and can't stand (dont blame you) the regular info viewer, then try this (don't remember where I originally got this from) :
    i()
    {
    info "$1" --subnodes --output - 2>/dev/null | less
    }
    I have this in a more comprehensive wrapper, which does other stuff like setting term & screen titles, etc - but the above function should suffice. Particularly useful if you are looking for something specific, and want to search directly for it.
  69. Re: Why info? by bfields · · Score: 1
    Galeon supports mouse gestures for this. Left-down is previous, right-down is next, and up-left-right-up is table of contents. These gestures use link rel tags, if present.

    Hmm. And I just noticed mozilla will use the link rel tags too (view->show/hide->site navigation bar), though I can't seem to find keyboard shortcuts. Also I can't figure out whether lynx does this.

    --Bruce Fields

  70. xml2man by Anonymous Coward · · Score: 0

    Try out xml2man

    Walden.

  71. Re:Lots of truth in the Parent! by wtrmute · · Score: 1

    But the man pages *are* written for people who already know the material. Man pages are *reference* -- you already know how to use select(), fstab, or what-have-you but just want to check the parameter list, valid modifiers, etc.

    If you want to learn how to use something, you go to the how-to, or the guide, or a tutorial on the Web. That's what they're for.

    And please ease on the attitude. Contrary to popular belief, people aren't branded as trolls for having opinions contrary to /. mainstream, they're branded for being rude and/or whiney about it :-(

  72. cascade-inspired by BorgCopyeditor · · Score: 1
    Let's try the full title:
    $ eat drink man woman
    bash: eat: command not found
    Bummer.
    --
    Shop as usual. And avoid panic buying.