log☇︎
16600+ entries in 0.121s
mircea_popescu: BingoBoingo can just reuse old one i guess ?
BingoBoingo: I need to know what changes to how I have been handling auctions would get people in WoT to start bidding on auctions.
BingoBoingo: This update raises a serious issue in the lack of success I have had setting a price point at auction this month http://pizarroisp.net/2019/02/10/pizarro-isp-update-february-10th-2019/#selection-31.0-49.104 ☟︎
mircea_popescu: other than that, from what i've seen i believe he's probably right, lilo setup possibly fucked your grub at some juncture. it'd be great to extract the juncture if at all possible.
a111: Logged on 2019-01-14 03:53 mircea_popescu: in other arcana : i have here a copy of trb that has died a mysterious death on dec 31st. the process itself hasn't returned, ps aux lists it as expected, however the last time it touched any files was two weeks ago, nor does a call to getinfo ever return.
mircea_popescu: fail that, even something as vague as "on particularly this-and-so hw mix this thing fails in a manner i can't fucking understand" is better than nothing, witness eg http://btcbase.org/log/2019-01-14#1886738 ☝︎
mircea_popescu: i have no doubt that you, as anyone who uses computers, occasionally encounters error messages, and occasionally has problems.
mircea_popescu: mod6 no man, the difference ain't that one's topic is ada and the other's topic is cuntoo. the difference is that she said "here's the top level problem, here's the list of possible solutions, here's the failure mode of each, let me know if either the list's missing an item or wtf." ; you said "here's an error message pasted and i've been having problems".
mod6: Guys, I'm gonna work on this blog post, then unbury myself from the latest 5" of snow that just landed on me. Let's take this all back up when this is done.
trinque: if I hated you, I'd let you proceed and negrate you in a few months. I personally tire of $howOneAppears being the aim, instead of the side-effect of *doing things*
a111: Logged on 2019-02-10 20:14 mod6: So during this adventure, I initially bought a WD 250Gb SATA SSD, upon which I installed cuntoo. Which I never did get to work. Upon initial suspicion that disk might be bad, I bought another 250Gb WD SSD and installed cuntoo on that also. Same error. So I at least removed the variable of "disk is bad".
trinque: you're evaluating things towards the purpose of avoiding negative reflection upon you, rather than from the cause of your circumstances. thus when I ask you what was on your workbench when http://btcbase.org/log/2019-02-10#1894746 happened, you either don't know or shy away from saying. ☝︎
BingoBoingo: I suggest lifting head, making some hot chocolate, taking a walk to dump some adrenaline off and get a bit of calm, then returning.
BingoBoingo: I'm seeing less punches and more error reports being presented in response to the way you are composing your own error reports. It's an error cascade.
mod6: I'm not focused on any feelings. I just would rather not bother you.
mod6: I mean "lately" as in, the last year or so... which is fine. I should have just started blogging immediately instead of trying to resolve my issues for 10 days.
BingoBoingo: For my own selfish reasons I want to see what you hit your head on, because there is a very real chance when I go to try things I will also hit my head on the same rocks ☟︎
mod6: This is perhaps why I never reached out.
mod6: I tend, lately to stay away from asking trinque questions, as I seem to get punched in the face as opposed to helpful responses.
BingoBoingo: mod6: The closest computers have come to the promised "intelligence amplified" I have ever seen is when detailed error reports in this channel and less frequently #pizarro and #asciilifeform yield detailed feedback.
mod6: Well, if your frustrated with me, I apologize. I'm just trying to get this up and going so I can test Keccak TRB on here.
mod6: Also, I'm remembering now, trinque, that I did ask alf about my inital hang that I had in #piz. He suggested that I had a kernel problem, but I never did really ask about it otherwise. I just tried to solve my own problem.
mod6: Anyway, I think I'm just a bit frustrated.
mod6: Well, it seemed to me there was a pretty lengthy conversation about Ada threading issues over the last two days, I didn't want to make my problems (with a possible questionable box) the center of attention for everyone.
a111: Logged on 2019-02-10 20:00 mod6: Well, during the information gathering of my blog post, I went to boot back into my never-has-failed me Gentoo installation on my 500Gb SSD. And now I'm getting: "Welcome to GRUB! \n error no such device: e45d853f-... \n error: unknown filesystem \n Entering rescue mode... \n grub rescue>" which doesn't let me boot by selecting: linux (hd0,1)/<kernel_name> root=(hd0,3) \n boot different than the normal gr
a111: Logged on 2019-02-10 16:02 diana_coman: http://btcbase.org/log/2019-02-08#1893804 -> sadly I must say that I failed to find a way to terminate the program if/when one of the tasks is just looping infinitely ; I tried: abort of the looping task -> nothing,because task is "not in an abortable region"; Abort_Task(Current_Task) from the main program -> still stuck because apparently it takes it to mean "will stop AFTER all my dependent tasks stopped too!"; raising an uncaught except
a111: Logged on 2019-02-10 20:54 mod6: trinque: what do you mean by 'angular'? If you mean, why so terse? Because I don't want to flood #t with a ton of information, as I'm afraid I'll also leave something out.
mircea_popescu: it very well fucking is not. it's not even remotely as important. having usg.cmu or usg.anything-else spew on actual literature is nothing short of vandalism. i don't want their grafitti, and i don't care why they think they're owed it.
mod6: Because after all the gentoo problems I had back in '15, I wanted to be sure that I had exausted all the things before bringing this forward.
trinque: I give even odds the lilo step of the script trashed your grub. one would love to know why.
trinque: I'm certain the cuntoo script is *not done* which is why I'm having folks test it, but I want more out of these tests than "ow, it wasn't a debian installer"
mod6: I've conducted quite a bit of work over these last 10 days, and I know mod6 seems like a "n00b" and "doesn't know what he's doing", but I have managed to install gentoo quite a few times since '15. But yeah, always learning.
a111: Logged on 2019-02-08 18:11 diana_coman: http://btcbase.org/log/2019-02-08#1893756 -> this makes in fact a lot of sense esp given asciilifeform's observation that indeed, that's an unrecoverable error state; so this sounds good: if child task doesn't die when aborted then kill self (taking the task with self too ofc); I'll experiment with this but afaik so far it should work
mircea_popescu: http://btcbase.org/log/2019-02-10#1894753 << i thought mbrs went out with the dos. still a thing ?! ☝︎
mod6: trinque: what do you mean by 'angular'? If you mean, why so terse? Because I don't want to flood #t with a ton of information, as I'm afraid I'll also leave something out. ☟︎
trinque: shinohai: lol at this rate I'm calling it a high priority feature request.
a111: Logged on 2019-02-10 18:41 spyked: BingoBoingo, that's a very good q. I'ma make some quick stats with file types and their sizes, then will add them to the post.
mircea_popescu: http://btcbase.org/log/2019-02-10#1894713 << i specifically don't even WANT the "rich media" / dvds / epubs / pdfs / whatever bullshit. i don't even want their pagelong blathers about how all-important inca is or whatever shit. ☝︎☟︎
a111: Logged on 2019-02-10 18:44 asciilifeform: diana_coman, mircea_popescu , et al : other observation : based on my reading of https://www.adaic.org/resources/add_content/standards/12rm/html/RM-9-8.html , 'abort' oughta work as a hard kill unless you specifically put a deliberate 'do this before death' in the task. but does gnat actually obey the standard here, i currently do not know
mircea_popescu: http://btcbase.org/log/2019-02-10#1894714 << it's not like there was any prior expectation for the malfunction on any basis whatever. yes, as far as i also knew, shit was supposed to work, from what i know of what they've said you'd expect it worked etc etc. ☝︎
trinque: whatever ritual you prefer. I'm sitting right here, wondering wtf this angular communication is.
mod6: trinque: I'm getting there, it'll be in the blog post.
a111: Logged on 2019-02-09 19:55 trinque: btw this means that e.g. what mod6 is experiencing are more likely to be "I need to go understand kernels and lilo better" than "cuntoo is broken"
trinque: mod6: you really need to push through this "I have 3 broken things and no idea why, time to junk the box" impulse.
mod6: files backed up. ok, well, i've re-run `grub-install /dev/sda && grub-mkconfig -o /boot/grub/grub.cfg`. we'll see if this resolves it.
BingoBoingo: I suspect there's space for error in the process of setting up and keeping up the filesystems that will persist without regard for how many boxes get junked along the way
mod6: I think I'm just going to junk this box.
mod6: But that's what I've got now. 2 250Gb SSDs with Cuntoo on them, neither boot, and now a 500Gb Gentoo disk that has worked perfectly up until just this very moment, which also doesn't boot.
mod6: So during this adventure, I initially bought a WD 250Gb SATA SSD, upon which I installed cuntoo. Which I never did get to work. Upon initial suspicion that disk might be bad, I bought another 250Gb WD SSD and installed cuntoo on that also. Same error. So I at least removed the variable of "disk is bad". ☟︎
BingoBoingo: I suspect file system corruption is more likely. This may mean hardware failure or it could mean an accumulation of small errors piling up during those power cycles.
mod6: Anyway, I'll dig up the artifacts off the gentoo disk with the Live CD and still make a post. But regardless, I think I'm gonna have to buy a new machine to mess with this any further.
mod6: What a nightmare. This box has been rock-solid for nearly a year, but now I suspect that perhaps this is a hardware problem with the MB or something? Perhaps the 78 power-cycles and SATA disk swapping that I did over the last 10 days totally hosed the machine itself.
mod6: I can still access the disk via Live CD... so at least I can get the data off the drive.
mod6: Well, during the information gathering of my blog post, I went to boot back into my never-has-failed me Gentoo installation on my 500Gb SSD. And now I'm getting: "Welcome to GRUB! \n error no such device: e45d853f-... \n error: unknown filesystem \n Entering rescue mode... \n grub rescue>" which doesn't let me boot by selecting: linux (hd0,1)/<kernel_name> root=(hd0,3) \n boot different than the normal gr ☟︎
asciilifeform: meanwhile ave1 didja ever genesis the gnat ? currently i haven't what to patch on.
asciilifeform: i'ma go and do meat chores, will return around 2300 hrs orcistani time, and build diana_coman's tester
asciilifeform: in re 'had to import exit()', i found that this is troo for ~100% of os i/o, not only e.g. udp but character i/o, etc. i dunlike the standard i/o glue thing came with at all.
diana_coman: ftr I DID look at it with gdb
diana_coman: k, I'll take it down and post it a bit later
asciilifeform: diana_coman: can you post plox the whole test jig, i'd like to reproduce the effect and see wtf , in gdb ( prolly won't get to it until nightfall tho )
diana_coman: and I mean abort_task(current_task) as well as abort that_task
diana_coman: i.e. it "works" in the sense that it politely waits until that wedge task is kind enough to please come out of the loop so you can abort
diana_coman: asciilifeform, nope; I tried raise Program_Error and it was just as stuck
asciilifeform: diana_coman, mircea_popescu , et al : other observation : based on my reading of https://www.adaic.org/resources/add_content/standards/12rm/html/RM-9-8.html , 'abort' oughta work as a hard kill unless you specifically put a deliberate 'do this before death' in the task. but does gnat actually obey the standard here, i currently do not know ☟︎
spyked: BingoBoingo, that's a very good q. I'ma make some quick stats with file types and their sizes, then will add them to the post. ☟︎
BingoBoingo: spyked: I'm curious what happens to the size of the archive if you split out the DVD's, mp3's and pdfs.
asciilifeform: diana_coman: it is exactly == to GNAT.OS_Lib.OS_Exit(0) , yes, btw; i did the 'import' for the same reason as for the character i/o, i.e. to lose the dependency on the standard lib
asciilifeform: diana_coman: how did you model 'wedged task' ? ( i.e. what didja put in it ? infinite loop? or eternal i/o wait ? )
asciilifeform: nao i'ma have to reproduce this
diana_coman: the issue at hand being that ADA doesn't kill ; and to add to this, note that in this case (i.e. some wedged task) it won't actually *finish* even when its checks fail; so that promise that "program will stop running if erroneous state" is at best mis-stated: no, it won't always stop, it might..wait to stop
asciilifeform: i dun know of a workaround for this, either, other than to finally fucking bury unix.
asciilifeform: will add to this also, that if yer thread is actually wedged, it will almost always be on acct of http://btcbase.org/log/2019-02-08#1893811 , i.e. waiting for a blocking unix i/o, and no matter what yer pthreads proggy is written in , c, ada, cobol, whatever, it will still become a zombie, cuz unix is retarded. ☝︎☟︎
asciilifeform: nuffin keeps you from calling exit(-1) and nuking whole process + all children. i have nfi where is the puzzler here.
a111: Logged on 2019-02-08 17:06 mircea_popescu: so then i'm guessing if indeed this problem is encountered thing should just die altogether.
asciilifeform: re the threads tho, i thought q was settled in the http://btcbase.org/log/2019-02-08#1893774 item. ☝︎
asciilifeform: i dun think it even makes sense to think of the problem in terms of 'write a new ada' tho. the way i see ada, is as a junkyard wars workaround against the retardation of pc arch, where pointerolade, overflowable arrays, etc. if you had a sane arch, you could program in moar or less whatever you want (e.g on bolix, ada, fortran, c, lisp, were implemented as simply skins around the arch, and all shared in the nonoverflowability etc )
a111: Logged on 2019-02-05 01:00 asciilifeform: the ultimate win would be to get something other than gnat ( say, an adatron implemented in cl... ) that can build something resembling a working gnat. but sadly i suspect this is yrs away.
a111: Logged on 2019-02-10 16:12 mircea_popescu: i'd rather write a new ada.
asciilifeform: http://btcbase.org/log/2019-02-10#1894658 << there is not , in long term, any escape from 'write a new ada' (at the very least, even if there were no known gnat bugs -- and i've already found at least 1 -- on acct of http://btcbase.org/log/2019-02-05#1892591 ). ☝︎☝︎
a111: Logged on 2019-02-10 16:05 diana_coman: I'm all ears if anyone has some idea re this supposedly simple thing: how to kill-self in ada, whole program but guaranteed to work i.e. without any bullshit "oh, but only if/when..."
diana_coman: so now I'll have to study that and see how it does it...
diana_coman: to kill whole program I mean
diana_coman: hopefully there still is some way I've overlooked/haven't yet found, what can I say
mircea_popescu: and ada kept to an arm's length absolutel minimum. i find it immoral to support development in femstate languages.
diana_coman: I suppose I still have to try...calling pthread_kill from within ada or somesuch madness
mircea_popescu: i'd rather write a new ada. ☟︎
mircea_popescu will NEVER fucking support this, i don't care what it is, people, software, whatever the fuck. husband above ALL children, operator above internal state, no fucking exceptions.
mircea_popescu: i'm not about to give control of the box to "ada".
mircea_popescu: what the fuck am i going to do ?
diana_coman: ugh, can't say though I'd really want to implement more c/cpp
diana_coman: I'm all ears if anyone has some idea re this supposedly simple thing: how to kill-self in ada, whole program but guaranteed to work i.e. without any bullshit "oh, but only if/when..." ☟︎
diana_coman: and I don't know what does this make re I/O operations because you can't quite control they are "in an abortable state" afaik
diana_coman: this is what I understand so far: IF you have the misfortune of calling something that won't stop for whatever reason, you're fucked
diana_coman: I also tried asynchronous transfer i.e. supposedly "try this and if timeout then do that" but apparently it's in fact still "oh, but ONLY if abortable" ☟︎
mircea_popescu: i tell you i dun see it. what amount ?
a111: Logged on 2019-02-08 18:11 diana_coman: http://btcbase.org/log/2019-02-08#1893756 -> this makes in fact a lot of sense esp given asciilifeform's observation that indeed, that's an unrecoverable error state; so this sounds good: if child task doesn't die when aborted then kill self (taking the task with self too ofc); I'll experiment with this but afaik so far it should work
diana_coman: http://btcbase.org/log/2019-02-08#1893804 -> sadly I must say that I failed to find a way to terminate the program if/when one of the tasks is just looping infinitely ; I tried: abort of the looping task -> nothing,because task is "not in an abortable region"; Abort_Task(Current_Task) from the main program -> still stuck because apparently it takes it to mean "will stop AFTER all my dependent tasks stopped too!"; raising an uncaught except ☝︎☟︎
mircea_popescu: nfi what i did above to get http://btcbase.org/log/2019-02-10#1894617, but anyway : 1800 coins / day, 3500 each say, 24 hours in that day, 3600 seconds in the hour and 35k or so PH/s network speed atm, give or take. makes the true value of the ~exa~hash about two bucks. ☝︎
mircea_popescu: yes, well, i wish to hear what that one guy has to say. then we see.
asciilifeform: iirc i got 40 on the x60.