9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] farewell to /sys/src/fs and IL
Date: Fri, 31 Aug 2007 15:35:52 -0400	[thread overview]
Message-ID: <a01bd0e927f8aded1e823b741f966186@coraid.com> (raw)
In-Reply-To: <887856e91bcd2ab6df84dbc089414f76@plan9.bell-labs.com>

> If you're running ken's fileserver, I trust that you're compiling your
> own kernels.
> 
> All you have to add to cpu kernels from sources to reinstate IL are
> the current /sys/src/9/ip/il.c and add "il" to the kernel
> configuration files (or keep your current ones).  replica/pull will
> remove il.c once, but thereafter pull should leave it alone (if it
> doesn't, I'll manually remove il.c from plan9.db on sources, which
> will force pull to leave it alone).  Likewise for /sys/src/fs (if
> that's the `kernel from sources' you're referring to).

we run kernels directly from sources on quite a number of machines.

one advantage of this is that if there's a problem with the kernel,
it's clear that local modifications are not to blame.

i can't see the harm in leaving il.c in the kernel.  it shouldn't require
much maintence at all.  i volunteer to do any work required to keep
it up-to-date.

- erik


      reply	other threads:[~2007-08-31 19:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-30 22:27 geoff
2007-08-31 18:22 ` erik quanstrom
2007-08-31 18:42   ` Skip Tavakkolian
2007-08-31 19:03     ` Francisco J Ballesteros
2007-08-31 19:04       ` Francisco J Ballesteros
2007-08-31 19:15         ` erik quanstrom
2007-08-31 19:23           ` erik quanstrom
2007-08-31 22:12       ` Steve Simon
2007-08-31 19:14     ` Eric Van Hensbergen
2007-08-31 19:42       ` geoff
2007-08-31 19:30   ` geoff
2007-08-31 19:35     ` erik quanstrom [this message]

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=a01bd0e927f8aded1e823b741f966186@coraid.com \
    --to=quanstro@coraid.com \
    --cc=9fans@cse.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).