Human_G33k | the website certificate is outdated or its just me ? | 04:14 |
---|---|---|
tuxd3v | expires on : 31 July 2020 | 04:16 |
tuxd3v | almost there but not so :) | 04:16 |
Human_G33k | for me it says outaded 01/03/2020. | 04:18 |
Human_G33k | strange | 04:18 |
tuxd3v | humm, you are talking about what domain? | 04:20 |
Human_G33k | you change the server ip ? | 04:21 |
Human_G33k | i use a custom host file fore my network tests (when no dns for ie) | 04:22 |
Human_G33k | with the good ip it s look good | 04:22 |
Human_G33k | but website can also access with the old one ip | 04:22 |
tuxd3v | I am not sure but here I looked into devuan.org:54.36.142.179 | 04:23 |
Human_G33k | me too now | 04:23 |
Human_G33k | old one was 46.105.191.76 | 04:23 |
tuxd3v | check your date :) | 04:24 |
Human_G33k | my date is good as i say i have a static entry in my hosts file | 04:24 |
tuxd3v | it could be that its outdated in some server, I believe its round drobin :) | 04:24 |
tuxd3v | drobin -> robin | 04:25 |
Human_G33k | ok | 04:25 |
ullet | i think i'm too retarded to build devuan for VIM3 tuxd3v :/ | 11:28 |
ullet | but i might be able to live convert debian to devuan again | 11:28 |
ullet | that worked on jetson nano | 11:29 |
ullet | where did .dtbs come from anyway. who keeps inventing this new stuff we don't need. | 11:30 |
ShorTie | they are part of the kernel | 12:58 |
ullet | since when | 12:59 |
ShorTie | Sorry, have no idea on exact date | 12:59 |
ShorTie | i know of them in 4.9.y, for arm atleast | 13:00 |
ullet | ~ 2009 | 13:01 |
ullet | http://lkml.iu.edu/hypermail/linux/kernel/0905.3/01942.html | 13:02 |
ShorTie | you just need a kernel | 13:17 |
ShorTie | a compiled kernel would be the nicest | 13:17 |
ShorTie | i use the raspberry pi arm64 compiled kernel with Devuan | 13:18 |
ullet | not saying it's a bad idea. just a new thing that means i can't upgrade kernel | 13:18 |
ShorTie | why you say that ?? | 13:19 |
ShorTie | it is an extra step when compiling a kernel to make them | 13:20 |
ShorTie | they do not just automagically appear | 13:21 |
ullet | well i have no .dtb for jetson nano | 13:23 |
ullet | not for newer kernel | 13:23 |
ullet | i am stuck with nvidia's | 13:23 |
ullet | and i have no .dtb for khadas vim3 | 13:24 |
ShorTie | guess nvidia does use/need them, but arm does | 13:32 |
ShorTie | i'd guess you just need a working kernel && u-boot, the rest is just a debootstrap | 13:33 |
ShorTie | debootstrap doesn't do the kernel | 13:34 |
ShorTie | so you can add any you want | 13:34 |
ullet | ty | 13:35 |
ShorTie | if you can grab someones deb, it makes it easy | 13:35 |
ShorTie | looks like a nifty board, you got 1 yet ?? | 13:42 |
ullet | yes ShorTie | 14:54 |
onefang | Something is wrong. Seriously wrong. My computers have been up for over two months. | 19:16 |
onefang | I suspect Debian isn't providing kernel updates for Stretch anymore, except for the backported 4.19. So my ASCII installs are not getting rebooted when there is a new kernel. | 19:17 |
onefang | Anyone tried the backported linux-image-amd64 4.19+105+deb10u3~bpo9+1 kernel on ASCII? Any problems? | 19:18 |
gnarface | it might be time to consider beowulf if you need continued kernel updates. i don't think that stretch is getting less attention is a surprise to anyone. i haven't tried building it myself though. | 19:22 |
gnarface | it might work but there's some question as to whether it's worth the risk | 19:23 |
gnarface | no wait, scratch that | 19:23 |
gnarface | it will probably work | 19:23 |
gnarface | i just remembered i did build 5.2 or 5.3 for ascii on arm64 | 19:23 |
gnarface | but there's still a question as to whether it's worth it | 19:23 |
gnarface | i guess the key info is i didn't build it on ascii. i built it on ceres and then tested it on ascii, beowulf and ceres. | 19:28 |
gnarface | so that should work but you're still off the rails at that point | 19:29 |
gnarface | (for arm64 there's no other choice though) | 19:29 |
gnarface | (note arm64 as in aarch64, not amd64, to be clear) | 19:30 |
onefang | Since this involves some servers, one of which is a Devuan mirror, as well as my main desktop, I tend to be conservative and stick with what's very stable. I wasn't planning on upgrading to Beowulf until later this year, after lots of testing. Think I'll stick with that plan. | 19:46 |
onefang | Just the lack of updated kernels got noticable. | 19:47 |
gnarface | yea, it's oldstable though so that's fairly expected | 19:50 |
gnarface | and it should be considered a risk, but if it's just a mirror then maybe your attack surface is low enough for it not to matter | 19:51 |
onefang | Not just a mirror. I run two virtual worlds on it, and a secure chat server for local activists. | 19:52 |
gnarface | er hmm. i'm changing my advice then. build the new kernels. | 19:53 |
gnarface | hopefully at least your hardware is uniform enough that you don't have to build a different kernel for every server | 19:54 |
onefang | Alas a mixture of Intel and AMD. | 19:55 |
gnarface | bummer | 19:55 |
gnarface | though that alone might not be enough for you to need different kernels | 19:55 |
gnarface | i don't know what you have over there exactly | 19:55 |
gnarface | on the plus side you can probably make the kernels significantly smaller in the process | 19:57 |
onefang | I don't really want the extra maintenance burden of compiling my own kernels. I sometimes do that for a living, but then people are paying me to. B-) | 19:58 |
gnarface | well, this too can be automated... | 20:03 |
gnarface | i don't have any better advice sorry. life is full of touch choices. in theory someone else might be providing 3rd party kernels that would fit the bill but i really wouldn't recommend going that way either. | 20:07 |
gnarface | *tough choices | 20:07 |
gnarface | onefang: for whatever it's worth i have a beowulf amd64 system here and it has been up for weeks with no problems so far. seems completely stable as long as i don't try to sleep it. | 20:12 |
gnarface | the "beta-ness" seems mostly to do with the upgrade process, but i didn't experience anything worse than a typical ceres upgrade | 20:13 |
onefang | Yep, lots of people with stable Beowulfs running, which is why it'll likely actually get fully released any day / week now. Only a few issues to sort out I believe. | 20:13 |
ullet | i find sid/beowulf caused me less problems than older ones | 20:15 |
_abc_ | slightly defocus but... a smart guy's comments on systemd in several articles, search systemd in page https://utcc.utoronto.ca/~cks/space/blog/__Index | 20:16 |
_abc_ | I wonder if Chris Siebenmann is aware of devuan.org | 20:31 |
_abc_ | To me he sounds like someone we would like to have on board here. At least I would. | 20:32 |
tuxd3v | does anyone notice the level of compression of xz in beowulf, or its just me? | 21:42 |
tuxd3v | maybe improvments compared with the version in ascii | 21:43 |
gnarface | tuxd3v: didn't notice but also wasn't paying attention... you sure it's not just a change to the default? | 22:10 |
gnarface | tuxd3v: (default compression level mentioned in the man page for xz is -6 but i note that tar can inherit a different value for that through an environment variable) | 22:12 |
tuxd3v | gnarface, it could be, yes 6 is a value greatly used for compression but I was astinished by a xz compression done on beowulf..usually they tended to be around ~400MB is ascii, and I got a ~250MB compressed file. | 22:20 |
tuxd3v | astinished -> astonished | 22:20 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!