9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Ethan Gardener <eekee57@fastmail.fm>
To: 9fans@9fans.net
Subject: Re: [9fans] renaming rio to rioc!
Date: Tue,  2 Oct 2018 18:31:06 +0100	[thread overview]
Message-ID: <1538501466.2475179.1528166336.6754D8D2@webmail.messagingengine.com> (raw)
In-Reply-To: <20181002142847.yfmkl4lm7324xrrr@v520.kathe.in>

On Tue, Oct 2, 2018, at 3:28 PM, Mayuresh Kathe wrote:
> since it's not the original rio in plan9port, how about renaming it to
> rioc (rio clone)?

Why? :)  I can think of a good reason, but why don't you say why you want to do it?  Just feelings of what is right and wrong?  Personally, my own feelings of right and wrong with respect to computing have too often proved to be harmful, so I try not to take too much notice of them these days.

If, on the other hand, you want to write a draw device implementation for the Linux framebuffer (or whatever) and port Plan 9's rio to it, bear in mind you'll also have to replace plan9port's devdraw binary.  Just renaming it won't do; other programs launch it by name.  Having users put your devdraw ahead of p9p in $PATH will work if I remember right, and the same trick will work for your rio.  If you're distributing your own fork of plan9port, you have every right to rename or remove its supplied rio and devdraw.

--
Progress might have been all right once, but it has gone on too long -- Ogden Nash



  reply	other threads:[~2018-10-02 17:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-02 14:28 Mayuresh Kathe
2018-10-02 17:31 ` Ethan Gardener [this message]
2018-10-02 18:08   ` hiro
2018-10-03 21:25     ` Aram Hăvărneanu

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=1538501466.2475179.1528166336.6754D8D2@webmail.messagingengine.com \
    --to=eekee57@fastmail.fm \
    --cc=9fans@9fans.net \
    /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).