2023-04-25 03:00:01 <veltas      > That's really cool crc. Did I see something to suggest you set up a framebuffer for access from ilo as well?
2023-04-25 04:43:42 <veltas      > Why does dr() set top of data stack to 0 before dropping?
2023-04-25 05:26:22 <crc         > veltas: framebuffer/graphical experiments  are ongoing. https://forth.works/temp/ilo-sdl.tar.gz for the latest I have on this. (My son is the primary person working on this aspect at present)
2023-04-25 05:29:06 <crc         > on dr(), it's not necessary to set to 0; I just prefer to have the stack space in a known state
2023-04-25 14:34:54 <KipIngram   > This is pretty fun:
2023-04-25 14:34:56 <KipIngram   > https://www.theguardian.com/environment/2023/apr/21/parrots-taught-to-video-call-each-other-become-less-lonely-finds-research
2023-04-25 14:50:08 <gordonjcp   > I'm using a plugin to automagically draw a diagram of a network topology
2023-04-25 14:50:15 <gordonjcp   > based on stuff in a database
2023-04-25 14:50:36 <gordonjcp   > I need to re-architect things a little because the diagram of the map is coming out kind of swastika-shaped
2023-04-25 15:18:43 <KipIngram   > You know, the systemd stuff looks like it will do what I was talking about the other day - let me run a couple of commands after the system has "gotten itself started," but it's awfully involved.  Sure seems like it would have been easy for them just to have an empty file somewhere to do that, that you could just put your commands in.
2023-04-25 15:19:04 <KipIngram   > I.e., it would have been easy for them to have done the systemd skeleton of that for us.
2023-04-25 15:19:26 <KipIngram   > Because that's basically what I'll be doing, establishing such a file.
2023-04-25 15:20:54 <thrig       > rc.d == throwing one lemon pie. systemd == throwing two rhubarb pies
2023-04-25 15:54:26 <KipIngram   > If I make a mistake setting up all these little bits of a new systemd service, does it carry any risk of making the machine not start up properly?
2023-04-25 15:54:42 <KipIngram   > I mean, I know what I wanted won't happen - but is there any chance I then wouldn't be able to ssh into it?
2023-04-25 15:55:09 <KipIngram   > Just from a mistake in the structure - certainly I understand I might run something that caused a problem.
2023-04-25 15:56:47 <thrig       > a common ploy would be to have a test virt and practice breaking that
2023-04-25 16:08:58 <KipIngram   > Yeah, that's just a bit of trouble.
2023-04-25 16:09:06 <KipIngram   > as in labor
2023-04-25 16:09:14 <KipIngram   > Since I don't have anything like that already set up.
2023-04-25 16:09:32 <KipIngram   > I did install virtual box on my notebook a while back, so I guess I could look into that.
2023-04-25 16:09:43 <KipIngram   > Once I set it up I'd have it.
2023-04-25 16:37:10 <gordonjcp   > systemd solves a problem that rc.d doesn't
2023-04-25 16:37:16 <gordonjcp   > but introduces a few that rc.d didn't have
2023-04-25 16:37:42 <gordonjcp   > basically with rc.d it's very hard to say "do this but not until this has happened, and if it doesn't happen don't worry about it, just wait"
2023-04-25 16:37:50 <gordonjcp   > you can say "do this then this then this"
2023-04-25 16:38:21 <gordonjcp   > you can't - as you can with systemd - say "do this, then try and do this but if you're still waiting for that then just get on with something else until you're good to go"
2023-04-25 16:39:08 <thrig       > ... utterly bizzare boot failures when systemd goes pear-shaped. somehow I figured out it was a line the user had put into /etc/fstab
2023-04-25 16:54:22 <gordonjcp   > o_O