Question: Issues that aren’t really major issues but are still issues

[xexyl]

TODO

• Close this issue when the great fork merge happens.

Original comment

Like the thread in the other repo this is to help us keep the actual issues free from clutter.

I'll start out by showing the problem of not being able to fork this repo instead of winner.git. I'll do that in a follow-up comment.

[xexyl]

UPDATE on forking: it's resolved!

My idea worked: deleting my fork and re-forking it allowed me to create a fork of this repo.

Now I can actually make changes. I do not, I'm afraid, see that happening today, and I will actually be taking a break now rather than replying to the other comments (though the break might be short) but I will get to them later on if not in a bit (though technically that IS later on).

[lcn2]

🤩

[xexyl]

🤩

What is this in reply to please ?

[xexyl]

Testing

Would it be possible to have a test subdomain of the main IOCCC website OR a temp / test subdirectory that has all the changes of THIS repo so we can make sure everything looks and works okay ? It might be a good way to verify that everything can be merged to the real website later on.

[xexyl]

...and I hope you're having a nice sleep my friend!

I'm going to be updating the keys (more recently recommended encryption standards) on the zones (DNSSEC keys I mean) and that will take a bit of time agains this repo but I'm a bit too tired for this and not that so that's okay. I did it with two domains yesterday as some keys were missing but I figure I might as well do it for the others too.

At least I think I'll be doing that now :-) .. either way I'll reply to your comments in the other issues later on.

UPDATE 0

