Young Hands
1h 34m2h 12m3h 57m7h 44m1d 16h 28m12h 17m1h 52m

diana_coman: - *when* should you have asked this?
ossabot: Logged on 2019-10-11 16:59:36 whaack: a little update on my interests post. first, i thought this was understood but i want to clarify with you diana_coman that this post is not supposed to be a continuation of previous/future tmsr work but instead a list of the things that i am personally interested in. (that would be aeparate post that will come later.) second, i've come up with six categories: pr
diana_coman: whaack: happily for you this time, the post is indeed a list of your interests, not a revision of the previous post, no; outline at this stage sounds ok but it's hard to say much on it at that level (other than you seem perhaps to overwork the classification before you even got in clear exactly what content you have; it generally works the other way around)
diana_coman: asciilifeform: thank you for the updated recipe, I'll try it out today.
diana_coman: asciilifeform: done, booted successfully, I'll have to still check everything but will run it also on at least one more amd today
diana_coman: and I tweaked an option at kernel compile time so my usual kbd works as well, lolz.
diana_coman: the sort of thing that works way better when not totally tired like yest.
diana_coman: asciilifeform: hm, apparently the recipe though results in / mounted as read-only ?!
diana_coman: from dmesg:
diana_coman: I don't get why it's trying to mount it as ext3; fstab clearly say ext4 for /dev/sda2, ugh
diana_coman: mk, I added to boot line rootfstype=ext4 and that at least got read of trying to mount it as ext3; onth, it's STILL read-only, grrr
diana_coman: got rid*
diana_coman: at least remount works fine so hm
asciilifeform: guten tag diana_coman . lemme check re these oddities, 1s
asciilifeform: diana_coman: confirmed, a) root mounts ro . will find out why ( did not occur, naturally, on actual dulap ) b) sad python. confirmed. may have occurred on actual dulap and fixed after imaging (or phuctor, lol, could never have worked ) . didja ever look on smg-primary ? had to also fix there ?
diana_coman: morning asciilifeform ; let me know what you find; I'll be around
diana_coman: asciilifeform: I don't recall having to fix python, no
diana_coman: then again, eulora doesn't actually use any python as such
diana_coman: meanwhile it's on my to-check list, hence ?!
asciilifeform: i suppose we see when you get the backup cut up
asciilifeform: mine, naturally, was troo-python (none of my proggies will execute under 3, it's exotically broken)
diana_coman: asciilifeform: the idea is/was that if I'm fine with the backups I have, then disks get destroyed, not sent about
asciilifeform: diana_coman: i rec to recreate machine before burnin'
diana_coman: and my backups are of smg data, not of the system
asciilifeform: aha
diana_coman: asciilifeform: this is why I'm installing dulaps, no?
asciilifeform: diana_coman: righto
asciilifeform: diana_coman: fwiw i had my disks sent, cuz they did not contain any proprietaries that hadn't already been stolen w/ the last dulap
asciilifeform: anyway i'ma go vivisect the tester, brb
diana_coman: asciilifeform: well, eulora server is a bit of a different thing, hence rather not send unless have-to
diana_coman: kk
diana_coman: I'll be away for about 30 minutes and then back at console
asciilifeform: np
asciilifeform: i expect will take at least that long, still waking up as the sun goes up.
asciilifeform: diana_coman: i expect (1) is sumthing to do with ext4, on orig dulap had set up w/ reiser but did not want to propagandize the use of obsolete fs . looking into why mounts ro.
asciilifeform: btw i also used mbr, rather than gpt, on orig, updated recipe so people could use >2tb disks. may be culprit (req's diff options)
diana_coman: asciilifeform: I was rather surprised at using gpt tbh; and why do you start first partition at 64?
asciilifeform: diana_coman: was looking just nao re why. apparently no good reason, carried over from rk recipe (where the chipset actually required it) , can just as well start from 1
asciilifeform: diana_coman: also found culprit re why mounts readonly ext4. the boot stick mkfs.ext4 enables 'huge files' opt by default, which needs kernel flag, aboutta rebuild w/ same
asciilifeform: will add all of this to recipe.
diana_coman: kk, thanks
asciilifeform: re python, apparently was in fact defect in the orig install, and had fixed immediately when setting up phuctor.
asciilifeform: will add also to recipe. (or, alternatively, will make a new fs tarball)
asciilifeform: still reading dox re (1) , cuz seems as if it may be red herring (applies only on 32bit kernels??)
asciilifeform: diana_coman: re gpt -- >2tb raid arrays require it. i didnt have one, but intend to when rebuild dulap, hence the patch.
diana_coman: ah, ok re gpt.
asciilifeform: update : confirmed that 'huge files' item is red herring, it is unneeded on 64bit kern. so continuing dig.
whaack: diana_coman: good morning. I should have clarified the task assignment upon receiving it. The reworking of my classification came after writing content and realizing that my 'programming' section was ~identical to my cryptography section. This follows from the fact that work related to crytographic tools is the ~only interesting programming work. At least for me.
diana_coman: whaack: morning; programming ~= controlling computers and if you want to do crypto, you kind of need to actually control your hardware so unless you have something other than existing computers, you need to know stuff around crypto itself as well; that being said, there's no problem in saying that your interest is in crypto really and that's it; ie you will learn anything else you need for & around
diana_coman: it but that's your goal, sure.
asciilifeform: diana_coman: found the eggog. without ancient notes, would never have found, troo cascade of liquishit. so, when made this tar, used 'exclude' command, with 'root'. and wrong regexp. so in fact 'evaporated' the initd script in /etc/init.d/root . which is what remounts / as rw .
asciilifeform: diana_coman: i suspect that the Right Thing nao is to roll new tarball , replace the prev.
asciilifeform: but 1st lemme demostrate the fix :
asciilifeform: 1st remount as rw : mount -o remount,rw ; then this goes in /etc/init.d/root ; then rc-update add root boot ; then reset. get proper boot.
asciilifeform: incidentally in /etc/fstab, prolly want ramdisk,
asciilifeform: shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
asciilifeform: i'ma make new dump tarball.
asciilifeform: incl. correctly-sel'd python.
diana_coman: asciilifeform: all right; what's the eta re new tarball?
asciilifeform: hr+. gotta write to slow usbstick and then upload to snail server.
diana_coman: I did precisely the remount earlier but anyway, didn't fix python otherwise so didn't really want to go ahead with all the rest on it as it is
diana_coman: fwiw at least the recipe worked with same results on a 2nd amd on a gigabyte board
asciilifeform: diana_coman: i'ma start.
diana_coman: so there is some support to "will work on various amd platforms"
diana_coman: asciilifeform: ok, thanks.
asciilifeform: diana_coman: it's expected to work on any amd after k7.
asciilifeform: 1s, gotta redo, forgot to 'make clean' in '/usr/src/linux', will massively bloat the tarball
diana_coman: heh
asciilifeform: uploading.
asciilifeform: steps 3-12, 3-18 should no longer be needed.
asciilifeform: upload oughta be done in ~30m
asciilifeform: sha512==51b339fd922497bbd11abc38375b54beb01a9737af55dd4114c328023927ce07e2bd90a6c9b1a3f793b862dc951b0ae438bfd3591c295254982c880c89190787 meanwhile.
thimbronion: diana_coman:
asciilifeform: diana_coman: if you have a ftp going on 1 of those cheapo leased machines, i can try and put there, faster.
diana_coman: thimbronion: answered.
diana_coman: asciilifeform: I didn't set up any, uhm.
asciilifeform: diana_coman: 45% in
asciilifeform: still goin'.
diana_coman: so prolly it will take ~same anyway
asciilifeform: this bugger is slow but not as slow as the bmore monkeys, last word from whom was 'i'ma get your order to the boss' who apparently took vacay
asciilifeform: diana_coman: while wait : when you do the kernel build, plox to examine whether it has the cp2101 (FG) thing , and the flags for iptables
diana_coman: thimbronion: was my own text on the role of feelings clearer/easier for you than hanbot's?
ossabot: Logged on 2019-10-05 11:03:54 diana_coman: thimbronion: re your question on - you are confusing the contexts there (or not really making a proper separation at all); read and see if that answers it for you; if it doesn't, ask me again.
diana_coman: asciilifeform: I thought iptables was deemed utterly un-necessary?
asciilifeform: diana_coman: iirc you used it
asciilifeform: i -- left off
diana_coman: well, not after the discussion and conclusion, no? otherwise what use is to discuss and conclude, lol
diana_coman: so no, not using anymore either
asciilifeform: aite.
diana_coman: if anything, it would help to check that an FG works well
diana_coman: iirc there was the need to downgrade via companion or some such shit
asciilifeform: point being that kernels are sorta intimate affair, it's like putting on another person's eyeglasses, to use kernel conf unexamined.
diana_coman: (it's in my notes somewhere, will get to it when reproducing all stuff anyway)
diana_coman: asciilifeform: I don't think this is very sane though for non-personal machines; precisely because if every machine has to have different kernel conf than it's not all that reproducible
diana_coman: sure, on my personal machine, I fuck the kernel whatever way I want; not same for non-personal machines though.
asciilifeform: diana_coman: the issue is that erryone has slightly diff machine. esp if they aint all built by 1.
asciilifeform: for instance if you have a raid, you gotta have the flags for ~that~ raid.
diana_coman: myeah
diana_coman: but I'm trying to keep those differences to a very minimum, ideally 0, ugh.
asciilifeform: the offered kernel is made so as to guarantee bootability on commonplace amd irons. but it cannot be guaranteed to operate ~arbitrary~ irons w/out some tailoring.
asciilifeform: this is consequence of 'tower of babel' of pc irons.
diana_coman: myeah, I know.
asciilifeform: fwiw it stood up on a circa-2010 box last night w/out changes.
asciilifeform: eta <20m
asciilifeform: i'ma go wash up , brb
diana_coman: crowncloud: are you there?
thimbronion: diana_coman: yes it was.
asciilifeform: diana_coman: . checksum pasted earlier.
asciilifeform: diana_coman: when this item is confirmed to pass basic smoke test, i'ma fix the recipe & sign.
asciilifeform: ( unless diana_coman would rather post own recipe )
asciilifeform: tarball will sign in any event.
asciilifeform: diana_coman: lemme know as soon as you get chance to try , cuz uploading these to my 1 remaining box takes ~45min. ea. time.
diana_coman: asciilifeform: ok, downloading it
diana_coman: asciilifeform: why is that box so slow, I don't recall?
asciilifeform: diana_coman: it's where my www. kolhoz .
diana_coman: at any rate, if that's the problem, I'll set up an account for you on younghands or somewhere, lolz
asciilifeform: diana_coman: at the rate bmore is going, i might need another, so ty.
asciilifeform: 'elderlyhands'
diana_coman: asciilifeform: do you still plan to send a box to maxim/mivo?
diana_coman: heh, quite
asciilifeform: diana_coman: indeed. already purchased the disk for that 1
diana_coman: kk
asciilifeform: i expect it'll take time to go across atlantic.
asciilifeform: diana_coman: i'ma colo a 'apu1' with him. will see how goes.
diana_coman: probably, yes; though not necessarily longer than bmore takes to give you a box locally from what I understand
asciilifeform: entirely possib
diana_coman: about 500M downloaded
asciilifeform: ha, much faster than when up
asciilifeform: they must have an asym. pipe.
diana_coman: usually for kolhoz sort of thing they do as far as I saw
diana_coman: asciilifeform: iirc you can get that with him via email only ie without account on website, correct?
asciilifeform: ftr i asked the bmore people about ddos. after ~that~ was told 'gotta ask boss' and made to wait.
asciilifeform: diana_coman: i haven't opened any type of acct at maxim's just yet, still in conveyor.
diana_coman: asciilifeform: heh; I asked some some "eu" thing; first they replied with "oh no, it's nothing to worry, as long as you update/blabla"; after which, when I asked specifically and exactly what do they do if there's an attack on MY box...silence
diana_coman: I don't even expect they'll come back to me, lolz
diana_coman: asciilifeform: try maybe you can get away without account; worth a try at least and as far as I can tell, if there's a chance of that, so far it's with them only.
asciilifeform: diana_coman: ah, but see, the bmore people bill for packet mass. so 1st gotta get answer to 'what when ddos?' cuz on my surface reading, the answer may be 'potentially infinite bill' and then no go
diana_coman: asciilifeform: heh, the eu had "potentially disconnect you", hence my q ~= wtf do you think I'm paying you for to disconnect me??
diana_coman: anyways, supposedly one way or another I'll get my blog back up and then do the write up of all that shit
asciilifeform: diana_coman: after latech i aint sure whether anyone can be believed, re 'when ddos'.
asciilifeform: only way is recon by fire.
diana_coman: asciilifeform: at the very least they *have to say it in writing*
diana_coman: that's the rub
diana_coman: and I fully intend to rub them in it
asciilifeform: BingoBoingo is busy rubbin' atm, iirc.
asciilifeform: i dun expect much to come from it.
diana_coman: asciilifeform: tarball downloaded and checksum checked, all fine
asciilifeform: ok, then ready for testfire.
diana_coman: asciilifeform: no, the point is *before* anything; because they won't quite want to say/admit "yes, you pay for us to disconnect you" but onth if they say "no, we don't", they are in a bigger pickle when they do so...
diana_coman: hence why I expect they won't come back to me at all, no
asciilifeform: diana_coman: which firm was this ?
asciilifeform: eu i mean
diana_coman: asciilifeform: some eunet iirc or if you really need it I'll look it up in the notes; a quite big corporation style thing but at that point I tried them too, why not
asciilifeform: aok
diana_coman: asciilifeform: are you writing the new recipe now?
asciilifeform: i am. the only diff tho is + the new tarball url atm.
ossabot: Logged on 2019-10-12 10:50:45 asciilifeform: steps 3-12, 3-18 should no longer be needed.
diana_coman: ah, then I'll try to proceed with it
asciilifeform: ty diana_coman
asciilifeform: diana_coman: and will deedbot after verified to work
diana_coman: asciilifeform: kk, thanks; working on it
diana_coman: asciilifeform: you should update that parted to start at 0 too
asciilifeform: a yes
asciilifeform: diana_coman: i'ma hold off on rewrite of instrs. until you return 'it worx'
asciilifeform: may need other fix.
diana_coman: kk
asciilifeform: parts cant start at 0 btw, that there's the mbr
asciilifeform: lilo needs to live somewhere too
asciilifeform: so usually people give it coupla sectors
diana_coman: yeah, 34
diana_coman: thimbronion: is the review-trouble clarified now?
diana_coman: asciilifeform: you forgot to update the name of the tarball in the new recipe at 3-16
diana_coman: 3-11, ugh
asciilifeform: indeed.
asciilifeform will put these in as diana_coman emits'em
asciilifeform: diana_coman: btw i found that if using 'grub' you actually needs those 63 spare blox.
asciilifeform: looked on a local box w/ 'grub', partitioned same.
asciilifeform: 'tis a pittance tho, block==512b.
thimbronion: diana_coman: yes but I am absolutely certain I will run into more questions when I try again tonight. Got to head out now.
diana_coman: asciilifeform: now the tar complained about timestamp; do you know if that is more than just a warning?
diana_coman: I never saw this before
asciilifeform: diana_coman: our clocks differ, i suspect
asciilifeform: so yours thinks 'from future'
diana_coman: asciilifeform: possibly; my q is whether it still unpacked everything or not
asciilifeform: these get tar'd with 'p' flag, i.e. preserve-all incl. times
asciilifeform: diana_coman: oughta have
diana_coman: seems so as far as I can see; ok, moving on
asciilifeform: looked, box where tar'd set to utc, so yes 'from future, martians'
asciilifeform: it's oct 13 on it.
asciilifeform: ( this problem, will fix self )
diana_coman: thimbronion: ok but you know, ack still needed on positive outcome too; don't do this "no news is good news"
diana_coman: compiling kernel, changed it to armoire at least to make sure it's the one I'm aiming; will remember to change in lilo.conf too, lolz.
asciilifeform: diana_coman: in the end may want to make yet another tarball, it is quite bare, and lacks such amenities as e.g. gnat.
diana_coman: asciilifeform: that I have & will deploy afterwards anyway
asciilifeform: aite
asciilifeform: speaking from the pov of hypothetical 'make 6 spare boxen' and similar.
diana_coman: asciilifeform: I suspect I'll have to make scripts really
asciilifeform: diana_coman: well trinque already made scripts. but iirc you had an item that still not 100% certified to live in cuntoo.
diana_coman: asciilifeform: is that rootfstype=ext4 parameter needed in the end?
asciilifeform: diana_coman: per the dox, seems to be. hence wai put in.
diana_coman: I had added up on previous install to get rid of idiotic attempt to mount it as ext3 (and it worked) but dunno if still needed it now
diana_coman: ah, ok
asciilifeform: i dun use ext4 myself, so had to look up.
diana_coman: asciilifeform: yes sadly, can't yet move on to cuntoo.
asciilifeform: right, is what i recalled.
diana_coman: plus honestly, cuntoo is still work in progress in fact, not yet really there.
diana_coman: more like "work in waiting" but anyway
asciilifeform: ( if could use, diana_coman would not have asked for this earlier barbarism, i inferred also )
asciilifeform: ftr 'dulap-gentoo' is, concretely, the last gentoo built by asciilifeform while traditional gentoo still was buildable ; incorporating the ban flags & cleanups discussed in '15-'17.
diana_coman: asciilifeform: certainly I'd have used cuntoo if I could.
asciilifeform: python3, ftr, was not entered into the ban list strictly because asciilifeform uses, sadly, 1 single program (ice40 toolchain) that runs in it. otherwise can be safely discarded afaik.
diana_coman: asciilifeform: success! booted Armoire-II; / is mounted in rw mode, gcc is 4.9, python is 2.7
asciilifeform: a+++ diana_coman
asciilifeform: diana_coman: didja end up fiddling w/ kern. conf ?
diana_coman: thank you for the new tarball asciilifeform !
asciilifeform: np diana_coman
diana_coman: I looked about, changed the one for my usual kbd (the emergency ps kbd is not that comfy on fingers) and otherwise looked around but I didn't see something directly needed/to change
asciilifeform: diana_coman: lemme know when you have chance to mirror the tar, mine is veheheheryslow
asciilifeform: would rather link folx to mirror.
asciilifeform: diana_coman: lemme know if you want other changes in the doc, i'ma revise , sign , deed.
diana_coman: I'm sure it can be tuned probably but I'm not all that interested in that + atm I really need to get on with installing all the stuff and bringing the eulora servers up at least here
asciilifeform: diana_coman: re kernel -- may have to turn knob to get FG.
asciilifeform: depending on what cables you have.
diana_coman: asciilifeform: hm, in this one it's on usb; do you know where is that knob in kernell?
asciilifeform looks
asciilifeform: i had to CONFIG_USB_SERIAL_PL2303 for mine
asciilifeform: if you have the cp210x one ought work as given in tarball tho.
diana_coman: I recall that is the knob (or at least one of the needed ones), yes
diana_coman: no, should be pl2303, ugh
asciilifeform: most people got the cp210x
diana_coman: hm, need to look in notes and check
asciilifeform: what colour is your plug ?
diana_coman: asciilifeform: I have both black and blue (usb 3)
asciilifeform: then you need the knob
asciilifeform: blue's a pl230x
diana_coman: hm, and black isn't ?
asciilifeform: black was the chinesium, it actually came in the 2 variants unlabeled, annoyingly
asciilifeform: initially i raged about it, then thought 'good to have mix, will see if there's oddities/noncomplicances in standard'
asciilifeform: my criteria for these was 'anyone but ftdi'
asciilifeform: diana_coman: looking again at my notes, turns out that no, all batch2 fg people have the pl.
diana_coman: asciilifeform: this is what I recalled, that it was ~always pl
asciilifeform: so yes, knob.
diana_coman: so I think at least mention the location of that knob, in the recipe perhaps
asciilifeform: aha, you should have 2 pl. (regardless of colour)
asciilifeform: diana_coman: will put in.
diana_coman goes back to recompile
asciilifeform: diana_coman: dun fughet this if you're plugging in 3 or moar.
ericbot: (trilema) 2018-08-01 asciilifeform: dwc_otg.speed=1 on kernel param line.
diana_coman: asciilifeform: good point; add to recipe too, please
asciilifeform: will.
asciilifeform: the bit re kbd is interesting -- none of the boxes where i had this going, ever had a classic ps/2 kbd.
asciilifeform: tried even last night several usb kbd, all worked.
asciilifeform brb, eating (very late breakfast lol)
diana_coman: asciilifeform: either I'm blind atm or it's one of those that depends on something else and so on ffs; I went to Device Drivers -> USB support but I can't find it anywhere, grr
diana_coman: ah, found it; it's in device drivers/usb support/usb serial converter support/usb prolific shit
diana_coman: gah
diana_coman: I will need to go for a few hours so I'll let it compile and then get back to it when I'm back
asciilifeform back
diana_coman: asciilifeform: confirmed compiled, booted and FG seen; now I'm going away for 2-3 hours, will move on to rest of installs after that
asciilifeform: a++
asciilifeform: diana_coman: lemme know if again puzzler, i'ma also walk for some hrs.
asciilifeform: will check log later today.
thimbronion: diana_coman: noted re: good news.
shinohai: I'm trying to write ebuild for Eulora client, but will alo require separate ones for cal3d/crystalspace it appears.
diana_coman: shinohai: yes, cal3d and crystalspace are the ones to start with because they will stay the same, most likely.
diana_coman: cal3d should be the easiest to start with really
diana_coman: for one thing getting it to build with gprbuild is quite straightforward and for the other, it's way less messy than cs
diana_coman: shinohai: so I'd say start with that and let me know how it goes
shinohai: Are they simply a specific version, could i mask them if already in portage?
diana_coman: shinohai: they are a specific version; I doubt they are in portage but look and let me know, why not
shinohai: <<< ebuild has hard requirement for gcc 4.9.4 / Ada
ossabot: Logged on 2019-10-12 16:32:21 diana_coman: for one thing getting it to build with gprbuild is quite straightforward and for the other, it's way less messy than cs
diana_coman: you'll need the exact versions used/mirrored by though, at least for the client as far as it'll be released (other than that you can always do your own /make it work with any version, ofc)
shinohai: Thats why I think I should just use the ones I have mirrored on my site, because exact match for ones from minigame
diana_coman: shinohai: what do you mean? they certainly compile with gcc 4.9.4 ofc; and fwiw I compiled cal3d with gnat/gprbuild, it worked fine
shinohai: (So ebuild is better method of doing this, I believe)
diana_coman: cs is messier because it has a ton of if-defism among other warts
diana_coman: shinohai: so yes, sure; use those; not sure in the end what are you trying to do exactly? (I thought you were trying to *make* ebuilds for those versions, yes)
shinohai: Yes, that's what I intend to do (write ebuild for all 3 components), just assuring I couldn't be lazy and just do package.mask xD
diana_coman: note that cs also has quite a few dependencies so you'll probably be better off doing first cal3d and then starting from those cs deps and only at the end the cs itself
diana_coman: shinohai: first of all: are they even in portage? because I seriously doubt but just check anyway, it's not a difficult thing to do
shinohai: yeah I checked, both available
diana_coman: if nothing else, an existing ebuild might help you as an example perhaps
diana_coman: ah; what versions compared to minigame ones?
diana_coman: cal3d is quite frozen so maybe lucky there
shinohai: emerge search shows:
shinohai: media-libs/cal3d
shinohai: Latest version available: 0.11.0-r1
shinohai: Latest version installed: [ Not Installed ]
diana_coman: the 0.11 sounds right, dunno about r1
diana_coman: so that might be handy if it works, worth a try at least
shinohai: Will report in when I have results o7
diana_coman: as I said: cal3d has been quite frozen for ages, so perhaps the easy way works for it
diana_coman: shinohai: ok, good luck
diana_coman: asciilifeform: mysql seems to try to pull in openssl (some of its deps) despite me specifying even same version of mysql I had hammered to work on the test server, ugh; this will be some fun, by the looks of it
asciilifeform waves to diana_coman
asciilifeform: so, lessee :
asciilifeform: diana_coman: do you remember how this gentoo was made ? in /etc/portage/package.mask/crapolade : there are banned pgkgs ;
asciilifeform: diana_coman: in /etc/portage/make.conf there are 'minused' gentooflags .
asciilifeform: diana_coman: ssl was not in the scope of either, if you had a custom ban, it was 100% your own work
asciilifeform: tho if you dun recall how you did it, dollars to doughnuts it was by putting a >=openssl-bannedverwhatever in 'crapolade' .
diana_coman: asciilifeform: I banned it specifically because otherwise it gets pulled in and conflicts with libressl
asciilifeform: right, so this was in your working piece but not in mine
diana_coman: asciilifeform: actually that is what I should do
asciilifeform: it's ~99% of the win from using gentoos, the fact that you can do this
diana_coman: ie so far I specifically masked it for dev-db/mysql but I should add it to crapolade
diana_coman: so it *did* help I complained here !
asciilifeform: crapolade perma-bans
asciilifeform: diana_coman: dun hesitate to complain even if re general operation of dulapgentoo and not concretely the given tar
asciilifeform: i might know the answ.
diana_coman: thanks!
asciilifeform: np.
asciilifeform: there are other packages you might haveto ban depending on what's being built. i cannot claim to have mapped out the entire known universe of liquishit.
asciilifeform: my orig ban concerned concretely poettering et al and their 'contributions'.
diana_coman: asciilifeform: sure; I *do* have my notes, but apparently at that time it was enough to ban it for mysql specifically ; possibly because other versions of the deps already installed or something (ie it's pulled in by a dep of mysql and it has MANY, ugh)
asciilifeform: fortunately i also -- have notes. but i used quite diff set of proggies , from smg's.
diana_coman: aha
diana_coman: I'll get to it, lots of stuff to compile and check still, ugh.
asciilifeform: re mysql, iirc BingoBoingo set up, worked, on rk.
asciilifeform: (rk is ~= this gentoo, but for arm64)
diana_coman: asciilifeform: well, I set *this versione exactly* on the test server so it has to work in the end.
asciilifeform: for that, put that ver in package.use
BingoBoingo: asciilifeform: Yes, just for a bloggatron on RockChip the secret MySQL sauce is some config (rather than compile) changes that keep it from eating all the ram.
asciilifeform: diana_coman: this forces concrete package.
diana_coman: I've just masked anything with higher version really
asciilifeform: the opposite of package.mask.
asciilifeform: that also worx.
asciilifeform: ( when you mask, it uses the latest permissible ver. )
asciilifeform: BingoBoingo: plz see if you can excavate the magick flag for mysql
asciilifeform tired and will go horizontal but will check here again before proper bed; bbl
diana_coman: asciilifeform: ah, shit; openssl is *installed* actually?
BingoBoingo: default-storage-engine = MyISAM is the MYSQL config flag to productively constrain MYSQL ram use on limited ram
BingoBoingo: << Lobbes guide to mysql on rockchip
asciilifeform: diana_coman: installed, nginx pulled in
asciilifeform: and curl
diana_coman: uhm, curl is not installed and precisely, I was setting up to install curl *without openssl"
asciilifeform genuinely bbl
diana_coman: but uhm, I thought the idea was no openssl really
asciilifeform: diana_coman: gentoo pulls tarballs from portage repos, and afaik cannot be installed w/out ~some~ sslism
asciilifeform: i have not experimented with alt-ssl's at the time of the writing of dulap-g.
diana_coman: hm; so only cuntoo is ssl-free?
asciilifeform: afaik
diana_coman: hm
asciilifeform: diana_coman: in principle possible to ban the pkg and then remake world. but i have not attempted.
asciilifeform: none of my proggies used sslism for anyffin. (i did not have trb on this dulap, and trb carries own ssl tarball)
diana_coman: given that I should have the servers up by tomorrow evening, I'd rather not rebuild world, hm
diana_coman: so I suppose I'll have to live with ssl for now at least.
asciilifeform: diana_coman: i expect you'll have >1 of these inexpensive boxen, from this can win ability to make constricted sets w/ rebuilt worlds etc. when time permits.
asciilifeform genuinely must bbl ; diana_coman et al plox to put in any q's re this item, in log, will answr. when i get back.
diana_coman: gn asciilifeform
diana_coman: fwiw going through the old notes re install on 1st smg server @pizarro (aka the production server), it turns out that indeed, I had to eselect python 2 so as to have python 2.7 as default.
thimbronion: diana_coman: how much time should I be spending on this review?
thimbronion: I'm at about 3 hours, but I'm not happy with it, and I'm running out of time.
diana_coman: thimbronion: that's the sort of question that you can answer best; what's wrong with it/why "not happy"?
diana_coman: thimbronion: the more important question is whether you see/know what you need to do to make it better; do you?
diana_coman: things are not to be measured by "time spent", at any rate.
diana_coman: thimbronion: better measure the time by return gained on spending it, really, if you are asking "should I spend more on it now?" ; in other words: if you see how to make it better so that another hour would make a significant improvement, then you should find that hour, yes; if onth you don't see how to make it better but you only see that it is broken, then you gain more by publishing it for
diana_coman: feedback (regardless of what "embarassment" might say otherwise)
diana_coman: asciilifeform: production eulora server is all running on local testbed!
whaack: diana_coman: grats re eulora! i published my interests post. also added pics to the Kyoto post and made a post for Seoul.
thimbronion: diana_coman: I don't see what to do to make it better.
thimbronion: diana_coman: I am going to publish with notes on where I see problems.

Random(ossasepia) | Download daily DB snapshot | Get Source Code