MétaCan
Menu
Back to cohort
Record W6894149183 · doi:10.5446/19186

Case Study: Switching from Linux to FreeBSD

2013· other· en· W6894149183 on OpenAlexaboutno aff

Bibliographic record

VenueTIB KMO / FLOWWORKS GmbH · 2013
Typeother
Languageen
Field
Topic
Canadian institutionsnot available
Fundersnot available
KeywordsServerWeb servernobodySoftwareProcess (computing)Application serverGNU/Linux

Abstract

fetched live from OpenAlex

This talk will outline the strategy used to migrate a small Canadian software company's Linux-based server infrastructure to FreeBSD. Part advocacy-strategy and part best-practices, the hope is that you'll come away with some extra tools to promote implementation of FreeBSD in your workplace. ExperiencePoint is a small (20 person) Canadian company that creates training simulations as web applications. The business is wholly dependent on its web server infrastructure for delivering its product. In 2011, I started working for ExperiencePoint and began the process of replacing its aging collection of Linux servers with a more robust FreeBSD server infrastructure. The Linux servers in question had been set up in a hurry, and the skilled software engineers who had set them up were not professional systems administrators. Linux was selected as the server operating system, but there were great opportunities for improvement and change. This talk is the story of that change. In addition to addressing the management concerns of replacing a "known" (Linux) with an "unknown" (FreeBSD), we'll explore the kinds of opportunities you should recognize in Linux environments you may come across. If you can improve reliability, reduce risk and improve performance, that's even better job security than switching to an operating system that nobody else knows.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

How this classification was reachedexpand

Full frame machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.003
metaresearch head score (Gemma)0.009
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Qualitative · Consensus signal: Qualitative
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.061
Threshold uncertainty score0.120

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0030.009
Meta-epidemiology (narrow)0.0010.000
Meta-epidemiology (broad)0.0000.001
Bibliometrics0.0010.002
Science and technology studies0.0120.003
Scholarly communication0.0030.003
Open science0.0030.003
Research integrity0.0050.005
Insufficient payload (model declined to judge)0.0100.002

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.025
GPT teacher head0.281
Teacher spread0.256 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designQualitative
Domainnot available
GenreEmpirical

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations0
Published2013
Admission routes1
Has abstractyes

Explore more

Same venueTIB KMO / FLOWWORKS GmbHFrench-language works237,207