From: umbraticus@prosimetrum.com
To: 9front@9front.org
Subject: Re: [9front] List archives
Date: Thu, 24 Mar 2022 15:25:39 +1300 [thread overview]
Message-ID: <12147A908A31062A0A97A9DDC9F05197@prosimetrum.com> (raw)
In-Reply-To: <753CE532CBA2F3A6640D634F7E6B358C@thinktankworkspaces.com>
> cpu% upas/fs -f /n/lists/9front/
> upas/fs: wridxfile: '/n/lists/9front/.idx' File system read only
> upas/fs: wridxfile: '/n/lists/9front/.idx' File system read only
> ...Where did I go wrong?
Looks like you should lose the trailing slash for a start.
You could bind in a ramfs or disk dir to allow creation of the idx
but it is not essential. It works; just takes a long time,
as explained on the website. This took a whole workday
to get to the prompt, but it got there in the end:
; 9fs 9front
post...
; upas/fs -f /n/lists/9front
!can't open /n/lists/9front 9front1648064740: '/n/lists/9front' does not exist
upas/nedmail: can't read
; ; upas/fs -f /n/lists/9front
upas/fs: wridxfile: '/n/lists/9front.idx' mounted directory forbids creation
upas/fs: wridxfile: '/n/lists/9front.idx' mounted directory forbids creation
; mail
upas/fs: wridxfile: '/n/lists/9front.idx' mounted directory forbids creation
upas/fs: wridxfile: '/n/lists/9front.idx' mounted directory forbids creation
upas/fs: wridxfile: '/n/lists/9front.idx' mounted directory forbids creation
upas/fs: wridxfile: '/n/lists/9front.idx' mounted directory forbids creation
upas/fs: wridxfile: '/n/lists/9front.idx' mounted directory forbids creation
upas/fs: wridxfile: '/n/lists/9front.idx' mounted directory forbids creation
upas/fs: wridxfile: '/n/lists/9front.idx' mounted directory forbids creation
upas/fs: wridxfile: '/n/lists/9front.idx' mounted directory forbids creation
8445 messages, 8445 unread
:
So, yeah, if you want to do anything significant
you probably want a local copy.
umbraticus
next prev parent reply other threads:[~2022-03-24 2:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 7:36 cosarara
2022-03-23 18:49 ` william
2022-03-24 2:25 ` umbraticus [this message]
2022-03-24 9:56 ` cosarara
2022-03-23 20:48 ` Humm
2022-03-25 0:58 ` sl
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=12147A908A31062A0A97A9DDC9F05197@prosimetrum.com \
--to=umbraticus@prosimetrum.com \
--cc=9front@9front.org \
/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).