9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@9fans.net
Subject: Re: [9fans] p9f mention of 9front
Date: Fri, 25 Jun 2021 10:31:27 +0100	[thread overview]
Message-ID: <2541a4a20e075ea90386c8d5e633e58b@hamnavoe.com> (raw)
In-Reply-To: <34364b48d19d7f99ec92882f534cd73b@quintile.net>

steve@quintile.net:
> However if fossil fills up - because more has been written to it than
> it can hold or because snapshots have been turned on without a venti
> attached, it will crash badly and can (I believe) lose user data.

No, it won't lose data (except in the sense that incoming mail, for
example, can't be stored anywhere while the disk is full).  You can't
usually boot from a completely full fossil, but if you have a fallback
boot method (from a CD or USB drive, from a network, or a spare recovery
fossil partition) you can then start a fossil on the full partition, and
run snapclean and/or delete some files, and all will be well. Even if
fossil data was damaged, you could recover with flfmt from venti if you
had archiving turned on.

Also, nowadays it doesn't actually "crash" ... it just becomes difficult
to do anything when no fossil blocks can be allocated. If the fossil on
a networked server is full, you may not be able to log into it because
that would require some fossil blocks. But you can still recover from
a client terminal, by importing its /srv/fossil and using that to issue
a snapclean command, or a remove command to delete something.

> As I have understood it (others may correct me) the difference between
> cpu and terminal kernels is only the value one global variable (cpuserver)
> in the kernel, and the list of drivers compiled in - traditionally there
> was no graphics support in cpu kernels for example.

I have a version of the 4e kernel which functions as either cpu or terminal
depending on the setting of environment variable 'service' in plan9.ini or
cmdline.txt. It requires only a handful of lines to be added in
/sys/src/9/boot/boot.c to make that work. Nowadays kernel RAM is plentiful
enough that there's no real reason to configure different sets of devices
between terminal and cpu.


------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T523d6e906a17a7cc-Md2b7a8425ae0681a784e7451
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

  reply	other threads:[~2021-06-25  9:31 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-23 19:11 hiro
2021-06-23 23:05 ` unobe
2021-06-23 23:35   ` Sigrid Solveig Haflínudóttir
2021-06-23 23:58     ` Romano
2021-06-24  4:06       ` Lucio De Re
2021-06-24  4:56         ` unobe
2021-06-24  5:52           ` Lucio De Re
2021-06-24 21:25             ` Wes Kussmaul
2021-06-24 23:29               ` silas poulson
2021-06-25 13:06                 ` Wes Kussmaul
2021-06-24  8:24         ` Frank D. Engel, Jr.
2021-06-24  9:25           ` [9fans] plan9 and touch screens Richard Miller
2021-06-24  9:59             ` Lucio De Re
2021-06-24 10:12           ` [9fans] p9f mention of 9front Philip Silva via 9fans
2021-06-24 16:05             ` unobe
2021-06-24 16:16             ` Ethan Gardener
2021-06-24 11:19   ` hiro
2021-06-24 15:01     ` AW: " sirjofri
2021-06-24 20:51     ` unobe
2021-06-25  8:28       ` Steve Simon
2021-06-25  9:31         ` Richard Miller [this message]
2021-06-25 12:41           ` [9fans] full fossil follies Richard Miller
2021-06-25 14:12             ` adr via 9fans
2021-06-25 15:17               ` tlaronde
2021-06-25 16:06                 ` adr via 9fans
2021-06-25 16:45                   ` adr via 9fans
2021-06-26  9:01                     ` Ethan Gardener
2021-06-25 17:23                 ` Iruatã Souza
2021-06-26  8:56                   ` Richard Miller
2021-06-26  8:34       ` [9fans] p9f mention of 9front Ethan Gardener
2021-06-26 12:55         ` noam

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=2541a4a20e075ea90386c8d5e633e58b@hamnavoe.com \
    --to=9fans@hamnavoe.com \
    --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).