We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

Converging image and package based OS updates

00:00

Formal Metadata

Title
Converging image and package based OS updates
Title of Series
Number of Parts
542
Author
License
CC Attribution 2.0 Belgium:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
Imaged based systems are considered safer to update as a new image will only be activated via reboot as a whole. Images are rather static though as the OS image is typically delivered by the OS vendor. Package based systems on the other hand are very flexible wrt installed software. However, since packages are typically updated individually at run time, there are non-atomic, intermediate states states that may lead to undefined behavior. This talk presents a hybrid model that behaves similar to an image based system while retaining flexibility of package based systems, building on ideas from SUSE's MicroOS.
Computer animation
Computer-generated imageryClient (computing)Component-based software engineeringSystem programmingServer (computing)Installable File SystemBootingSpacetimePartition (number theory)Dirac delta functionSynchronizationData storage deviceFlagFormal verificationScripting languageTrailBinary fileEmailElectronic mailing listFingerprintComputer fileComputer wormFormal verificationSign (mathematics)Partition (number theory)EmailElectronic signatureRevision controlBit rateBootingKernel (computing)Server (computing)Table (information)File systemDirectory serviceCASE <Informatik>Computer fileRegular graphDistribution (mathematics)System callGame controllerInstallation artView (database)Network topologyMilitary baseResolvent formalismSemantics (computer science)Arithmetic meanElectronic mailing listClient (computing)System programmingComponent-based software engineeringDatabaseVolume (thermodynamics)MereologyOperating systemComputer wormDirac delta functionSpacetimeFlagBitComputer animation
Computer wormComputer-generated imageryLink (knot theory)VolumeRootkitSystem programmingSimilarity (geometry)SoftwareServer (computing)Network topologyKernel (computing)Directory servicePrototypeRollback (data management)SynchronizationData managementScripting languageKernel (computing)Data miningPlug-in (computing)1 (number)Game controllerComputer fileBitMultiplication signBinary fileDatabaseFormal verificationRevision controlArithmetic meanUniform resource locatorMiniDiscBootingBlock (periodic table)TimestampData compressionWeb pageFile systemHash functionCASE <Informatik>Right angleClient (computing)Electronic mailing listVolume (thermodynamics)Identity managementEmailView (database)Partition (number theory)Model theoryDirectory serviceComputer wormServer (computing)Link (knot theory)Point (geometry)PrototypeVariety (linguistics)Operating systemAreaRun time (program lifecycle phase)Category of beingNetwork topologyContent (media)Patch (Unix)RootkitProof theoryInformationSystem programmingDirac delta functionIntrusion detection systemNumberDisk read-and-write headMereologyImplementationOpen setRollback (data management)Computer animation
Program flowchart
Transcript: English(auto-generated)