Red Hat, Fedora, and More
-
IT leadership: Seven spectrums of choice for CIOs in 2023 | The Enterprisers Project
Three years ago, the pandemic disrupted where and how people worked, forever changing the traditional workplace. Today, leaders are grappling with questions about how to move forward – when to return to the office, what work looks like today, and how to prepare for the future.
These questions and more are addressed in the new book Office Shock. It discusses why it’s necessary to use future-back thinking to anticipate directions of change, identifies spectrums of choices to guide decision making, and explores how to plan for more sustainable ways of working.
-
3 tips to land an IT role without a tech background | The Enterprisers Project
By 2025, nearly 70 percent of employees will be expected to use data at some level in their jobs, compared to 40 percent in 2018. That expectation, combined with the ongoing shortage of skilled tech talent, will force organizations to start considering nontraditional candidates – including those who might lack formal education or a degree but are eager to learn and grow.
As the Chief Operating Officer of a company with a mission to empower the world through data literacy, I’ve witnessed firsthand the exceptional talent individuals from all backgrounds bring to the workplace. Rather than looking at formal education as an indicator of success, focusing on candidates’ aptitude, willingness to learn, and data literacy skills will help lay a foundation for the future of the IT workforce.
-
3 new improvements to the RHEL download experience | Red Hat Developer
In today's age of hyperscalers and hybrid cloud environments, developers like you need to obtain the appropriate Red Hat Enterprise Linux (RHEL) image based on the desired deployment destination. Developers want choices for their download experience. We are excited to introduce three new options that improve the traditional experience of downloading a RHEL ISO image.
-
Fedora's tempest in a stack frame [LWN.net]
It is rare to see an extensive and unhappy discussion over the selection of compiler options used to build a distribution, but it does happen. A case in point is the debate over whether Fedora should be built with frame pointers or not. It comes down to a tradeoff between a performance loss on current systems and hopes for gains that exceed that loss in the future — and some disagreements over how these decisions should be made within the Fedora community.
A stack frame contains information relevant to a function call in a running program; this includes the return address, local variables, and saved registers. A frame pointer is a CPU register pointing to the base of the current stack frame; it can be useful for properly clearing the stack frame when returning from a function. Compilers, though, are well aware of the space they allocate on the stack and do not actually need a frame pointer to manage stack frames properly. It is, thus, common to build programs without the use of frame pointers.
Other code, though, lacks insights into the compiler's internal state and may struggle to interpret a stack's contents properly. As a result, code built without frame pointers can be harder to profile or to obtain useful crash dumps from. Both debugging and performance-optimization work are made much easier if frame pointers are present.
-
Changing Fedora's shutdown timeouts [LWN.net]
On today's Fedora systems, a reboot cycle—for a kernel update, say—is normally a fairly quick affair, but that is not always true. The system will wait for services to shut down cleanly and will wait for up to two minutes before killing a service and moving on. A recent proposal to change the default timeout to 15 seconds, while still allowing some services to require more time, ran into more opposition than was perhaps anticipated. Not everyone was comfortable shortening the timeout period, though the decision has now been made to reduce it, but not as far as was proposed.