600+ entries in 0.173s
: so back to the bsd-side-quest.... i built `coreutils 8.21' on my openbsd
box. now have `gdd` on there. which has a 'fullblock' iflag.
: i went back to my linux output entropy files to see about the 'ff fd' thing; I'm really jammed up on openbsd
. and that's a different side-quest we can discuss later. but now i'm wondering about the flow-control/output from collections done on linux
: I haven't gotten openbsd
to do quite what I want yet, even with the -crtscts flag set for stty.
<< ah. good find. that's almost certainly the culprit on openbsd
. but god help anyone try to find ~only one~ such snag on the flaming shitpit that is macosx. *spits*. stty dun even pretend to work in 'terminal' because it doesn't talk to serial devices. at all. no luck yet with coolterm, quickterm, etc. either. they just... freeze. ☝︎
does not know, because his only openbsd
box has a couplea cm of dust on it, and also lacks usb ports
: i was actually reading through `dd` (openbsd
) impl yesterday.. -.-
: asciilifeform: yup. just, openbsd
with the config I was talking about yesterday didn't hit that. im sure it's just something on the openbsd
side, ie. my configuration.
: ALSO, forgot to mention, that openbsd
`dd` doesn't have a 'fullblock' iflag or whatever, so that needs to be looked at a bit too
: on macppc openbsd
6,1 using stty. and maybe i will check my wiring!
: Logged on 2017-05-30 04:38 pete_dushenski: mod6: openbsd
commands worked! thx muchly. though i'm still getting crazy low bitrates with fg. consistently under 1000b/sec and some runs as low as 100b/sec.
: mod6: openbsd
commands worked! thx muchly. though i'm still getting crazy low bitrates with fg. consistently under 1000b/sec and some runs as low as 100b/sec. ☟︎
: anyway, incase anyone cares, on openbsd
once I connect my FG via USB-TTL, i was able to use device 'cuaU0' to read from the FG:
: and do that like on a bunch of different environments; gentoo, ubuntu 12/14/16, freebsd recent, openbsd
(old?) and recent, deb 7 & 8, osx whatever versions
: looks like mircea_popescu was quite right to tune out openbsd
when he had.
: but what i was actually going to say, is that openbsd
disks apparently weren't pressed. it seems like theo de raadt has been burning them by hand up until now
: i may give some other boxen a try here at some point too. got a handfull of gentoo boxes, freebsd, openbsd
: danielpbarron: hey, did you ever figure out whatever with your openbsd
deed you were trying to do?
: on a related note, which openbsd
cds are specifically wanted? i did 5.5 cd1 because i have that pack opened already, and because the more useful cd2 (containing amd64) got damaged when i tried to remove it from one of my iMac G3s that wouldn't spit it back out (it also has ppc -- probably the arch of interest)
: 'Only two remote holes in the default install, in a heck of a long time!' -- openbsd
: says openbsd
in a "jesus fish" that's redesigned to look like a rocket
: i was about to refresh my openbsd
version and discovered that openbsd
no longer make/sell a 3-cd set. end of an era
: i've been browsing the web using dillo/netserf from openbsd
box and realized just how broken it become compared to even 5 years ago. only places that you can still render on old browser are the backalleys. uncle al style homepages, tmsr, *chans
: we discussed this for trb openbsd
: it's the same with openbsd
's ports, netbsd pkgsrc, mac's homebrew, etc.
: i also got OpenBSD
on iMac G3 and G5 but they aren't as nice. the G3 i gave up before getting a windows manager, and the G5 has too-new hardware that assumes you run OSX or whatever, the most annoying of which being the fan that defaults to full-throttle unless told to slow down
: microshit's sponsorship did not ~immediately~ turn openbsd
to liquishit, but it is foolish to expect that it can withstand infinitely many years of it with 0 symptoms
: Logged on 2016-06-20 18:40 trinque: I'm clutching to hand-compiled driftwood on openbsd
: i've taken an interest in openbsd
on powerpc and found there are folks here doing just that
: and i thought my openbsd
'libretto' that loses its x11 frame buffer was rotten
: i just opened an openbsd
laptop a second ago and it greeted me with ddb (kernel debugger on panic)
: from what phf has described ( and from my own experiments ) it is not clear to me that openbsd
is salvageable .
: if you're going to try crosscompiling things from one openbsd
machine to your older ppc boxes make sure you have the right os versions set. the abi changes, and that bit me a few times
settles quite nicely onto old macs
: i'm trying to figure out why genera's x client is crashing openbsd
x server. but once i do i'll try the chip
: i ended up running openbsd
on that box
: ben_vulpes: i've spent the last couple evenings since ppc thread re-emerged trying to run openbsd
6 on macppc. can't get the bloody machine to recognise cdrom OR usb. open firmware, boot screen, etc nada zilch zip.
: ben_vulpes: openbsd
's package for the thing is neutered to use the system
: for every theo de raadt where you could argue some kind of "openbsd
vs tmsr", there's thousands of potentially useful folks who waste their time with "job" and "side projects", that never amount to anything
: and in fact, meanwhile found that it was my own build environment hauling in libressl on openbsd
: <+ben_vulpes> make macs great again <+ben_vulpes> install openbsd
on them << :D
: asciilifeform: consider our conversation about the openbsd
patches in another castle
: to briefly revisit upstack, linux as we have it now is a direly and fatally centralized, in the worst possible sense, item: to the extent it runs on in-production iron at all, it is because some stingy but present support exists from the vendors, and from the megaconglomerates (rathead et al). if withdrawn, linux turns into openbsd
: point being it may not be unreasonable system tuning work to modify the build process of packages; what openbsd
has is quite close to having portage feature parity
: it didn't take me longer than 5min to copy the openbsd
emacs makefile and remove everything I didn't want
: to briefly revisit my actual complaint re openbsd
-- if i want emacs but NOT dbus, i am reduced to, more or less, 'make own unix', rather than using openbsd
: I have still on my disk a semi-working portage on openbsd
: i soured almost totally on openbsd
when i labouriously set up a box, with all of the proggies i rely on for daily use, and found that emacs COULD NOT be de-poetteringized without eschewing the ports system entirely
: (rather like what happened to openbsd
-- d00d gets tired, 'eager young thing' steps up)
: windows for a longest time had a very stable abi, as per "you can run windows 95 programs still!1", where's i suspect mac os x probably doesn't. it's the same problem on openbsd
, sure you can static link, but you will have to recompile after the next release.
: One could say same about OpenBSD
except their mp (Theo) was and stayed poor and stooges (Bob Beck) rallied to gatekeeper and treasury positions
: it is of the same type as the openbsd
compiling for vaxen
: certainly noted! assumed as much :) includes increased pessimism for funding OS projects (such as openbsd
) etc i guess...
: i remember the openbsd
thing but not the blender one
: other than the openbsd
turpitude you may recall the blender idiocy etc.
: asciilifeform: I moved portage over to openbsd
(which had been done once before by another) only to decide the thing had gotten far too complicated.
: Logged on 2016-12-08 02:13 danielpbarron: come to think of it, that probablem happened with openbsd
on a powerpc using firefox
: come to think of it, that probablem happened with openbsd
on a powerpc using firefox ☟︎
: it's a glibc2 variant, i wonder what openbsd
: asciilifeform: that's a good question, i haven't isolated the bug, but i'm pretty sure on openbsd
crashes instantaneously. note that c++ threads are involved, so perhaps they try to initialize things even before you start using them?
: researching the problem i came across a lot of "my static linked openbsd
program just crashes! ... ... -lpthread ... ...", but also a handful of linux ones
: phf: lemme get this straight, ~all~ pthread proggies hosed on openbsd
: i think it only manifests on openbsd
: 'of note, previously static compilation on OpenBSD
resulted in segmentation fault. this is due to libpthread not being fully linked into the final static binary...' << what did this dig lead to , phf ?
: So a venture called "Smartisan" was this year's late donor "saving" Openbsd
: ben_vulpes: asciilifeform: neat, so the pill has worked on alf-linux, os x, and openbsd
at this point?
: ben_vulpes: I'd rather freeze an openbsd
and steal portage from gentoo
: on openbsd
for example, /usr contains things shipped with the release. anything installed from ports is in /usr/local .
: newer gdb worked great. I'll now write up my notes, did all this from openbsd
: asciilifeform: "cu" on openbsd
seems pretty minimalistic, dunno if it meets your requirements.
has a proper static file dev
: what does openbsd
future look without you know, "that guy who didn't save it before microsoft" ?
: I went to mount an encrypted openbsd
drive on a different (same endian) arch
: BingoBoingo: are you running the openbsd
: ben_vulpes: Restart every few weeks to back up blockchain. Is not trb, but other on Openbsd
with trb shit bolted onto sides
: there was some old obscure reason why we ditched openbsd
. i think it was driver support on that backup gardget
: hoose to use corporate-maintained tools like OpenSSL, which are deeply compromised. Do you think the people responsible for HeartBleed were held accountable, and fundamental changes were made? Guess again. It’s simply ignored by most of Linux. (You’ll notice real UNIXes like OpenBSD
did not ignore it and have begun serious changes. Yet even there, it took such a serious, obvious exploit for them to see the engineering problem.)'