Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: GNU-Linux vs Linux naming [was RE: LAM/MPI Parallel processing]
- To: tlug@example.com
- Subject: Re: GNU-Linux vs Linux naming [was RE: LAM/MPI Parallel processing]
- From: Simon Cozens <simon@example.com>
- Date: Thu, 7 Sep 2000 13:18:38 +0100
- Content-Disposition: inline
- Content-Type: text/plain; charset=us-ascii
- In-Reply-To: <14775.29695.536967.913439@example.com>; from turnbull@example.com on Thu, Sep 07, 2000 at 07:54:55PM +0900
- References: <FOEBIKDLMFBGOKGGBGDEAENPCEAA.jshore@example.com> <m2u2bu84tz.fsf@example.com> <20000906100813.A15622@example.com> <m2n1hk6hfx.fsf@example.com> <14775.4589.886336.421908@example.com> <20000907105314.A27774@example.com> <14775.29695.536967.913439@example.com>
- Reply-To: tlug@example.com
- Resent-From: tlug@example.com
- Resent-Message-ID: <2HtxED.A.XDF.BH5t5@example.com>
- Resent-Sender: tlug-request@example.com
- Sender: Simon Cozens <simon@example.com>
- User-Agent: Mutt/1.2.5i
On Thu, Sep 07, 2000 at 07:54:55PM +0900, Stephen J. Turnbull wrote: > >>>>> "Simon" == Simon Cozens <simon@example.com> writes: > Simon> This is what /bin/sync *should* look like, dammit: > > Wow, that _is_ disgusting; the docs for GNU sync say that "sync does > nothing but exercise the kernel call" So what's this: % sync --help Usage: sync [OPTION] Force changed blocks to disk, update the super block. --help display this help and exit --version output version information and exit Report bugs to <bug-fileutils@example.com>. > but the "author" managed to put his name into the version string. To be honest, I did omit 46 lines of copyright info and version strings. But on average, BSD binaries appear to be half the size of GNU equivalents. > Still, sync is an extreme case. Programs should be self-documenting. > (And not by reading source, either.) Self-documenting without reading the source? Hmm, are you advocating literate programming, or something like POD or Javadoc? > Simon> [1] I'd do it myself but I'm mainly offline due to the UK's > Simon> extremely backwards Internet connectivity. > So you haven't been following the "Beavis is back" thread? Look. I connect to Cable and Wireless. It doesn't get *much* worse. Simon -- 10. The Earth quakes and the heavens rattle; the beasts of nature flock together and the nations of men flock apart; volcanoes usher up heat while elsewhere water becomes ice and melts; and then on other days it just rains. - Prin. Dis.
- Follow-Ups:
- Re: GNU-Linux vs Linux naming [was RE: LAM/MPI Parallel processing]
- From: "Stephen J. Turnbull" <turnbull@example.com>
- References:
- RE: GNU-Linux vs Linux naming [was RE: LAM/MPI Parallel processing]
- From: "Jonathan Shore" <jshore@example.com>
- Re: GNU-Linux vs Linux naming [was RE: LAM/MPI Parallel processing]
- From: SL Baur <steve@example.com>
- Re: GNU-Linux vs Linux naming [was RE: LAM/MPI Parallel processing]
- From: Simon Cozens <simon@example.com>
- Re: GNU-Linux vs Linux naming [was RE: LAM/MPI Parallel processing]
- From: SL Baur <steve@example.com>
- Re: GNU-Linux vs Linux naming [was RE: LAM/MPI Parallel processing]
- From: "Stephen J. Turnbull" <turnbull@example.com>
- Re: GNU-Linux vs Linux naming [was RE: LAM/MPI Parallel processing]
- From: Simon Cozens <simon@example.com>
- Re: GNU-Linux vs Linux naming [was RE: LAM/MPI Parallel processing]
- From: "Stephen J. Turnbull" <turnbull@example.com>
Home | Main Index | Thread Index
- Prev by Date: Re: GNU-Linux vs Linux naming [was RE: LAM/MPI Parallel processing]
- Next by Date: PCMCIA Card Not Working in OpenLinux 2.3
- Prev by thread: Re: GNU-Linux vs Linux naming [was RE: LAM/MPI Parallel processing]
- Next by thread: Re: GNU-Linux vs Linux naming [was RE: LAM/MPI Parallel processing]
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links