From: ori@eigenstate.org
To: 9fans@9fans.net
Subject: Re: [9fans] 9front: fossil broken in Humanbiologics rel.
Date: Tue, 12 Dec 2023 16:44:38 -0500 [thread overview]
Message-ID: <01DCF1E542F8C96599AD76932A79EF44@eigenstate.org> (raw)
In-Reply-To: <17024101730.0c2E2.99591@composer.9fans.topicbox.com>
Just tested using this script:
#!/bin/rc
fossil/flfmt $1
fossil/conf -w $1 <<EOF
fsys main config
fsys main open -AWP
fsys main
create /active/adm adm sys d775
create /active/adm/users adm sys 664
users -w
srv -p fscons.test
srv fossil.test
EOF
fossil/fossil -f $1
mount -c /srv/fossil.test /n/fossil
and it seems to work for me; note, I don't have a venti
set up, so I have no idea if there's anything around that
which might cause problems.
Quoth wb.kloke@gmail.com:
> Till I upgraded my 9front I was using a fossil server (from9legacy) on my 9front FreeBSD Bhyve system, probably 9front release Emailschaden.
>
> Now it doesn't work anymore. Remaking the programs did not help either. The fossil server now hangs immediately after start. Neither file nor console service nodes are created.
>
> Are there any other users of this combi?
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tac8d983292c826c1-M46c996472dad8a7ddc13844c
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2023-12-12 21:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 19:42 wb.kloke
2023-12-12 21:04 ` ori
2023-12-12 21:10 ` cinap_lenrek
2023-12-12 21:21 ` ori
2023-12-12 21:44 ` ori [this message]
2023-12-12 21:49 ` cinap_lenrek
2023-12-13 17:36 ` wb.kloke
2023-12-14 4:05 ` Noam Preil
2023-12-14 14:43 ` wb.kloke
2023-12-14 17:46 ` Noam Preil
2023-12-14 22:31 ` wb.kloke
2023-12-15 14:13 ` wb.kloke
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=01DCF1E542F8C96599AD76932A79EF44@eigenstate.org \
--to=ori@eigenstate.org \
--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).