From: "Boyd Roberts" <boyd@noos.fr>
To: "Alexander Viro" <viro@math.psu.edu>
Cc: <9fans@cse.psu.edu>
Subject: Re: [9fans] Progeny Linux's Linux NOW
Date: Fri, 28 Jul 2000 00:09:46 +0200 [thread overview]
Message-ID: <009c01bff817$6192a540$03c684c3@psychobasketcase.org> (raw)
In-Reply-To: <Pine.GSO.4.10.10007271657150.4986-100000@weyl.math.psu.edu>
_learn_ them BOZO? he'll i've grown up with 'em.
man i've forgotten more clues than you'll _ever_ learn.
you _tried_ to fix linux? that says a _lot_.
207:boyd:boyd:
--
Boyd Roberts boyd@psycho-basket-case.org
``I come over here to kill them cocksuckers, not work for 'em''
-- Moon Dog, _Pettibone's Law_, John Keene
----- Original Message -----
From: Alexander Viro <viro@math.psu.edu>
To: Boyd Roberts <boyd@planete.net>; <9fans@cse.psu.edu>
Sent: Thursday, July 27, 2000 11:15 PM
Subject: Re: [9fans] Progeny Linux's Linux NOW
>
>
> On Thu, 27 Jul 2000, Boyd Roberts wrote:
>
> > yeah, just a bit more code in linux and then we'd really have
> > something -- a bigger piece of shit than we already have.
>
> _less_ code, please. And you are apparently confusing the thing with GNU.
>
> > you do MORE with LESS.
>
> You know, that bright idea occured to many people. It would be really fine
> if you would manage to learn arcane utilities called find(1), wc(1) and
> tar(1) and took a look at 2.2 and 2.4. Particulary, at the subtree called
> "fs".
>
> IOW, getting some clue before posting is usually a good idea. Keeping
> advocacy in the gutter where it belongs is also considered a Good
> Thing(tm).
>
> PS: let's not go into DSW on Linux LI, OK? I really can bring more
> examples of its suckitude than you will ever be able to. Honest.
> BT,DT,fixed quite a few of them.
>
> Al "-15kLOC during the last year" Viro
>
>
next prev parent reply other threads:[~2000-07-27 22:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ru@ohio.river.org>
2000-07-27 18:05 ` Richard Uhtenwoldt
2000-07-27 18:42 ` Alexander Viro
2000-07-27 20:30 ` Scott Schwartz
2000-07-27 20:46 ` Alexander Viro
2000-07-27 20:49 ` Boyd Roberts
2000-07-27 21:15 ` Alexander Viro
2000-07-27 21:49 ` Richard
2000-07-27 22:01 ` Alexander Viro
2000-07-27 22:09 ` Boyd Roberts [this message]
2000-07-27 22:30 ` Alexander Viro
2000-07-27 22:39 ` Boyd Roberts
2000-07-27 22:55 ` [9fans] Alexander Viro <viro@math.psu.edu> Boyd Roberts
2000-07-27 23:09 ` Alexander Viro
2000-07-28 0:02 ` Boyd Roberts
2000-08-02 21:57 ` [9fans] Progeny Linux's Linux NOW Tom Duff
2000-08-02 22:02 ` Tom Duff
2000-08-03 8:35 ` Boyd Roberts
2000-08-02 22:38 dhog
2000-08-03 5:12 forsyth
2000-08-03 5:57 ` Alexander Viro
2000-08-03 16:00 ` Tom Duff
2000-08-03 16:06 ` Tom Duff
2000-08-04 9:18 ` Boyd Roberts
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='009c01bff817$6192a540$03c684c3@psychobasketcase.org' \
--to=boyd@noos.fr \
--cc=9fans@cse.psu.edu \
--cc=viro@math.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).