Was troubleshooting a strange problem .. solved that so now I can continue the above. Then if I have time I'll reply to the other comments. Else I'll do that after a break. I then maybe (we'll see!) can get more work done on this repo.

UPDATE 1

... it wasn't solved after all but what is done works well enough for now. I didn't finish the task because of it. I will be taking a quick break and then I will work on the comments here. Hopefully by the time you're awake I will be done with that.

[xexyl]

Questions about moving forwards

What issues have things that can be done before the json tools are made?

If there are any what are they? I guess some (perhaps not all) typos and consistency in some (not all - an example where it's probably possible is the Makefiles) would be something that can be done. Is this so? Anything else that you can think of?

I'll be doing other things now and might not work on this today. I'm feeling pretty worn out right now. That certainly might change but right now I definitely need to do something else.

[lcn2]

Questions about moving forwards

What issues have things that can be done before the json tools are made?

If there are any what are they? I guess some (perhaps not all) typos and consistency in some (not all - an example where it's probably possible is the Makefiles) would be something that can be done. Is this so? Anything else that you can think of?

Issue #1, issue #2, and issue #3 can be done.

[lcn2]

We have not forgotten about comment 1418905409.

[xexyl]

Questions about moving forwards

What issues have things that can be done before the json tools are made?
If there are any what are they? I guess some (perhaps not all) typos and consistency in some (not all - an example where it's probably possible is the Makefiles) would be something that can be done. Is this so? Anything else that you can think of?

Issue #1, issue #2, and issue #3 can be done.

But if the fourth one might impact some of these is this wise? That's kind of what I was getting at. I mean some things in the issues can be done but what can't be or what shouldn't be might be a better way of putting it?

[xexyl]

We have not forgotten about comment 1418905409.

Oh thank you!

[lcn2]

Questions about moving forwards

What issues have things that can be done before the json tools are made?

If there are any what are they? I guess some (perhaps not all) typos and consistency in some (not all - an example where it's probably possible is the Makefiles) would be something that can be done. Is this so? Anything else that you can think of?

Issue #1, issue #2, and issue #3 can be done.

But if the fourth one might impact some of these is this wise? That's kind of what I was getting at. I mean some things in the issues can be done but what can't be or what shouldn't be might be a better way of putting it?

As you didn't seem inclined to want to edit years.html when you went about renaming and removing files .. that is OK, we just have to adjust our approach to that fact .. we will have to accelerate the building of the pre-directory .winner.json files via a tool that we will write .. a tool that needed to be written eventually anyway, BTW.

Also now, before this forked repo can be merged into the main IOCCC winner repo and web site, another tool to build the years.html web page from all .winner.json files .. also one that we need to also write eventually anyway .. will need to automatically build the years.html web page before the the main IOCCC winner repo and web site can be updated.

[xexyl]

Questions about moving forwards

What issues have things that can be done before the json tools are made?

If there are any what are they? I guess some (perhaps not all) typos and consistency in some (not all - an example where it's probably possible is the Makefiles) would be something that can be done. Is this so? Anything else that you can think of?

Issue #1, issue #2, and issue #3 can be done.

But if the fourth one might impact some of these is this wise? That's kind of what I was getting at. I mean some things in the issues can be done but what can't be or what shouldn't be might be a better way of putting it?

As you didn't seem inclined to want to edit years.html when you went about renaming and removing files .. that is OK, we just have to adjust our approach to that fact .. we will have to accelerate the building of the pre-directory .winner.json files via a tool that we will write .. a tool that needed to be written eventually anyway, BTW.

Also now, before this forked repo can be merged into the main IOCCC winner repo and web site, another tool to build the years.html web page from all .winner.json files .. also one that we need to also write eventually anyway .. will need to automatically build the years.html web page before the the main IOCCC winner repo and web site can be updated.

Hmm .. what should have been changed in years.html ? What did I miss ?

[xexyl]

Though it's true I didn't want to do a major update as I think editing html files directly is risky. Then again maybe editing markdown is as well without testing it.

So what should be done please? I will look at doing it if that's helpful?

[lcn2]

We were taken out to dinner at a new place by a friend and ate something that was "off". Lack of sleep and frequent access to "you know what" (🚽🧻) while humming the SouthPark "Mr. Hanley💩" song, is our current focus until it flushes out of our system.

To maintain something to do, we have our iPhone to answer questions and provide feedback and encouragement .. interrupted as just happened now from time to time until things are flushed out of our system .. followed by rest .. followed by resetting our sleep clock.

In between all that, we will design the tool in our head, to generate the .winner.json files, the tool to build the years.html page, and the format of the author based JSON files.

[xexyl]

We were taken out to dinner at a new place by a friend and ate something that was "off". Lack of sleep and frequent access to "you know what" (🚽🧻) while humming the SouthPark "Mr. Hanley💩" song, is our current focus until it flushes out of our system.

I shouldn't laugh but I did! I'm sorry. It's the way you worded it. I also know what having to use that in the night a lot is like. Does not help with my sleep issues I can tell you. I hope you feel better soon.

If it's liquid (and I do not mean the yellow/clear one) too please remember to remain hydrated! You can even make your own isotonic drink by putting ½ teaspoon of salt into 1 cup of warm water. I've known this for years but it was also mentioned in the medical book I finally got through (quite quickly .. I did say it was light reading .. it was fun and I learnt a lot from it - not at all the only medical book I've read) so it's recently on my mind.

To maintain something to do, we have our iPhone to answer questions and provide feedback and encouragement .. interrupted as just happened now from time to time until things are flushed out of our system .. followed by rest .. followed by resetting our sleep clock.

Best wishes!

In between all that, we will design the tool in our head, to generate the .winner.json files, the tool to build the years.html page, and the format of the author based JSON files.

Sounds good.

[lcn2]

If it's liquid (and I do not mean the yellow/clear one) too please remember to remain hydrated! You can even make your own isotonic drink by putting ½ teaspoon of salt into 1 cup of warm water. I've known this for years but it was also mentioned in the medical book I finally got through (quite quickly .. I did say it was light reading .. it was fun and I learnt a lot from it - not at all the only medical book I've read) so it's recently on my mind.

Thanks, we are keeping well hydrated, which means more frequent trips .. but that is part of the process.

We have people in the house that are checking in on us too.

[xexyl]

The strings of the form "years.html#2020_ferguson2" refer to name tag in the top level years.html file. And thus will refer to the 2020/ferguson2/ winning entry directory (a rather fine entry if you ask us 🤓). So the file 2020/ferguson2/.winner.json will contain things like the manifest for that particular entry as well as JSON stuff for the list if authors .. which in this case will be "Cody_Ferguson".

Thank you for the great compliment! I enjoyed making that one. I found it fitting that I finished it on 30 April 2020, exactly 75 years after a certain man ended his life, he who started the Second World War and brought the world to such misery (though ironically we've gained things from it .. a sad thing about humans is that we both strive for and thrive on conflict).

I don't wish any harm on them either. We're all human beings and we could all be the worst sadist in different situations. This is well documented but it's something that a lot of people have a problem accepting. There's so much to that but it's OT for even OT so I won't go there. I just wanted to thank you!

I enjoyed the fact that some previous entries played with the Morse code which could be used with my Enigma machine (I found a bug in one of those two entries but I don't remember which one without looking at my remarks .. perhaps that should be mentioned somehow in the remarks but how? I guess to start out I can extract the bug I found for you to think about).

I only thought of the idea for that entry after the contest closed but due to Covid you opening it I lucked out. I had a feeling that entry had a good chance of winning - as well as Snake (which was by far the most fun for me to write ... and play).

[xexyl]

If it's liquid (and I do not mean the yellow/clear one) too please remember to remain hydrated! You can even make your own isotonic drink by putting ½ teaspoon of salt into 1 cup of warm water. I've known this for years but it was also mentioned in the medical book I finally got through (quite quickly .. I did say it was light reading .. it was fun and I learnt a lot from it - not at all the only medical book I've read) so it's recently on my mind.

Thanks, we are keeping well hydrated, which means more frequent trips .. but that is part of the process.

I know how that goes far too well! :-( ... I had two huge kidney stones (see below for fun word) in 2020 so I have to be extra careful. But I also have a highly sensitive bladder (normal function but hypersensitive) so it's a problem in other ways. I know this because of a horrible medical procedure.

We have people in the house that are checking in on us too.

That's good.

Fun word for kidney stone: renal calculus. Can you figure out why ? I guess you can but I can tell you if you don't know.

[lcn2]

Hmm .. what should have been changed in years.html ? What did I miss ?

See in issue #3, the stuff at the top about years.html links.

[lcn2]

🤩

What is this in reply to please ?

comment 1422487862

[xexyl]

Hmm .. what should have been changed in years.html ? What did I miss ?

See in issue #3, the stuff at the top about years.html links.

Oops. My mistake. I'll fix those. I have to remember what files changed.

[xexyl]

Hmm .. what should have been changed in years.html ? What did I miss ?

See in issue #3, the stuff at the top about years.html links.

Oops. My mistake. I'll fix those. I have to remember what files changed.

Oh actually. I did update it. It includes README.md. Did I miss others?

UPDATE 0

Though it does refer to README.html. Any such lines should be deleted, right?

UPDATE 1

What about hint.html ? author.html ?

[xexyl]

🤩

What is this in reply to please ?

comment 1422487862

Ah .. I thought it was a laugh so I wasn't sure what was funny. But that could be my misinterpreting that emoji (my vision certainly does not help there either)! Maybe it's just a happy smile or something.

[lcn2]

Hmm .. what should have been changed in years.html ? What did I miss ?

See in issue #3, the stuff at the top about years.html links.

Oops. My mistake. I'll fix those. I have to remember what files changed.

Oh actually. I did update it. It includes README.md. Did I miss others?

UPDATE 0

Though it does refer to README.html. Any such lines should be deleted, right?

UPDATE 1

What about hint.html ? author.html ?

For now, all files in a winning directory need a link in the years.html file.

And for now, those files can cannot be directly displayed (and thus force someone to download them) should be link into the github repo, not the web site. This "hack" allows someone to use the GitHub view to see the contents of a file.

For an example, see how near the bottom of years.html we have links such as:

<UL TYPE=square>
<LI><A HREF="1984/laman/index.html">index.html</A> - <B>README</B>
<LI><A HREF="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1984/laman/laman.c">laman.c</A>
<LI><A HREF="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1984/laman/Makefile">Makefile</A>
<LI><A HREF="1984/laman/README.md">README.md</A> - <I>original README</I>
<LI><A HREF="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1984/laman/orig.Makefile">orig.Makefile</A> - <I>original Makefile</I>
</UL>
<A NAME="1984_mullender"></A>
<P><B>mullender</B></P>

The links into the GitHub repo give the user quick viewer of the code for those files that might otherwise compel the browser to download it instead (which isn't much fun).

This is touched on in issue #3, BTW.

BTW: Later on we will change the HTML to directly display the content, similar to how GitHub does it, without causing a "download file" to occur.

BTW: For the compressed tarballs that might be present, the link WILL force a downloads .. which presumably is what the user wants. But this is a technicality to be addressed later.

[xexyl]

Hmm .. what should have been changed in years.html ? What did I miss ?

See in issue #3, the stuff at the top about years.html links.

Oops. My mistake. I'll fix those. I have to remember what files changed.

Oh actually. I did update it. It includes README.md. Did I miss others?

UPDATE 0

Though it does refer to README.html. Any such lines should be deleted, right?

UPDATE 1

What about hint.html ? author.html ?

For now, all files in a winning directory need a link in the years.html file.

Right. I was more thinking of those related to the files I renamed/removed.

And for now, those files can cannot be directly displayed (and thus force someone to download them) should be link into the github repo, not the web site. This "hack" allows someone to use the GitHub view to see the contents of a file.

Yes that's an unfortunate issue indeed!

For an example, see how near the bottom of years.html we have links such as:

<UL TYPE=square>
<LI><A HREF="1984/laman/index.html">index.html</A> - <B>README</B>
<LI><A HREF="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1984/laman/laman.c">laman.c</A>
<LI><A HREF="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1984/laman/Makefile">Makefile</A>
<LI><A HREF="1984/laman/README.md">README.md</A> - <I>original README</I>
<LI><A HREF="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1984/laman/orig.Makefile">orig.Makefile</A> - <I>original Makefile</I>
</UL>
<A NAME="1984_mullender"></A>
<P><B>mullender</B></P>

The links into the GitHub repo give the user quick viewer of the code for those files that might otherwise compel the browser to download it instead (which isn't much fun).

Agreed.

This is touched on in issue #3, BTW.

Resolving it you mean? Ah .. you mean the directory clean up and consistency checks.

BTW: Later on we will change the HTML to directly display the content, similar to how GitHub does it, without causing a "download file" to occur.

That will be nice for sure.

But in the meantime this means all the links have to be updated, is that correct? Any idea how to best go about this ? It seems like it might be tedious unless a simple (or not many) regex can be contrived.

BTW: For the compressed tarballs that might be present, the link WILL force a downloads .. which presumably is what the user wants. But this is a technicality to be addressed later.

Of course.

[xexyl]

Do you want to add the GitHub check template to the repo ?

Unrelated I just fixed the FAQ - a missing entry from 2020 in a theme for entries not likely to win.

I also noticed the joke in there:

Fun reference to WarGames.

[xexyl]

Did you remember to update the other files including the test data files so that make prep works?

Yes, make prep works.

We hope the subtle humor added to the BUGS section of the mkiocccentry(1) and chkentry(1) man pages is sufficient. 😉
I am sure it will though I haven't seen it yet.
I also hope you updated the txzchk man page but if not I will try doing that today. But I don't know either. I feel like it might be a slow and hard day.

We didn't: See the BUGS section of the mkiocccentry(1) and chkentry(1) man pages.

And there are probably a few other minor things that might need to be adjusted. But don't go too far. See the comment-2115482287 below.

I didn't go too far I think .. a lot of files were updated but that's because of a comment that was in many files that had the word 'entry' that probably shouldn't have at all but certainly it's not needed.

I mostly just updated the man pages (saying that just because a term might be in a file does not mean it's incorrect) and the FAQ to point out the strange files (not to modify them) and to be consistent with the BUGS section in the man pages you updated (noting that just because a term seems to be incorrect does not mean it is incorrect as it depends on context).

[xexyl]

I saw something about another G5 solar flare but am I right in saying that it's not aimed at Earth so that we won't get to see the effects (or have it affect communication and other things here)?
Thanks!

Or maybe it was a Kp 5 ? Anyway same question.

The X8.7 flare was 17th on the list of all time measured solar flares.

Thanks.

The white circle represents the size of the Sun.

The CME (Coronal Mass Ejection: a lot of stuff being ejected into space), however was ejected to the side and will be unlikely to reach the Earth and cause an aurora event.

That's what I thought. If it does change though please do let me know! Thanks.

Where do those screenshots come from btw ?

[xexyl]

Before I go for the day (returning here tomorrow I am sure): my mum said thank you for the well-wishes and she is sure she'll be fine.

She had an infection in her eye and unfortunately the antibiotic they use she cannot take so she fought with it for over a year. It ruined the tear duct in her eye so they have to address this. Once she's healed post surgery things should be much better for her. They had to poke at her eye at times and that was painful but I don't know more specifics other than she had a hard time seeing, her eye hurt a lot and it took a lot of time to resolve. Worse is her vision had changed but as long as she had the infection she couldn't get new glasses (she has those now).

I'll be back tomorrow I'm sure. Good day!

[xexyl]

Late start today but I hope that I can do a little bit at least.

That won't be possible for at least an hour though.

I have to reboot the server too. Not happy about that. Only because I upgraded Rocky and now it's telling me that the installed kernel is a security update and that will happen every day. Plus it should be done anyway.

I just hope no services will have any problem and prevent a successful boot.

I did have to fix some problems already so hopefully they are all resolved.

Late next month I will have to have a day with extended power outage so I will just shut the server down and turn off the UPSes. That day will not be fun!

I had a thought that might help here though: every day I get on the exercise bike. But why not look into the issue templates when on the bike? I might have to do some test commits on a repo that I made for this purpose but if I do the research when I can't actually do the tests it might speed things along.

It would be nice to be able to close that issue as complete.

But for now I have other things I have to do.

I don't know what I will get done here today but we shall see. Hopefully something but if not I will at least try and look into the issue templates.

In a little bit I will be rebooting the server and hopefully all is good but if not that could also delay things here. But probably it's okay.

Anyway back later today hopefully!

[lcn2]

Where do those screenshots come from btw ?

SOHO satellite 🛰️

[xexyl]

Where do those screenshots come from btw ?

SOHO satellite 🛰️

Is that a private access thing? Or is it public? I guess it's private?

[lcn2]

Where do those screenshots come from btw ?

SOHO satellite 🛰️

Is that a private access thing? Or is it public? I guess it's private?

The data is public. There is an iOS app involved if you are interested.

[xexyl]

Where do those screenshots come from btw ?

SOHO satellite 🛰️

Is that a private access thing? Or is it public? I guess it's private?

The data is public. There is an iOS app involved if you are interested.

What is the name of it please? It seems interesting at least. I don't know how much I would use it but it might be fun to at least see.

Thanks.

[lcn2]

Where do those screenshots come from btw ?

SOHO satellite 🛰️

Is that a private access thing? Or is it public? I guess it's private?

The data is public. There is an iOS app involved if you are interested.

What is the name of it please? It seems interesting at least. I don't know how much I would use it but it might be fun to at least see.

Thanks.

For an iPad there is:

https://apps.apple.com/app/id425368517

But see also:

https://apps.apple.com/app/id1435501021

For the iPhone:

https://apps.apple.com/app/id1317284385

[xexyl]

Where do those screenshots come from btw ?

SOHO satellite 🛰️

Is that a private access thing? Or is it public? I guess it's private?

The data is public. There is an iOS app involved if you are interested.

What is the name of it please? It seems interesting at least. I don't know how much I would use it but it might be fun to at least see.

Thanks.

For an iPad there is:

https://apps.apple.com/app/id425368517

But see also:

https://apps.apple.com/app/id1435501021

I actually installed that one the other day. Thanks!

For the iPhone:

https://apps.apple.com/app/id1317284385

As for the other one for the iPad and iPhone I will have to look at it later and consider it. Not a lot of money but as I am not an expert I am not sure how much I can make use of it.

Still I thank you for the information!

I will be back here tomorrow morning most likely.

[lcn2]

We still have not had the time to properly review and test #5 (comment) to our vim question, and probably won't until Friday or Saturday.

It will take even longer due to medical issues in the family, graduating students, and our focus on the submit server. To properly work the solution to the vim question requires us to focus on non-IOCCC stuff which is a lower priority.

We did make some initial changes, but we have not completed our changes.

We hope to review and test comment-2093121295 sometime week.

[lcn2]

That's what I thought. If it does change though please do let me know! Thanks.

We await the spin of the Sun and the return of sunspot group 3664 to the side of the Sun facing us: perhaps by the end of May.

The Sun 🌞 being a gassy (well "plasma-y") squishy object, rotates 25 days at the Sun’s equator and as slow as 34.4 days near the Sun’s poles. Sunspot groups can move away from the equator towards one of the Sun’s poles thus changing how fast they take to return to facing the Earth. And that assumes the Sunspot group 3664 remains active for a 1/2 Sun “return”.

[xexyl]

That's what I thought. If it does change though please do let me know! Thanks.

We await the spin of the Sun and the return of sunspot group 3664 to the side of the Sun facing us: perhaps by the end of May.

The Sun 🌞 being a gassy (well "plasma-y") squishy object, rotates 25 days at the Sun’s equator and as slow as 34.4 days near the Sun’s poles. Sunspot groups can move away from the equator towards one of the Sun’s poles thus changing how fast they take to return to facing the Earth. And that assumes the Sunspot group 3664 remains active for a 1/2 Sun “return”.

Is it possible we will see anything? I guess at this point the answer is 'we don't know yet' but if it's possible please keep me informed! Even so it is interesting.

I'm making excellent progress on the manifest but I'm getting to the point where I want to do other things. Still if I can finish it I can do those things when the script is updating the files. We shall see. If not I'll either do a partial fix or wait until i have finished it (hopefully no later than tomorrow).

[xexyl]

Two quick things and that's all I will be doing today and likely for a few more days.

First as far as the other repo and your announcement: you should remove.

Second is that .. hmm, what was the second thing? Perhaps it was just a thank you for the note: not sure now. Been a long day already and have a lot on my mind. Ah yes! It just popped back into my head!

Here's a great thing that I realised: as of the work I did yesterday (completed TWO (!!) high priority issues) we now only have one high priority issue remaining! Of course we might have another one open up but this is great news! When I return in a few days I will start at that task. And it might be that I return to it sooner. Perhaps even tomorrow. If not then I guess that I will be back the following day.

Anyway I hope you have a great day!

[xexyl]

We still have not had the time to properly review and test #5 (comment) to our vim question, and probably won't until Friday or Saturday.

It will take even longer due to medical issues in the family, graduating students, and our focus on the submit server. To properly work the solution to the vim question requires us to focus on non-IOCCC stuff which is a lower priority.

The VERY BEST for your family health issues! I don't know what it is (and I am absolutely not asking!) but I can relate in the sense that I have a lot of medical problems ever since I was a very young child and I was likely born with some of them (even if they didn't necessarily show up right away).

Actually I wasn't breathing when I was born. A scary moment for my mum I am sure (well my father probably too). Though my mum is very calm in emergencies as am I. There have been many other times when I was not breathing. There's a hilarious story about one case which I will share next as I can't do anything else really when exercising.

We did make some initial changes, but we have not completed our changes.

I am fine in waiting: after all I have plenty to do. Right now I am on the exercise bike but in a bit I will have to take care of my mum. I also later on have an appointment (but on zoom).

I have also prepared a cake so that my mum has something nice to eat when she's here (though not until after breakfast of course). Though I won't bake it until she's in recovery so that it's warmer.

I was contemplating brownies but I often make those and I thought it would be a nice change .. I often make brownies.

Fortunately I do live with her. I help her with some things and vice versa but the most important one was when she fell in early May 2020. It was really bad.

I have seen her do so many things despite having permanent back damage since she was a teenager (rear ended twice) and has had severe migraines since she was 7 after she was accidentally hit in the head with a trapeze. Anyway it was really hard to see her lying there In agony obviously with broken bones but trying to get up.

I had to keep her still. I immediately called an ambulance. She had to have major surgery. She ended up shattering the bones in her knee and in her wrist. She still has pain but she manages it good.

She knows how to fall but the way it happened means she was lucky that she didn't hit her head. And of course she's lucky she didn't get a compound fracture: that could have killed her!

To give you an idea of how tough she is: she refused an analgesic at first: she wanted to make sure things would be okay so when in the ambulance they didn't give her anything. Then in emergency it was suggested that the pain killer probably had worn off enough that she would want more. But she then told them that she actually hadn't had any yet!

But then for a long time I had to help her out with mobility and other things.

We also are pretty sure that she got Covid before we knew about the virus let alone the disease. Fortunately I didn't get it: I would have very likely have died but I certainly would have been in hospital.

But she woke up some mornings and was afraid she wasn't going to survive. It was very bad. And yet you had people to this day that don't take it seriously *sigh*. Of course we have all our boosters but so many people don't. But we're both high risk and that's how we both got breakthrough. I just wish everyone would take it seriously so we could hopefully move on.

You know the people who complain about it have no idea how easy things are compared to Black Death: where they would lock entire households in their house from the outside and mark the house. They got no medical care and were left to die a horrific death.

We have it so much better in comparison and people whine about quarantine.

Anyway it does make it easier for the both of us and we help each other out a lot. We're also very close.

We hope to review and test comment-2093121295 sometime week.

Let me know and if it's not enough I would be happy to evaluate what it ends up doing for you and seeing if I can further help.

[xexyl]

As far as not breathing here's a hilarious story. One night I was hypoxic and blue from cyanosis. That was frequent and just like the other times she rushed me to emergency.

I was on a first name basis with the hospital staff. The triage nurse saw that I wasn't breathing and she said to my mother to just bring him right back. I was of course told this story later on (years later): I wasn't conscious at the time of course.

So this woman who had been waiting there for hours, ungrateful and not aware that emergencies have different severities and those with lower severity have to wait longer, stood up and loudly complained: 'I have been here for HOURS and he just comes in and you take him right back!!'

So the triage nurse shot back immediately: 'stop breathing and we'll take you in next!'

We don't know the way she responded because we were on the way to a room but I would have loved to have seen her reaction. Still it's a funny story and I hope she felt embarrassed and learnt a lesson.

Anyway that's the story I referred to. I will be doing other things for the day: unsure if I will be back tomorrow but if not it's likely that I will do at least a little bit the following day.

But since I completed two high priority issues yesterday I think that's quite all right.

Have a great day!

[xexyl]

To make a terrible but funny pun that you would get but most people probably wouldn't: say rather Death Down!

[lcn2]

First as far as the other repo and your announcement: you should remove.

Done. Although you might have to do:

git tag -d v1.1
git fetch
git rebase

If you or anyone else had the old tag copy of the v1.1 tag.

[xexyl]

First as far as the other repo and your announcement: you should remove.

Done. Although you might have to do:

git tag -d v1.1
git fetch
git rebase

If you or anyone else had the old tag copy of the v1.1 tag.

It seems like I might have but for the first one I got:

error: tag 'v1.1' not found.

Is that a problem that you can think of?

[lcn2]

First as far as the other repo and your announcement: you should remove.

Done. Although you might have to do:

git tag -d v1.1
git fetch
git rebase

If you or anyone else had the old tag copy of the v1.1 tag.

It seems like I might have but for the first one I got:

error: tag 'v1.1' not found.

Is that a problem that you can think of?

You didn't have the tag previously.

UPDATE 0

This is what can happen if one tries rewrite tag history and someone else fetched the tag before it was updated.

[xexyl]

First as far as the other repo and your announcement: you should remove.

Done. Although you might have to do:

git tag -d v1.1
git fetch
git rebase

If you or anyone else had the old tag copy of the v1.1 tag.

It seems like I might have but for the first one I got:

error: tag 'v1.1' not found.

Is that a problem that you can think of?

You didn't have the tag previously.

UPDATE 0

This is what can happen if one tries rewrite tag history and someone else fetched the tag before it was updated.

I could have sworn I replied to this... hmm. Well yesterday was a slow tiring day. Anyway yes of course the -d option deletes!

And yes that and other things can cause similar problems of course.

Thanks for taking care of the problem!

[xexyl]

I am afraid that based on how today has been going I likely will be an extra day before I can get back to this.

I don't know if that will be Thursday or Friday but it shouldn't be beyond that at least. I hope that I can get a fair amount done then but I will have to see. It might be that there actually isn't that much to do with the final high priority issue but we shall see.

Have a great day!

[xexyl]

QUESTION - etymology of a UNIX command

Most commands are easy to figure out if not documented: cp, rm, ln, dd, od .. many many others. But one I've always wondered is touch. Do you know the etymology of it? If anyone does it would be you. I'd love to know the story if you have more details! Thanks!

I have some other things to say but for other comments, one possibly here, another in another issue.

[xexyl]

This morning I was taking care of a problem with bacula on the server. Ever since I changed to a 4TB RDX cartridge I frequently have to label new volumes. It should do the pre-backup script first which would allow it to create new volumes (pre backup does chattr -i and post does +i) but for some reason it's no longer working right so I have to do chattr -i and then manually run label.

Anyway I noticed something odd too. Previously as I had only 1TB of storage I had quite small incremental and also differential pools and worse is very few jobs. Not sure how that ever was not a problem but that config carries over from CentOS. But now the volumes were tiny when rotating out so I changed the maximum jobs and maximum volumes as well as the retention period.

I don't think that'll solve the inability to label new volumes when the time comes but at least I won't have to do it so frequently. As it is I'm not even sure it happened until I got spare cartridges (I got them for really good prices so I wanted to get them for after this one dies which should be years from now .. also got it this year or else late last year) and then wanted to put the other computer's backup on one of the spares. On that note I thought of something that might help me salvage it though I somehow doubt I'll be that lucky. Unfortunately anaconda is very poor with md raid + lvm so I'm fearing that very much. I unfortunately don't remember how I even managed it before. Next time I have to do it though I'll be saving how I do it. I think I had to use the command prompt and do it but then for some reason the fedora box is not working well. But I might be able to manage if I use the /etc/mdadm.conf file from the system itself which of course is on backup. Still so annoyed I without thinking changed /boot to raid5.

But I won't be playing with that until I'm fully recovered and then also have the energy. I think I'm almost fully recovered but energy is another matter entirely. Still as fedora release cycle is so short I will have to do it sooner than later or else risk EOL. That's all another matter entirely.

In other news I might have come up with a way that will let me feel like I have more time here. But that remains to be seen I guess.

I do have another comment to make in another issue and then I will be doing other things. Someone is here right now and that's preventing me from doing something I need to do (air con maintenance). But in the meantime I should at least be able to get some reading or something if I can't do anything I have to do (the other thing I need to do but it can be put off until he's gone).

[lcn2]

QUESTION - etymology of a UNIX command

Most commands are easy to figure out if not documented: cp, rm, ln, dd, od .. many many others. But one I've always wondered is touch. Do you know the etymology of it? If anyone does it would be you. I'd love to know the story if you have more details! Thanks!

I have some other things to say but for other comments, one possibly here, another in another issue.

The touch(1) first appeared in Bell Labs UNIX 7th edition. It was in response to make(1) whose use file modification times could result in a long compile session (when computers and compilers were much slower) if the wrong file were modified even when the contents remained the same. "Who touched the source code?!?" So a tool to "touch" the resulting executable so that make(1) would not try to remake the executable came about.

[lcn2]

We still have not had the time to properly review and test #5 (comment) to our vim question, and probably won't until Friday or Saturday.

It will take even longer due to medical issues in the family, graduating students, and our focus on the submit server. To properly work the solution to the vim question requires us to focus on non-IOCCC stuff which is a lower priority.

We did make some initial changes, but we have not completed our changes.

We hope to review and test comment-2093121295 sometime week.

Still no date this week to review and test comment-2093121295. Perhaps next week.

[xexyl]

QUESTION - etymology of a UNIX command

Most commands are easy to figure out if not documented: cp, rm, ln, dd, od .. many many others. But one I've always wondered is touch. Do you know the etymology of it? If anyone does it would be you. I'd love to know the story if you have more details! Thanks!
I have some other things to say but for other comments, one possibly here, another in another issue.

The touch(1) first appeared in Bell Labs UNIX 7th edition. It was in response to make(1) whose use file modification times could result in a long compile session (when computers and compilers were much slower) if the wrong file were modified even when the contents remained the same. "Who touched the source code?!?" So a tool to "touch" the resulting executable so that make(1) would not try to remake the executable came about.

Ah. So it was figurative (I guessed that but I mean that it was a figurative reaction or requirement). If editing a file even if without modifying the contents is touching (messing with, modifying, opening and saving even if no changes were made) it (and touch is a perfectly valid word), then there might be a use to have a tool that does it without having to edit the file (as in open it and save it) too.

And useful indeed it is. It can solve all sorts of problems. I remember when compiling the linux kernel sometimes a file had an invalid timestamp, sometimes due to time drift, and I had to touch the file to fix it.

Thanks as always! Very interesting story.

[lcn2]

Delay due to emergency

A few weeks ago, a critical piece of infrastructure we had been relying on has been decided by others to be going away soon.

The reasons for their decision appear to be based on a fundamental misunderstanding: complicated further by even worse rationalizations on their part. Others have been unsuccessfully arguing with those responsible for this decision for a several weeks, all without success.

We only discovered this situation yesterday due in part to the way their decision was communicated.

Rather than trying to argue with those responsible for this situation, we have decided to solve this problem by removing our dependence on that infrastructure entirely.

We now have a design to work around this unfortunate situation. We need to start testing this design, and then produce a full solution and deploy. This will take at least several days to complete. Until then, we need to fully focus on this process.

We will return after we have completed this emergency procedure.

Best wishes 👍

[xexyl]

Delay due to emergency

A few weeks ago, a critical piece of infrastructure we had been relying on has been decided by others to be going away soon.

The reasons for their decision appear to be based on a fundamental misunderstanding: complicated further by even worse rationalizations on their part. Others have been unsuccessfully arguing with those responsible for this decision for a several weeks, all without success.

We only discovered this situation yesterday due in part to the way their decision was communicated.

Rather than trying to argue with those responsible for this situation, we have decided to solve this problem by removing our dependence on that infrastructure entirely.

We now have a design to work around this unfortunate situation. We need to start testing this design, and then produce a full solution and deploy. This will take at least several days to complete. Until then, we need to fully focus on this process.

We will return after we have completed this emergency procedure.

Best wishes 👍

Best wishes to you too my friend! Good luck with what you have to deal with and I'm sorry you do have to deal with it! Always annoying that kind of thing. BCNU.