| whaack: | diana_coman: EOD Report: I did 9h of saltmines and my bidaily article. A little extra time on the saltmines/article + some inefficiency + 1hr30min of surfing left no time for my Spanish study. I'll get some of my reading block done before I fall asleep. | [01:22] |
| diana_coman: | lobbes: that much I had seen in the logs, sure; except that was only an ack on your part with no specifics re what and *when* you'll DO it, you know? | [04:15] |
| diana_coman: | you are fine with it, cool for you; what about the stuff people were waiting on you to deliver otherwise? it's not the provider's scammy status the most interesting thing there. | [04:16] |
| diana_coman: | jfw: did it fit within the time? reading the text sounds like on occasion you remembered it for a bit but not much, indeed, heh. | [04:18] |
| diana_coman: | http://ossasepia.com/2020/04/21/ossasepia-logs-for-28-Jan-2020#1016550 - I gather next time people are bewildered by what you are getting into, you can admit that maniacal slavedriver indeed but you enjoy it like that! | [04:22] |
| ossabot: | Logged on 2020-01-28 21:07:19 jfw: Though I find I did enjoy the exercise a bit anyway. | [04:22] |
| ossabot: | Logged on 2020-01-12 13:35:32 jfw: They did some reading; were pretty bewildered by what's going on here or what I was getting into. But they were delighted that you'd got me writing and your no-nonsense but sympathetic & reasonable approach | [04:22] |
| ossabot: | Logged on 2019-10-15 21:10:24 jfw: all, rather than go on spinning along the lines of "diana_coman is a maniacal slavedriver and I can never sleep again, or I'm inadequate for unfathomable reasons" | [04:22] |
| feedbot: | http://younghands.club/2020/01/29/jfw-review-week-of-jan-20-2019/ << Young Hands Club -- JFW review, week of Jan 20 2019 | [04:23] |
| diana_coman: | jfw: I guess that answered my question re time, huh. | [04:31] |
| jfw: | diana_coman: yes, both summary and review went quite over time, the latter over bedtime. The just get moving problem again there | [13:08] |
| ossabot: | Logged on 2020-01-25 15:50:16 diana_coman: jfw: yeah, you need to learn to just get moving; time for pondering is when you go for a walk/set aside time specifically/can't do anything else anyway, that sort of thing but not when you should just start on something; takes some practice though, like everything else. | [13:08] |
| jfw: | there was plenty of written material to consult for the review, but my mind didn't seem to want to help on recalling or putting it together. | [13:10] |
| jfw: | re slavedriving I'm not sure where I could have done better. I didn't want to cut sleep but also didn't want the task to continue hanging over, I figured that would mess up the rest of the week even more than the sleep. Is there a better option I'm missing besides the obvious "don't take so long"? | [13:14] |
| whaack: | I'm looking into seeing if I have the right driver for my network interface card. First I need to find out what NIC i have. Through my search I saw I should use lspci. However this command does not come bundled with the minimal centos 6.9 install. Should I try to install lspci or should I find an alternative method to figure out what NIC I have / what driver I need? | [14:35] |
| diana_coman: | jfw: since the trouble is at the getting started part, it's that you need to address really; sure, once you get started too late, it will spill one way or another. | [14:36] |
| diana_coman: | jfw: how about you split this sort of thing into 2 "tasks": one is of the type "ponder and prepare", to be done on one day; the 2nd comes after that and picks up from the notes/output of the first; I'm making some assumptions here re what is keeping you from starting, since you haven't really said anything on that score so if it doesn't fit, you'll have to dig as to what the trouble really is. | [14:39] |
| diana_coman: | whaack: uhm, how come you don't know what nic you have, to start with? | [14:40] |
| diana_coman: | didn't you make this computer with your own hands? how can it be you don't ...know what is in there? | [14:40] |
| diana_coman: | at any rate, you can try lshw perhaps (and more specifically lshw -class network); or ifconfig -a if it says anything | [14:42] |
| diana_coman: | jfw: also, when you find yourself postponing starting on a task - did you try to just pick a different task from the full list for the week and see if there's any on which you'd start directly? | [14:43] |
| diana_coman: | because if there is, it would at least give you some clues re what's exactly going on. | [14:44] |
| diana_coman: | (and if there isn't, that also says something - namely that you need to learn to bake in proper breaks as well, because you most probably end up using household chores or whatever as "breaks") | [14:45] |
| whaack: | diana_coman: I did not spend time studying the motherboard and all its components | [14:45] |
| diana_coman: | whaack: why not? | [14:45] |
| diana_coman: | whaack: where did you ever lose your curiosity ? | [14:46] |
| diana_coman: | there are all those components that you get to see directly and otherwise end up afterwards doing all sorts from playing your others-are-working shit to everything else and you ...don't even look at it when you specifically take it out and put it back in; why? | [14:47] |
| diana_coman: | you know, it's this sort of thing that turns out any task into "minimal effort and I'll call it a day"; does it need to bite you so you actually look at it properly? or what, do you need me to ask you to draw detailed diagrams of everything? | [14:49] |
| whaack: | diana_coman: I am not sure why not. I guess because I saw the mission be to get the computer built and thought that studying the mobo in more detail was a large task for another day. | [14:50] |
| diana_coman: | whaack: as in for another day that never comes. | [14:50] |
| diana_coman: | whaack: mk, so turn it off, open it up, study the mobo. | [14:52] |
| diana_coman: | write it down; turn it on, try the lshw and see. | [14:53] |
| whaack: | diana_coman: alright. | [14:53] |
| diana_coman: | and yes, the mission was to get the computer built but that includes knowing *what* you are building it out of! ffs, how can it NOT include that to this degree that you don't even know what nic you have? (or maybe you don't even have one? lolz) | [14:54] |
| whaack: | diana_coman: I am not going to be surprised at this point if I don't have one / I have a broken one. | [14:54] |
| BingoBoingo: | whaack: One mildly annoying, probably possibility you run into is that it's a realtek that wants a firmware binary that your Centos Install image didn't have. May have to ferry it over manually. | [14:57] |
| whaack: | BingoBoingo: I believe that is the case | [14:58] |
| whaack: | I say that because while doing research on my mobo I found Realtek LAN Driver's for windows. | [15:00] |
| whaack: | diana_coman: To address your other q's: I hope that I have not 'lost my curiosity.' But based on this I must say 'i hope my curiosity has gone dormant only temporarily.' Looking at the mobo now and taking in what's there, it's clear that I did not observe the thing at all previously. For example, before I did not even notice it had an optical connector. A quote from An Outpost of Progress comes to mind. | [15:14] |
| whaack: | "They lived like blind men in a large room, aware only of what came in contact with them (and of that only imperfectly), but unable to see the general aspect of things. The river, the forest, all the great land throbbing with life, were like a great emptiness. Even the brilliant sunshine disclosed nothing intelligible. Things appeared and disappeared before their eyes in an unconnected and aimless kind of way. The river seemed to c | [15:15] |
| whaack: | ome from nowhere and flow nowhither. It flowed through a void." | [15:15] |
| whaack: | I have questions about the mobo, I can ask them all in here if you'd like or I can first research and see if I can answer them on my own. | [15:19] |
| diana_coman: | whaack: don't you have /didn't you find already the full spec & docs for your mobo? | [15:51] |
| whaack: | diana_coman: yes | [15:52] |
| diana_coman: | so doesn't that hold the answers to your questions re mobo? | [15:52] |
| diana_coman: | and myeah for the rest; wake up already, it's worth it way more than drifting about. | [15:53] |
| jfw: | http://ossasepia.com/2020/04/21/ossasepia-logs-for-29-Jan-2020#1016567 - ok. I wish I could say more on what the trouble is, it's not clear to me either. I will try this split and see how it goes | [15:55] |
| ossabot: | Logged on 2020-01-29 14:39:11 diana_coman: jfw: how about you split this sort of thing into 2 "tasks": one is of the type "ponder and prepare", to be done on one day; the 2nd comes after that and picks up from the notes/output of the first; I'm making some assumptions here re what is keeping you from starting, since you haven't really said anything on that score so if it doesn't fit, you'll have to dig as to what the trouble really is. | [15:55] |
| diana_coman: | jfw: do you do that sort of feet dragging for all tasks? | [15:55] |
| jfw: | I believe it is task-specific so not about inadequate breaks in general | [15:56] |
| jfw: | ^ lines crossed but similar point; it's not all tasks. | [15:56] |
| diana_coman: | so what's the crucial difference between the 2 classes of tasks then? | [15:56] |
| jfw: | hm. first thing coming to mind is 'writing' but that's not it since it depends on the subject | [15:57] |
| diana_coman: | and that's not a difference either :) | [15:58] |
| diana_coman: | jfw: anyway, do you really mean you never drag your feet on anything *other* than writing? | [15:59] |
| whaack: | diana_coman: the questions are of the 'what does this thing (that is likely a part of all mobos) do?' type | [15:59] |
| diana_coman: | (because hm, I think I have counterexamples at the ready, lol) | [15:59] |
| jfw: | no, other things too but... I think I get over the resistance quicker. but maybe I'm blacking out your examples? | [16:00] |
| diana_coman: | whaack: so research that, but do mind your sources; and you know, it's not *only* mobo that has spec and docs. | [16:00] |
| whaack: | ok | [16:00] |
| diana_coman: | jfw: the obvious that I recall seemed mainly of the "don't really care/want to deal with this" | [16:01] |
| diana_coman: | jfw: anyways, try then to basically prepare it that way in advance and see how it goes; hopefully you don't then drag feet on even pondering & preparing it, ha; maybe set up the time for that when convenient/you'd do some thinking/planning anyway. | [16:03] |
| jfw: | will do. | [16:04] |
| jfw: | whaack: the traditional model in Windows was that peripheral vendors ship their own driver binaries, whereas in Linux, open source drivers for all supported hardware are included in the kernel tree (though not necessarily built/installed everywhere). Around the 'vista' era, Windows started gaining more generic drivers out of the box, but still the existence of a realtek driver isn't that | [16:11] |
| jfw: | surprising and doesn't tell you much about the linux situation. | [16:11] |
| jfw: | I kinda doubt 'lshw' will be there if 'lspci' isn't; but I still suspect there's yet things to be learned from closer study of 'dmesg'. | [16:13] |
| whaack: | diana_coman: I want to clarify that I understand the problems with my most recent article on fleetbot's pseudocode and the right way forward. As I see it what I did wrong was I published something closer to a dump of notes than a clear explanation of what the bot does. (and that dump of notes was awkwardly worded.) As you said what I published was a draft. For the revise | [18:04] |
| ossabot: | Logged on 2020-01-27 12:38:24 diana_coman: basically you published a draft, what can one do. | [18:04] |
| whaack: | d article I plan to focus on what the bot does, by going through that draft and cutting out everything that I deem an implementation detail that does not aid in understanding. Then, with what I have left, I will revise the pseudocode/explanations so that they are as clear as possible. | [18:04] |
| whaack: | jfw: ok. I was using that link just as evidence/a clue that the nic on my graphics card is a realtek. (Of course, there are better methods to find out what my NIC is) | [20:48] |
| whaack: | jfw: There was something else I saw in dmesg, when I connect my computer again I | [20:49] |
| whaack: | I'll take a look again and post what I saw that may be relevant to my problem | [20:50] |
Comments feed: RSS 2.0