9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Francisco J Ballesteros <nemo@lsub.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Cc: mirtchovski@gmail.com
Subject: Re: [9fans] quote o' the day
Date: Thu, 25 Mar 2010 22:17:30 +0100	[thread overview]
Message-ID: <8ccc8ba41003251417x1ec6a645y171736b0fbe6a352@mail.gmail.com> (raw)
In-Reply-To: <badd51f0aec9483d9cdf7ac72b81dcbd@bellsouth.net>

As a example for our students we use

http://git.savannah.gnu.org/gitweb/?p=coreutils.git;a=blob;f=src/cat.c;hb=HEAD

versus

http://plan9.bell-labs.com/sources/plan9/sys/src/cmd/cat.c

In fact, we have both printed on paper hanging from the wall of the corridor
near our office. Let's hope they learn.


On Thu, Mar 25, 2010 at 7:51 PM,  <blstuart@bellsouth.net> wrote:
>> in similar vein, there's this handful guide on how to make your life
>> really hard in 11 easy steps:
>>
>> http://www.pixelbeat.org/docs/unix_file_replacement.html
>>
>> make sure you check out the final copy.c linked at the bottom of the page
>
> It's a sign of the apocalypse.  The configuration of the 6th edition
> kernel Lions presented was about 10,000 lines of code.  This version
> of cp is nearly 1/4 of that, and the function copy_internal() is over
> 1000 lines long.  I'm clearly not smart enough to function in a world
> where cp is that complex...
>
> Back to real work...again...for real this time...I promise...
> BLS
>
>
>



  reply	other threads:[~2010-03-25 21:17 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-25 14:08 erik quanstrom
2010-03-25 15:04 ` maht
2010-03-25 16:56   ` ron minnich
2010-03-25 17:11     ` Corey Thomasson
2010-03-25 17:15       ` maht
2010-03-25 17:26         ` Corey Thomasson
2010-03-25 17:33         ` Robert Raschke
2010-03-25 17:42       ` David Leimbach
2010-03-25 17:29     ` erik quanstrom
2010-03-25 17:31 ` blstuart
2010-03-25 16:44   ` Patrick Kelly
2010-03-25 18:31     ` blstuart
2010-03-25 18:33     ` andrey mirtchovski
2010-03-25 18:37       ` erik quanstrom
2010-03-25 18:51       ` blstuart
2010-03-25 21:17         ` Francisco J Ballesteros [this message]
2010-03-25 20:26           ` Patrick Kelly
2010-03-25 21:58           ` Tim Newsham
2010-03-25 21:21             ` Patrick Kelly
2010-03-25 22:37               ` Justin Jackson
2010-03-25 22:53                 ` erik quanstrom
2010-03-25 22:57             ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2010-03-26  0:03               ` Anthony Sorace
2010-03-26  2:16                 ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2010-03-26  6:43               ` Tim Newsham
2010-03-26 13:54                 ` andrey mirtchovski
2010-03-28 23:22                   ` Jack Johnson
2010-03-26  0:36             ` Corey Thomasson
2010-03-26  9:19           ` hugo rivera
2010-03-28 23:05           ` Eris Discordia
     [not found]           ` <989B4954D6C952C13793229D@192.168.1.2>
2010-03-28 23:31             ` hiro
2010-03-28 23:41             ` Connor Lane Smith
2010-03-28 23:51   ` hiro

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=8ccc8ba41003251417x1ec6a645y171736b0fbe6a352@mail.gmail.com \
    --to=nemo@lsub.org \
    --cc=9fans@9fans.net \
    --cc=mirtchovski@gmail.com \
    /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).