𝙼𝚘𝚒𝚗𝚁

Network and System Admin|FreeBSD Doc/Ports Committer|Conference hopper|Open to short-term/long-term/full-time REMOTE contracts/gigs

[Warner Losh @bsdimp]

Dear #FreeBSD and #Qemu community... I am trying to organize a school visit in Munich Germany for next week. I have reached the end of other options and am looking for someone in or around Munich that might help me. Please DM if you can help. Thanks!

[𝙼𝚘𝚒𝚗𝚁 @5u623l20]

The time of the year when there is a new #FreeBSD release and I am not excited and there is no action needed from my side.

[𝙼𝚘𝚒𝚗𝚁 @5u623l20]

@ngortheone I like to do anything that is challenging. Sysadmin skills are my bread and butter. And I don’t know why whenever I went outside C all other languages just didn’t make any sense to me. Refreshing my Lua knowledge is the next target as we have that in FreeBSD base now.

[𝙼𝚘𝚒𝚗𝚁 @5u623l20]

Trying to find a new hobby in the #FreeBSD world

[𝙼𝚘𝚒𝚗𝚁 @5u623l20]

@klarainc The question I often get is why can’t modload a linux kernel into FreeBSD ? 🤣

[𝙼𝚘𝚒𝚗𝚁 @5u623l20]

@DLangille Oh that’s in the https://t.co/Wxvp6EXsrs hook. We don’t need that hence didn’t implement it therebut should be fairly easy

[𝙼𝚘𝚒𝚗𝚁 @5u623l20]

@DLangille It’s in poudriere repo. Check the file etc/poudriere.d/hooks/bulk.sh.sample. I was the one who added the support there.

[𝙼𝚘𝚒𝚗𝚁 @5u623l20]

@gbergling Those cannot be ordered. Those are only available during the RIPE Meetings or the Regional Internet Registry meetings sometimes operated under the jurisdiction of RIPE regions.

[𝙼𝚘𝚒𝚗𝚁 @5u623l20]

#FreeBSD at #ripe 87. Feel free to knock me if you want to discuss anything about FreeBSD

[𝙼𝚘𝚒𝚗𝚁 @5u623l20]

Hi everyone I am up for a new challenge again and looking forward for long/short term remote/hybrid contracts on #freebsd or #Automation or #networking

[𝙼𝚘𝚒𝚗𝚁 @5u623l20]

@Tatuze2 @vermaden @kaevans91 @Xxvalen Now on another note normally FreeBSD maintains the compatibility during the lifetime of a major version but I just don'e know exactly what are failing to build or work on 13.2 that builds on 13.1. But entirely the work is not as easy as it seems to be for now.

[𝙼𝚘𝚒𝚗𝚁 @5u623l20]

@Tatuze2 @vermaden @kaevans91 @Xxvalen We have multiple major versions of supported release and different versions has multiple architectures. So how does a host know where to pull the pkg from? If you look into pkg.conf you will see a variable named ABI is expanded which results to something like FreeBSD:12:amd64.

[𝙼𝚘𝚒𝚗𝚁 @5u623l20]

@Tatuze2 @vermaden @kaevans91 @Xxvalen Now on the other hand as we never put minor versions in this tag there is no easy way for a web server to distinguish whether a 13.1 is asking for resources or a 13.2 is asking for resources. Hence we cannot serve the files.

[𝙼𝚘𝚒𝚗𝚁 @5u623l20]

@Tatuze2 @vermaden @kaevans91 @Xxvalen Or FreeBSD:13:aarch64. This is also set in our web server configuration and that's how the web server knows where to serve the file from.

[𝙼𝚘𝚒𝚗𝚁 @5u623l20]

@vermaden @kaevans91 @Xxvalen The underlying problem is not tiny itself. We will need to rewrite pkg. If you try to search a plg meta info you will see that plg has FreeBSD:13:amd64 which is the ABI. Currently there is mo easy way to fix this.

[𝙼𝚘𝚒𝚗𝚁 @5u623l20]

@incin200 So far the plan is backporting patches to avoid POLA.

[𝙼𝚘𝚒𝚗𝚁 @5u623l20]

@dgoodkin Fixing ports that fails with llvm16

[𝙼𝚘𝚒𝚗𝚁 @5u623l20]

@WaqarSaaS ok