Work plan for M3 2020

March 9, 2020 by Lucian Mogosanu

I haven't much to show for last month, unfortunately: I fixed some shit on my blog and that about sums it up. On the bright side, this means that you don't have all that much to read about in this report -- the bad part being that you don't have all that much to read about in this report, of course. Well, at least this time I was expecting it, and yet no, I'm not happy with the current situation at all, which I believe calls for some deep reevaluation of what the fuck's happening with my time and how to fix this1.

But until then, let's look at the current state of things:

  • TMSR-supported hardware still requires mapping: at the moment I have merely a bunch of incomplete notes that have yet to coagulate; I must gather some more information and organize it properly, following last December's UEFI study. This, by the way, is to my eye a first priority item.
  • My Bitcoin node is still down. On one hand, this calls for an oportunity to do another Gales run; on the other, at the moment I have absolutely no idea how much time it'd take to stand up a TRB node on Gales, which is why I'm calling to the readership for advice and help -- especially its owner, since... well I'm still on my way towards owning it myself. If standing up TRB on Gales proves unfeasible, I'll have to fall back to an old Debian or something. So wut do?

Long story short, for the remainder of March I'll take a bit of rest, regroup my thoughts and start planning and scheduling all this in more detail. Furthermore, I'm committing to properly laying out how and where my time gets wasted and getting out at the very least a draft plan2 for the two items above.

P.S.: In case anyone's wondering, yes, I did notice that:

feedbot: http://trilema.com/2020/god-did-it-to-himself/ << Trilema -- God did it to himself
feedbot: http://qntra.net/2020/03/control-of-steem-altcoin-network-successfully-sold-despite-challenger/ << Qntra -- Control Of "Steem" Altcoin Network Successfully Sold Despite Challenger
feedbot: http://qntra.net/2020/03/some-cia-passwords-unveiled-at-trial-123abcdef-and-mysweetsummer/ << Qntra -- Some CIA Passwords Unveiled At Trial: 123ABCdef and mysweetsummer
feedbot: http://trilema.com/2020/upditty/ << Trilema -- Upditty
feedbot: http://qntra.net/2020/03/intel-cfo-concedes-competitors-will-maintain-process-node-lead-for-at-least-two-more-years/ << Qntra -- Intel CFO Concedes Competitors Will Maintain Process Node Lead For At Least Two More Years

Remember when I fixed this? Well, it seems my fix works except when it doesn't, which reveals a deeper problem with the complexity of my multithreaded Feedbot, its synchronized notifications soaring on the winds of internets. I will have to rewrite the queuing mechanism, of course, and it's not that big of a deal either, except this ain't much of a priority at the moment.


  1. Though at the moment "fixing this" is quite far away, since I don't fully grasp where the core problem lies in the first place. Sure, I could state the plain fact that saecular projects currently take up more than the full time's worth of work. I also know for a fact that this won't be the case anymore in April, although it can sure as hell happen again in November if I don't grow my own legs until then.

    Not even mentioning that the beginning of March hit me with a flu which sapped me of energy for almost a week. Hell, at this point I could just, as the man observed, simply state that:

    it could be that this whole world is against me

    which, don't you agree? is a monumentally crappy excuse to hide behind. But I'm getting ahead of myself here. Read on. 

  2. No, the current isn't much of a plan, as it contains no estimate of the effort required for one, and for the other, the second item is vague enough that I can't even break it into subproblems at the moment. 

Filed under: asphalt.
RSS 2.0 feed. Comment. Send trackback.

2 Responses to “Work plan for M3 2020”

  1. #1:
    Robinson Dorion says:

    at the moment I have absolutely no idea how much time it'd take to stand up a TRB node on Gales

    Jacob has a patch to boost so it builds with the gcc-4.7.4-demangler-amputation.patch. A part from that he also has a patch to the makefiles to remove the rotor orchestra since Gales is musl. He has a deadline of Thursday to get these published in preparation for MP using GBW. So, once you have the patches, TRB is operable on Gales and takes less time and overhead than building TRB with rotor (with the caveat that TRB w/ rotor uses musl-1.1.8 and Gales uses musl-1.1.21).

    I'm committing to properly laying out how and where my time gets wasted and getting out at the very least a draft plan2 for the two items above.

    Ok, looking forward to it. What's your eta on the updated plan ?

    Not even mentioning that the beginning of March hit me with a flu which sapped me of energy for almost a week.

    Sorry to hear about that, hope you've recovered.

  2. #2:
    spyked says:

    > Jacob has a patch to boost so it builds with the gcc-4.7.4-demangler-amputation.patch.

    Sounds great, looking forward to giving it a test run.

    > with the caveat that TRB w/ rotor uses musl-1.1.8 and Gales uses musl-1.1.21

    Noted, although I'm not sure if there are any changes between the two version that I should be aware of in particular.

    > What's your eta on the updated plan ?

    I'll say the end of the month, although I hope to deliver it earlier. Given the new info about TRB on Gales, I probably won't have much of a plan to lay out for this particular task. However, I must confess mapping hardware has been quite tricky so far, especially for AMD, which doesn't seem to have any centralized place to look for hardware -- there is an official one for Intel and it's been quite easy to look through so far, although there's still quite a bit of work on that front as well. So for now I want to take a step back and take another look at the criteria for "TMSR-OS bootable hardware" so that it can help me in this search.

    > Sorry to hear about that, hope you've recovered.

    Thanks! I'm back on my feet, though still taking it slowly for the moment.

Leave a Reply