We had a great session on #OpenScience Education. Excellent impulse statements and a very active audience, fantastic. Thank you! We will summarise the results later and publish them on Zenodo. #EOSCsymposium24 #OSC2024

@tamaraheck, @GuidoScherp and Verena Weimer organise a session on "Bringing Open Science into action: The role of educating young researchers" as part of the #EOSCsymposium24 #OSC2024 cooperation. Three recognised experts will give impulse statements on the topic:
๐Ÿ‘‰ Julia Pries-Buchheit, Kiel University
๐Ÿ‘‰ Maura Burke, Utrecht University
๐Ÿ‘‰ @HelenClare, Jisc

In case you have a ticket (on-site/online), join us! ๐Ÿ˜Š
๐Ÿ—“ Wednesday, 23.10.24, 11:00 โ€“ 12:30 (CEST)

More info:
๐Ÿ‘‰ https://indico.cern.ch/event/1408259/timetable/?layout=room#b-563355-zbw-open-science-sess

EOSC Symposium 2024

Indico
The #opensuse board meeting is happening now. #osc2024
@wombelix talking about using #Neuvector with a pipeline for vulnerability scanning in #aws codepipeline. #osc2024 #oSC24 #opensuse conference.
On my way to the #osc2024 #openSUSE conference. Looking forward to a day full of talks and nice people...

#FediHelp-Frage zur #oSC2024:

Treffe ich da jemande*n, mit der*m ich mir mal angucken kann, wie man angepasste Images von #openSUSE Tumbleweed oder #MicroOS baut? Am Besten so, dass sie mit den systemd-A/B-Images kompatibel sind.

Irgendwie mit Kiwi oder sowas oder so...

So mal am Rande ne Stunde zusammensetzen wรคre super. Please ping me!

I just registered for #osc2024.

Unfortunately, I could not submit a talk due to lack of replies to questions regarding the CfP from the conference organisers, but at least I found a way to attend!

See you in Nuremberg!

#opensuse

๐Ÿ•’ Solve the #Y2038 problem with #openSUSE! 64-bit systems with 32-bit compatibility still face issues due to specific #data structures. See how we are ensuring systems are future-proof. #oSC2024 #Y2038 https://events.opensuse.org/conferences/oSC24/program/proposals/4578
Y2038: utmp, wtmp and lastlog

The year 2038 problem (also known as Y2038) is a time formatting bug on Unix systems with representing times after 03:14:07 UTC on 19 January 2038. This happens with a 32bit time_t, not with a 64bit time_t. The general statement so far has always been that on 64bit systems with a 64bit time_t you are safe with respect to the Y2038 problem. But this isn't correct: on bi-arch systems like x86-64 (so which can execute 64bit and 32bit binaries) glibc defines __WORDSIZE_TIME64_COMPAT32, which leads to the fact, that struct utmp (used for utmp, wtmp and btmp) and struct lastlog uses int32_t instead of time_t. So we have a Y2038 problem, which is not easy fixable, as this would require ABI and on disk format changes. In this talk I will speak about the background, which tools are affected and how we solved that in openSUSE by dropping utmp, wtmp, btmp and lastlog completely and make use of systemd-logind and other tools instead.

openSUSE Events

The registration for the EOSC Symposium 2024 (in cooperation with the Open Science Conference) is now open! Expect a thought-provoking programme with twenty-six sessions, including six unconferences.
#EOSCsymposium24 ๐Ÿค #OSC2024

๐Ÿ“… October 21-23, 2024, Berlin or online
๐Ÿ‘‰ Register here: https://eosc.eu/symposium2024/#registration

EOSC Symposium 2024: Berlin - EOSC Association

Online participation is still open, but in-person attendance is sold out and the waiting list is closed.

EOSC Association