Conversation

Notices

1. Embed this notice
   :p: (p@bae.st)'s status on Monday, 08-Apr-2024 18:01:38 JST :p:
   It really bugs me how often ntpd produces slightly out of sync clocks by trying to be overly clever with skew and with trying to not break software that relies on a monotonically increasing clock. If something breaks when the clock fails to increase monotonically, it's shit, I don't care if it crashes. I'd rather it crash so that I know to uninstall it.
   
   So, I tried to do it "right" this time, but I am going with the strategy that works: run `ntpdate pool.ntp.org` after the net comes up and then periodically run it again from a cronjob. ntpd(1) has some warnings about how if you do it that way, you don't get the cool skew detection, and it should be the opposite
   
   In other news, `cargo` is a total piece of shit and this should come as no surprise to me because Rust is a language made by children that have no idea what they're doing but every time I have to interact with software written in Rust, the compiler and the tooling find new ways to disappoint me. I should just get a bunch of RISC-V gear so Rust shit won't run and I don't run into problems like this.
   boxesallinarow.png
   • Haelwenn /элвэн/ :triskell: and ✙ dcc :pedomustdie: :phear_slackware: like this.
   • Embed this notice
     :p: (p@bae.st)'s status on Monday, 08-Apr-2024 19:19:12 JST :p:

     in reply to

     • dobó istván
     @istvan I write Go so immunity to Go is a downside for me.
     ✙ dcc :pedomustdie: :phear_slackware: likes this.
   • Embed this notice
     dobó istván (istvan@noauthority.social)'s status on Monday, 08-Apr-2024 19:19:13 JST dobó istván

     in reply to

     @p I think POWER is similarly immune to rust. Also go.

   • Embed this notice
     :p: (p@bae.st)'s status on Wednesday, 10-Apr-2024 06:04:05 JST :p:

     in reply to

     • 𝚝𝚑𝚛𝚎𝚊𝚝@𝚜𝚑𝚒𝚝𝚙𝚘𝚜𝚝𝚎𝚛.𝚌𝚕𝚞𝚋
     @threat Bring it. I have wanted to punch Klabnik in the dick for at least 15 years.
     :blobancap: :blobcattrans: :blobancap: :blobcattrans: :blobancap: :blobcattrans: likes this.
   • Embed this notice
     𝚝𝚑𝚛𝚎𝚊𝚝@𝚜𝚑𝚒𝚝𝚙𝚘𝚜𝚝𝚎𝚛.𝚌𝚕𝚞𝚋 (threat@shitposter.world)'s status on Wednesday, 10-Apr-2024 06:04:06 JST 𝚝𝚑𝚛𝚎𝚊𝚝@𝚜𝚑𝚒𝚝𝚙𝚘𝚜𝚝𝚎𝚛.𝚌𝚕𝚞𝚋

     in reply to
     @p i'd love to see you in a cage match with steve klabnik.
   • Embed this notice
     :blobancap: :blobcattrans: :blobancap: :blobcattrans: :blobancap: :blobcattrans: (allison@hidamari.apartments)'s status on Wednesday, 10-Apr-2024 06:05:46 JST :blobancap: :blobcattrans: :blobancap: :blobcattrans: :blobancap: :blobcattrans:

     in reply to

     • dobó istván
     @istvan @p Does endianness matter? I have a Powermac G5 laying around but that can only run big-endian binaries. (I guess I can check Chimera's package search on the matter)
   • Embed this notice
     dobó istván (istvan@noauthority.social)'s status on Wednesday, 10-Apr-2024 06:05:47 JST dobó istván

     in reply to

     @p Looks like go has some support for ppc64, no ppc32

   • Embed this notice
     :blobancap: :blobcattrans: :blobancap: :blobcattrans: :blobancap: :blobcattrans: (allison@hidamari.apartments)'s status on Wednesday, 10-Apr-2024 06:06:41 JST :blobancap: :blobcattrans: :blobancap: :blobcattrans: :blobancap: :blobcattrans:

     in reply to

     • :blobancap: :blobcattrans: :blobancap: :blobcattrans: :blobancap: :blobcattrans:
     • dobó istván
     @istvan @p ... yeah, looks like it isn't packaged
   • Embed this notice
     Lina Inver?e (lina@eientei.org)'s status on Wednesday, 10-Apr-2024 06:36:31 JST Lina Inver?e

     in reply to

     • syzygy
     • 𝚝𝚑𝚛𝚎𝚊𝚝@𝚜𝚑𝚒𝚝𝚙𝚘𝚜𝚝𝚎𝚛.𝚌𝚕𝚞𝚋
     @syzygy @p @threat he has a face though
   • Embed this notice
     syzygy (syzygy@gh0st.live)'s status on Wednesday, 10-Apr-2024 06:36:32 JST syzygy

     in reply to

     • 𝚝𝚑𝚛𝚎𝚊𝚝@𝚜𝚑𝚒𝚝𝚙𝚘𝚜𝚝𝚎𝚛.𝚌𝚕𝚞𝚋
     @p @threat
     He has no dick, balls, or arse.
   • Embed this notice
     Lina Inver?e (lina@eientei.org)'s status on Wednesday, 10-Apr-2024 06:55:27 JST Lina Inver?e

     in reply to

     • syzygy
     • 𝚝𝚑𝚛𝚎𝚊𝚝@𝚜𝚑𝚒𝚝𝚙𝚘𝚜𝚝𝚎𝚛.𝚌𝚕𝚞𝚋
     @syzygy @p @threat and no grace
   • Embed this notice
     syzygy (syzygy@gh0st.live)'s status on Wednesday, 10-Apr-2024 06:55:28 JST syzygy

     in reply to

     • Lina Inver?e
     • 𝚝𝚑𝚛𝚎𝚊𝚝@𝚜𝚑𝚒𝚝𝚙𝚘𝚜𝚝𝚎𝚛.𝚌𝚕𝚞𝚋
     @lina @p @threat
     He has no style.
     Lina Inver?e likes this.
   • Embed this notice
     Lina Inver?e (lina@eientei.org)'s status on Wednesday, 10-Apr-2024 07:26:48 JST Lina Inver?e

     in reply to

     • syzygy
     • 𝚝𝚑𝚛𝚎𝚊𝚝@𝚜𝚑𝚒𝚝𝚙𝚘𝚜𝚝𝚎𝚛.𝚌𝚕𝚞𝚋
     @threat @p @syzygy this dev
     is a fucking disgrace
   • Embed this notice
     𝚝𝚑𝚛𝚎𝚊𝚝@𝚜𝚑𝚒𝚝𝚙𝚘𝚜𝚝𝚎𝚛.𝚌𝚕𝚞𝚋 (threat@shitposter.world)'s status on Wednesday, 10-Apr-2024 07:26:49 JST 𝚝𝚑𝚛𝚎𝚊𝚝@𝚜𝚑𝚒𝚝𝚙𝚘𝚜𝚝𝚎𝚛.𝚌𝚕𝚞𝚋

     in reply to

     • Lina Inver?e
     • syzygy
     @lina @p @syzygy most closet-antifa do not maintain grace, only milkshake
     Lina Inver?e likes this.
   • Embed this notice
     :p: (p@bae.st)'s status on Wednesday, 10-Apr-2024 08:43:42 JST :p:

     in reply to

     • Lina Inver?e
     • syzygy
     • 𝚝𝚑𝚛𝚎𝚊𝚝@𝚜𝚑𝚒𝚝𝚙𝚘𝚜𝚝𝚎𝚛.𝚌𝚕𝚞𝚋
     @lina @syzygy @threat He has to.
     youmustwearaface.png
     Haelwenn /элвэн/ :triskell: and Lina Inver?e like this.
   • Embed this notice
     syzygy (syzygy@gh0st.live)'s status on Wednesday, 10-Apr-2024 08:45:37 JST syzygy

     in reply to
     @p
     I used ntpd on a laptop and it sucked ballz.
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Wednesday, 10-Apr-2024 08:45:37 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • syzygy
     @syzygy @p Yeah on a laptop you probably want something like chrony. (In fact it's what I put everywhere)
   • Embed this notice
     dobó istván (istvan@noauthority.social)'s status on Wednesday, 10-Apr-2024 08:47:48 JST dobó istván

     in reply to

     • :blobancap: :blobcattrans: :blobancap: :blobcattrans: :blobancap: :blobcattrans:

     @p @allison Mostly.

     Some POWER chips can do LE.

     https://lwn.net/Articles/408845/

   • Embed this notice
     :p: (p@bae.st)'s status on Wednesday, 10-Apr-2024 08:47:48 JST :p:

     in reply to

     • :blobancap: :blobcattrans: :blobancap: :blobcattrans: :blobancap: :blobcattrans:
     • dobó istván
     @istvan @allison Oh, holy shit. I remember that kernel option to swap the framebuffer's endianness, I bet it was for avoiding running the whole box with the endianness swapped.
     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     :p: (p@bae.st)'s status on Wednesday, 10-Apr-2024 08:47:49 JST :p:

     in reply to

     • :blobancap: :blobcattrans: :blobancap: :blobcattrans: :blobancap: :blobcattrans:
     • dobó istván
     @allison @istvan Yeah, ARM can hop endianness, but I think it's the only one, PowerPC is all BE. (I am going from memory, this may be lies.)
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Wednesday, 10-Apr-2024 08:52:07 JST Haelwenn /элвэн/ :triskell:

     in reply to
     @p Like cargo just thinks REALTIME should only ever increase similarly to MONOTONIC?
     Shit really ought to crash, although I could see that causing cases of data corruption.
   • Embed this notice
     :p: (p@bae.st)'s status on Wednesday, 10-Apr-2024 08:57:47 JST :p:

     in reply to

     • Haelwenn /элвэн/ :triskell:
     • syzygy
     @lanodan @syzygy Holy shit, I never used it but it looks like it behaves exactly the way I wish ntpd would behave.
     
     Meanwhile, ntpd is...I don't know what it's doing, it appears to be making drift *worse*:
     meanwhile_ntpd.png
     Haelwenn /элвэн/ :triskell: and ✙ dcc :pedomustdie: :phear_slackware: like this.
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Wednesday, 10-Apr-2024 09:05:13 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • syzygy

     @p @syzygy I think by default chrony sets the clock at launch and then drifts.

     At least if I'm reading the manpage right, here with makestep 0.1 3 (which is given in the manpage, hence my guess of me not modifying the config) it adjusts by steps of 0.1 seconds unless it's bigger than 3 seconds.

   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Wednesday, 10-Apr-2024 09:18:55 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • Haelwenn /элвэн/ :triskell:
     • syzygy
     @p @syzygy Which I'd say is the correct behavior, 3s being RTC drift over quite a long period of time, more than that and your clock is likely entirely off.
   • Embed this notice
     :p: (p@bae.st)'s status on Wednesday, 10-Apr-2024 10:02:42 JST :p:

     in reply to

     • syzygy
     • 𝚝𝚑𝚛𝚎𝚊𝚝@𝚜𝚑𝚒𝚝𝚙𝚘𝚜𝚝𝚎𝚛.𝚌𝚕𝚞𝚋
     @syzygy @threat
     itistrue.gif
     ✙ dcc :pedomustdie: :phear_slackware: likes this.
   • Embed this notice
     ✙ dcc :pedomustdie: :phear_slackware: (dcc@annihilation.social)'s status on Wednesday, 10-Apr-2024 10:07:47 JST ✙ dcc :pedomustdie: :phear_slackware:

     in reply to

     • :blobancap: :blobcattrans: :blobancap: :blobcattrans: :blobancap: :blobcattrans:
     • dobó istván
     @p @allison @istvan I think we are all eating :nixon_smug:
   • Embed this notice
     :p: (p@bae.st)'s status on Wednesday, 10-Apr-2024 14:05:49 JST :p:

     in reply to

     • Haelwenn /элвэн/ :triskell:
     • syzygy
     @lanodan @syzygy
     
     > I think by default chrony sets the clock at launch and then drifts.
     
     Yep, this is what the docs indicate, this is exactly the behavior I want (and apparently they use the ethernet hardware timestamps). ntpd tries to guess at and anticipate drift and then jump to the target time in 250ms increments. As far as I can tell, it has never done that correctly, or those clocks would get *closer* together rather than one of them speeding up and one slowing down.
     
     > it adjusts by steps of 0.1 seconds unless it's bigger than 3 seconds.
     
     Yeah, reasonable.
     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     :p: (p@bae.st)'s status on Wednesday, 10-Apr-2024 14:11:10 JST :p:

     in reply to

     • Lina Inver?e
     • syzygy
     • 𝚝𝚑𝚛𝚎𝚊𝚝@𝚜𝚑𝚒𝚝𝚙𝚘𝚜𝚝𝚎𝚛.𝚌𝚕𝚞𝚋
     @threat @lina @syzygy
     facesemotions.jpg
     ✙ dcc :pedomustdie: :phear_slackware: likes this.
   • Embed this notice
     𝚝𝚑𝚛𝚎𝚊𝚝@𝚜𝚑𝚒𝚝𝚙𝚘𝚜𝚝𝚎𝚛.𝚌𝚕𝚞𝚋 (threat@shitposter.world)'s status on Wednesday, 10-Apr-2024 14:11:11 JST 𝚝𝚑𝚛𝚎𝚊𝚝@𝚜𝚑𝚒𝚝𝚙𝚘𝚜𝚝𝚎𝚛.𝚌𝚕𝚞𝚋

     in reply to

     • Lina Inver?e
     • syzygy
     @p @lina @syzygy
   • Embed this notice
     :marseyloadingneon: m0xEE :marseyloading: (m0xee@breloma.m0xee.net)'s status on Saturday, 13-Apr-2024 05:53:32 JST :marseyloadingneon: m0xEE :marseyloading:

     in reply to

     • :blobancap: :blobcattrans: :blobancap: :blobcattrans: :blobancap: :blobcattrans:
     • dobó istván
     @p
     No, your memory deceives you. Newer PowerPCs are little-endian — and that is the architecture still supported by a lot of distros, unlike BE.
     64 PowerPC CPUs could switch endian-ness too: https://en.wikipedia.org/wiki/PowerPC#Endian_modes
     That G5 just doesn't support it, at least I've never seen it done on real hardware and doing so would be trouble anyway as old Apple's OpenFirmware surely doesn't support that.
     ppc64le is even supported by the reference Go toolchain, again, unlike BE — which is supported by gccgo though, but there's little use in it as most modules do not support that anyway and you'd have to do a lot of work porting those too. I think I've even succeeded building gccgo for 32-bit PowerPC, which is no longer possible as it looks like some definitions got removed from gcc's source. You can in theory add those back of course, but like I already said — there'd be little use in it as most modules won't work as is anyway.
     
     Unlike Rust BTW! Which works on nearly anything and the kitchen sink, here's the machine this instance runs on. And it's probably a relatively recent version even.
     I'm not even that sure that RISC-V machines aren't supported — they are probably worse supported than more mainstream architectures and have a similar problem — even more mainstream modules won't work. I have this problem on PowerPC too, e.g. ring is a pretty popular cryptography crate, but it can't even be built as is. IBM made a series of patches so it's possible for ppc64le and with a little effort I could make it build on this 32-bit machine even, but autotests still fail — looks like there are more underlying issues. I originally started these effort with intent to host libreddit — but as Reddit went to shit anyway, I've just given up :marseyshrug:
     
     @allison @istvan
     :blobancap: :blobcattrans: :blobancap: :blobcattrans: :blobancap: :blobcattrans: likes this.
   • Embed this notice
     :p: (p@bae.st)'s status on Wednesday, 17-Apr-2024 06:38:16 JST :p:

     in reply to

     • :blobancap: :blobcattrans: :blobancap: :blobcattrans: :blobancap: :blobcattrans:
     • :marseyloadingneon: m0xEE :marseyloading:
     • dobó istván
     @m0xEE @allison @istvan
     
     > Newer PowerPCs are little-endian
     
     Yeah, that is fuckin' weird. @istvan just pointed that out.
     
     > they are probably worse supported than more mainstream architectures
     
     I am running regular-ass Slackware on my RISC-V chip and basically everything works. Less hassle than ARM, even, which surprised me: you'd think ARM would be ironed out in current year, or at least in a nicer state than RISC-V.
     ✙ dcc :pedomustdie: :phear_slackware: likes this.