From: bqt@update.uu.se (Johnny Billquist)
Subject: [TUHS] Early non-Unix filesystems?
Date: Thu, 24 Mar 2016 12:37:31 +0100 [thread overview]
Message-ID: <56F3D17B.5080002@update.uu.se> (raw)
In-Reply-To: <002e01d185c1$502c06e0$f08414a0$@ronnatalie.com>
On 2016-03-24 12:35, Ron Natalie wrote:
>
>> Ok. Color me stupid, but I don't get it. I totally do not understand how this locks anything out.
>
> I misstated that a bit. The issue is if the next instruction is also an SPL instruction, then interrupts never get enabled. So if you have a run of SPL instructions, interrupts are locked out for the duration. If you can fill your address space with SPL instructions (provided the OS doesn't fail in the process), you can cause an uninterruptable loop. Interupt includes the HALT switch on the front. You have to use the BUS RESET to jab it out of its catatonic state.
Hmm. Ok. Gotta check this out. Thanks for the details.
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
next prev parent reply other threads:[~2016-03-24 11:37 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1.1458784801.4499.tuhs@minnie.tuhs.org>
2016-03-24 10:17 ` Johnny Billquist
2016-03-24 11:35 ` Ron Natalie
2016-03-24 11:37 ` Johnny Billquist [this message]
2016-03-24 22:50 ` Peter Jeremy
2016-03-24 23:06 ` Johnny Billquist
[not found] ` <9CBDF635-2FC9-4855-8419-0413EC0336A7@centurytel.net>
2016-03-25 0:35 ` Johnny Billquist
2016-03-27 0:48 ` Dave Horsfall
2016-03-24 19:13 Nemo
2016-03-24 19:54 ` Milo Velimirović
2016-03-26 21:05 ` Ronald Natalie
2016-03-26 21:34 ` Charles Anthony
2016-03-26 22:09 ` Ronald Natalie
2016-03-28 20:32 ` scj
-- strict thread matches above, loose matches on Subject: below --
2016-03-23 1:58 Doug McIlroy
2016-03-22 0:56 Doug McIlroy
2016-03-18 2:26 Noel Chiappa
[not found] <mailman.1.1458266402.23080.tuhs@minnie.tuhs.org>
2016-03-18 2:13 ` Johnny Billquist
2016-03-18 2:36 ` Charles Anthony
2016-03-18 0:48 Warren Toomey
2016-03-18 2:49 ` Greg 'groggy' Lehey
2016-03-18 3:59 ` John Cowan
2016-03-18 5:11 ` Warren Toomey
2016-03-18 17:45 ` John Cowan
2016-03-18 8:00 ` Dave Horsfall
2016-03-18 8:42 ` Peter Jeremy
2016-03-18 13:04 ` Clem Cole
2016-03-18 17:12 ` scj
2016-03-18 17:45 ` Random832
2016-03-18 18:02 ` scj
2016-03-21 14:11 ` Dave Horsfall
2016-03-21 21:43 ` Greg 'groggy' Lehey
2016-03-21 22:57 ` scj
2016-03-21 23:05 ` Lyndon Nerenberg
2016-03-22 0:27 ` Greg 'groggy' Lehey
2016-03-23 22:46 ` Dave Horsfall
2016-03-24 0:32 ` Ron Natalie
2016-03-24 0:43 ` Milo Velimirovic
2016-03-24 0:47 ` Ron Natalie
2016-03-24 1:05 ` Clem Cole
2016-03-23 1:28 ` Dave Horsfall
2016-03-23 1:51 ` Milo Velimirovic
2016-03-23 6:49 ` Greg 'groggy' Lehey
2016-03-23 7:02 ` Peter Jeremy
2016-03-23 7:12 ` Greg 'groggy' Lehey
2016-03-23 13:54 ` Ron Natalie
2016-03-23 16:28 ` John Cowan
2016-03-23 8:20 ` Dave Horsfall
2016-03-21 11:07 ` Tony Finch
2016-03-21 12:06 ` John Cowan
2016-03-22 0:13 ` Greg 'groggy' Lehey
2016-03-22 0:48 ` John Cowan
2016-03-18 17:01 ` Pat Barron
2016-03-22 5:21 ` shawn wilson
2016-03-23 0:54 ` Clem Cole
2016-03-23 1:07 ` Clem Cole
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=56F3D17B.5080002@update.uu.se \
--to=bqt@update.uu.se \
/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).