From: "Ethan Gardener" <eekee57@fastmail.fm>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] full fossil follies
Date: Sat, 26 Jun 2021 10:01:27 +0100 [thread overview]
Message-ID: <db41c8d5-a711-4026-8062-a1e0bbe4b2c8@www.fastmail.com> (raw)
In-Reply-To: <ac924426-6cc6-e3e2-2aad-fd2776b21331@SDF.ORG>
On Fri, Jun 25, 2021, at 5:45 PM, adr via 9fans wrote:
>
> In a multi-user environment you can make the file system do something
> similar when the system is full, but instead of starting a console
> session, delete the last file modified and presenting the user
> an error.
The last file modified could be the log file which documents what went wrong. ;) I thought this through years ago, it's an annoying problem. I think the current situation isn't too bad. If I remember right, it's much better than CWFS, but I don't remember too clearly. I do remember my early Linux experience, trying to arrange several 100-200MB disks in such a way as to have both Emacs and X installed at the same time. (Impossible!) I was also root all the time because A: I didn't know what it was, and B: non-root authentication was broken in that release of that distro and I didn't know how to use the patch disks. My tiny disks inevitably filled up and somehow I managed to deal with them. (It helped that I had no data to lose, having just lost everything I wanted to keep from DOS, but it was still annoying.) It was harder than dealing with a full Fossil because Linux had no ramdisk at the time, I don't think there were any live CDs, and Linux didn't yet support `init=/bin/sh`. I don't think I understood how to start it in runlevel 1, or maybe I did everything in runlevel 1 so when that went wrong, I had to do something else. Sometimes, I had to unplug all the drives but the root, edit the boot config to make a recovery system, plug the drives back in... etc. By comparison, booting a Plan 9 iso and mounting Fossil is very simple and easy! :D It's essentially the same as how I'd repair any OS with a full disk today. Wonderful things, live-CDs.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T4ec62ed03a91d7a4-M0b4c16b88cb43f6182e94a8b
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2021-06-26 9:02 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-23 19:11 [9fans] p9f mention of 9front 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
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 [this message]
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=db41c8d5-a711-4026-8062-a1e0bbe4b2c8@www.fastmail.com \
--to=eekee57@fastmail.fm \
--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).