From: FODEMESI Gergely <fgergo@eik.bme.hu>
To: 9fans <9fans@cse.psu.edu>
Subject: Re: [9fans] Can`t install inferno
Date: Tue, 17 Sep 2002 14:30:37 +0200 [thread overview]
Message-ID: <Pine.GSO.4.43L0.0209171420100.18044-100000@goliat> (raw)
In-Reply-To: <NGBBJNFOILCFKKEIGJCEMEDECDAA.athiele@charter.net>
If you want to use inferno under 4e plan9, you have to download a full
distribution and the latest (experimental) update and use the emu from the
update to install inferno. Otherwise it will only copy the license file.
1. download the 18.06.2001 release (inferno.tgz, plan9.tgz)
2. unpack both (read release notes)
3. download the update files from 15.07.2002 (inferno.tgz, plan9.tgz)
4. unpack both (read release notes)
5. rename emu binary from 18.06.2001 release to emu.old
6. rename emu.new (from 15.07.2002) release to emu
I can't comment on the permission denied message.
hope this helps: gergo
ps: acme won't work: you probably can't get it running under 4e plan9
without sources. (It is an experimental release)
On Tue, 17 Sep 2002, Adrian wrote:
> I downloaded inferno.tgz and Plan9.tgz
> cp`d them to plan9 machine and extracted them to
> /usr/glenda/build
> edited /adm/users
> created /usr/inferno
> extracted the tgz files to /usr/glenda/build
> ran rc /usr/glenda/build/install/Plan9.rc -u /usr/inferno
> got
> libinit: open /dev/conctl: permission denied
> keyboard rawon (n=-1, fd out of range or not open)
> initialize Dis: /dis/emuinit.dis
> installation complete.
> All I get is the LICENSE in /usr/inferno.
>
> Any help ?
> All I have done is install the base system and Python ( Thanks to Russ)
> Should I use the adduser command so I don`t have to make the usr/inferno dir
> ?
>
> Adrian
>
>
next prev parent reply other threads:[~2002-09-17 12:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-17 12:00 Adrian
2002-09-17 12:30 ` FODEMESI Gergely [this message]
2002-09-17 12:44 ` Adrian
2002-09-17 12:54 ` FODEMESI Gergely
2002-09-17 19:27 ` adrian
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=Pine.GSO.4.43L0.0209171420100.18044-100000@goliat \
--to=fgergo@eik.bme.hu \
--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).