9front - general discussion about 9front
 help / color / mirror / Atom feed
From: thinktankworkspaces@gmail.com
To: sl@stanleylieber.com, 9front@9front.org
Subject: Re: [9front] werc noob
Date: Sat, 15 Jan 2022 12:12:01 -0800 (PST)	[thread overview]
Message-ID: <329CBC24B4E2BD0FD7FB19813262A591@gmail.com> (raw)

On January 15, 2022 5:01:25 PM UTC, thinktankworkspaces@gmail.com wrote:
>Okay inside /usr/www/werc/etc/initrc:21
>path=($plan9port/bin . ./bin ./bin/contrib /bin /usr/bin)
>But honestly I don't know what this means. I"m not running linux or 
>debian. What is poan9port and why do I need it if I"m running 9front?

werc ships that way so it doesn't need modification on plan 9 or unix.

the bug you're encountering is the result of recent rc changes. i ran into the same thing, but it was fixed after i complained.

you need to make sure you have the latest rc, and that it's actually installed in /bin/rc.


Its working now I had to exit connect again via drawterm. I shouldn't of needed to do that
and yes I needed to change initrc line 21

path=(/usr/www/werc/bin . ./bin ./bin/contrib /bin /usr/bin)


             reply	other threads:[~2022-01-15 20:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-15 20:12 thinktankworkspaces [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-01-15  9:07 thinktankworkspaces
2022-01-15  9:46 ` Kurt H Maier
2022-01-15 17:01   ` thinktankworkspaces
2022-01-15 18:26     ` Stanley Lieber
2022-01-15 19:40       ` thinktankworkspaces
2022-01-15 19:47         ` Stanley Lieber
2022-01-15 20:02           ` thinktankworkspaces
2022-01-15 17:20   ` thinktankworkspaces
2022-01-15 14:18 ` Stanley Lieber
2022-01-15 17:18   ` thinktankworkspaces
2022-01-15 18:22     ` Stanley Lieber
2022-01-15 19:24       ` thinktankworkspaces
2022-01-15 19:52         ` ori
2022-01-15 19:32       ` thinktankworkspaces

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=329CBC24B4E2BD0FD7FB19813262A591@gmail.com \
    --to=thinktankworkspaces@gmail.com \
    --cc=9front@9front.org \
    --cc=sl@stanleylieber.com \


* 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).