9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: forsyth@caldo.demon.co.uk
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Df command in Plan9?
Date: Sun, 22 Oct 2000 18:06:11 +0100	[thread overview]
Message-ID: <20001022170959.4512B199D9@mail> (raw)

[-- Attachment #1: Type: text/plain, Size: 380 bytes --]

thank you.  i suppose the .renamin technique was adopted to allow
patching binaries.  to draw things back to plan 9,
i thought the following rule was interesting:

``for a binary to expect a file at a specific full pathname is bad practice.''

curiously, that is regarded as standard practice and
perhaps even essential for both Plan 9 and Inferno.
o tempora, o mores!


[-- Attachment #2: Type: message/rfc822, Size: 2095 bytes --]

From: Rick Hohensee <humbubba@smarty.smart.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Df command in Plan9?
Date: Sun, 22 Oct 100 12:05:44 -0400 (EDT)
Message-ID: <200010221605.MAA11584@smarty.smart.net>

>
> >>BTW, the stuff I HAVE basically silently been informed won't be going into
> >>the Linus Linux tree is my stuff to support booting to /.sbi/init so that
> >>the dirnames the user sees can be internationalized or otherwise
> >>localized. 2 execve's in init/main.c.
>
> i didn't understand this bit.
>
>

   Linkname: seedoc of the Dotted Standard Filename Hierarchy
        URL: ftp://linux01.gwdg.de/pub/cLIeNUX/descriptive/DSFH.html
       size: 251 lines

Rick Hohensee

             reply	other threads:[~2000-10-22 17:06 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-22 17:06 forsyth [this message]
2000-10-23  2:23 ` Rick Hohensee
  -- strict thread matches above, loose matches on Subject: below --
2000-10-22 11:04 forsyth
2000-10-22 12:49 ` Boyd Roberts
2000-10-22 13:16 ` Alexander Viro
2000-10-22 16:07   ` Rick Hohensee
2000-10-22 16:31     ` Alexander Viro
2000-10-23  2:07       ` Rick Hohensee
2000-10-22 16:05 ` Rick Hohensee
2000-10-20 21:51 presotto
2000-10-20 20:31 Russ Cox
2000-10-20 21:44 ` Alexander Viro
2000-10-20 21:51   ` Boyd Roberts
2000-10-21  0:37   ` Rick Hohensee
2000-10-21 10:13     ` Alexander Viro
2000-10-22  0:13       ` Rick Hohensee
2000-10-22  0:25         ` Boyd Roberts
2000-10-22 15:41           ` Rick Hohensee
2000-10-23  9:02           ` Douglas A. Gwyn
2000-10-23 10:30             ` Alexander Viro
2000-10-24 11:37             ` Boyd Roberts
2000-10-25  8:30               ` Douglas A. Gwyn
2000-10-26  4:54                 ` Alexander Viro
2000-10-26  5:44                   ` Boyd Roberts
2000-10-22 11:34         ` Alexander Viro
2000-10-22 15:59           ` Rick Hohensee
2000-10-22 16:43             ` Alexander Viro
2000-10-23  5:06             ` Boyd Roberts
2000-10-20 20:22 Mark C. Otto

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=20001022170959.4512B199D9@mail \
    --to=forsyth@caldo.demon.co.uk \
    --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).